Feature changed by: Johannes Meixner (jsmeix) Feature #306393, revision 4 Title: BrowsePoll support in yast2-printer openSUSE-11.2: Rejected by Andreas Jaeger (a_jaeger) reject date: 2009-07-10 11:41:21 reject reason: A complete redesign is too much work for this feature. Priority Requester: Neutral Requested by: Johannes Meixner (jsmeix) Description: yast2-printer "Print via Network": request for BrowsePoll support Usually there is no need for BrowsePoll support in yast2-printer because currently it is designed to make a setup according to the "Intrinsic design of CUPS for printing in the network", see http://en.opensuse.org/SDB:CUPS_in_a_Nutshell (http://en.opensuse.org/SDB:CUPS_in_a_Nutshell) But there is a valid use case for BrowsePoll: See https://bugzilla.novell.com/show_bug.cgi?id=433047#c10 (https://bugzilla.novell.com/show_bug.cgi?id=433047#c10) I know a use-case for BrowsePoll: When in a bigger company there are several CUPS servers for various departments each server may allow access for all client hosts in the whole company but it would usually send browsing information only to the client hosts of the particular department to which a particular server belongs. When a user in department A likes to see additionally the queues on the server for department B he would use BrowsePoll to poll the queues from the server for department B. Adding BrowsePoll support requires a re-design of the whole "Print via Network" dialog. I like to have it evaluated if it is worth the effort ("business case" and so on). Discussion: #1: Andreas Jaeger (a_jaeger) (2009-07-10 11:42:58) Let's not redesign the UI for this at them moment. My only requirement is the default YaST policy: YaST should not overwrite user configuration changes, so if a user adds BrowsePoll and later runs YaST, the contents is still the same. + #2: Johannes Meixner (jsmeix) (2010-11-16 17:14:46) + Done for openSUSE 11.3 see + https://bugzilla.novell.com/show_bug.cgi?id=433047#c12 -- openSUSE Feature: https://features.opensuse.org/306393