🚀 go-pugleaf

In article <1519@eklektik.UUCP> danbabcock@eklektik.UUCP (/dev/ph1) writes:

[Dan Barrett's editor inquiry deleted]

>Open a custom, one-bitplane screen. Do not use the operating system for
>text output. Do not use the blitter. Instead, write a very efficient
>character output routine (in machine code, naturally) that performs eight
>moves per character.
>
>For scrolling, use the copper, not the blitter or the CPU. By making
>clever use of the copper, it's possible to scroll very efficiently.
>obscure features. 
>
>I have a few user interface suggestions too: utilitize the numeric
>keypad as in the IBM-style arrangement of Home, PgUp, PgDown, etc. And
>it would be EXTREMELY nice if the Help key actually brought help, and
>the Escape key actually escaped! One last suggestion: do not implement
>infinitely long lines; instead, simply wrap at 80 columns (at least when
>the user is entering text).
>
>-- Dan Babcock

Good advice at the last, but how do you intend for him to use the copper?
Have a larger than screen size bitmap and smooth scroll it?  Not a bad
idea, but one that would certainly prevent working a window or screen
under 1.3 or less, no?

A fast editor would be great, but the old PD version of TxEd is speedy
enough, without taking up an inordinate amount of memory or being
Intuition unfriendly.

I would personally suggest waiting until 1.4 comes out, then write a nice
editor using all the new and nifty Intution features to make it fast and
friendly.  Don't forget the AREXX port! 8-) 8-)


Jonathan Abbey                    (512) 926-5934 | Amiga Programmer Wanna-be 
jonabbey@ccwf.cc.utexas.edu        bix: jonabbey +----------------------------- 
The University of Texas at Austin - CS Undergrad | Speaking for myself, at best