[MacPerl-Toolbox] RE: Glue

[Chris Nandor <pudge@pobox.com>]

I am doing this in macperl-modules, not macperl-toolbox.  :)

At 18.10 -0500 1999.03.15, Mat Marcus wrote:
>Right. I've been using the version that is currently on your web site. It
>does open the app, but garbage is produced in the resulting Glue.pm file.
>Does things work with CodeWarrior for you?

I have not done it with CW, but I have had problems with BBEdit.  There are
bugs somewhere.  But the point is that the design is to do what you want,
to get the plugins and their aete resources.  If the implementation is
lacking, that's OK for now.  :)



>When opening an AppleScript (well Script Editor anyway) will decide on how
>to display the "strings" associated with each four-char ID (tag). Pity the
>poor dictionary implementor who mistakenly maps two different strings to the
>same tag. Anyone opening a script written against this dictionary will find
>it difficult to use since AppleScript/ScriptEditor will arbitrarily choose
>only one string to use for both properties.

Yep.  But sometimes this is wanted, maybe to provide common synonyms.  I
was just pointing out that there is not necessarily a one-to-one mapping,
but it could be many-to-one.


>Given this behavior my point is
>that Glue's power would appear not to be weakened by flattening the "string"
>to "four-char ID" mapping into one big hash. Then _doObj could accept
>active_spread as a property of active_window. But this is all details. What
>I'm after is a more natural port for AppleScripts containing constructs such
>as "propertyX of propertyY" where the IDs of property X and Y do not match
>those of the associated class.

I don't know how I will implement it, but this is basically the conclusion
I came to a few days ago.  For each glue instance, to have one namespace
for lookups.  The whole architecture of this thing may change, so I can't
say what the specific implementation will be yet, but it should do what you
ask.

But ignoring implementation for now, let me ask you and anyone else out
there: should there be one lookup table for everything, or do events have a
separate lookup table?  IM: IAC mentions that properties and classes etc.
can have the same name as long as they point to the same ID, but it does
not mention events there.

--
Chris Nandor          mailto:pudge@pobox.com         http://pudge.net/
%PGPKey = ('B76E72AD', [1024, '0824090B CE73CA10  1FF77F13 8180B6B6'])

==== Want to unsubscribe from this list?
==== Send mail with body "unsubscribe" to macperl-toolbox-request@macperl.org