Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!maverick.ksu.ksu.edu!rutgers!aramis.rutgers.edu!remus.rutgers.edu!traffic.rutgers.edu!declan From: declan@traffic.rutgers.edu (Declan McCullagh/LZ) Newsgroups: comp.sys.next Subject: Re: 2.0: Initial Reactions Message-ID: Date: 14 Dec 90 02:42:37 GMT References: <4490@media-lab.MEDIA.MIT.EDU> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 47 In article <4490@media-lab.MEDIA.MIT.EDU>, simsong@media-lab.MEDIA.MIT.EDU (Simson L. Garfinkel) writes: > * Although 2.0 is binary compatiable with 1.0a, it is not source-code > compatiable. You will need to change your applications in order to > get it to recompile. Yes... Keep that copy of 1.0 around for compiling programs that you find in the /pub/next/sources directories of archive sites. > * Stuart 2.0 doesn't work properly. It leaves turds at the bottom of > each line on redisplay. This is odd, and kind of flies in the face of > binary compatiability. Well, at least it works. That's strange. I used Stuart 2.0 with NeXTstep 2.0 for a day or two, then switched back to Terminal (because of the lack of the Services menu in Stuart). While I used it (with Emacs), I only saw garbage text on the last line once. > * Icon is *gone*. I don't know how to make an icon now. Make a > backup of your program before doing the upgrade. Huh? Do you have the extended version of 2.0? Icon's still there, and much improved, though not as stable as the 1.0 version. > In other news, I've gotten my News reader to the same level of > completion that Will Shipley's is. Oh, I've got posting almost > working too, Rich Text and all! The idea that I like best about > dealing with the Rich Text / non-rich-text problem was suggested by > Will: do a writeRichText: and a writeText:. Post the normal text, a > ^l, and then a uuencoded, compressed, binary diff of the two. That seems the most straightforward way to do things. If (that's a big IF, in terms of space) you're going to support NeXTmail-like attachments, you'll probably have to tar/compress/uuencode anyway. Also, as the person following a thread is reading messages, perhaps you could be checking the articles ahead in the thread and uudecoding/uncompressing/untaring those. The performance might get a bit less than optimal if the person is jumping around a thread, but if he/she's consistently reading messages sequentially, it might be worthwhile. > Hopefully I'll have something that can be FTP'ed by January. Great! Good luck. Declan McCullagh Independent NeXT Developer