From: henryn <henryn@ms.spacebbs.com>
To: Ian Roxborough <irox@redhat.com>
Cc: <sourcenav@sources.redhat.com>
Subject: Re: SN4.5.2 Win32 setup/usage for call-freq.tk
Date: Mon, 26 Mar 2001 15:22:00 -0000 [thread overview]
Message-ID: <B6E50F0C.2851%henryn@ms.spacebbs.com> (raw)
In-Reply-To: <3ABFB94F.6EA90ACF@redhat.com>
Ian:
Thanks for your email:
>
> Hi,
>
> call-freq.tk isn't a really utility, it's more of an example
> on how to rewrite addons or utilities for SN.
Yes I understand that, though I believe I've seen some dox somewhere that
seem to promise a bit more for this script.
A little history: I was a paying customer for SN 4.2 Developer. Haven't
used it for a while.
What I want is --no surprise-- the call frequencies for the code. Handy for
my work.
I had heard the "enterprise" version of SN 4.2 had this feature built in.
Just now came back to look for the latest and found the model had changed
entirely.
>
> You can run it like this:
>
> ./hyper -f ../share/sdk/api/tcl/database/examples/call-freq.tk
>
> But you'll need to pass the project directory and project name.
> I'm not sure how well it'll work on Windows, you may have to
> use snsdk.exe to launch it (if it's results are sent to the
> console).
After a few experiments --aided by the very nice Tcl debug framework-- I got
this working. The usage is:
./hyper full-path-of-script full-path-of-SN-bin projectname
>
> These scripts aren't well maintained, it wouldn't suprise me
> if they don't work.
Well, this script works, but not perfectly. The scatter plot is poorly
scaled -- most everything is bunched up in a corner. Clicking on a data
point (to get specific call frequency data) is difficult. There's some
strange effect that brings up an error message on a mis-aim. But I can't
reproduce it now.
Would it be a worthwhile contribution for me to try to reproduce the error
and report it? If no one cares, I won't bother.
I'll probably try to excise all the graphics and dump the call frequency to
the console (but then I may have to deal with "snsdk.exe" -- whatever that
is) or to a file. I've done just enough Tcl hacking to be dangerous.
Thanks for your help.
Henry
Henry Neugass
Microsystems Consultant
Palo Alto
650/856-0357
>
> Ian.
>
> henryn wrote:
>>
>> Folks:
>>
>> Could someone give me at least somewhat detailed instructions on how to use
>> the utility "call-freq.tk" supplied in the SN4.5.2 Win32 release?
>>
>> I've got as far as a completely functioning SN project, no problem, and I've
>> grokked that the "hyper.exe" console window is somehow required, but the
>> path is pretty obscure beyond that.
>>
>> There's no "usage" comment in "call-freq.tk" and --even if there was-- it's
>> a bit difficult for those of us not immersed in this technology to see how
>> what to do with it. I tried the similar utilities --which do have some
>> usage information-- with no success.
>>
>> It would be really helpful for someone to give me cookbook guidance on the
>> order of "given an existing project in directory 'x' with a name 'y', open
>> window 'z' and utter '<<incantation>>' to get the call frequency
>> information from the database."
>>
>> Thanks,
>>
>> Henry
>>
>> Henry Neugass
>> Microsystems Consultant
>> Palo Alto
>> 650/856-0357
>
prev parent reply other threads:[~2001-03-26 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-26 13:14 henryn
2001-03-26 13:49 ` Ian Roxborough
2001-03-26 15:22 ` henryn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B6E50F0C.2851%henryn@ms.spacebbs.com \
--to=henryn@ms.spacebbs.com \
--cc=irox@redhat.com \
--cc=sourcenav@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).