Mailinglist Archive: opensuse-ux (48 mails)

[Johannes Meixner <jsmeix@xxxxxxx>]

Hello,

On Nov 15 10:58 Martin Schmidkunz wrote (shortened):
> ... if you are doing
> something that doesn't meet the user's expectations you have to explain
> that to him ...

Exactly!

This is what I like to get all the time.
I think a YaST setup module should be better than just show
choices to the user but leave him (mostly) alone what to choose.

I think a YaST setup module should establish some kind of
communication or dialog with the user to find out what he wants
and then guide him to a reasonably good possible setup
(in particular when what he wants is not exactly possible)
or be brave and tell him frankly when what he wants is
impossible (e.g. configure an unsupported printer).


> And we should really, really focus on bringing the printing model to the
> user. That means of course that it is not enough to hide the explanation
> in the help text :-)

YES!

I think this is our key problem:
How to display the basics of the real printing model to the user
so that he gets a basic understanding what the heck this weird
and confusing printing config stuff is all about.


I think Rajko's understanding is perfectly sufficient:
A queue is a software black box that does whatever is necessary
to give appropriate printout and sends it to the printer. 

The exact right point in his understanding is "queue is software".

I assume when he does "lpstat/lpq" or whatever graphical stuff
to query the printing system, then his understanding helps him
to be aware that he gets only the state of a piece of software
and not necessarily the state of a piece of hardware (the printer).


Kind Regards
Johannes Meixner
-- 
SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany
AG Nuernberg, HRB 16746, GF: Markus Rex
-- 
To unsubscribe, e-mail: opensuse-ux+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-ux+help@xxxxxxxxxxxx