VectorScript developer wish list

[Alexandre Villares]

For the script editor:

• Find and Replace
  Syntax coloring (or a more dynamic link to an external editor like BBedit)
  Standard Pascal/VS keywords in the procedure menu
  Key-in-the-first-letter to search the procedure menu

For the workspace editor:

• drag & drop of multiple selection of plug-ins (i.e. drag a whole category to create a whole palette at once)

More code examples:

• the new path PIOs have Path *and* Profile
  File I/O code example
  3D Path Object
  Path Objects path replacement
  [update: event aware objects examples]

New Procedures:

• Procedure that would call a command's parameter dialog
  [update: there seems to be a 'event aware' class of calls that could let one create a custom preferences panel]
  Procedures to read/alter classes and layers inside standards

Other:

• Searchable archives for the NNA VScript-List
  [update: the VS-List now has archives!]
  Paste as VectorScript: copy some objects and paste their script descriptions inside the script editor...

A

[ 07-26-2004, 09:02 AM: Message edited by: Alexandre B A Villares ]

[dave96]

At the minimum, the Vectorscript Editor needs colour. If not, make the plug-in file a simple text file capable of being opened directly by BBEdit.

A tutorial on how to structure large scripts would be a great help to amateur scripters like me. Although the basic information is available it is extremely difficult to start building up know-how and good practice if you have no technical background.

[matto]

Yep all it would be very helpful in scripting

especially syntax colouring, and The ablity to cut something out of a drawing and paste it in to the script as Vectorscript would be very useful.

An environment similar to Xcode Applescript Studio might be worth looking at.

The ability to colapse parts of the a script, say subroutines to just there procedure title.

Auto Indenting of sub rountines and such would help track larger scripts as well.

Could the Plugin editor be treated as a document, instead of a dialog box. So that Editor could be open in the background (this might need to lock out the script in questions from acting on the other documents). It might help with processor use for what is basicly a text editor.

Auto Variables ,or an improved way of tracking variables. an easierly accessable variables list or such? colouring defined and undefined Variables differently?

Just a couple of extra thoughs, i'm sure there is more, if the editor is getting a serious overhaul.

[Alexandre Villares]

quote:

---

Originally posted by dave96:

At the minimum, the Vectorscript Editor needs colour. If not, make the plug-in file a simple text file capable of being opened directly by BBEdit.

A tutorial on how to structure large scripts would be a great help to amateur scripters like me. Although the basic information is available it is extremely difficult to start building up know-how and good practice if you have no technical background.

---

Dave,

Have a look at the VS-List archive on how to edit includes...

[MullinRJ]

Pressing ENTER used to close the VS-Editor by accepting changes (OK Buton), now it does nothing. You now have to mouse-click one of the buttons to close the window. Please reinstate that key's function. It would also be nice if ESC closed the window without accepting changes (Cancel Button).

Thank you,

Raymond

User since MC+2/1990