It's also worth noting that QtXml is very
slow, which is noticeable on project load/save.
Is it really the xml parsing which is slow? I would have expected that
xml parsing only is fast and the things QGIS is doing on project load
are slow (e.g. restoring connections, creating print composers, ...).
Did you do some profiling / testing related to xml parsing speed?
Regards,
Marco
On 04.12.2014 09:44, Nyall Dawson wrote:
On 4 December 2014 at 19:25, Jürgen E. <[email protected]> wrote:
Hi Matthias,
On Wed, 03. Dec 2014 at 16:46:11 +0100, Matthias Kuhn wrote:
I didn't look at it in detail and just based this recommendation on the
one from the QtXml documentation linked at the end of the original message.
Is there something in particular you think we will be missing? If so, it
might be good to start looking for alternative ways to go.
We could just keep using it and fork it if need be. Any idea why it was
discontinued?
This link [1] suggests that it hasn't been discontinued, it's just
unmaintained, and isn't scheduled for removal. That doesn't solve the
PyQt5 problem though... It's also worth noting that QtXml is very
slow, which is noticeable on project load/save.
Nyall
[1] https://bugreports.qt-project.org/browse/QTBUG-32926
_______________________________________________
Qgis-developer mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-developer
--
Dr. Marco Hugentobler
Sourcepole - Linux & Open Source Solutions
Weberstrasse 5, CH-8004 Zürich, Switzerland
[email protected] http://www.sourcepole.ch
Technical Advisor QGIS Project Steering Committee
_______________________________________________
Qgis-developer mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-developer
