🚀 go-pugleaf

Steven F. Bryant wrote: "But In JavaScript The Language Is Too Loose To Accurately Predict The Applicable Properties."

It's not a matter of strong vs. loose typing. It's a matter of resources for writing the ESTK. Autocomplete doesn't need to know about the type of the object you're entering, only what the DOM says its properties/methods are.

For whatever it's worth, I get pretty good autocompletion on things like enumerations in the CS4 ESTK, but it guesses poorly or not at all on most other things.

I think a lot of it has to do with performance and the size of the DOM--you'll note that you'll get faster/better responses for basic JavaScript terms or for terms from smaller object models than you do for InDesign (with its monster DOM). I also note that it works better on faster machines. It's clearly dependent on the time it takes to look up a specific object name in the OMV XML file.

Thanks,

Ole