This content has been marked as final. Show 5 replies
I figured out what my problem was. I did not include the #target directive in the script. When I added it, the problem went away.
I would still like some help on #1, however. I stand by my observation that the object model in ESTK is inadequate for learning JS for InDesign.
Make sure that in the top left of your edit window it says "Adobe InDesign CS3". You probably see "ExtendScript Toolkit 2" there now. To avoid this in future, make a habit of including this line at the beginning of every script:
As to your two questions, (1) there isn't any; (2) depends on what you want. Press Shift+Cmd/Ctrl+D to display it on screen, or use
to print all link names in ESTK's console.
>I stand by my observation that the object model in ESTK is inadequate for learning JS for InDesign.
Everybody, including Adobe's engineers, would agree with that. They would also say that the object model in the ESTK is a reference, not a learning tool. For learning about the object model you need other resources. There are several scripting guides around -- see Adobe's web site.
Thank you for your input. I appreciate it.
re: "I stand by my observation that the object model in ESTK is inadequate for learning JS for InDesign."
I agree, but I have to add: the information in the ESTK is pretty much the same as that in the earlier PDFs. Both are generated from InDesign's object model--the main difference is that we fixed errors in the source, rather than fixing them over and over again in the PDF.
Reference documentation is never a good way to learn about an object model--for that, you need tutorials and examples. As I've said in other posts, that's why we did away with the PDF version of the reference--so I could concentrate on the Scripting Guide.
For an HTML version of the reference information, see other threads about Jongware's XSLT converter (which turns the XML used by the ESTK object model viewer into a hyperlinked HTML document).