> > But one warning-- QWK is just about THE worst message format there is for
> > the internet. SOUP is just so much better it's not funny. QWK works OK
> > for certain types of BBSes, and that's it. QWK can't come close to
> > handling email addresses properly.
> I don't care about the internet now. This is for BBS's. To complement
> Jerry Reno's comm program.
That's an enormous pity. (I would use Reno's comm program to access the
Internet, BTW.)
One suggestion for you, if possible: it would be just wonderful if your
program was a databaser rather than a simple reader. That way you
wouldn't have to reply to every single message before being able to get a
new packet-- your program would store all messages in a database after
extracting them from the packet, after which they could be read, deleted,
etc. at the user's discretion, without having to worry about downloading
new packets.
In fact, if you did it this way, it would be possible to seperate the
message import from the message reading; you could simply write a
seperate geode to handle parsing and importing QWK, and later on another
one to handle SOUP. (This is just a side effect, though; the main effect
would be the ease of use in reading.)
See Yarn for and example of the usefulness of this.
> | Edward Di Geronimo Jr.
- -Billy (Jr.)