🚀 go-pugleaf

On 11/3/09 9:12 PM, "jongware" <member@adobeforums.com> wrote:

> If you ever, EVER consider a platform transfer, or -- as I do -- work in a
> multi-platform office, use JS   exclusively.

On the other hand, if you ever plan to build workflows that involve more
than one app, and especially using non-Adobe apps (think spreadsheets,
databases, mail apps, command line, etc), you need to use AppleScript or VB
rather than Adobe's proprietary js engine.

JS has a lot going for it: cross-platform, more built-in stuff like grep,
persistent engines, plus access to stuff like ScriptUI. But it also has
disadvantages -- you don't have droplets (my favorite UI because of its
speed and simplicity) like AppleScript, ESTK is, IMO, fragile and ugly, and
not a patch on a professional IDE like Script Debugger, and it has scope
issues.

To me, cross-app is more important than cross-platform -- I generally only
use one platform, but I use and automate lots of apps. Others have different
priorities. Be thankful for the choice, and if you have the time, learn 'em
all. The hardest part of scripting InDesign is understanding the object
model, and that's much the same whatever the scripting language.

-- 
Shane Stanley <sstanley@myriad-com.com.au>
AppleScript Pro Sessions <http://scriptingmatters.com/aspro>