Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!harvard!think!mit-eddie!genrad!decvax!ittatc!dcdwest!sdcsvax!sdcrdcf!ism780c!marty
From: marty@ism780c.UUCP (Marty Smith)
Newsgroups: net.micro,net.micro.pc
Subject: Re: Turbo Editor Toolbox
Message-ID: <2143@ism780c.UUCP>
Date: Mon, 5-May-86 12:51:08 EDT
Article-I.D.: ism780c.2143
Posted: Mon May  5 12:51:08 1986
Date-Received: Sat, 10-May-86 12:43:43 EDT
References: <1771@panda.UUCP>
Reply-To: marty@ism780c.UUCP (Marty Smith)
Organization: Interactive Systems Corp., Santa Monica, CA
Lines: 27
Xref: linus net.micro:13217 net.micro.pc:7735

In article <1771@panda.UUCP> plw@genrad.UUCP (Pete Williamson) writes:
>Does anybody have any experience using Borland's Turbo Editor Toolbox?

I'm using the Borland Editor Toolbox as the base for an editor for
screenwriters.  I'm not far enough along yet to comment on the quality of the
package, but I'm finding that I'm rewriting a great deal of the code from
scratch.  This is probably due more to the different requirements of an
editor for screenwriters than it is due to any problem with the Toolbox.

So far, I'm pleased that I bought it, because I've learned some things
about editors by reading the code, and it has allowed me to start off
with a system that already has the dirty problems of editors solved.

One problem is that the Toolbox itself takes up most of the 64K of code
space allowed.  So if the system you're building on top of it needs a lot
of space, you might run into problems.

The Toolbox writes to the screen directly, which, if I'm not mistaken, puts
it in the class of programs that are not "well-behaved".  That might mean
problems if you want your editor to run under control of a system like
MicroSoft Windows, but I'm not sure about that.  Maybe someone who knows
more could comment?

				martin smith

				marty@ism780c.UUCP
				(213) 459-6729