Thread View: adobe.scripting.indesign
6 messages
6 total messages
Started by Ariel_Walden
Wed, 25 Mar 2009 23:33
AutoComplete? ESTK CS4
Author: Ariel_Walden
Date: Wed, 25 Mar 2009 23:33
Date: Wed, 25 Mar 2009 23:33
17 lines
1156 bytes
1156 bytes
Hello. I would expect the automcomplete of the ESTK to function as follows: Let's say I type, somewhere in my code LocationOptions. I would expect, once I've typed that last dot, to be given a list of possibilities (e.g., "AFTER, AT_BEGINNING, AT_END") etc. But I'm not given such a list. Have I misunderstood it's purpose? Thanks for any clarifications, Ariel
Re: AutoComplete? ESTK CS4
Author: Harbs
Date: Thu, 26 Mar 2009 01:06
Date: Thu, 26 Mar 2009 01:06
7 lines
823 bytes
823 bytes
Autocomplete in ESTK CS4 is a bit iffy... It worked better in the last version. -- Harbs http://www.in-tools.com
Re: AutoComplete? ESTK CS4
Author: Ariel_Walden
Date: Thu, 26 Mar 2009 13:05
Date: Thu, 26 Mar 2009 13:05
1 lines
932 bytes
932 bytes
Alright. (By the way, how was the shlach manos? ;-)
Re: AutoComplete? ESTK CS4
Author: Steven_F._Bryant
Date: Thu, 26 Mar 2009 15:24
Date: Thu, 26 Mar 2009 15:24
1 lines
1030 bytes
1030 bytes
I Don't Think A Language Like JavaScript Could AutoComplete Like That. Only A Strong Typed Language Like C++ Or VB When Variable Types Are Declared Gives The AutoComplete The Knowledge Needed To Know What Properties And Methods Exist. But In JavaScript The Language Is Too Loose To Accurately Predict The Applicable Properties. Even In CS3 The AutoComplete Would Show All Properties Of All Elements, And Not Of The Current Element
Re: AutoComplete? ESTK CS4
Author: Olav_Kvern
Date: Thu, 26 Mar 2009 18:12
Date: Thu, 26 Mar 2009 18:12
11 lines
1656 bytes
1656 bytes
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
Re: AutoComplete? ESTK CS4
Author: Fred_Goldman
Date: Thu, 26 Mar 2009 18:31
Date: Thu, 26 Mar 2009 18:31
7 lines
1025 bytes
1025 bytes
Another thing to note is that auto-complete doesn't work on custom variables. For example: d = app.documents[0]; d. It will not show me any auto-complete options after typing the d.
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads