![](https://seccdn.libravatar.org/avatar/11b4b3cf016b1d6a62454324eaaacc59.jpg?s=120&d=mm&r=g)
On Wednesday 21 November 2007 04:34:21 am Johannes Meixner wrote:
Hello,
On Nov 18 02:42 kevindupuy@bellsouth.net wrote (shortened):
I think you hit the nail on the head there.
Guess what: I hit this nail since several years now and what is the result?
Probably it is the time for bigger hammer ;-)
Set up several printers which are locally conected to a computer (e.g. via parellel port or via USB) is no problem. In some cases it may fail (=> Bugzilla) but there is no real problem behind.
Set up the "printing in the network" stuff is the problem.
It is not only UI problematic, but also process. I had a problem to remove networked printer and replace with local. For to me not clear reason YaST was trying to find computer in a network with attached printer that was sitting disconnected on the table. I left module trying and did other stuff and after some time checked again, printer was finally removed. This is one example where even experienced Linux user would have to start reading manuals to find first where to start troubleshooting. YaST didn't gave any information what it is doing and option to quit if user wants that. I know that it is searching network by lights on router. Adding local printer was easy, it could be put in very simple UI with information what was done, test button and greetings.
It is still our key problem how to display the basics of the real printing model to the user so that he gets a basic understanding what this weird and confusing printing stuff is all about. I think it cannot work well when only printing experts and YaST programmes try to solve such a key problem.
I touched the basic idea of black box within computer with good reason, it simplifies user need to know much about software behind. This black box can be explained with detailed schematic diagram for those that want to learn, and than even more details for guys that want to help development, as programmers and testers.
A usability expert who is really interested in printing is needed. I mean someone who is willing to learn the real printing model so that we could add real value and not only "yet another setup tool user interface beautification" ( YaST -> YaSTUIB ;-)
You as printing expert can help a lot, by creating some schematics to present smaller blocks of a black box, so that guys that have interest can ask questions. When we have diagram it is easier to understand how setup works for non programmers, and from there it is easier to see what can be simplified and for which printer models.
By the way:
It seems we are back to a "syntax versus semantics" problem, see the "syntax versus semantics in UI" thread, http://lists.opensuse.org/opensuse-ux/2007-05/msg00075.html
Our key problem seems to be related how to display at least semantics to the user. Perhaps it is even more: "Pragmatics"?.
I guess that external help in form of diagrams may be very pragmatic way to start with. It will help experienced Linux users to understand internal working and than translate that in help to newcomers. Following mails can help to see what can be improved. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse-ux+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ux+help@opensuse.org