btw, the aem complication increases my motivation to rewrite the
applescript...i only used a/s because ired & vdvhs are a/s-able,
and appscript solves that problem;-)
aem's easy enough to use if you know a little bit about how Apple
events work, and you can easily extend its Application class to call
user-defined subroutines with positional parameters, e.g.:
#!/usr/local/bin/python
import aem
class Applet(aem.Application):
def initwithname(klass, name):
return klass(aem.findapp.byname(name))
initwithname = classmethod(initwithname)
Adding convenience methods for calling standard event handlers (run,
reopen, quit, etc.) and extending callsub to support labelled
parameters wouldn't be too hard if you want to make a general-purpose
module out of it.
