🚀 go-pugleaf

Hi there,

I've worked quite a bit with the text object and also had problems with those 
scanning and drawing functions. I've debugged the whole thing and think, that  
its just too much work to write your own functions. 
Originally I wanted to write a small wordprocessor using the text object, 
and wanted to implement decimal and right justified tabs and also justified 
text. Because of missing documentation and bugs in the text object I've 
dropped the project. I'm not sure, whether its simpler, to rewrite the whole 
thing so you know whats going on, or to explore the text object and find out
 how to write your own functions.

I don't understand why NeXT makes those functions public, but doesnt 
document them at all. The documentation tells us, that things like 
NX_JUSTIFIED and NX_RIGHTTAB are not implemented #yet#. But 3.0 didn't 
change anything. 

There are flames going on in next/misc about the horrible situation 
with wordprocessors for the NeXT. It's true - except FrameMaker there is
no serious WP for the NeXT. WriteNow is too simple and WordPerfect is a pain 
in the a.. And there's still no WP you could use in connection with a database. 
The text object could be a good basis for a more serious wordprocessor for the 
NeXT, but without documentation you just have to rewrite the whole thing.

Anybody out there, who wrote a new text object or who found out how to use the 
scan and draw functions?

Meinrad 

--
** Meinrad Zeller - Foehrenweg 1 - 3400 Goettingen - Germany **
** email: mzeller@namu01.gwdg.de      Phone: +49-551-300095  **