--------------- FIDO MESSAGE AREA==> TOPIC: 214 POWER BASIC Ref: C4E00011 Date: 04/07/95 From: LOU SANDERS Time: 08:44pm \/To: ERIC SCHONNING (Read 6 times) Subj: Echo Project! 06 Apr 95 23:27, Eric Schonning wrote to Chris Adams: CA>> general, nope. Someone mentioned RBBS, and that is a good example ES> i try, when making code that others may look at, to limit gosubs and ES> gotos to within a sub/end sub. if the gosub or goto is used by more ES> than 1 other routine then i make it a sub or function. works for ES> me... ES> eric Hello Eric! I agree, goto and gosub are fine and have their place but in a project like this, functions and subs would be the disired method. Not only does it make for easier debuging but I would think easier to maintain the sub/function library. Easier to test and replace a sub/function if need be and it would allow he/she, the programmer to contribute a function to the project without having to understand the entire works. "refering to the likes of RBBS code." TTYL: Lou Sanders --- GoldED/2 2.50.Beta5+ * Origin: The Basic OutPost System (1:143/333) --------------- FIDO MESSAGE AREA==> TOPIC: 214 POWER BASIC Ref: C4F00000 Date: 04/10/95 From: CHRIS ADAMS Time: 05:45am \/To: ROWAN CROWE (Read 6 times) Subj: DSE-PB/Vision On (05 Apr 95) rowan crowe wrote to Chris Adams... CA> I'll second, third, and move that we pass the motion on that one. CA> Outside a nasty little conflict with Norton Cache (Intelliwrites) and rc> NCACHE trashed my FAT, and every file accessed during the short time it rc> was active ended up being truncated to 2048 bytes (1 cluster). rc> Now, what sort of conflict did YOU have? It would lock solid while using PB/VISION and intelliwrites. Switching intelliwrites off solved the problem. I think it was an ISR death-feud... ... I'm running OS/2, cause I'm sick of being a crash dummy for Windows --- PPoint 1.88 * Origin: The Point of Obfuscation! (1:212/2001.5) --------------- FIDO MESSAGE AREA==> TOPIC: 214 POWER BASIC Ref: C4F00001 Date: 04/08/95 From: CHRIS ADAMS Time: 10:47pm \/To: LOU SANDERS (Read 6 times) Subj: Echo Project! 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 * Origin: The Point of Obfuscation! (1:212/2001.5) --------------- FIDO MESSAGE AREA==> TOPIC: 214 POWER BASIC Ref: C4F00002 Date: 04/09/95 From: ERIC SCHONNING Time: 2:18:am \/To: CHRIS ADAMS (Read 6 times) Subj: Re: Echo Project! ES> that was me. Bob Harris used to ask me to look at the rbbs source code CA> I thought so. ^^^^^^^^^^ Sounds semi-familar, was he running a BB CA> in 805 in the last year? He ran HIS Board. He moved to Pensacola, Fl beginning of march this year though and hasn't gotten the bbs fully up again yet. CA> Yeah. Like that EBBS that came on the PB/XTRA disk, it was okay to CA> compile, but a real pain to mod. I have never looked at that code. I think its also posted on the PB BBS as well as being on those disks. Just too much going on to mess around with other people code... CA> I generally use GOSUB only for error/event handlers (Why can't they ad CA> subs?) and GOTO only for REALLY complicated looping if/then structures CA> (like what I got in my project for trig, which suffered from CA> "Just-one-more-feature"-itis) Yeah I often wondered why it was an "ON ERROR GOTO" sort of thing and "ON KEY GOSUB" as well as "ON COM GOSUB". Guess its just holdovers from early basic daze. My use of goto and gosub within sub's is if the code in the CASE/IF/LOOP/etc is getting a little too big. Its easier to read sucessive if/thens then have to wade thru an if/then a bunch of code/then next else. So I tend to use gosub for these, so it will be if then/gosub/else/gosub sort of structure, and you can name your gosub labels by what you are trying to do to make it more readable. thats only for stuff that others may read, my own stuff could care less (you should see the cd-rom door code, some parts are really clean while others it takes me a few minutes to figure out just what in the @#$%#$ i was trying to do!). btw, for easy cd-rom support i recommend allowing the file database to be broken into "conferences" so to say, ie: allow for separate file databases for each cd-rom disc. merging different cd-rom discs into same file database is a nightmare. this way also if they change cd's then its just a matter of taking that database out of the config and putting the new one in. we can discuss this more as you approach the time when you are going to add the file area code if you want. Eric --- QM v1.00 * Origin: Creekside Manor (805) 484-8016 CdCom Support BBS (1:206/2512.0) --------------- ** A related thread FOLLOWS this message. FIDO MESSAGE AREA==> TOPIC: 214 POWER BASIC Ref: C4GP2220 Date: 04/12/95 From: MICHAEL SCHWENN Time: 08:37pm \/To: ERIC SCHONNING (Read 5 times) Subj: R: Re: Echo Project! ES I would like to see avoided as much as possible. Someone should be ES able to look at this code and figure out what is going on rather quickly, ES instead of threading your way thru gosub calls and tracking global ES variables. That is the biggest nightmare of rbbs source code. OK RBBS was good for that time. It is not all the hard to figure out. I worked with the code for two years and it not all that difficult to operate with. But I do agree that the code is that the easiest thing to add mods too. Many are still working with the code and finding the ins' and outs' of programming RBBS. And many of good things have happen with the code since the first release. I hope this project will show new ways and ideas on how programming a BBS does not have to be confusing and difficult to follow. I know that I will be keeping a eye on the development of the code. Michael --- JABBER v1.2 !CONNECT! Milwaukee Wisconsin --------------- >>>>>>>>>>>>>>>>>>>>>> LAST Message In Thread <<<<<<<<<<<<<<<<<<<<<< FIDO MESSAGE AREA==> TOPIC: 214 POWER BASIC Ref: C4F00003 Date: 04/09/95 From: ARNIE SOSSNER Time: 11:53pm \/To: DANNY LAROUCHE (Read 6 times) Subj: "print screen"??? DL>Is someone know how to do a "print screen" when using dos application DL>under windows ?? Press Shift-Print.Screen, just as you do in DOS running without Windows. ...Arnie in Hurley, NY --- OLX 2.2 Alex, I'll take "Things Only I Know" for $1000. --- WILDMAIL!/WC v4.12 * Origin: Acorn I BBS * 1:2624/503 * Marlboro, NY * USR 28.8 (1:2624/503.0) --------------- FIDO MESSAGE AREA==> TOPIC: 214 POWER BASIC Ref: C4F00004 Date: 04/09/95 From: ARNIE SOSSNER Time: 11:57pm \/To: CHINIAN WANG (Read 6 times) Subj: Command$ CW>My PB31's command$ can't work in the IDE environment. Do you mean that when you select Alt-Run|Command$, the values you enter there aren't input into the program you are developing? ...Arnie in Hurley, NY --- OLX 2.2 I fought the lawn and the lawn won... --- WILDMAIL!/WC v4.12 * Origin: Acorn I BBS * 1:2624/503 * Marlboro, NY * USR 28.8 (1:2624/503.0) --------------- FIDO MESSAGE AREA==> TOPIC: 214 POWER BASIC Ref: C4F00005 Date: 04/09/95 From: CHINIAN WANG Time: 02:11am \/To: ALL (Read 6 times) Subj: PB under NW3.x/PNW Hello all! I got a problem running PB31 under Personal Netware... PB.EXE won't allow me to load any files, also the executed file which PB31 compiled can't access the network files. Is this a known bug? Chinian, chinian@eespcb.ncku.edu.tw --- * Origin: The FUTURE NETWORK ! (6:721/100) --------------- FIDO MESSAGE AREA==> TOPIC: 214 POWER BASIC Ref: C4F00006 Date: 04/09/95 From: LAWRENCE GORDON Time: 02:56pm \/To: DARRYL KIMMEL (Read 6 times) Subj: test Quoting Darryl Kimmel to All: DK> Are we getting out to the PowerBasic Echo? DK> Thankyou, DK> Darryl DK> --- VFIDO 7.00.05 DK> * Origin: Synthetic Development Systems (1:207/209) Gotcha and welcome. * WCE 2.0/2081 * --- WILDMAIL!/WC v4.12 * Origin: Toast House * (314) 994-0312 * (1:100/560.0) --------------- FIDO MESSAGE AREA==> TOPIC: 214 POWER BASIC Ref: C4H00000 Date: 04/10/95 From: JOHN MILLER Time: 07:37am \/To: TROY JONES (Read 6 times) Subj: Re: echo project! Stamp: 04/06/95 TJ> Ohh, I got my PB demo today. While I am impressed with the overall TJ>features and options, the IDE is just plain UGLY! ;-) If I could atleast TJ>change the colors to my liking I would be MUCH more happy. These are changeable with the commercial version as well as the key assignments and default menu/Ide environment settings.. PB includes a utility called PBINST.EXE that allows you to change all of this. ___ * UniQWK v4.1 * The Windows Mail Reader --- WILDMAIL!/WC v4.10 * Origin: DSE Software Publishing BBS 707-459-4484 (1:125/123.0)