[Printing-architecture] Status and future of the Common Printing Dialog (CPD)

Ira McDonald blueroofmusic at gmail.com
Sat Mar 26 19:31:23 UTC 2016

Hi Michael,

Many thanks to GTK and QT folks for responding.

My comments are informal.  CPD was focused on large-screen laptops and
desktops and explicitly ruled out UI for smartphones.  That focus drew some
criticism at the time.

Before his retirement from EPSON, Glen Petrie did some excellent work
on a lightweight Common Mobile Print Dialog that was scaleable across all
mobile devices, screens, and input methods and specifically optimized for
small-screen smartphones and written in pure C (for portability).  The
code, and presentations are archived on the IEEE-ISTO PWG FTP server at:


Till and I would both be delighted to see CMPD work resumed and completed.

- Ira

Ira McDonald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music / High North Inc
mailto: blueroofmusic at gmail.com
Winter  579 Park Place  Saline, MI  48176  734-944-0094
Summer  PO Box 221  Grand Marais, MI 49839  906-494-2434

On Sat, Mar 26, 2016 at 2:19 PM, Michael Weghorn <m.weghorn at posteo.de>

> Thank you for your quick replies.
> If neither GTK+ nor Qt are planning to support the CPD, this does not
> sound like it had a very bright future.
> Maybe it might be a good idea to add some note about the current status
> in the CPD section on the website so that other people looking at it can
> quickly get an idea of it.
> Are there possibly other plans/ideas to provide a more consistent user
> experience in printing dialogs across various applications?
> The current situation with so many different printing dialogs (e.g. GTK,
> KDE, LibreOffice, Java, several applications having their one one's,
> ...) that look differently and have a different set of features does not
> seem optimal to me.
> Also, from a developer's point of view it is non-optimal when adding a
> new feature or fixing a bug potentially requires making that change
> several times in totally different code bases (I only know LibreOffice,
> Qt 4 and GTK)...
> Best regards,
> Michael
> On 2016-03-26 18:01, John Layt wrote:
> > On 26 March 2016 at 15:42, Richard Hughes <hughsient at gmail.com> wrote:
> >> On 26 March 2016 at 15:03, Michael Weghorn <m.weghorn at posteo.de> wrote:
> >>> Could somebody possibly say something about the current status of the
> >>> Common Printing Dialog?
> >>
> >> Last time I spoke to the GTK maintainers and the GNOME Design team
> >> there was a total lack of support for the project.
> >>
> >> Richard
> >
> > While the usual Qt policy is to use the host platform facilities where
> > available, Qt has no interest in using CPD either, at least not in the
> > architecture proposed. There were too many implementation issues and
> > no funding for the required cross-platform architectural changes that
> > Qt would have required.
> >
> > John.
> > _______________________________________________
> > Printing-architecture mailing list
> > Printing-architecture at lists.linux-foundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/printing-architecture
> >
> _______________________________________________
> Printing-architecture mailing list
> Printing-architecture at lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/printing-architecture
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/printing-architecture/attachments/20160326/97c5b3b9/attachment-0001.html>

More information about the Printing-architecture mailing list