Differences

This shows you the differences between two versions of the page.

--- gsoc:google-season-of-docs-2020-openprinting-projects [2020/04/08 21:17]
till created
+++ gsoc:google-season-of-docs-2020-openprinting-projects [2020/04/10 17:46] (current)
till
@@ Line 19: / Line 19: @@
 ======Project Ideas======
+=====Tutorial and Design Guidelines for Printer/Scanner drivers in Printer Applications=====
+Classic printer drivers consisting of printer-specific filters and PPD (Postscript Printer Description, describes printer capabilities and which filters to call) files which has to be dropped in certain directories of the file system are replaced by so-called Printer Applications, emulation of an IPP network printer.
+Physical IPP network printers work driverless, meaning that a client can poll the printer's capabilities from the printer and then knows how to print on it. The Printer Application as an emulator of an IPP printer contains the software to print incoming jobs on the printer(s) it supports, converting the data to the printer's native language, and it provides the info about the printer's capabilities to clients on request. The Printer Application even has a web administration interface, like an actual network printer.
+This has two major advantages: First, the ancient concept of PPD files coming from PostScript printers is discontinued. We were already hitting the limits of it a lot with modern printers. In addition, by coupling the CUPS system and the printer driver by an IP connection instead of dropping files into the CUPS system, both the CUPS system and the Printer Appplication can be in separate sandboxed packages (Snap, flatpak, ...).
+Also scanner drivers can be handled this way. Instead of dropping a SANE driver (a shared library) into the appropriate directory of the system, we emulate an IPP scanner, so we have a Scanner Application, and only one application is needed to fully support a multi-function device with print, scan, and fax capabilities.
+This is the format for printer and scanner drivers of the future, and to make it easy for hardware manufacturers to design drivers this way we want to have a tutorial with design guidelines for drivers. And this is the task of this project.
+The base for creating such Printer/Scanner Applications is [[https://github.com/michaelrsweet/pappl|PAPPL]], a library providing most functionality for this, but also [[https://github.com/OpenPrinting/cups-filters|cups-filters]] contains code to be used for Printer Applications. The concept is still under development, mainly in this year's [[https://wiki.linuxfoundation.org/gsoc/google-summer-code-2020-openprinting-projects|Google Summer of Code]], but on September 14, when the documentation writing period starts, the coding period of GSoC has already ended and this is when we need the tutorial.
+Mentors: Till Kamppeter, Project Leader OpenPrinting (till at linux dot com), Michael Sweet, author of CUPS/LPrint/PAPPL and original creator of Gutenprint (msweet at msweet dot org), Ira McDonald, OpenPrinting (blueroofmusic at gmail dot com), Smith Kennedy, HP (smith kennedy at hp dot com), Dheeraj Yadav (dhirajyadav135 at gmail dot com), Sahil Arora (sahilarora dot 535 at gmail dot com)
+License: Apache 2.0 + (L)GPL2 exception
 =====Documenting the Usage details for cups-filters=====
@@ Line 27: / Line 45: @@
 Mentors: Till Kamppeter, Project Leader OpenPrinting (till at linux dot com)
-License: MIT
+License: Apache 2.0 + (L)GPL2 exception
 =====Documenting the Automatic Queue Creation and printing Process for a IPP - Driverless printer in Linux=====
@@ Line 36: / Line 54: @@
 This could be made available both on the OpenPrinting web site and also in files coming with the software packages, like [[https://github.com/OpenPrinting/cups-filters|cups-filters]].
-Mentors: Aveek Basu, (aveek dot basu at gmail dot com)
+Mentors: Aveek Basu, (aveek dot basu at gmail dot com), Sahil Arora (sahilarora dot 535 at gmail dot com)
+Licens: MIT

Wiki

User Tools

Site Tools

Differences

Page Tools