On Thu, Aug 30, 2001 Jeanne said...
Hello Jeanne,
Thanks for the hint. I'll look further into it.
I just checked out one of the HC stacks I'd be interested in converting.
It's main background script is almost 13,000 characters in 30 handlers.
The stack script is almost 18,000 characters in 26 handlers and 6
functions. There's a secondary background who's script is almost 4,000
characters in 6 handlers.
Glancing through them I see that quite a few of the handlers are short
enough to fit into the 10 line limit, but obviously quite a few are not.
Several are in the range of 50 or more lines, and they already call out
to sub-handlers or functions so I'm not sure I could make them any more
granular.
Is it possible I'm mis-understanding something? You suggest insert script
to place objects in the message path. Fair enough, but aren't all of
those objects, indeed all of those inserted scripts, limited to the same
10 lines? Or is it possible to place a much longer script into, say, a
hidden field, then use insert script to read that in and run it when
needed? Seems to me that if that were possible, then the 10 line limmit
would be no limit at all. I could have a hidden field called BG_script
and another called Stack_script and I'd have just what I have now. Which
may be a happy thought for me but not for the people who are trying to
earn a living from selling Rev to the rest of us.
On another topic, my favourite resource for working in HC was a book
called "HyperTalk 2.2 The Book" by Winkler, Kamins and DeVoto. (Danny
Goodman's book was a very close second.) Consider this a nudge in that
direction for Rev. I am one of those unable, for whatever reason, to get
much out of on-line docs. (You know when you go on a trip and you buy a
trashy novel while passing through the airport? Well I buy a computer
book and read it during my vacation. Go figure!) To put it plainly and
forcefully: Rev needs a book!
Rob
--------------------------
>
>At 6:53 AM -0700 8/30/2001, Rob Stevenson wrote:
>>I should state my personal bias here. I don't get paid for prgramming -
>>so $350 is not happenin' for me. And $995 is in another galaxy. I've
>>downloaded the free trial version, but I don't think I can even make new
>>versions of the many tools I created in HyperCard, because I trained
>>myself to program in 2 main places - the background script and the stack
>>script. All other objects had very short scripts which simply passed the
>>action on to those main scripts. I'd hate to start to make spagetti code,
>>after all that effort learning to do it 'right'.
>
>Just a note here - your method is actually quite similar to one of the
>methods Raymond discusses in "Using the Starter Kit". You can use the
>insert script command to place objects in the message path. These would
>hold your routines, and might be invisible controls or "ghost" groups that
>contain no controls. Then your objects would have short scripts, as now,
>that call those routines.
>
>I think it's probably possible to continue using the Starter Kit the way
>you describe using HyperCard, with some slight adjustments (mostly putting
>routines in different objects rather than all in a stack or background).
>
>--
>Jeanne A. E. DeVoto ~ [EMAIL PROTECTED]
>http://www.runrev.com/
>Runtime Revolution Limited - Power to the Developer!
---------------------------------
Rob Stevenson - MSCS
Mus.Soft Computer Services
email: [EMAIL PROTECTED]
---------------------------------
