Re: TechNote 2106
Re: TechNote 2106
- Subject: Re: TechNote 2106
- From: steve harley <email@hidden>
- Date: Sat, 6 Mar 2004 12:06:38 -0700
on 6 Mar 2004, at 4:42 AM, Chris Page wrote:
Most editors today edit text. Plain text, usually, despite editors
that color code or even apply fonts. The editors have no knowledge of
how to edit a program. They edit character streams. A "program editor"
would edit programs or code. The editor would work with some binary
representation, possibly a tree.
pragmatically, i think outlining editors can offer a lot of the
benefits you are looking for.. while still treating nodes in an outline
as "text", the structure of the nodes has an unambiguous relation to
the block structure of the code.. some languages (such as AppleScript,
Frontier, Python ...) already have syntax rules that make them natural
for outline editing, but Frontier is the only environment i've ever
seen that applies the outliner paradigm effectively.. i recently looked
at a bunch of different editors with a thought toward Python coding.. i
found some intriguing outliners, like Leo, and some decent code-folding
editors like JEdit, but none of them really touches Frontier as a
"structure editor"
so i would suggest starting with an outlining editor for the block
structure and above, then experimenting within that for ideas how to do
"code-editing" at the "line" level
also, i don't have a line on anything specific, but i strongly suspect
work has been done in this area in the Lisp/Scheme world
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.