[QGIS-Developer] QgsQuick removal

[Matthias Kuhn]

Hi Peter,

Indeed the QgsQuick library is mostly an externalized library for input at
the moment and I can understand the reasons for coming forward with this
proposal.

One of the reasons for not picking it up completely in QField was that some
of the included components have been under heavy development on QField side
too, sometimes with app specific changes.

However there are some core parts which can be well mutualized and a
collaboration was envisioned on QField side too.
They are kept in a dedicated folder in the QField repository
https://github.com/opengisch/QField/tree/master/src/core/qgsquick

I think keeping these in place would be good, this way we can preserve a
nucleus of a generic library. If you are ok with that, we'll make sure to
integrate the latest changes from the QField repository soon.

Thank you
Matthias

On Wed, May 12, 2021 at 9:51 AM Peter Petrik <
peter.petrik at lutraconsulting.co.uk> wrote:

> Hi devs,
>
> I will be removing QgsQuick library related pieces from the qgis/QGIS
> repository if there are no strong objections.
>
> The reasons are:
> - the release cycle for QgsQuick is different than QGIS core, more based
> on the InputApp releases
> - QgsQuick is not used by other projects but InputApp despite being on
> master for few years (as far as I know)
> - In case we would like to use Qt QML in QGIS desktop, we will probably
> need different QML classes than for mobile devices (e.g. on mobile devices
> you do not edit form config, etc) anyways
> - QgsQuick library is not shipped with the regular QGIS packaging system,
> not build/tested in the CI mostly (e.g. the tests on master are coredumping
> ATM), so it doesn't really matured to the common QML library
> - There is an extra maintenance of the QgsQuick (pull requests in
> qgis/QGIS, CI setup, code maintenance, test runs) for the QGIS developers
> and to the QGIS infrastructure as such.
> - There is quite a maintenance cost of Lutra Team to backport the changes
> from Input back to qgis/QGIS, keep the code in sync, test and in general
> use a library+application split when not necessary.
>
> Therefore we do not see the reasons why to spend extra time on the
> community and us to maintain this bit. The code will be still present in
> the https://github.com/lutraconsulting/input open-source project, so in
> case other Qt/QGIS related mobile projects would like to build something on
> top of it, we would be happy to cooperate.
>
> Cheers,
> Peter
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20210513/286d67ac/attachment.html>