On Fri, 26 Oct 2007 06:44:52 -0500 Aaron Konstam <akonstam@xxxxxxxxxxxxx> wrote: > On Fri, 2007-10-26 at 12:34 +0100, Tim Waugh wrote: > > On Fri, 2007-10-26 at 06:26 -0500, Aaron Konstam wrote: > > > But the real problem is that the cups web interface is how one is > > > supposed to configure printers in cups. system-config-printer is > > > something that has only recently evolved to really work, Why use > > > the fake when you can use the real thing. > > > > By that argument, the 'real thing' is /usr/sbin/lpadmin -- another > > libcups utility that performs the same functions. > That is what is called "reducto ad absurdum". > > > > > Further. although it is not important in this case, there are > > > certain printer sharing situations that are hard to deal with in > > > system-config-printer. > > > > Are they easier to deal with in the CUPS web interface? > Yes they are since using the web interface you are forced to deal with > the structure of the cupsd.conf and client.conf files to do the > sharing. With system-config-printer you are lulled into the fantasy > that you can conrol sharing completely with the GUI interface and you > can't. Right, that's not very constructive. The point of system-config-printer is that it integrates into the system and the CUPS web interface really does not. Seeing as system-config-printer is relatively new and CUPS was built with the webinterface in mind, of course you're right -- the web interface functionality will always be as complete as possible. But it's not very user friendly. And system-config-printer will get better to the point where every task desktop users need to do with printers will be integrated. It just takes a bit more time. I'd rather the CUPS web interface was ditched altogether in favor of system-config-printer for users and the command line for administrators but unfortunately it seems that CUPS upstream is pushing for their web interface. --Stijn
