[Printing-architecture] Automatic printer setup with Printer Applications

Till Kamppeter till.kamppeter at gmail.com
Wed Feb 24 19:21:35 UTC 2021

On 24/02/2021 18:48, Michael Sweet wrote:
> ... which is why I suggested you create a registry for printer applications so that you can map a printer to one or more printer applications that you then run "autoadd" on.

Printer Applications should have a way to query the full list of 
printers they support by model and also the full list of generic (for 
example by-PDL) support options they have. So some "Printer Application 
finder" tool could find whether support for a certain printer is 
available and then add the printer (with driver "auto") on the right 
Printer Application.

> I *don't* think that users should have every printer application installed - that is wasteful and confusing.

I think so, too. The Printer Applications should be available in the 
Snap Store and the Snap Store should have the 
search-by-hardware-signature thingy which I suggested:


> If the printer applications are based on PAPPL, you can use DNS-SD to find their system service endpoints and then have them add the printer using standard IPP operations, all through a common GUI.  Similarly, you can use DNS-SD to find the web pages, if that is the way you want to go...

Yes, I was also thinking this way for the network/local service manager 
application I suggested in the other thread. The manager could also have 
a button to start the "Printer Application finder" at each Printer 
Application entry.

The "Printer Application finder" will, once the correct Printer 
Application is selected (and installed if it was not installed yet) 
actually set up the printer via IPP operations.


More information about the Printing-architecture mailing list