[MUD-Dev] Re: Let's talk about numbers.

[Jon A. Lambert]

On 25 Sep 98, Caliban Tiresias Darklock wrote:
> On 08:03 AM 9/25/98 -0600, I personally witnessed T. Alexander
> Popiel jumping up to say:
> >
> >Users are finicky things; they claim to want flexibility, but what
> >they really want is flexibility to do what _they_ want, without
> >having to even think about what other people might want.  
> 
> That's probably the most succinct and accurate way I've ever heard
> it put. :)
> 
> My take on how to do this: provide reasonable defaults for
> everything, and allow configuration in tiers -- i.e. by a list of
> possible things you could configure, arranged in order of both topic
> and complexity. 
> 
> I've been thinking about how to do this with a Windows app (yes, I
> am still building a Win9x MUD server), and what I came up with as a
> reasonable solution was to put a list of bright labeled icons on the
> left of the configuration window, populating the right-hand portion
> with property sheets in which the most common and basic functions
> are on the top sheet. As you move to the right, you have more
> complex functions and options, until you finally reach the "Deep
> Magic" section. 

For configuration options, I like using tab controls.  A few Windows 
apps make use of these, but they are much more commonly seen as 
standard fare on OS/2.   Each tab is a different category.  Saves
screen space and prevents the endless drill down and back up to find
what you want.  The Win95 System and Display properties make light 
use of tabs, but rather inconsistent use.  I prefer the vertical tabs
though.  

> This lets the majority of users go through and set their options
> quickly and easily, by just going down the list on the left where
> they normally look for button menus. Advanced users will quickly
> pick up on the property sheets and be able to go through them with
> ease, checking and modifying things no one in his right mind wants
> to mess with unless he REALLY knows what he's doing. 
> 
> I still don't have a reasonable safety net in there. I should
> install one, but I'm not sure what to use. It needs to be something
> that protects the inexperienced without inconveniencing the
> experienced.
 
Another advantage of the dialog approach over a config flatfile is 
that you then have editing, validation, bubble help and context level
help easily available.  Still the information can be stored in a 
flatfile in any format (.ini is rather handy) so the experienced user
can use any editor on it.

--
--/*\ Jon A. Lambert - TychoMUD     Internet:jlsysinc at ix.netcom.com /*\--
--/*\ Mud Server Developer's Page <http://www.netcom.com/~jlsysinc> /*\--
--/*\   "Everything that deceives may be said to enchant" - Plato   /*\--