Le Ven 10 février 2006 12:45, Tim Waugh a écrit : > On Thu, Feb 09, 2006 at 08:31:34PM +0100, Nicolas Mailhot wrote: > >> 2.6.1 Inheritance of settings for one printer model >> >> Also, when a new queue is setup for a printer model which the user >> already used before, it should inherit the settings of the most recently >> used queue of the same model >> >> Printer model is either autodetected or declared by the user >> >> (typical use case : bigcorp site where all the floors use the same >> printers, and where dying printers are replaced by the same model from >> the corp stocks) > > This sounds like a really good idea. I think there are two cases: > > a. all floors use the same printer model > > This really becomes the idea that Arjan suggested, which was (I think) > that there is a site policy on which printer models should have which > settings. > > Arjan, is that what you meant? > > b. dying printers are replaced by same model > > This doesn't really seem to be any different to 'unplug printer; > re-insert it', already covered in 2.6. No, because in the USB case they'll have a different serial number, so HAL will declare a new device. Also it should be possible for the user to have different settings for two printers of the same model (ie by default copy settings of most recently used for new queue creation, but allow the user to change them later on a printer-per-printer basis). Sometimes two printers will declare the same model but one will have one or more addons installed (trays, memory, duplex unit, stappler, whatever) >> 2.6.2 Memory of configuration strategies >> >> I'd also be nice if generic settings (use best quality available or >> fastest printing, PS or PCL, duplex or not) could be remembered by the >> tool and applied to new queues > > I don't think this can really be done in general. Different PPDs > can have widely differing options. That's tricky. they all have different options, but the options all have similar meanings (they're all printers after all) Regards, -- Nicolas Mailhot
