> Then there's the AppleScript dictionary issue that Jesper pointed out.
That *may* be there, thanks to recent developments in exposing my poor research, by which I mean that Apple's sample code covers scenarios canonically that Apple's canonical documentation doesn't. Let's not make the assumption that AppleScript has the market on useful integration cornered, though. (Or the further assumption that that previous sentence means "let's drop AppleScript" instead of "let's think beyond AppleScript as well".) There will be people that are more productive and comfortable in a given non-AppleScript language. These people may be programmers, and that may not be a valid counter-argument since it's actually a matter of programming. This group includes me, it includes many others on this list and I even think El Presidente squeaks in, despite being the kind of guy that know of AppleScript's strong suits. /Jesper _______________________________________________ [email protected] mailing list List help: http://lists.ranchero.com/listinfo.cgi/email-init-ranchero.com
