>> AppleScript demands a single static dictionary file (one .sdef), >> mapping the commands to Apple Events. > > Actually, it is possible to dynamically construct an Applescript dictionary > based on specifications given by plugins. Apple has some sample code that > demonstrates how to do this at: > > http://developer.apple.com/mac/library/samplecode/SimpleScriptingPlugin/index.html
I'll be damned -- I read the Cocoa Scripting Guide and that wasn't clear at any point. > But like John said, if being able to extend the Applescript dictionary via > plugins is desirable, then this should be something that's considered very > early on when designing the plugin architecture. Either come up with a way > it can be done sanely, or declare that the dictionary won't be extensible and > decide on a core set of classes and commands to expose. Agreed. Script sprawl isn't very far off, even if I guess not having the plugins would be a blocker even with a sort of script that wouldn't fail to compile on such an incompatibility. /Jesper _______________________________________________ [email protected] mailing list List help: http://lists.ranchero.com/listinfo.cgi/email-init-ranchero.com
