Editing Script with QuoEdit

Features Known problem of editing script with QuoEdit

Features

QuoEdit provides minimal features to edit scripts as auxiliary functionality. But it won’t show the menu commands to edit scripts explicitly.* You can just:


◊	open a script file by Open Script menu command in Extras menu that is available only while holding down Option key.**
◊	compile (or check syntax of) the source text by Enter key.***
◊	run the compiled script by double Enter key.
◊	save the script by Save menu command or Save As menu command.


You can also open applet or droplet as a script file but note that when you choose the Save As menu command, QuoEdit always saves it just as a compiled script.

QuoEdit has no menu commands to make a new window to edit script. To make a new one, take one of the following procedures.


◊	Prepare a stationery of a script file and open it.
◊	Execute a script to make a new document with the initial data value of a script object. For example; tell application "QuoEdit" to make new document with data script 1


QuoEdit also has no functions to show the result of running script. To see the script result, try an included applet “Show Script Result”.

Visually, ordinary window (to edit text) and window to edit script are same. The only differences are that:


◊	name of window to edit script is shown in italic style in the Window menu.
◊	in Mac OS 8.5 and later, the proper proxy icon is shown on the window title.


Also in AppleScript terms, document to edit script is handled as ‘document’ class object. That means, it is the same class object as ordinary document (to edit text). If you need to determine the difference in your scripts, refer to the ‘edit type’ property of the document object. Either way, there is not a way to change the edit type (whether to edit text or script) of the document in QuoEdit.

To input ‘¬’ (continuation character), type Option+L.



*	If you are a novice scripter, it is recommended to learn the Script Editor first. In QuoEdit, the functionality to edit script is something like a tiny premium just using some features of the scripting component to get the source text, compile the text, and run the script. Note that QuoEdit is never supposed to be a script editor. That is why it doesn’t provide the menu commands and specific type of windows to edit script.
**	QuoEdit doesn’t accept drag and drop to open scripts (unless you modify the 'BNDL' resource). To open script by drag and drop, use an included droplet “Open Any File by QuoEdit”. QuoEdit actually can open any application file as a script file (as well as applets and droplets) if the file contains its script data as a 'scpt' resource of ID 128.
***	In ordinary windows (to edit text), the Enter key independently has no effect (as suggested in the guidelines by Apple Computer).

Known problem of editing script with QuoEdit

When AppleScript compiles the source text requested by QuoEdit, it tends to interpret each term (human word) as QuoEdit’s term (using QuoEdit’s dictionary) if both osax and QuoEdit has the same term, even if the term is out of ‘tell’ statement to QuoEdit. The following is known osax terms that are not directly interpreted.*



	Term		Code		Defined as...
	offset		«event sysooffs»		a command of a standard osax
	folder		«property asdr»		a property of ‘file information’ class defined in a standard osax


If you are using AppleScript included in Mac OS 9 or later, you can avoid this problem with ‘using terms from’ statements specifying the osax file. If you are using the earlier AppleScript, you have to input the raw specifier (the code like «property asdr») for the osax terms every time you compile it with QuoEdit. In this case, using the Script Editor is recommended.



*	The both are not standard terms of AppleScript. QuoEdit uses term (and the code) of the ‘offset’ property («property ofse») from the STE, and the ‘folder’ class («class cfol») from the Finder.

---

Table of contents