creating new tools

[Steve Messimer]

Hi,

Years ago I created a set of objects for HyperCard that allowed users to
significantly truncate the educational development process. Using stack
templates and compoundObjects (like buttonField objects, button card
objects, hotText objects, quizObjects, examObjects etc ) teachers could
create educational titles in days rather than months.  Now that revolution
is here I am inspired to attempt to port the code.  The question is ... what
is the best approach. Here's a brief outline of what I would like to do.

The app/plugin when invoked would display a palette of tools. selecting a
tool would create a compound object on the target card.  For example: when a
user selects a buttonField Object ( a button and field that act as a single
object - bFO).  The code would create a button and field on a card of a
target stack. The Objects would be related . When the button was clicked the
field would show itself when clicked again it would hide the related field.
bFOs have relationships to all other bFOs on a card... only one companion
fld can be showing at any given time.

The process would work the same for any other object selected from the
palette.

There are several issues of course. :-)

1.  Should these tools be created within a plugin or as a main stack or as a
substack? Ideally I would like these tools available to anyone who uses RR.
I'm thinking that perhaps a plugin might be the best approach.
Unfortunately I have been unable to find any information about plugins. What
are the advantages / disadvantages of using this method.  Where can I find
details about creating plugins w RR.

2.  How does RR "know" which stack to create an object in?  Does it just
assume that it is supposed to create the Object on the card in the Active
window? Suppose I want to make changes in the script of the stack that is in
the active window.  How do I get that information?

3.  compoundObject IDs: In HyperCard I tracked the creation of all new
compoundObjects in hidden text fields.  This was useful to prevent
duplication of Object names and to help identify object components when a
compoudObject was deleted.  I could create a separate ID generation
script/function but it would be cleaner if I could get access to the code
that generates IDs for RR objects.  Is there a way to do this? Other ideas?

As I think about this some internal compoundObject accounting must be
located in the stack being developed.  It doesn't make much sense for the
plugin to do anything but generate the ID or Name.

4.  Object Names:  In HyperCard I used specific characters to identify
certain types of compoundObjects. To identify a bFO I used a terminal "*".
This worked fine but every bFO button had a "*" in its display name.  Is the
a way to avoid this with RR and are there any Cross platform gotchas using
extra characters like "*". I presume that if I stick with standard ascii I
should be OK?  Right?

Thanks for any input.

Steve
-- 
Stephen R. Messimer, PA
Messimer Computing, Inc.
www.messimercomputing.com
ph: 906-420-5804