All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Weghorn <m.weghorn@posteo.de>
To: printing-architecture@lists.linux-foundation.org
Subject: Re: [Printing-architecture] Status and future of the Common Printing Dialog (CPD)
Date: Sat, 26 Mar 2016 19:19:10 +0100	[thread overview]
Message-ID: <56F6D29E.3090603@posteo.de> (raw)
In-Reply-To: <CAM1DM6nYKfkH0TvePysc5zu35WVrwZ3xO8EruQOw0RpFGgKe1Q@mail.gmail.com>

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@gmail.com> wrote:
>> On 26 March 2016 at 15:03, Michael Weghorn <m.weghorn@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@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/printing-architecture
> 

  reply	other threads:[~2016-03-26 18:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-26 15:03 [Printing-architecture] Status and future of the Common Printing Dialog (CPD) Michael Weghorn
2016-03-26 15:42 ` Richard Hughes
2016-03-26 17:01   ` John Layt
2016-03-26 18:19     ` Michael Weghorn [this message]
2016-03-27 16:04 ` peter sikking
2016-03-28 19:49   ` Michael Weghorn
2016-03-29  9:23   ` Richard Hughes
2016-03-29 11:36     ` peter sikking
2016-03-29 12:19       ` Richard Hughes
2016-03-29 13:31         ` Till Kamppeter
2016-03-29 18:41         ` peter sikking
  -- strict thread matches above, loose matches on Subject: below --
2016-03-26 19:31 Ira McDonald
2016-03-26 22:19 ` Michael Weghorn
2016-03-26 22:21 ` Richard Hughes
2016-03-26 22:59   ` Ira McDonald

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56F6D29E.3090603@posteo.de \
    --to=m.weghorn@posteo.de \
    --cc=printing-architecture@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.