I have now released version 2.0b6 of cpdb-libs, with a lot of bug fixes,
especially of crashers, and with some changes which needed to apply to ease
sandboxed packaging (Snap, OCI containers, ...) of the backends.
This changes caused slight changes in the API, which could also cause slight
Hi all,
The support for Common Print Dialog Backends has been in the works for a while.
As of last year we are provisioning the SDK in our CI nodes:
https://codereview.qt-project.org/c/qt/qt5/+/471258
but the change on Qt is stuck a bit. Could someone with experience and
knowledge about the
I have added CPDB support to the print dialog, and opened a pull request
here: https://codereview.qt-project.org/c/qt/qtbase/+/437301. It would be
great if anyone is able to review it.
To build qt with CPDB support, make sure you have CPDB frontend library:
That’s awesome, nice work Gaurav!
- Tor Arne
On 26 Sep 2022, at 18:47, Gaurav Guleria wrote:
Yes, CPDB is just a different backend for the existing print dialog GUI. It's
merely a different way of enumerating printers and their features.
I have already prepared a simple CPDB plugin (still
Yes, CPDB is just a different backend for the existing print dialog GUI.
It's merely a different way of enumerating printers and their features.
I have already prepared a simple CPDB plugin (still requires a few
changes and additions) which can already respond to
I am willing to maintain the CPDB code I will add to the Qt print
dialogs for a while. Though I am currently not familiar with the time
commitment it will require on my end.
Also, do we currently have a maintainer for the print dialogs?
Regards,
Gaurav Guleria
On 9/26/22 20:57, Tor Arne
On 2022 Sep 26, at 16:54, Volker Hilsheimer
mailto:volker.hilshei...@qt.io>> wrote:
I think it will be easier to understand what abstraction we need once we have a
patch to look at that implements CPDB support. That we don’t have a QPA-level
abstraction for print dialogs in Qt shouldn’t block
> On 26 Sep 2022, at 17:19, Till Kamppeter wrote:
>
> But we must also take into account that Gaurav has not arbitrarily much time.
> His GSoC project is already in the extension. So he needs to know now how he
> can get CPDB support in quickly, especially without need to design a new GUI
>
But we must also take into account that Gaurav has not arbitrarily much
time. His GSoC project is already in the extension. So he needs to know
now how he can get CPDB support in quickly, especially without need to
design a new GUI and to create the code for all ins and outs of a print
dialog.
On 26 Sep 2022, at 16:54, Volker Hilsheimer
mailto:volker.hilshei...@qt.io>> wrote:
On 25 Sep 2022, at 20:58, Albert Astals Cid
mailto:aa...@kde.org>> wrote:
El dissabte, 24 de setembre de 2022, a les 12:45:00 (CEST), Tor Arne Vestbø va
escriure:
On 23 Sep 2022, at 19:21+02:00, Gaurav
> On 25 Sep 2022, at 20:58, Albert Astals Cid wrote:
>
> El dissabte, 24 de setembre de 2022, a les 12:45:00 (CEST), Tor Arne Vestbø
> va
> escriure:
>>> On 23 Sep 2022, at 19:21+02:00, Gaurav Guleria
>>> wrote:
>
>>> As far as I know, the CUPS is currently implemented in Qt at two
El dissabte, 24 de setembre de 2022, a les 12:45:00 (CEST), Tor Arne Vestbø va
escriure:
> > On 23 Sep 2022, at 19:21+02:00, Gaurav Guleria
> > wrote:
> > As far as I know, the CUPS is currently implemented in Qt at two different
> > places: src/plugins/printsupport/cups/ and directly within
> On 23 Sep 2022, at 19:21+02:00, Gaurav Guleria wrote:
>
> As far as I know, the CUPS is currently implemented in Qt at two different
> places: src/plugins/printsupport/cups/ and directly within the dialog
> src/printsupport/dialogs/qprintdialog_unix.cpp. By implementing CPDB support
> as
As far as I know, the CUPS is currently implemented in Qt at two
different places: src/plugins/printsupport/cups/ and directly within the
dialog src/printsupport/dialogs/qprintdialog_unix.cpp. By implementing
CPDB support as a plugin, does it mean that we create a similar
El dilluns, 19 de setembre de 2022, a les 14:59:46 (CEST), Shawn Rutledge va
escriure:
> On 2022 Sep 19, at 12:38, Till Kamppeter
> mailto:till.kamppe...@gmail.com>> wrote:
> On 16/09/2022 08:32, Shawn Rutledge wrote:
> But Qt has its own D-Bus implementation, so we tend to prefer using that,
>
> On 19 Sep 2022, at 18:21, Till Kamppeter wrote:
>
> On 19/09/2022 15:43, Tor Arne Vestbø wrote:
>>>
>>> First is to create a new Qt print backend, what, instead of communicating
>>> directly with CUPS, communicates with the CPDB backends. It is some kind of
>>> "middle end", on one end
On 19/09/2022 15:43, Tor Arne Vestbø wrote:
First is to create a new Qt print backend, what, instead of communicating directly with
CUPS, communicates with the CPDB backends. It is some kind of "middle end", on
one end being a Qt print backend and on the other end being a CPDB frontend.''
On 19/09/2022 14:59, Shawn Rutledge wrote:
A re-implementation of the frontend part of CPDB with Qt's D-Bus
implementation to overcome the need of two different libraries for
D-Bus access in the whole Qt print dialog would lead to a maintenance
overhead. Any change in the D-Bus interface in
> On 19 Sep 2022, at 00:51, Till Kamppeter wrote:
> We do not do any GUI design or change as part of our project. We only add a
> new method to obtain the available printers, their capabilities and options,
> and to send off print jobs to them.
That’s good news.
>
> First is to create a
On 2022 Sep 19, at 12:38, Till Kamppeter
mailto:till.kamppe...@gmail.com>> wrote:
On 16/09/2022 08:32, Shawn Rutledge wrote:
But Qt has its own D-Bus implementation, so we tend to prefer using that,
rather than using some external library that uses some other library that talks
to D-Bus.
On 16/09/2022 08:32, Shawn Rutledge wrote:
Along with Chris, I’m wondering why you think it should be a plugin.
Anyway it seems some misunderstandings are possible. Lars wrote "code
that uses the CPDB dialogs instead of our own implementations”… but are
there replacement GUI dialogs? The
On 16/09/2022 07:32, Lars Knoll wrote:
But the native print dialogs do currently all live inside Qt print support, so
I don’t see why we shouldn’t add one more.
Lars, note that we do not create a new print dialog here. We do not do
any GUI design or change as part of our project. We only
e done eventually.
From: Development
mailto:development-boun...@qt-project.org>>
on behalf of Ilya Fedin mailto:fedin-ilja2...@ya.ru>>
Sent: Friday, September 16, 2022 14:56
To: development@qt-project.org<mailto:development@qt-project.org>
mailto:development@qt-project.org>&
.
From: Development on behalf of Ilya Fedin
Sent: Friday, September 16, 2022 14:56
To: development@qt-project.org
Subject: Re: [Development] Adding CPD support to Qt print dialog
On Fri, 16 Sep 2022 06:32:38 +
Shawn Rutledge wrote:
> Another aspect tha
On Fri, 16 Sep 2022 06:32:38 +
Shawn Rutledge wrote:
> Another aspect that I haven’t kept up with very well is how
> containerized applications should do printing. We have “portal”
> support for file dialogs, for example, but is CPDB intended to work
> the same way regardless whether the
On 2022 Sep 16, at 00:20, Gaurav Guleria
mailto:gaurav.g...@gmail.com>> wrote:
Hello all,
I am Gaurav Guleria, a GSoC student, working with Till Kamppeter to add and
improve Common Print Dialog (CPD) support to existing print dialogs like GTK
and Qt. More about CPD can be read here:
> On 16 Sep 2022, at 03:36, Chris Adams wrote:
>
> Hi Gaurav,
>
> First, I want to make clear: I know nothing about printing at all,
> either in Qt or in general.
> But I did a quick archive search and found the following:
>
Hi Gaurav,
First, I want to make clear: I know nothing about printing at all,
either in Qt or in general.
But I did a quick archive search and found the following:
https://lists.qt-project.org/pipermail/development/2020-May/039584.html
On Fri, Sep 16, 2022 at 8:22 AM Gaurav Guleria wrote:
>
>
28 matches
Mail list logo
