On 25-Jan-10 15:27, Jesper wrote:
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.)
I think that we can have a single AppleScript dictionary that allows
interaction with the core (LetterBox). This will cover the vast amjority
of script needs (creating messages, running find queries, queueing
messages, checking mail, creating new folders, all the core functions).
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.
I think we can have a robust appleScript dictionary without worrying
about the plugins.
Also, we COULD rebuid the script dictionary when new plugins are added.
It's a 'one time' rebuild. Of course, this assumes the newly installed
plugin has an AppleScript dictionary.
--
I loved you when our love was blessed I love you now there's
nothing left But sorrow and a sense of overtime
_______________________________________________
[email protected] mailing list
List help: http://lists.ranchero.com/listinfo.cgi/email-init-ranchero.com
