Cool Visual Basic
 
Main
Frequently Asked Questions
VB Helpdesk
Message Boards
Library
Downloads
View Guestbook
Add to Guestbook
Product Reviews
Bookstore
Links
Newsgroups
Vendors
Affiliates
Cooltech.org


With the sudden proliferation of wizards, they've becom vital to any application. We'll takea look at the many styles and types of wizards.

Tree-view Wizard.

The tree-view wizard looks familar to users. You can collapse and expand various options, justlike windows explorer.
When you click on a setting node, you see the options for it appear in the ajoining window. Borland C++ has a excellent example of this type of wizard.

This has an advantage in that it is common to windows applications, and most users willknow what it is right away. Another advantage is that it utilizes screen space very efficently.

Microsoft-style

We are all probably familar to this kind of wizard. You see it in VB5, MSOffice, VC, and almost all MS applications. It's a multistep, navigatable wizard. One of thedisadvantages is that sometimes users can get bored of having to click the next button fiftytimes to make sure all data is correct. However, because it uses multiple steps, it is extremely space efficient.

Single Screen Wizard

The single screen wizard is rather simple. The idea is you fill in a few fields andclick a button, and then it finishes up for you. This type of wizard does not use multiple steps.
It is very simple to program, but is not space efficient. In fact, itis only suitable for wizards with a small amount of data.

The single screen wizard is similar to a Microsoft-style wizard with only one step.

Automagic Wizard

The "Automagic Wizard" is a somewhat new invention. It is either

A: In the background without user interaction.
B: Runs when the users requests but requires no input.
C: In the background but requests user interaction when it feels appropriate.

Programming this type of wizard generally involves either gathering data in the background aboutthe user or using Artificial Intelligence routines to make sense of whatever the user is doing.
Ideas similar to this are used very often in applications, although most do not make use of this technology enough for them to be called "Wizards".

A example of a primitive form of this is the "Wrist Strain Reminder."The Wrist Strain Reminder application pops a message box every 20 minutes reminding you totake a break from typing. While this is certainly not a wizard, it is a similar concept.

One way to make use of this kind of technology is to pop up a message box asking the userwhether they would like to run your preexisting wizard.

A good application of this is creating something that automates a users tasks withouttheir intervention. For example, a program that corrects common typing mistakes in thebackground of your application.

Don't irritate your users

If you use any kind of "Automagic" technology, you must be sure that you users canshut it off. Otherwise, it is very possible that they will get frustrated quickly ifyour wizard makes a mistake.

For example, a user was once running Word 6© with AutoCorrect on.The previous user have made extensive use of AutoCorrect, and as a result many meaningless(or so he thought)acronyms were converted to full sentences.

Unfortunately, the acronym actually needed to be typed. When the second user could notfigure out how to turn it off, he became very frustrated.

Obviously, we don't want our users to be frustrated, particulary any of the users happen to be 6-foot-7 gun-toting ex-wrestlers named Mungo.


Copyright 2000, David J Berube<Form1@aol.com>. All Rights Reserved.