ExtendScript2 CS3 Object Model Viewer (very complicated - any alternative viewer ??)

[_Rosta_Vanek_]

hallo iam just starting with JavaScript in CS3 and what i found most confusing is the Adobe's Object Model Viewer in ExtendScript2...

its no help whatsoever and i didnt figure out the logics of the various dictionary items listed, whatsoever...

if this is currentlly the only complete reference to CS3 JavaScript model than god help us....

the ExtendScript2 Object Model Viewer needs to be COMPLETELLY REWORKED to become a full powered dictionary tool instead of an unorganized pile of items

have you tried InDesign CS3 AppleScript Dictionary in Apple's ScriptEditor... thats a dictionary of object model as i would imagine

1) its FULLY tree-structured dictionary from topmost level down
2) all items are categorized and sorted BY TYPE using various icons
3) every item has a properties catalog card with nice english explanations of that function with hyperlinks to all other relevant items

IS THERE ANY ALTERNATIVE TO VIEW CS3 JAVASCRIPT OBJECT MODEL AND NOT USE THE EXTENDSCRIPT2 WEAK VIEWER ?????

[_xbytor_]

Rosta_Vanek@adobeforums.com wrote:

> IS THERE ANY ALTERNATIVE TO VIEW CS3 JAVASCRIPT OBJECT MODEL AND NOT USE THE EXTENDSCRIPT2 WEAK VIEWER ?????

I've used the ID CS2 PDF with some success. I'm not particularly enamored with
the ESTK2 object model viewer.

-X

[Martin Fischer]

Take a look at jongwares transformation of Indesigns DOM to HTML using XSLT: http://www.adobeforums.com/cgi-bin/webx/?128@@.3bc44040

The set can be downloaded as indesigncs3jshelp.zip by http://www.jongware.com/binaries/indesigncs3jshelp.zip

Or use a CHM-file: http://www.xml2000.de/indesigncs3script_model.zip

Martin

[_Rosta_Vanek_]

The set can be downloaded as indesigncs3jshelp.zip by http://www.jongware.com/binaries/indesigncs3jshelp.zip

indesigncs3jshelp.zip is probably the best CS3 model reference i have seen so far thanks for the tip...

nevertheless it is not perfect...

1) although most items are hyperlinked some entries lack the links where they should be mandatory for example:

"Basic Suite / Application / activeWindow - The front-most window. Can return: Window, LayoutWindow or StoryWindow."

the "Window, LayoutWindow or StoryWindow" returns should be hyperlinked to respective entries...

still FAR better than ExtendScript2 Model Viewer...

ANYBODY WOULD FIND SOMETHING EVEN MORE "INTERACTIVE" SAY SOME FULLY SEARCHABLE MODEL VIEWER or A COMPLETELLY HYPER-LINKED OBJECT MODEL

p.s. DOM to HTML approach is too complicated for my skills level and CHM file lacks any hyperlinks between the entries

ANY OTHER SUGGESTIONS

[Peter Kahrel]

>ANY OTHER SUGGESTIONS

Control your caps.

Peter

[_Olav_Kvern_]

Hi Rosta,

I have to admit that I don't understand. I see very little difference between the ESTK object model viewer and the AppleScript dictionary viewer. If anything, I think the ESTK version is superior because it connects methods with their objects--something that the AppleScript viewer doesn't do at all. But I pretty much find them equivalent.

Regardless, the descriptions are *identical* between the object model viewer in the ESTK, the AppleScript dictionary viewer, and the Visual Basic/VBA object browser. All descriptions come from the scripting resources in InDesign, and all languages use the same description string.

Jongware's HTML version, however, is much better than any of the above. Its hyperlinking is very good, and everything else can be found with your browser's Find command.

Relying on the object model viewers has freed me from the task of maintaining the reference PDFs--which was taking almost all of my time. Without that burden, I can focus on writing the Scripting Guides, Scripting Tutorial, and example scripts. While I agree that the object model viewers aren't perfect, I believe that this is a better use of my time. I think that scripting examples are more useful, overall, than reference documentation (which simply repeats the information from the scripting resources, in any case).

One very nice thing--because we have to rely on the object model viewers, we were allowed to fix literally hundreds of errors in the descriptions in the scripting resources.

Thanks,

Ole

[_Gerald_Singelmann_]

>Control your caps.

Hear, hear...

[_Rosta_Vanek_]

Hallo Olav

please i didnt mean to offend your and your teammates work... i think Adobe is doing the best job to free human minds creativity and unleash its beauty with the help of incredible wonder toolset... a true age of digital art

nevertheless some of us customers are never completelly satisfied, we are just taking things too much for granted :)) maybe a restless karma :))

CS3 was the first application that was so lovelly that i took the courage to unroll the curtains of wonderland of scripting and programming... now iam just discovering the sheer complexity (and versatility) of scripting so please bear with me some of my initial shocks and maybe a little quick judgements of a beginner...

scripting AHOY :)

[liedzeit]

Although I do mostly javascripting these days, I still use the AppleScript dictionary viewer most of the time. ESTK object model viewer is too slow.

Ralf