https://bugzilla.novell.com/show_bug.cgi?id=852850 https://bugzilla.novell.com/show_bug.cgi?id=852850#c12 --- Comment #12 from Johannes Meixner <jsmeix@suse.com> 2013-12-05 10:23:18 CET --- Generalization of "Empty list with 'Add' button => user clicks 'Add'.": I thought I could use the case "Empty list" as indication that the user may actually wnat to print via network but this would be wrong. Rationale: Assume the user has a local USB printer set up and additionally he wants to print via network. This is the usual case for a mobile system (e.g. a laptop) where a local queue exists (e.g. for an USB printer at home) and when not at home the user wants to print via network (e.g. in the office). In this case the list of already available print queues would not be empty (the USB printer's queue exists). When the user is not at home (e.g. in the office with a CUPS server) and wants to print from an application, the application's print dialog only shows the queue for his USB printer at home because the firewall that must run on a mobile system must block CUPS server's queue announcements see in particular "print job phishing" at http://en.opensuse.org/SDB:CUPS_and_SANE_Firewall_settings The user misses queues to print via network. When the user is not aware of the firewall (cf. https://features.opensuse.org/316708), the user may launch yast2-printer to set up printing via network but for the same reason (firewall blocks CUPS queue announcements), the user would see only the queue for his USB printer at home in the overview dialog but no queues to print via network. The user misses queues to print via network in the list but there is that "Add" button next to that list so that it is totally obvious what to do next... Therefore from my point of view a generalization of "Empty list with 'Add' button => user clicks 'Add'." is the following finding: Usability hypothesis: "Missing entry in list with 'Add' button => user clicks 'Add'." To get at least some kind of evidencde (or even a proof) for that hypothesis: Christopher De Nicolo, Juergen Weigert, and whoever is listening here: please provide feedback whether or not you think my above analysis is correct. Outlook: If my hypothesis is right, the yast2-printer initial overview dialog needs a fundamental re-design. Basically (if my hypothesis is right), it means one cannot have two different buttons to set up printing (one via "Add" and one via "Printing via Network") which means the setup for printing via network must somehow be integrated with the setup for local print queues (the current "Add" setup). This would need a fundamental re-design of the whole workflows in yast2-printer. Retrospect: Setup for printing via network was not a major goal at the time when the YaST printer module was made anew. The main goal at that time was to clean up the mess of the old YaST printer module, see in particular "Basic Design Ideas" and "Strict Compliance With CUPS" at http://en.opensuse.org/Archive:YaST_Printer_redesign The current YaST printer module does not specifically implement anything that guides the user towards "Print via Network". The user is currently on his own to somehow know in advance that he must click "Print via Network" (but not "Add") when he wants to set up printing via network (cf. "Regarding a more windows centric world" in comment#4). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.