On (06 Apr 95) Lou Sanders wrote to Chris Adams...
 LS>> You can not do the program or the user justice by integrating the
 LS>> two.
 CA> You can certainly gain a LOT of benefits from it.
 LS> Name some...
For instance, you get rid of the whole configuration problem for sysops.
Just hook it up, and it takes care of your fidonet automatically. Adding
areas, you just create an area, select the echo_tag and then it could 
even tell Areafix for you. And so on. Basically, it makes it easier on 
the sysop.
 CA> The built in mailer would be selectable. If you felt like it, you
 CA> could switch to Binkley or something... It would still directly toss
 CA> mail packets.
 LS> And now we add a tosser, this is going to be one huge package. :)
Yes. Probably 3 parts, chained together...
 LS> Chris, why not write a front end mailer, "stand alone" but part of the
 LS> whole package. Instead of having an option to turn off part of the
 LS> integrated package and leaving unused code in memory, the user will have
 LS> the option to use the front end or not. Once the front end mailer is
 LS> written, we now have the springboard for the BBS software. They both are
 LS> done justice and can stand on their own.
That's what I was planning, having it chain to the mailer. That gets all
the EMSI/FTS1/YooHoo code out of the way if you don't need it. Of
course, if PB had overlays, that'd solve that problem.
 LS> Here's a couple of items I see needed...
 LS> 1. We need to elect board members. the board will decide what goes in 
nd
 LS> what stays out. The board members will also be the keepers of the code.
 LS> Lawrence and you should automatically be voted to the board since this 
was
 LS> you're idea and he's the moderator of this conference.
Sounds good, I was planning some sort of committee for this.
 LS> 2. We need is a flow chart or some kind of layout as too what we intend 
to
 LS> do and how we should go about it.
Yes.
 LS> 3. We need more input from others, I've seen very little on this topic, 
we
 LS> need to make everyone feel part of this project with or without code 
input.
True, true. I should be doing more, but I've been extremely busy (not to
mention sick) for about 2 weeks.
 LS> 4. We need to KISS IT! "keep it simple stupid!"
1st law of programming.
 LS> This is not all I have to say on this subject but it will due for now.
 LS> If I'm speaking out of turn say so...
Nope, glad to hear it. (And you note, more of your worries were my
failure to explain clearly than anything else)
... The key to success: forgetting you screwed up before.
--- PPoint 1.88
---------------