Article View: comp.sys.next.programmer
Article #2353Re: TEXT.H TextFunc how does it work???
From: Garance A. Drosehn
Date: Tue, 12 Jan 1993 22:50
Date: Tue, 12 Jan 1993 22:50
23 lines
1420 bytes
1420 bytes
dave@prim.demon.co.uk (Dave Griffiths) writes: > 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. [skipping over additional comments on text object] > > 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. I guess the question is, why doesn't everyone else (all the people who are reinventing the text object) get together and release *their* work? -- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu ITS Systems Programmer (handles NeXT-type mail) Rensselaer Polytechnic Institute; Troy NY USA
Technical Details
Message-ID:
<q#=32sn@rpi.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!caen!zaphod.mps.ohio-state.edu!rpi!usenetReferences:
<1993Jan8.000700.16819@prim>Show Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.programmer Path: arc1-ca.pugleaf.net!sparky!uunet!caen!zaphod.mps.ohio-state.edu!rpi!usenet From: gad@eclipse.its.rpi.edu (Garance A. Drosehn) Subject: Re: TEXT.H TextFunc how does it work??? Message-ID: <q#=32sn@rpi.edu> Nntp-Posting-Host: eclipse.its.rpi.edu References: <1993Jan8.000700.16819@prim> Date: Tue, 12 Jan 1993 22:50:13 GMT Lines: 23