gsoc:google-summer-code-2017-openprinting-projects
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
gsoc:google-summer-code-2017-openprinting-projects [2017/01/27 02:05] till [Flattening non-static content (like filled forms) in PDF files for printing (1 student)] |
gsoc:google-summer-code-2017-openprinting-projects [2017/01/27 14:08] (current) till [Common Print Dialog for desktop applications and mobile devices (up to 3-4 students)] |
||
|---|---|---|---|
| Line 19: | Line 19: | ||
| For the dialog itself there is already a design of how the user interface could look like. It was done by the design team of Canonical (the company behind Ubuntu) and can be found [[https://wiki.ubuntu.com/Printing|on the Ubuntu Wiki]]. The dialog should support three ways of obtaining available printers: Most importantly it should list the local CUPS queues and get printer properties and options through CUPS. It also should be able to pick IPP network printers from the network via Bonjour/DNS-SD and query the printer's properties via IPP (mainly for mobile devices to use IPP Everywhere and AirPrint printers). The third way is to connect to the user's Google account to list the Google Cloud Print printers which the user has registered. | For the dialog itself there is already a design of how the user interface could look like. It was done by the design team of Canonical (the company behind Ubuntu) and can be found [[https://wiki.ubuntu.com/Printing|on the Ubuntu Wiki]]. The dialog should support three ways of obtaining available printers: Most importantly it should list the local CUPS queues and get printer properties and options through CUPS. It also should be able to pick IPP network printers from the network via Bonjour/DNS-SD and query the printer's properties via IPP (mainly for mobile devices to use IPP Everywhere and AirPrint printers). The third way is to connect to the user's Google account to list the Google Cloud Print printers which the user has registered. | ||
| - | To allow for the print dialog being provided by the currently running desktop (Unity, GNOME, KDE, ...) or mobile environment while the different applications use different GUI toolkits (GTK, Qt, ...) the print dialog and the application should be implemented in different executables which communicate by D-Bus. An appropriate D-Bus interface got already [[:openprinting:cpdapi|designed earlier]]. Probably the designe can already be used as it is, perhaps it needs some slight modifications. | + | To allow for the print dialog being provided by the currently running desktop (Unity, GNOME, KDE, ...) or mobile environment while the different applications use different GUI toolkits (GTK, Qt, ...) the print dialog and the application should be implemented in different executables which communicate by D-Bus. An appropriate D-Bus interface got already [[:openprinting:cpdapi|designed earlier]]. Probably the design can already be used as it is, perhaps it needs some slight modifications. |
| - | The task for the student(s) is to implement the dialog with a major toolkit (GTK or Qt) or to add the D-Bus interface to call the Common Print Dialog to a major toolkit or an aimportant application. | + | The task for the student(s) is to implement the dialog with a major toolkit (GTK or Qt) or to add the D-Bus interface to call the Common Print Dialog to a major toolkit or an important application. |
| At OpenPrinting there has already been worked on a similar project earlier. See the resources [[:openprinting:commonprintingdialog|here]]. | At OpenPrinting there has already been worked on a similar project earlier. See the resources [[:openprinting:commonprintingdialog|here]]. | ||
gsoc/google-summer-code-2017-openprinting-projects.1485482716.txt.gz ยท Last modified: 2017/01/27 02:05 by till
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
