> But how do I write "<
You need to use the lower-level aem API to construct references/commands using raw AE codes. However, while both APIs are well documented in themselves, it's not currently explained to end users how to combine them in order to work around dodgy terminology. (Writing up this topic has been on my to-do list for some time, but it's low priority compared to other jobs.)
e.g. Given an appscript reference:
app('Firefox').windows[1]
you might turn that into a low-level aem reference in order to refer to the window's 'curl' property, and then back into an appscript reference for further manipulation via the high-level appscript APIs.
This is actually pretty simple to do since appscript 'references' are just thin wrapper objects around aem references. To extract an aem reference from an appscript one, refer to the appscript reference's AS_aemreference attribute. To convert an aem reference into an appscript reference, pass it to an appscript application object's AS_newreference method.
from appscript import *
ff = app('Firefox')
appscriptref = ff.windows[1]
aemref = appscriptref.AS_aemreference
aemref = aemref.property('curl')
appscriptref = ff.AS_newreference(aemref)
print appscriptref.get()
There are other possibilities as well, e.g. dumping out FF's flawed terminology to a module via appscript.terminology.dump(), patching it by hand, and then using that module as appscript.app()'s 'terms' argument. Though again, user documentation isn't currently available so you might need to rummage a bit in the source for details.
HTH
has
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
