AppleScript demands a single static dictionary file (one .sdef), mapping the commands to Apple Events. There are scripting additions that, from what I can tell, only extend the capability of the system or hand you a disembodied extra part with little hope of useful integration with the application's own scripting suite. If everything is a plugin, the Letters scripting dictionary is going to be anemic and, er, distributed, or dynamically recompiled (oh dear); a suboptimal mess in either case.
If this is *really* a programmer's mail client, I posit that we forgo AppleScript support entirely or at least leave out every command but a few choice ones in the non-plugin foundation. (One of these commands could be a Safari-like "do script" to run something in the internal scripting system and provide a passable bridge.) While I've seen Welch's list of arguments (and agree with most of them), I hope it stands to reason that if we actually can't build that support in the first place without tossing away a fundament of the application architecture, it's something that's hard to provide. /Jesper _______________________________________________ [email protected] mailing list List help: http://lists.ranchero.com/listinfo.cgi/email-init-ranchero.com
