🚀 go-pugleaf

Richard--

re: "Wow, this means script runs "in process", yes? This should mean faster execution than external VB?"

Yes, but you can already get that by running VBScripts from the Scripts palette. What you get now is the ability to create dialog boxes, so most of your InDesign-only scripts can be run from the palette.

re: "Can the new JS do floating pallet like function? Or must script run/exit to interact with app again?"

No floating palettes, just modal dialog boxes this time out. Yes, you can use the do script method to run any script or string.

re: "I assume this will include guide on JavaScript? Wow, that's triple work."

It's on the InDesign CS CDs, and it includes a JavaScript tutorial and reference information. (Most of it is just reference--you'll have to refer to the sample scripts for examples.)

Yeah, I hadn't really realized how big it would be. Add a language, add about a hundred new objects, and many many new properties/methods...there's no wonder it's over 1800 pages.

re: "I think you guys should drop *documenting* VB and AS and just concertrate on JS. But I'm sure I'll get flame on this."

We're pretty committed to supporting both platform-specific and cross-platform scripting. If I have anything to say about it we won't be *dropping* anything--just adding.

re: "Anyway, can't wait to see the new guide and ditch VB."

You'll still need VB for any interapplication communication stuff you need to do, and for creating any controls you can't get with InDesign's scripting UI features. It's also good for connecting with system services you can't reach from InDesign JavaScript--the Microsoft XML parser, for example.

But for InDesign-only scripts--heck, yeah!<g>

Thanks,

Ole