🚀 go-pugleaf

In article <HNJ060R@gwdu03.gwdg.de> mzeller@namu01.gwdg.de (Meinrad Zeller) writes:
>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. 
>

It seems to be agreed that the Text object is the worst part of the app kit. 
Most WordProcessors for the NeXT don't use it, which is wasteful because 
you've got all these developers reinventing the wheel. NeXT don't seem to be 
putting much effort into supporting it.

Solution? I think NeXT should release the source for the Text object. What do 
they have to lose? It's hardly a jewel in their crown. And there's loads to 
gain for all of us.

Dave Griffiths