home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
HATCH
/
WWIVNEWS.ZIP
/
9407_11.NWS
< prev
next >
Wrap
Text File
|
1994-07-24
|
15KB
|
373 lines
/* +QRZ */ } else {
/* +QRZ */ pla(" \003"
/* +QRZ */ "4+--------------------------------+----------+", &abort);
/* +QRZ */ }
/* +QRZ */ nl();
/* +QRZ */ }
2. Later in BBS.C, make this change to void mainmenu(void):
/* =QRZ */ if ((strcmp(s,"NET")==0) || (strncmp(s,"NET=",4)==0))
/* =QRZ */ print_net_listing(0);
/* +QRZ */ if (strcmp(s, "QRZ") == 0) {
/* +QRZ */ list_hams();
/* +QRZ */ }
/* =QRZ */ if (strcmp(s,"QSCAN")==0) {
/* =QRZ */ nl();
3. Recompile. Should be quick -- you only changed one file.
4. Add //QRZ to the slash-commands menu (menu #15).
5. If you have my MODLIST mod installed, the CHANGES.MSG description line
for this mod is:
QRZ 02-23-94 1@5806 Display all users with amateur radio calls.
─────────────────────────────────────────────────────────────────────────────
The Mod of the Month for May-June was written by Spotnick, who incidentally
is one of those most instrumental in providing the French menus and string
files for WWIV.
─────────────────────────────────────────────────────────────────────────────
┌┬─── ── ─ ─ ── ───────────────────────────────────────────────────┬─ ∙∙
││ Alternative Worlds Presents │
└┼─────────────────────────────────────────────────────────────────────┐
││ Mod Name » ALTW-13.MOD │∙
││ Difficulty » █▒▒▒▒▒▒▒▒▒▒ (1/10) │:
││ WWIV Version » 4.23 and higher ││
││ Date Affected » 06/04/94 ││
:│ Files Affected » COM.C ││
∙│ Description » Multilingual Yes/No Prompts Toggable With Space ││
└─────────────────────────────────────────────────────────────────────┼┐
│ A French Mod Division Release - (C) 1994 Logicom Softwares ││
∙∙ ─┴─────────────────────────────────────────────────── ── ─ ─ ── ───└┘
┌┬══════════════════┐
││ Long Description ││
└══════════════════┴┘
This is an update to SPOT015.MOD. Actually all it does is to display
a yes/no prompts in the language of the user, and this prompt is toggable by
hitting the space key. It's easy to install and it is very useful.
───[Step 1]────────────────────────────────────────────────────────────────────
Load COM.C and add this function before int yn(..) :
void rprompt(int pos, int redo)
{
int i,i2;
if (!wfc) {
i2=(strlen(str_yes)+strlen(str_no)+5);
if (redo)
for (i=0;i<i2;i++)
npr("\b");
if (pos==0)
npr("7[3%s/4%s7]9: ",str_yes,str_no);0
else
if (pos==1)
npr("7[4%s3/%s7]9: ",str_yes,str_no);0
}
}
───[Step 2]────────────────────────────────────────────────────────────────────
Remplace the following 2 functions:
int yn(void)
/* The keyboard is checked for either a Y, N, or C/R to be hit. C/R is
* assumed to be the same as a N. Yes or No is output, and yn is set to
* zero if No was returned, and yn() is non-zero if Y was hit.
*/
{
char ch=0,pos=0,done=0;
rprompt(pos,0);
do {
ch=upcase(getkey());
if (ch==*str_yes)
done=1;
if (ch==13) {
if (pos==0)
ch=*str_no;
else
ch=*str_yes;
done=1;
}
if (ch==*str_no) {
done=1;
}
if ((ch==32) || (ch=='')) {
if (pos==0)
pos=1;
else
pos=0;
rprompt(pos,1);
done=0;
}
} while((!done) && (!hangup));
if (ch==*str_yes)
print_yn(2);
else
print_yn(3);
return(ch == *str_yes);
}
int ny(void)
/* This is the same as yn(), except C/R is assumed to be "Y" */
{
char ch=0,pos=1,done=0;
rprompt(pos,0);
do {
ch=upcase(getkey());
if (ch==*str_yes)
done=1;
if (ch==13) {
if (pos==0)
ch=*str_no;
else
ch=*str_yes;
done=1;
}
if (ch==*str_no) {
done=1;
}
if (ch==32) {
if (pos==0)
pos=1;
else
pos=0;
rprompt(pos,1);
done=0;
}
} while((!done) && (!hangup));
if (ch==*str_no)
print_yn(3);
else
print_yn(2);
return((ch == *str_yes) || (ch==13));
}
───[Step 3]────────────────────────────────────────────────────────────────────
Compile back the BBS and you're done.
French Proverb: Un tien vaut mieux que deux tu l'auras.
For comments, bug report and suggestion, e-mail at the following address:
Spotnick 1 @5497 (soon to be @20397)
Dark Shadow 3 @5497
French Division Support Sub: Sub Type "ESE", Host 5497. A Must!
───────────────┬─────────────────────────────────────────────┬───────────────
│ Dateline: @#$*()#! │
│ Editor's Notes by Omega Man (1@15117) │
└─────────────────────────────────────────────┘
Is it my turn on the soapbox yet? It is? Good, because I've got quite a few
things to cover this issue...
THE GRAND NETWORK RENUMBERING
─────────────────────────────
By the time you read this, Wayne should have implemented Stage 2 of the
WWIVNet renumbering scheme. As this went to press, this had not taken place,
and as a result most of the network addresses listed for the authors of the
articles you see here in this issue are probably not going to be accurate
by the time you read this. This was an editorial decision, and one that I
suspected would happen based on the timing of both this issue's release and
Wayne's desire to implement Stage 2 prior to WWIVCon.
So, if you wish to correspond to one of the authors whose words of wit appear
in this issue, you might want to doublecheck those network addresses before
you send that E-Mail off to never-never-neverland.
WW4NEWS?
────────
Ok, ok, ye editor decided to get a little humorous with the title of this
issue. This isn't a permanent change, obviously :-)
WWIVCON
───────
As most of you know, I will be unable to attend this year's WWIVCon for
several reasons, most of which were job-related. I sincerely hope everyone
that does show up has an enjoyable time, and doesn't let H2O Doc and Filo
tear up the hotel too much during the post-seminar debaucheries I'm told will
occur.
I would, however, like to make an aside note of commentary to the organizers
of WWIVCon itself, one that echos some of the sentiments surrounding the
organization and promotion prior to the event.
Folks, WWIVCon needed to be promoted -quite- a bit more than it was this
time around. There were a lot of people complaining on the WWIVCon'94 sub
as well as directly to myself through E-Mails to WWIVNews about "how little
[they're] plugging the event, and how repeated requests to [the organizers]
for event schedules are being ignored!"
Now, while Filo posted a rough event schedule just after the last round of
"what the -hell- is going on?" postings on the WWIVCon'94 sub, quite a few
people had already reversed their decisions on attending the convention.
For many, a trip to New Orleans - especially during the July 4th Weekend -
is somewhat of a financial burden. Those who cancelled their plans did so
citing the lack of accessability to con information prior to attending,
which is something that simply shouldn't have happened in the first place.
Despite this, I suspect that WWIVCon will be considered enough of a success to
merit a repeat in '95. However, I strongly suggest that the organizers for
next year's convention should concentrate on getting the word out quite a
bit wider than it was this time around. The more people who know about an
event, the more people are likely to attend.
Finally, a suggestion for a location for WWIVCon'95: San Antonio, Tx would
be a perfect place to hold this event. There's numerous historical and
family-oriented landmarks and attractions in this city, and hotel rates
are actually a little bit cheaper than in N'Orleans. Oh, and the Riverwalk
is a great place to get blasted after the con, too!
ALT.BBS.RENEGADE?
─────────────────
Word from the Internet/Usenet side of the fence tells of a proposal to create
an alt.bbs newsgroup dedicated to the Renegade BBS program. Renegade, as
most WWIV sysops are aware, is an acknowledged derivative of Telegard, which
in turn was derived from the unauthorized use of the source code for WWIV
3.21d. While the formal Request for Discussion (RFD) will no doubt garner
quite a few flame wars, considering the heated nature of this particular
topic, one can't help but wonder that if the Call for Votes (CFV) for this
newsgroup manages to pass, will comp.piracy.for.fun.and.profit be far behind?
Regardless of how this turns out, it might be wise to look into at least an
RFD for comp.bbs.wwiv, seeing as how WWIVnet-Usenet gateways are beginning
to proliferate these days...
INTERNAL QWK FOR WWIV
─────────────────────
This seems to be one of -the- hot topics on the sysop subs these days, with
the dividing lines being set three ways: those who want a -free-, built-in
internal .QWK manager - whether it be by Wayne or by someone else's mod -
those who are external .QWK developers, and those who don't want -either- on
their systems. Needless to say, there have been a few heated commentaries, and
as you've seen already some of the more "sedate" ones were reprinted in the
Type 0 Forum for this issue of WWIVNews.
My own opinion tends to side with those who want a basic-featured 100% Wayne
Bell-written or installed internal .QWK manager. However, I also side somewhat
with the designers of the external managers in the fact that were such a
feature added internally to WWIV, it should be toggleable only through a
#define, which of course requires that you be a registered WWIV sysop with
an equally registered copy of the source code. This fence straddling approach
addresses the two major concerns surrounding this particular improvement:
In case you haven't noticed it yet, those siding against inclusion of an
internal .QWK manager into WWIV come from two different camps - those who
don't want to waste memory on a feature they don't use or need, and those who
actually -write- external .QWK managers. The former is comprised of sysops
whose systems are a bit short on memory for any number of reasons, and need
WWIV to remain as small as possible while within conventional memory. Those
in the latter category, of course, are looking out not only for their own
finanical interests, but for the interests of those in the first category as
well.
On the other side of that fence, those supporting an internal .QWK manager do
so for several reasons. Most agree that making .QWK management an internal
part of WWIV would solve three major problems cited with external managers:
special configuration problems, external shrinking lockups, and difficulties
regarding customer support. All three of these problems, most proponents claim,
would be eliminated if Wayne were to incorporate a basic-featured QWK manager
in WWIV; after all, if a bug can't be fixed by Wayne in a timely fashion, the
source code would at least be available for -someone- to devise a fix. At the
same time, those writing external managers can continue to do so without fear
of losing too much business. As the internal QWK manager would only have the
very basis features, external QWK authors would be free to continue development
of their utilities, and use whatever extra features their programs provide as
their selling point.
Such a modification already exists, as the autobiographical article by the
Asylum Group in this issue explains.
While I have not personally installed or used a WWIV BBS that has such an
internal manager, all the reports I've received regarding the Asylum/QWK mod
have been either on the borderline of "flawless performance!" or "It crashed
my system, but that's because I goofed up with some cut & paste in Borland's
crappy editor!" It's these latter types of reports that has me convinced that
a pre-installed, but #defineable internal QWK manager is preferable to
expecting everyone to install such a complex mod from scratch.
Wayne has stated that no internal QWK manager is planned for 4.24. However,
he did not rule out one for a later release of WWIV. Currently, a poll on
this topic is being conducted on several of the Sysop subs, and the results
will be posted in the next issue of WWIVNews. In the meantime, express your
opinions on this matter by participating in this poll, and by submitting
your comments to the Type 0 Forum.
WWIV NETWORKS LISTING
─────────────────────
Some of you may have noticed a lack of this feature in this issue. This was
due to a loss of contact with Red Adept prior to press time. We should have
this problem rectified by next issue, and WWIVNews apologizes for any
inconvenience this omission has caused.
COMING UP NEXT ISSUE
────────────────────
By next issue, 4.24 should either be out, or just seconds away from being
released. We'll have the latest news on this new release, as well as Filo's
first "mods of the month" specific to 4.24. The first reports from WWIVCon
will be out, and WWIVNews will have those, as well as the first site proposals
for WWIVCon'95. We'll also have more commentary on the "internal QWK" debate,
an update on "comp.bbs.renegade?", as well as the usual plethora of news and
information.
Until then, folks, don't give, back WWIV!
┌───────────────────────────────────────────────────────────────────────────┐
│ Closing Credits │
├───────────────────────────────────────────────────────────────────────────┤
│ WWIVnews is an independent newsletter NORMALLY published every 6 weeks as │
│ a service to the WWIV community of sysops & users. The opinions & reviews │
│ expressed herein are the expressed views of the respective writers, & do │
│ not necessarily reflect those of the WWIVnews staff. Reproduction in whole│
│ or in part is allowed provided credits are given. All rights reserved by │
│ WWIVnews, and all articles are copyright of their respective authors. │
├───────────────────────────────────────────────────────────────────────────┤
│ The source site for WWIVnews is the Klingon Empire BBS (512-459-1088), │
│ WWIVnet node @15117. Requests for information regarding articles & other │
│ editorial submissions, as well as back issue requests and the WWIVnews │
│ Writer's Guide, can be sent E-Mail to the WWIVnews editor, c/o 1@15117 │
├───────────────────────────────────────────────────────────────────────────┤
│ WWIV and WWIVnet, copyright 1986,1990 by Wayne Bell │
│ Any product or company mentioned or reviewed herein are copyrighted of │
│ their respective owners, creators, and other corporate pseudoentities. │
└───────────────────────────────────────────────────────────────────────────┘