[Pythonmac-SIG] appscript terminology caching
has
hengist.podd at virgin.net
Thu Oct 21 13:12:09 CEST 2004
Bob wrote:
>>one small consideration to add: some apps update their terminology
>>without a version change.. the means i have in mind is that some
>>XTensions to QuarkXPress (4.x, at least) would dynamically extend
>>the dictionary when the app launched.. the new terminology could
>>only be obtained when the app was running, not from parsing the
>>AETE in the resource fork.. i don't how or whether this situation
>>has changed with Mac OS X versions of XPress or other apps..
>>Frontier did a parse of the static AETE, and so i had to hand add
>>entries to the glue table, but if the AETE API that appscript uses
>>ensures that dynamic entries are returned to queries, then i guess
>>this isn't an issue
>
>appscript shouldn't be reading anything directly from resources, so
>that's not an issue. However, if appscript gets ahold of the
>QuarkXPress aete before it's loaded all of its extensions (which
>might happen if appscript does the launching, I guess), then you
>have an issue.
Appscript uses OSAGetAppTerminology, so supply the right aete(s) is
the OS's responsibility.
One scenario where it would have a problem is when the user adds or
removes scriptable application extensions while the app is running -
this change wouldn't be picked up by appscript/ATS so it wouldn't
know the cached terminology has gotten out of date.
has
--
http://freespace.virgin.net/hamish.sanderson/
More information about the Pythonmac-SIG
mailing list