KAssistantDialog proposal
Tim Beaulen
tbscope at gmail.com
Thu Aug 24 21:07:44 BST 2006
I think the clickabel steplist is an awfull idea.
Why would someone need a clickable steplist ?
To skip several steps (and use the default values) and set some other
values in relevant steps?
If so, the problem is that there are too many steps.
The solution is to reduce those steps.
Why not ask the user what he wants to configure?
Something like a switch between a basic setup (default values) or
advanced setup.
In the advanced setup present the user with a list of maximum 5 or 6
items that he can choose to setup individually and return to that list
after configuring.
If you need more, I think the design is wrong and the assistant should
be split up in multiple assistants.
Instead of a clickabel steplist on the left, show a (non clickabel)
context tree so the user knows where he is.
Example:
First page: welcome page with the purpose and goal of the assistant/wizard.
Second page: ask the user if he wants to keep the default values with
the exception of those values that need to be set. Or ask if the user
wants to fine tune the settings.
If the user wants to tweak/fine tune the settings, give him/her a
short list with the main topics he/she can change. Try not to give too
many options (as it's going to be confusing for the user). Also
explain those topics in clear text, don't give five cryptic words for
example. An assistant should help the user make his/her decisions.
Now, when a user clicks on one of the options, a new page shows with
more options to fine tune and so on. But don't create a tree that goes
too deep here.
In the mean time, give a context tree of where the user is on the left.
If needed, it can be made clickable to go back. Clicking should not be
available to go forward, which is ok if you only show the context
because then you can't go forward only backwards. Going back should be
seen as a cancel operation and should not set any values. Going back
is a panic solution in most cases. Only clicking next should actually
set values.
After finetuning the options the user gets back to the original topics
he can finetune. There he still has the option to finish the assistant
and keep the defaults for the other options. Maybe the user can be
shown visually which topics he altered and which not.
In short, what I want to say is that I have the feeling that a
clickable steplist will eventually lead to super complex wizards with
all the bells and whistles one can think of. Instead, these should be
seperated in different assistants.
My opinion of course.
More information about the kde-core-devel
mailing list