> On 21-Dec-2017, at 2:52 PM, Albert Astals Cid <albert.astals....@kdab.com>
> wrote:
>
> I see a big-ish problem that is that it uses QtQuick so it can't really go
> into qtbase where the current printing dialog lives, so if this was to be
> accepted the printing module would need to split off from qtbase (no idea if
> that is planned or not).
>
This has been one of our main concerns too. At the time of project planning, we
were thinking more about QML support because of the missing printing support
within QML. However, if it is not possible to split the dialog off qtbase, we
could probably redo the QML part and write the UI using QWidget instead but
that would be our last option.
> Looking at the code Advanced.qml seems to be collection of items that really
> don't do anything at all?
The CUPS backend API doesn’t support all of these options yet. So we just put
up dummy dropdown and we’ll add backend functions to them as soon as the API
supports it.
Thanks,
Rithvik
_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
