Feature changed by: Simon Lees (simotek) Feature #316789, revision 16 Title: Fundamental re-design how to set up the whole printing stuff Requested by: Johannes Meixner (jsmeix) Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: The current YaST printer module provides different buttons (i.e. entry points) with different workflows for the different kind of printing setup actions: One via "Add", one via "Printing via Network", one via "Share Printers", and so on. This means the user must know in advance what to choose for his particular kind of printing setup. The software cannot guide the user towards the right entry point according to what the user wants to get in the end. To guide the user towards an actually right solution the initial dialog should show the list of currently available print queues plus one single button to "do whatever can be done" when something is not as expected (e.g. when something is missing) in that list. This means a fundamental re-design of the dialogs and workflows to set up the whole printing stuff is needed. Relations: - Bug 852850 - yast2-printer: better guide the user away from "Add" towards an actually right solution (mainly towards "Print via Network") (novell/bugzilla/id: 852850) https://bugzilla.novell.com/show_bug.cgi?id=852850 - simple laptop user firewall experience (e.g. printing) (feature/id: 316708) - Allow printer add and modification to users (feature/id: 313287) - Full automated setup for printers in the network (feature/id: 313282) - Let the admin ("root") download and install untrusted third-party RPMs from known URLs guided via YaST (feature/id: 307745) - Explicit IPv6 support for YaST printer module (feature/id: 312491) - RFC: No longer install printer driver RPMs when no printer was autodetected? (novell/bugzilla/id: 808315) https://bugzilla.novell.com/show_bug.cgi?id=808315 Discussion: #1: Johannes Meixner (jsmeix) (2013-12-11 11:50:43) If a fundamental re-design of the printing setup happens, then it would be the right time to also fundamentally improve how to deal in a user- friendly way with the case when a firewall blocks printing stuff, see the related Feature # 316708 (/316708) : "simple laptop user firewall experience (e.g. printing)". #2: Johannes Meixner (jsmeix) (2013-12-11 11:59:52) Regarding a more Windows centric world (e.g. outside of a Linux network) where one cannot expect to have any CUPS servers: The current YaST printer module does not specifically implement anything that guides the user in such a network environment towards an actually right solution. I.e. in a Windows network environment the user is currently on his own to "somehow know what he must set up" and then he can do this setup with the YaST printer module using the so called "Connection Wizard" (which can of course not do any magic to help the user). If a fundamental re-design of the printing setup happens, then it would be the right time to also fundamentally improve how to deal in a user- friendly way with the case to set up printing in a non-Linux network environment (in particular in a Windows network environment). For some of the possible issues even for a manual setup (to guide the user towards an actually right solution means some kind of automatism is needed) see the related Feature # 313282 (/313282) : "Full automated setup for printers in the network". #3: Johannes Meixner (jsmeix) (2013-12-11 12:02:30) If a fundamental re-design of the printing setup happens, then it would be the right time to also implement how to "Allow printer add and modification to users", see the related feature #313287 #4: Johannes Meixner (jsmeix) (2014-05-13 10:31:32) If a fundamental re-design of the printing setup happens, then it would be the right time to also implement so that users are better guided to printer driver package installation, see https://bugzilla.novell.com/show_bug.cgi?id=808315#c7 #5: Johannes Meixner (jsmeix) (2016-05-30 12:49:07) In http://ftp.pwg.org/pub/pwg/openprinting/presentations/cups-plenary-april-16.... (http://ftp.pwg.org/pub/pwg/openprinting/presentations/cups-plenary-april-16....) there is a new CUPS 2.2 feature "Local Print Queues" announced which could make the main task of the YaST printer module (create print queues) mostly dispensable. Excerpt from the above PDF: CUPS 2.2 Preview Local Print Queues The scheduler now supports a new CUPS-Create-Local-Printer user operation Local printers only accept local print jobs and live only as long as needed to print jobs to IPP printers The CUPS printing APIs now create local print queues automatically when printing to a discovered printer Any uncompleted jobs are lost if the system is reebooted Local print queues can be "upgraded" to regular queues by an administrator When CUPS 2.2 creates local print queues automatically when printing to a discovered printer the main issue could be no longer to create a print queue but to to discover printers. Whether or not automatically created print queues really work in practice for usual printers totally depends on how good the automatism can find a matching printer driver for a discovered printer model, cf. "Automated Printer Configuration" versus "Manual Printer Configuration ..." in https://en.opensuse.org/YaST_Printer (https://en.opensuse.org/YaST_Printer) #6: Johannes Meixner (jsmeix) (2016-05-30 13:04:09) (reply to #5) Typo in URL (last 'f' is missing), right URL is http://ftp.pwg.org/pub/pwg/openprinting/presentations/cups-plenary-april-16.... + #7: Simon Lees (simotek) (2017-01-10 00:53:45) + Given this topic is pretty broad it may as well also discuss the + printing pattern seen as it will probably be indirectly involved. (If + you feel that this is hijacking this fate feel free to get me to open + another. -- openSUSE Feature: https://features.opensuse.org/316789