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
cha
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 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.''
Th
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 the
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 web
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 add
