Re: messages from the WWW Library
montulli@stat1.cc.ukans.edu (Lou Montulli)
From: montulli@stat1.cc.ukans.edu (Lou Montulli)
Message-id: <9307060215.AA19734@stat1.cc.ukans.edu>
Subject: Re: messages from the WWW Library
To: www-talk@nxoc01.cern.ch
Date: Mon, 5 Jul 93 21:15:26 CDT
In-reply-to: <199307060000.AA19203@milton.cs.uiuc.edu>; from "Aleksandar Totic" at Jul 5, 93 7:00 pm
X-Mailer: ELM [version 2.3 PL2]
Status: RO
> The error routine is void * ErrorAlert(short errorNumber, ...).
> Arguments following errorNumber are equivalent to printf. All the errors,
> and their reasons would be declared in a header file. There, arguments
> expected for each type of alert would be listed, as well as arguments
> expected to be returned from ErrorAlert. In case when user can take
> action upon error, an argument returned from ErrorAlert would specify
> the action to be taken.
>
Don't forget, not all messages are errors. There are progress messages like
"connecting to news host" and such. I also think that there should be much
more progress messages, at least as an option, to let the user know whats
going on. I don't mean trace mode, but something that shows at least
resonable progress.
We could use standards similar to, or the same
as X windows, with "informative" dialogs, "alert" dialogs, and "error"
dialogs. Alert dialogs could give the user a chance to respond, error
and informative dialogs would just inform, not query.
:Lou
--
**************************************************************************
* T H E U N I V E R S I T Y O F K A N S A S *
* Lou MONTULLI @ Ukanaix.cc.ukans.edu *
* Kuhub.cc.ukans.edu ACS Computing Services *
* 913/864-0436 Ukanvax.bitnet Lawrence, KS 66044 *
* UNIX! Cool! I know that! Jurassic Park - The Movie *
**************************************************************************