tcl and editor

davox!malcom@uunet.UU.NET (Malcom Strandberg 289)
Errors-To: brian@grot.starconn.com
Date: Thu, 3 Feb 94 07:16 PST
Message-id: <9402030252.AA12853@xplor.olympus>
X-Comment: Zoomer PDA List
Originator: zoomer-list@grot.starconn.com
Errors-To: brian@grot.starconn.com
Reply-To: <zoomer-list@grot.starconn.com>
Sender: zoomer-list@grot.starconn.com
X-Listserv-Version: 5.5 -- Copyright (c) 1991/92, Anastasios Kotsikonas
From: davox!malcom@uunet.UU.NET (Malcom Strandberg 289)
To: Multiple recipients of list <zoomer-list@grot.starconn.com>
Subject: tcl and editor
Status: OR

Thanks to  johnm "John D. Mitchell" for describing tcl!
One other thing that is fun, is that the TCL is pronounced "tickle".

After putting out first email on the subject, I was quite surprised,
when reading through the GEOS SDK CDROM that the Geos Swat debugger
incorporated TCL, as mentioned in johnm's email. They also include
the complete Berkeley documentation on the language on the CDROM.

On the CDROM there are two Swat's, one is 600kb
and the other is 100kb. Knowing that the tclTest compiles on the
Sun to 368kb, I suspect the smaller swat is tcl-less.

I guess the big issue will be to determine the best subset for
tcl to be useful on the zoomer, and still fit, and still
provide the necessary gui extensions.

The good news is that tcl has been compiled for the geos OS by
the good folks at geos, and the tcl.a library might be on the
sdk disk or at least available from geosworks.


In reply to tanksley "Billy":
whatever I do to put a tcl interpreter on the zoomer will be freeware.
(After all it is based on freeware source.)

And to your question, "can I help?":
  Besides testing the result. What I feel we need is a better
  zoomer editor, here is some of what I feel it should have:

1. everything the aol editor can do, must be ascii based editor.
   (There was some earlier comments about Palm's Notebook file
    format being efficient..maybe for Palm, but it clearly
    isn't efficient for storage compared to straight ascii text.
    TCL will definitely run standard ascii scripts.)
2. add a user customizable scrolling word paste list
3. add a user customizable symbol/short-word pallette.
   2. and 3. are basically 2 ways to do the same thing: provide
	a pick list for common words or symbols.
	The scoll list lets you store longer words and more
	of them..this could be used by tcl to store commands and variables.
	The pallette replaces the floating keyboard, lets you store
	symbols, numbers, and the enter, tab, space, backspace you need.
Also nice but not necessary would be:
4. longer file support
5. text search capability.

An editor like this could be used for anything, but with specific
scroll lists and pallettes it will take on the flavor of the job
or programming language as appropriate.

     ...
   .:'  `.
   :.[o]o]
   @    > 
  :}\_ ~/
 {:
 :} malcom