From: "Chris Antos (Exchange)" 
the only thing that inherently changes in speed between a GUI version
and a non-GUI version of a product, is updating the screen.  a GUI TSE
will update the screen at about the same speed as the console mode TSE
running in a window.  everything else should be the same speed as it
currently is.
when other non-drawing things are slower, it is generally due to
non-optimal data structures or inefficient algorithms.  Sammy seems to
put a lot of effort into optimizing his code, and hence his TSE is one
of the fastest editors on the market.  i'm a speed fanatic too, and i've
been quite impressed with the consistent attention to speed and
optimization that TSE has shown over the years.  it won't change with a
GUI release.
//chris
> -----Original Message-----
> From: Thomas Martin [SMTP:tmartin@abraxis.com]
> Sent: Friday, November 21, 1997 6:23 PM
> To: Joe Souza; tsepro@semware.com
> Subject: RE: Looking for...
> 
> 
> At 04:54 PM 11/21/97 -0800, you wrote:
> >An editor does not have to be really fast.  Most of the time it's
just
> >sitting there in a loop, waiting for user input.  I'm not sure we'll
> see a
> >noticable speed difference when compared with TSE/32.
> >
> >I'm looking forward to the GUI version.
> >
> 
> 
> Interesting viewpoint, and TOTALLY valid.  I happen to use TSE to work
> with
> textual data files, some of which are quite large (20-50MB).  When I
ask
> for a sort or a compressed view, speed counts for me!
> 
> It certainly is a "big" world, and I respect that many (if not most)
> other
> people may not "need the speed" that I crave.  I just hope that they
> don't
> abandoned the console mode product -- unless they can keep up the
speed!
> 
> Tom Martin
> 
---
---------------