Announcement

Collapse
No announcement yet.

PAPPL 1.0 Beta Released For Ultimately Replacing CUPS Printer Driver

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • hikingpete
    replied
    s/stagnate/stagnant/

    Leave a comment:


  • Old Grouch
    replied
    Originally posted by oiaohm View Post
    https://openprinting.github.io/docum...r-application/

    First you need to read this.

    There will be a compadiblity layer there is already a snap package that makes the existing cups a pappl. That is above link.



    It detects the supported printers and advertises those printers on the localhost as an IPP Everywhere printer.
    This is also in the above link. Horrible as it sounds cups for old printers totally gets to remain.



    Really this is could be worse. Printer Application’s Web Interface This now means each printer can have a unique printer interface. The concept of every printer maker providing their own printer driver this nicely adds to more interface fragmentation.

    So now you need to know how to use cup interface for old printers and what ever random interface with bugs the vendors come up with.

    Yes the horrible part about pappl is lets expose a web application as the printer configuration that can be designed how ever the vendor likes. This is also true for so call driverless printers. The hard reality is all this work to change to pappl may be almost totally pointless as vendors just make all their new printers the new IPP driverless class.

    Why almost totally pointless by making cups just another driverless printer applications can simplify their code that all printing is IPP driverless.

    https://openprinting.github.io/drive...nd-their-pdls/

    Please note driverless printer is already 4 different standards.

    Idea that this mess is getting better could be a big case of wishful thinking.
    https://xkcd.com/927/

    Further comment unnecessary.

    Leave a comment:


  • pal666
    replied
    PAPPL looks like some stock

    Leave a comment:


  • Mani
    replied
    The basic idea is that most/all newer printers support IPP everywhere (thanks to Apple AirPrint and consorts), which is a *driverless* (meaning the printer tells CUPS what it can do and CUPS will advertise this to you) printing standard. Therefore, for newer generation printers CUPS only has to provide the IPP handling.

    Older drivers are a huge PITA to develop (ppd files are not very straightforward to write/understand). So instead of CUPS having to provide multiple paths for older and newer printers the older printer drivers will be converted to PAPPL-printer applications. All the driver specifics are within these programs which advertise themselves via IP or dbus-services as IPP everywhere printers, so CUPS only has to handle the IPP part. From CUPS' point of view the new printer applications are just some random IPP everywhere printer in the local network.

    While on the one hand side this results in quite some code duplication (due to "highering" of functionality, although mitigated as long as the PAPPL library is used) this should only affect older printer generations AND will ensure a more sophisticated path of forward compatibility for these printer drivers (at least when they are converted to printer applications which should happen to the open printing drivers within the next months).
    This change lightens up CUPS by quite some amount and I really think this is the right way to go
    Last edited by Mani; 12 November 2020, 05:44 AM.

    Leave a comment:


  • oiaohm
    replied
    https://openprinting.github.io/docum...r-application/

    First you need to read this.
    Originally posted by Kemosabe View Post
    Well does pappl bomb us back to the dark early 90ies or will there be some compatibility layer to reuse old drivers?
    There will be a compadiblity layer there is already a snap package that makes the existing cups a pappl. That is above link.

    Originally posted by pininety View Post
    Also, does pappl still use the great idea of files which are both written by the user and the program making read only root and splitting configuration from state impossible?
    Really hoped for some replacement for the dreaded cups bullshit, just do not have much hope in the developers of cups.
    It detects the supported printers and advertises those printers on the localhost as an IPP Everywhere printer.
    This is also in the above link. Horrible as it sounds cups for old printers totally gets to remain.

    Originally posted by R41N3R View Post
    I hope it makes printing easier, while CUPS works it often was a long procedure to figure out all the necessary details.
    Really this is could be worse. Printer Application’s Web Interface This now means each printer can have a unique printer interface. The concept of every printer maker providing their own printer driver this nicely adds to more interface fragmentation.

    So now you need to know how to use cup interface for old printers and what ever random interface with bugs the vendors come up with.

    Yes the horrible part about pappl is lets expose a web application as the printer configuration that can be designed how ever the vendor likes. This is also true for so call driverless printers. The hard reality is all this work to change to pappl may be almost totally pointless as vendors just make all their new printers the new IPP driverless class.

    Why almost totally pointless by making cups just another driverless printer applications can simplify their code that all printing is IPP driverless.

    https://openprinting.github.io/drive...nd-their-pdls/

    Please note driverless printer is already 4 different standards.

    Idea that this mess is getting better could be a big case of wishful thinking.

    Leave a comment:


  • R41N3R
    replied
    I hope it makes printing easier, while CUPS works it often was a long procedure to figure out all the necessary details.

    Leave a comment:


  • pininety
    replied
    Also, does pappl still use the great idea of files which are both written by the user and the program making read only root and splitting configuration from state impossible?
    Really hoped for some replacement for the dreaded cups bullshit, just do not have much hope in the developers of cups.

    Leave a comment:


  • Kemosabe
    replied
    Well does pappl bomb us back to the dark early 90ies or will there be some compatibility layer to reuse old drivers?

    Leave a comment:


  • PAPPL 1.0 Beta Released For Ultimately Replacing CUPS Printer Driver

    Phoronix: PAPPL 1.0 Beta Released For Ultimately Replacing CUPS Printer Driver

    PAPPL as the printer application framework created by the CUPS founder is approaching the v1.0 release...

    http://www.phoronix.com/scan.php?pag...-Beta-Released
Working...
X