Re: [Qgis-developer] Qt4->Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
Hi, On Wed, 07. Sep 2016 at 11:26:34 +0200, Jürgen E. Fischer wrote: > Nightlies still underway, they should popup in stretch, sid and xenial today. Dawn :) stretch/i386 failed for some reason, but the others should be available now. Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode pgpYuW4Y4BoHa.pgp Description: PGP signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4->Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
Thanks x100, Juergen. I'll see if I can get some tests done - very much appreciated. +1 for backporting, to fix a lot of broken plugins. - Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Qt4-Qt5-timeline-Qt4-s-status-and-Qt4-s-webkit-removal-in-Stretch-tp5203810p5284474.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4->Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
Hi Matthias, On Wed, 07. Sep 2016 at 11:40:14 +0200, Matthias Kuhn wrote: > Thanks Jürgen! > Should this be backported also to release-2_16? Sure, but I'd wait for feedback (or the lack of any ;)) about the nighlies first. Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode pgpE8NursK0Fw.pgp Description: PGP signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4->Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
Thanks Jürgen! Should this be backported also to release-2_16? Matthias On 09/07/2016 11:26 AM, Jürgen E. Fischer wrote: > Hi Tim, > > On Sun, 10. May 2015 at 14:46:25 +0200, Tim Sutton wrote: >> What about considering alternative packaging methods? > > I added internal python QtWebKit bindings in master_2 (as the C++ webkit as > still around). > > Nightlies still underway, they should popup in stretch, sid and xenial today. > > > Jürgen > > > > ___ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer > ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4->Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
On 09/07/2016 11:26 AM, Jürgen E. Fischer wrote: > I added internal python QtWebKit bindings in master_2 (as the C++ webkit as > still around). The WebKit support has so far only been removed from python-qt4 in Debian, but the C++ packages (from qtwebkit) will also been removed eventually. Most probably before the stretch freeze on January 5th 2017. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 signature.asc Description: OpenPGP digital signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4->Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
Hi Tim, On Sun, 10. May 2015 at 14:46:25 +0200, Tim Sutton wrote: > What about considering alternative packaging methods? I added internal python QtWebKit bindings in master_2 (as the C++ webkit as still around). Nightlies still underway, they should popup in stretch, sid and xenial today. Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode pgp9GgGjBXRqa.pgp Description: PGP signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4->Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
On 12/07/2015 07:42 PM, Sebastiaan Couwenberg wrote: > On 02-05-15 10:19, Luigi Pirelli wrote: >> http://perezmeyer.blogspot.com.es/2015/05/qt4s-status-and-qt4s-webkit-removal-in.html > > As reported in Debian Bug #784514 [0], the WebKit support will be > removed from python-qt4 in earlier 2015 (but not before January 7th, one > month from now). > > [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784514#43 It took longer than expected, because the Qt maintainers were waiting for QGIS to move away from its reliance on WebKit in Qt4. Because that wasn't going to happen before the WebKit support was actually no longer available, I asked the Qt maintainers to stop waiting for QGIS and go ahead and break it with the python-qt4 upload initially planned for earlier this year. QGIS now shows lovely stacktraces informing the user about the missing QtWebKit modules. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4->Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
While written by a gnome developer, this gives insights into the current state of QtWebkit. https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-security-updates/ As a reminder: Qt4->Qt5 transition and QtWebkit issues are only partially linked. Regards -- Matthias Kuhn OPENGIS.ch - https://www.opengis.ch Spatial • (Q)GIS • PostGIS • Open Source signature.asc Description: OpenPGP digital signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4->Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
On 10-05-15 14:44, Sebastiaan Couwenberg wrote: > On 05/10/2015 02:16 PM, Anita Graser wrote: >> On Sun, May 10, 2015 at 1:45 PM, Paolo Cavallini wrote: >>> Seems a rather serious issue. Shouldn't we reconsider our roadmap >>> accordingly? >>> >> >> I don't seem to be able to find any dates mentioned in the linked >> resources. When (date) will Debian remove Qt4? > > The Debian Qt maintainers didn't give definitive dates in their > announcement [1], but they mention that Qt upstream is about to release > the last Qt4 point release (4.8.7), Qt upstream also recommends keeping > Qt4 until 2017 which translates to the end of the jessie stable release. > > The next two years must be used to move away from Qt4 to Qt5. During > that time Qt4 components will be removed when they cannot be supported > anymore. The Qt4 Webkit component will be the first to go. Regarding its > removal the Qt maintainers said: > > " > Of course we still have a lot of KDE stuff using Qt4's webkit, so it > won't disappear "soon", but it will at some point. > " > > [1] https://lists.debian.org/debian-devel-announce/2015/05/msg1.html The severity of the "Qt4's WebKit removal" bugreport in Debian has been raised to serious (Release Critical), because a "new python-qt4 upload with removed QtWebKit module will happen shortly". QGIS will no longer build on Debian sid after this upload as long as it requires Qt4's WebKit. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4->Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
On 02-05-15 10:19, Luigi Pirelli wrote: > http://perezmeyer.blogspot.com.es/2015/05/qt4s-status-and-qt4s-webkit-removal-in.html As reported in Debian Bug #784514 [0], the WebKit support will be removed from python-qt4 in earlier 2015 (but not before January 7th, one month from now). [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784514#43 Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4-Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
Seems a rather serious issue. Shouldn't we reconsider our roadmap accordingly? All the best. Il 10 maggio 2015 11:25:23 CEST, Sebastiaan Couwenberg sebas...@xs4all.nl ha scritto: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 05/10/2015 10:51 AM, Matthias Kuhn wrote: Hi On 05/09/2015 03:28 PM, Paolo Cavallini wrote: Il 09/05/2015 12:38, Sebastiaan Couwenberg ha scritto: How feasible is switching to Python 3? I believe this would be a huge issue: most or all plugins will not work, both the internal and the external ones, so our qgis will be badly lame. Thanks for raising this point. There will probably be no PyQt4/Qt5 package but only a PyQt5/Qt5 package? If there's a PyQt4/Qt5 package the upgrade process should be rather painless. If there's none, all plugins will need an update anyway and IMO the two changes PyQt5 and Python 3 should be grouped. Sebastiaan, do you know anything about this package? I'm not involved in the Python or PyQt packaging, so I have no intimate knowledges of those packages. Both the python-qt4 [1] and pyqt5 [2] packages in Debian have the same people involved. They may be willing to provide a python-qt4 package built with qt5. [1] https://tracker.debian.org/pkg/python-qt4 [2] https://tracker.debian.org/pkg/pyqt5 The other issue is that there's a rather big dependency on QtWebkit currently. We are struggling already with that on Android. Alternatives * QtWebEngine is the future but only available starting from Qt 5.4. So this is not an option now. * QLabel/QML: Where it's only used for richtext, a QLabel can be used. Where there's javascript involved it may be worth investigating the use of QML. The planned removal of the Qt4 WebKit component in Debian is the primary reason to switch to Qt5. Sticking to the Qt5 Webkit until Qt 5.4 is widely available seems like the road of least resistance. Kind Regards, Bas - -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJVTyQDAAoJEGdQ8QrojUrxg6kP/Aj8sSsq6eOSG5EKQbbzG2YP xazhDxSbrPJGKql2LaPDOwMb5ChlkTQUi13SZi9Y3B6iUU0IQ11B8zvsTDz+qUC5 t3srte+XyJDCDky7gLhRWIikm92F3lusfyrk0t3MCDVdetvt15k3kEUH2M7Nt3jD t1FzhypFVbxLSR7S1a7oM+fy9wp3Z301yYwnpAj8OdhCPL9XM9BxHg2g88hydYMC L/4KdWO3i82HTUsAO1iG6CtY+oYc0a9EL0pelRtcV+icvDycgID1+As/PZrgA3sN 990HWsT4PUgeO2dISte5NtQcLzZw3GrKDiwU3VCU2Zaa2JZWYbKmbHtLWPQIgjMD Tf6hw9QJORIVP58m1I9loF+fT0emBp5fe6FcoIiSAKfLNEVYNJRRMz7y/4Nm4T9p ALnwgSvJQdNpPx5KluPOg4QecCCkmWj8xQ7IpuFVcpxLMrINGKRokzamL5mzHFFW fSkO/zE6lYWeXX8SiT/suavpWi1hQOxqXGRLy0KBeNRSqGywVDQAqxzt3+LWKwZs 8cAv9ySdQqmx2GLOUIzkl8g/zfwudI9WN1/n/oLl2GZ5GIGS9yZgka+N1VrFvAb3 gcd3hQxyMxnYBvJ98eLEUlHuNgp9Y74QX4Ap6i8ss53WtTQG+dcBFjrJDFvaU2GO QzV9i13DJiKUdDj6/Lx8 =3Ioh -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- http://faunalia.eu/ Sent from mobile, sorry for being short___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4-Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
That's a pretty serious drawback. If there's no way around this, we need to make sure composer labels are improved (and hopefully plug in the canvas label drawing engine to the composer labels). M On Sun, May 10, 2015 at 4:19 PM, Nyall Dawson nyall.daw...@gmail.com wrote: On 10 May 2015 at 18:51, Matthias Kuhn matth...@opengis.ch wrote: The other issue is that there's a rather big dependency on QtWebkit currently. We are struggling already with that on Android. Alternatives * QtWebEngine is the future but only available starting from Qt 5.4. So this is not an option now. * QLabel/QML: Where it's only used for richtext, a QLabel can be used. Where there's javascript involved it may be worth investigating the use of QML. This change also affects composer in a big way, in that it's no longer possible to have a HTML composer item. QtWebEngine has no support for rendering using a QPainter, and without this ability we lose the possibility of vector rendering of HTML content. Hopefully this is addressed before QWebPage is removed from Qt5, but I honestly doubt it will be. I'm not sure what our alternatives are. We could fall back to using QLabel and it's limited subset of HTML, or ..? In the meantime, I'd suggest not relying too heavily on HTML content in compositions! Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4-Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
On Sun, May 10, 2015 at 1:45 PM, Paolo Cavallini cavall...@faunalia.it wrote: Seems a rather serious issue. Shouldn't we reconsider our roadmap accordingly? I don't seem to be able to find any dates mentioned in the linked resources. When (date) will Debian remove Qt4? This basically warms up our discussion on http://lists.osgeo.org/pipermail/qgis-psc/2015-April/002974.html Best wishes, Anita All the best. Il 10 maggio 2015 11:25:23 CEST, Sebastiaan Couwenberg sebas...@xs4all.nl ha scritto: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 05/10/2015 10:51 AM, Matthias Kuhn wrote: Hi On 05/09/2015 03:28 PM, Paolo Cavallini wrote: Il 09/05/2015 12:38, Sebastiaan Couwenberg ha scritto: How feasible is switching to Python 3? I believe this would be a huge issue: most or all plugins will not work, both the internal and the external ones, so our qgis will be badly lame. Thanks for raising this point. There will probably be no PyQt4/Qt5 package but only a PyQt5/Qt5 package? If there's a PyQt4/Qt5 package the upgrade process should be rather painless. If there's none, all plugins will need an update anyway and IMO the two changes PyQt5 and Python 3 should be grouped. Sebastiaan, do you know anything about this package? I'm not involved in the Python or PyQt packaging, so I have no intimate knowledges of those packages. Both the python-qt4 [1] and pyqt5 [2] packages in Debian have the same people involved. They may be willing to provide a python-qt4 package built with qt5. [1] https://tracker.debian.org/pkg/python-qt4 [2] https://tracker.debian.org/pkg/pyqt5 The other issue is that there's a rather big dependency on QtWebkit currently. We are struggling already with that on Android. Alternatives * QtWebEngine is the future but only available starting from Qt 5.4. So this is not an option now. * QLabel/QML: Where it's only used for richtext, a QLabel can be used. Where there's javascript involved it may be worth investigating the use of QML. The planned removal of the Qt4 WebKit component in Debian is the primary reason to switch to Qt5. Sticking to the Qt5 Webkit until Qt 5.4 is widely available seems like the road of least resistance. Kind Regards, Bas - -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJVTyQDAAoJEGdQ8QrojUrxg6kP/Aj8sSsq6eOSG5EKQbbzG2YP xazhDxSbrPJGKql2LaPDOwMb5ChlkTQUi13SZi9Y3B6iUU0IQ11B8zvsTDz+qUC5 t3srte+XyJDCDky7gLhRWIikm92F3lusfyrk0t3MCDVdetvt15k3kEUH2M7Nt3jD t1FzhypFVbxLSR7S1a7oM+fy9wp3Z301yYwnpAj8OdhCPL9XM9BxHg2g88hydYMC L/4KdWO3i82HTUsAO1iG6CtY+oYc0a9EL0pelRtcV+icvDycgID1+As/PZrgA3sN 990HWsT4PUgeO2dISte5NtQcLzZw3GrKDiwU3VCU2Zaa2JZWYbKmbHtLWPQIgjMD Tf6hw9QJORIVP58m1I9loF+fT0emBp5fe6FcoIiSAKfLNEVYNJRRMz7y/4Nm4T9p ALnwgSvJQdNpPx5KluPOg4QecCCkmWj8xQ7IpuFVcpxLMrINGKRokzamL5mzHFFW fSkO/zE6lYWeXX8SiT/suavpWi1hQOxqXGRLy0KBeNRSqGywVDQAqxzt3+LWKwZs 8cAv9ySdQqmx2GLOUIzkl8g/zfwudI9WN1/n/oLl2GZ5GIGS9yZgka+N1VrFvAb3 gcd3hQxyMxnYBvJ98eLEUlHuNgp9Y74QX4Ap6i8ss53WtTQG+dcBFjrJDFvaU2GO QzV9i13DJiKUdDj6/Lx8 =3Ioh -END PGP SIGNATURE- -- Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- http://faunalia.eu/ Sent from mobile, sorry for being short ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4-Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
On 05/10/2015 02:16 PM, Anita Graser wrote: On Sun, May 10, 2015 at 1:45 PM, Paolo Cavallini wrote: Seems a rather serious issue. Shouldn't we reconsider our roadmap accordingly? I don't seem to be able to find any dates mentioned in the linked resources. When (date) will Debian remove Qt4? The Debian Qt maintainers didn't give definitive dates in their announcement [1], but they mention that Qt upstream is about to release the last Qt4 point release (4.8.7), Qt upstream also recommends keeping Qt4 until 2017 which translates to the end of the jessie stable release. The next two years must be used to move away from Qt4 to Qt5. During that time Qt4 components will be removed when they cannot be supported anymore. The Qt4 Webkit component will be the first to go. Regarding its removal the Qt maintainers said: Of course we still have a lot of KDE stuff using Qt4's webkit, so it won't disappear soon, but it will at some point. [1] https://lists.debian.org/debian-devel-announce/2015/05/msg1.html This basically warms up our discussion on http://lists.osgeo.org/pipermail/qgis-psc/2015-April/002974.html Switching to Qt5 and Python 3 for QGIS 3.0 sounds good. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4-Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
Hi What about considering alternative packaging methods? For example making an equivalent of the windows standalone package for Linux. A long time ago I used to build QGIS and all its dependencies into a directory (e.g. /opt/qgis2.8) and then use a launcher script to update the library paths to each in that dir with priority over the system libs. The result is something pretty portable and self contained. There are free NSIS like tools for Linux and we would no longer be reliant on which libraries are available on the host system. More recently we achieved similar results with Docker (e.g. https://registry.hub.docker.com/u/kartoza/qgis-desktop/ https://registry.hub.docker.com/u/kartoza/qgis-desktop/) I appreciate that there are many good reasons to use shared libraries on an operating system, but there are also many good reasons not to: * cross distribution binaries * ability to install multiple concurrent versions of QGIS and know they will work (e.g. we recently had pain when software we wrote depended on QGIS 2.2 but was no longer installable from debian archives) * we could provide all the extra goodies that give you a good experience and that are hard to get configured on each distort (grass, saga, OTB, goal with lots of drivers) IIRC gdal used to follow this route in the past, and other non FOSS packages like Google Earth etc do too. In our PSC thread referred to by Anita below, it became apparent that a lot of people will have a hard time if we jump to Qt5 Python 3 as a requirement, so we should look for approaches (such, as but not necessarily, the one above) that provide use some level of independence from the underlying OS and its provisioned packages. Also much as I love debian, lets keep some perspective, it is probably a very small part of our established user base (the bulk being on Windows) and it does’t make sense to me to make the majority of users unhappy to keep the minority happy. In our road map for migration from QGIS 2.x to 3.x we should definitely plan on supporting 2.x for an extended period in order to allow users and developers to migrate their work to the new platform. so any approach which implies a hard cut off of 2.x support would be suboptimal in my opinion. Last thought: I wonder if debian plans on supporting the new snappy package format from Ubuntu which I believe will be used for desktop packages too from 15.10 (in addition to deb packages). Regards Tim On 10 May 2015, at 14:16, Anita Graser anitagra...@gmx.at wrote: On Sun, May 10, 2015 at 1:45 PM, Paolo Cavallini cavall...@faunalia.it mailto:cavall...@faunalia.it wrote: Seems a rather serious issue. Shouldn't we reconsider our roadmap accordingly? I don't seem to be able to find any dates mentioned in the linked resources. When (date) will Debian remove Qt4? This basically warms up our discussion on http://lists.osgeo.org/pipermail/qgis-psc/2015-April/002974.html http://lists.osgeo.org/pipermail/qgis-psc/2015-April/002974.html Best wishes, Anita All the best. Il 10 maggio 2015 11:25:23 CEST, Sebastiaan Couwenberg sebas...@xs4all.nl mailto:sebas...@xs4all.nl ha scritto: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 05/10/2015 10:51 AM, Matthias Kuhn wrote: Hi On 05/09/2015 03:28 PM, Paolo Cavallini wrote: Il 09/05/2015 12:38, Sebastiaan Couwenberg ha scritto: How feasible is switching to Python 3? I believe this would be a huge issue: most or all plugins will not work, both the internal and the external ones, so our qgis will be badly lame. Thanks for raising this point. There will probably be no PyQt4/Qt5 package but only a PyQt5/Qt5 package? If there's a PyQt4/Qt5 package the upgrade process should be rather painless. If there's none, all plugins will need an update anyway and IMO the two changes PyQt5 and Python 3 should be grouped. Sebastiaan, do you know anything about this package? I'm not involved in the Python or PyQt packaging, so I have no intimate knowledges of those packages. Both the python-qt4 [1] and pyqt5 [2] packages in Debian have the same people involved. They may be willing to provide a python-qt4 package built with qt5. [1] https://tracker.debian.org/pkg/python-qt4 https://tracker.debian.org/pkg/python-qt4 [2] https://tracker.debian.org/pkg/pyqt5 https://tracker.debian.org/pkg/pyqt5 The other issue is that there's a rather big dependency on QtWebkit currently. We are struggling already with that on Android. Alternatives * QtWebEngine is the future but only available starting from Qt 5.4. So this is not an option now. * QLabel/QML: Where it's only used for richtext, a QLabel can be used. Where there's javascript involved it may be worth investigating the use of QML. The planned removal of the Qt4 WebKit component in Debian is the primary reason to switch to Qt5. Sticking to the Qt5 Webkit until Qt 5.4 is widely available seems like
Re: [Qgis-developer] Qt4-Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
On 10 May 2015, at 14:46, Tim Sutton t...@kartoza.com wrote: Hi What about considering alternative packaging methods? For example making an equivalent of the windows standalone package for Linux. A long time ago I used to build QGIS and all its dependencies into a directory (e.g. /opt/qgis2.8) and then use a launcher script to update the library paths to each in that dir with priority over the system libs. The result is something pretty portable and self contained. There are free NSIS like tools for Linux and we would no longer be reliant on which libraries are available on the host system. More recently we achieved similar results with Docker (e.g. https://registry.hub.docker.com/u/kartoza/qgis-desktop/ https://registry.hub.docker.com/u/kartoza/qgis-desktop/) I appreciate that there are many good reasons to use shared libraries on an operating system, but there are also many good reasons not to: * cross distribution binaries * ability to install multiple concurrent versions of QGIS and know they will work (e.g. we recently had pain when software we wrote depended on QGIS 2.2 but was no longer installable from debian archives) * we could provide all the extra goodies that give you a good experience and that are hard to get configured on each distort (grass, saga, OTB, goal with lots of drivers) IIRC gdal used to follow this route in the past, and other non FOSS packages like Google Earth etc do too. In our PSC thread referred to by Anita below, it became apparent that a lot of people will have a hard time if we jump to Qt5 Python 3 as a requirement, so we should look for approaches (such, as but not necessarily, the one above) that provide use some level of independence from the underlying OS and its provisioned packages. Also much as I love debian, lets keep some perspective, it is probably a very small part of our established user base (the bulk being on Windows) and it does’t make sense to me to make the majority of users unhappy to keep the minority happy. In our road map for migration from QGIS 2.x to 3.x we should definitely plan on supporting 2.x for an extended period in order to allow users and developers to migrate their work to the new platform. so any approach which implies a hard cut off of 2.x support would be suboptimal in my opinion. My apologies I missed the part about a 2 year transition period from Sebastiaan - which probably negates part of my message above. Regards Tim Last thought: I wonder if debian plans on supporting the new snappy package format from Ubuntu which I believe will be used for desktop packages too from 15.10 (in addition to deb packages). Regards Tim On 10 May 2015, at 14:16, Anita Graser anitagra...@gmx.at mailto:anitagra...@gmx.at wrote: On Sun, May 10, 2015 at 1:45 PM, Paolo Cavallini cavall...@faunalia.it mailto:cavall...@faunalia.it wrote: Seems a rather serious issue. Shouldn't we reconsider our roadmap accordingly? I don't seem to be able to find any dates mentioned in the linked resources. When (date) will Debian remove Qt4? This basically warms up our discussion on http://lists.osgeo.org/pipermail/qgis-psc/2015-April/002974.html http://lists.osgeo.org/pipermail/qgis-psc/2015-April/002974.html Best wishes, Anita All the best. Il 10 maggio 2015 11:25:23 CEST, Sebastiaan Couwenberg sebas...@xs4all.nl mailto:sebas...@xs4all.nl ha scritto: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 05/10/2015 10:51 AM, Matthias Kuhn wrote: Hi On 05/09/2015 03:28 PM, Paolo Cavallini wrote: Il 09/05/2015 12:38, Sebastiaan Couwenberg ha scritto: How feasible is switching to Python 3? I believe this would be a huge issue: most or all plugins will not work, both the internal and the external ones, so our qgis will be badly lame. Thanks for raising this point. There will probably be no PyQt4/Qt5 package but only a PyQt5/Qt5 package? If there's a PyQt4/Qt5 package the upgrade process should be rather painless. If there's none, all plugins will need an update anyway and IMO the two changes PyQt5 and Python 3 should be grouped. Sebastiaan, do you know anything about this package? I'm not involved in the Python or PyQt packaging, so I have no intimate knowledges of those packages. Both the python-qt4 [1] and pyqt5 [2] packages in Debian have the same people involved. They may be willing to provide a python-qt4 package built with qt5. [1] https://tracker.debian.org/pkg/python-qt4 https://tracker.debian.org/pkg/python-qt4 [2] https://tracker.debian.org/pkg/pyqt5 https://tracker.debian.org/pkg/pyqt5 The other issue is that there's a rather big dependency on QtWebkit currently. We are struggling already with that on Android. Alternatives * QtWebEngine is the future but only available starting from Qt 5.4. So this is not an option now. * QLabel/QML: Where it's only
Re: [Qgis-developer] Qt4-Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
Hi Tim, On Sun, 10. May 2015 at 14:48:14 +0200, Tim Sutton wrote: My apologies I missed the part about a 2 year transition period from Sebastiaan - which probably negates part of my message above. Apparently a lot of people seem to miss that. We might loose unstable support at some point over the next two years. But when that happens, we can adapt to what's there then. And I guess we'll have a much clearer picture of that will require then. If debian's timeframe was like ours, we would be in trouble - 2.8 can't be maintained w/o Qt4, Python2 and PyQt4. But when stretch is released, support for 2.8 is long gone. So I don't really see the urgency about this. I would rather like to know what it actually takes to support Python3 and PyQt5. Did anyone try yet? See also: http://lists.osgeo.org/pipermail/qgis-psc/2015-April/003004.html Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode signature.asc Description: Digital signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4-Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
On 10 May 2015 at 18:51, Matthias Kuhn matth...@opengis.ch wrote: The other issue is that there's a rather big dependency on QtWebkit currently. We are struggling already with that on Android. Alternatives * QtWebEngine is the future but only available starting from Qt 5.4. So this is not an option now. * QLabel/QML: Where it's only used for richtext, a QLabel can be used. Where there's javascript involved it may be worth investigating the use of QML. This change also affects composer in a big way, in that it's no longer possible to have a HTML composer item. QtWebEngine has no support for rendering using a QPainter, and without this ability we lose the possibility of vector rendering of HTML content. Hopefully this is addressed before QWebPage is removed from Qt5, but I honestly doubt it will be. I'm not sure what our alternatives are. We could fall back to using QLabel and it's limited subset of HTML, or ..? In the meantime, I'd suggest not relying too heavily on HTML content in compositions! Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4-Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
Hi On 05/09/2015 03:28 PM, Paolo Cavallini wrote: Il 09/05/2015 12:38, Sebastiaan Couwenberg ha scritto: How feasible is switching to Python 3? I believe this would be a huge issue: most or all plugins will not work, both the internal and the external ones, so our qgis will be badly lame. Thanks for raising this point. There will probably be no PyQt4/Qt5 package but only a PyQt5/Qt5 package? If there's a PyQt4/Qt5 package the upgrade process should be rather painless. If there's none, all plugins will need an update anyway and IMO the two changes PyQt5 and Python 3 should be grouped. Sebastiaan, do you know anything about this package? The other issue is that there's a rather big dependency on QtWebkit currently. We are struggling already with that on Android. Alternatives * QtWebEngine is the future but only available starting from Qt 5.4. So this is not an option now. * QLabel/QML: Where it's only used for richtext, a QLabel can be used. Where there's javascript involved it may be worth investigating the use of QML. Regards, Matthias signature.asc Description: OpenPGP digital signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4-Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 05/10/2015 10:51 AM, Matthias Kuhn wrote: Hi On 05/09/2015 03:28 PM, Paolo Cavallini wrote: Il 09/05/2015 12:38, Sebastiaan Couwenberg ha scritto: How feasible is switching to Python 3? I believe this would be a huge issue: most or all plugins will not work, both the internal and the external ones, so our qgis will be badly lame. Thanks for raising this point. There will probably be no PyQt4/Qt5 package but only a PyQt5/Qt5 package? If there's a PyQt4/Qt5 package the upgrade process should be rather painless. If there's none, all plugins will need an update anyway and IMO the two changes PyQt5 and Python 3 should be grouped. Sebastiaan, do you know anything about this package? I'm not involved in the Python or PyQt packaging, so I have no intimate knowledges of those packages. Both the python-qt4 [1] and pyqt5 [2] packages in Debian have the same people involved. They may be willing to provide a python-qt4 package built with qt5. [1] https://tracker.debian.org/pkg/python-qt4 [2] https://tracker.debian.org/pkg/pyqt5 The other issue is that there's a rather big dependency on QtWebkit currently. We are struggling already with that on Android. Alternatives * QtWebEngine is the future but only available starting from Qt 5.4. So this is not an option now. * QLabel/QML: Where it's only used for richtext, a QLabel can be used. Where there's javascript involved it may be worth investigating the use of QML. The planned removal of the Qt4 WebKit component in Debian is the primary reason to switch to Qt5. Sticking to the Qt5 Webkit until Qt 5.4 is widely available seems like the road of least resistance. Kind Regards, Bas - -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJVTyQDAAoJEGdQ8QrojUrxg6kP/Aj8sSsq6eOSG5EKQbbzG2YP xazhDxSbrPJGKql2LaPDOwMb5ChlkTQUi13SZi9Y3B6iUU0IQ11B8zvsTDz+qUC5 t3srte+XyJDCDky7gLhRWIikm92F3lusfyrk0t3MCDVdetvt15k3kEUH2M7Nt3jD t1FzhypFVbxLSR7S1a7oM+fy9wp3Z301yYwnpAj8OdhCPL9XM9BxHg2g88hydYMC L/4KdWO3i82HTUsAO1iG6CtY+oYc0a9EL0pelRtcV+icvDycgID1+As/PZrgA3sN 990HWsT4PUgeO2dISte5NtQcLzZw3GrKDiwU3VCU2Zaa2JZWYbKmbHtLWPQIgjMD Tf6hw9QJORIVP58m1I9loF+fT0emBp5fe6FcoIiSAKfLNEVYNJRRMz7y/4Nm4T9p ALnwgSvJQdNpPx5KluPOg4QecCCkmWj8xQ7IpuFVcpxLMrINGKRokzamL5mzHFFW fSkO/zE6lYWeXX8SiT/suavpWi1hQOxqXGRLy0KBeNRSqGywVDQAqxzt3+LWKwZs 8cAv9ySdQqmx2GLOUIzkl8g/zfwudI9WN1/n/oLl2GZ5GIGS9yZgka+N1VrFvAb3 gcd3hQxyMxnYBvJ98eLEUlHuNgp9Y74QX4Ap6i8ss53WtTQG+dcBFjrJDFvaU2GO QzV9i13DJiKUdDj6/Lx8 =3Ioh -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4-Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 05/10/2015 03:13 PM, Jürgen E. Fischer wrote: I would rather like to know what it actually takes to support Python3 and PyQt5. Did anyone try yet? My trials ended with missing dependencies. The changes for Qt5 are in the Debian GIS git repository: http://anonscm.debian.org/cgit/pkg-grass/qgis.git/log/?h=qt5 Kind Regards, Bas - -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJVT2BMAAoJEGdQ8QrojUrxt8kQAMbb757jgEVnFACWJ8NMkfe7 z1c/bQPYb4XeVZ8UfHIo8U4pwJhl477zBuBiDzOYMRDorr/VuzueCI1V/348P7EG rM/6I53L0kUr0x2IyYfqFkdvtjIxTYTdvPN+MbmEWxGbV1HRP1noI4vJxmuU/Xr9 k1XqTJglqxY9gs5P6VYL0N0rl5Kdt3t7YtuC7dWBkQwxGT4KQypdDMiIkGlO2ifA vX8EIeVf8Qv3kyLA5aHp+4hs2cbXxWk5X5FQO6wlcs4crUD/Hlx2kt3q7vGDSaf6 IHuWM+/WDpLv+sVUAUcILDisVeTywO9ihCmhTRqVOqGxBfDCBOCHtepSZ4kvTERM 70uhgSROPZMapu1EsPr17LHrz5PE/wStxOaV9tpD+Kl0DYUt7fB8frPkvzw+hCHV PhQlBj1sBC7Lf1mJcJYLIymqRMSUYRnjFeEt4HQ0HQrlLO0MICHZZidyRuhavPVE 4tYjeJonNVOgYgukLvTFfeq2C5HV1Ec0LlAq8j37OfHtokgcVk9DRMpsQRy6C+Al colLcyhwRAufCTkOt2eesIvwYoEcjIaDdaoABhBRN4/3GDhW7sufuQS5ICiZ//9u M9cjHzNX1b2v1GBg+vtlaoex3Pt4dpVN831Gp4t6H2UZ1ZAuzpE4FbhyP4pG9L1G 9qmAO5Rqlki1gbi4nKaX =cCbc -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4-Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 05/10/2015 03:13 PM, Jürgen E. Fischer wrote: On Sun, 10. May 2015 at 14:48:14 +0200, Tim Sutton wrote: My apologies I missed the part about a 2 year transition period from Sebastiaan - which probably negates part of my message above. Apparently a lot of people seem to miss that. We might loose unstable support at some point over the next two years. But when that happens, we can adapt to what's there then. And I guess we'll have a much clearer picture of that will require then. If debian's timeframe was like ours, we would be in trouble - 2.8 can't be maintained w/o Qt4, Python2 and PyQt4. But when stretch is released, support for 2.8 is long gone. So I don't really see the urgency about this. There is indeed no urgency yet. Since Debian has just released the jessie stable release we're now at the point where we start working on goals for stretch. These include moving away from Qt4 and Python 2. The qgis package in the Debian testing/unstable (from which Ubuntu syncs) will most likely stick to the LTRs from now on, and skip the non-LTR releases in between. Users in need of the latest non-LTR can still get it from QGIS repo. I would rather like to know what it actually takes to support Python3 and PyQt5. Did anyone try yet? See also: http://lists.osgeo.org/pipermail/qgis-psc/2015-April/003004.html Improving support for Python 3 and Qt5 are worthly goals for 3.0, switching to those by default where supported seems ideal for the next LTR or the one after. Because of the wide variety of platforms supported by QGIS both Python 2/3 and Qt4/5 will need to be maintained alongside for some time. Kind Regards, Bas - -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJVT1+YAAoJEGdQ8QrojUrxlOwQALDPWS9bqE8kaKO9cT3l2yFC 9WsLYtBRbn/aOiDEYc5zYHRPcYmQdDGGmeM44T2luxMeLgxAP7XYAhdZ+rK921mZ eYk8oenk7NyunUGKXbCEf8oiZSSew1GK/7cyfaIu3fiBS71kHbBYe4dFlF1AVBBi FfX70kArItJnamn7YqlV59XgmiH3CeRxGT3jlxQ4wAelxW6vAoZPgagU1+OgGUuV VyUWyPCwMPHs2LSVt486jYtf1a7MQliYnl1q2KSV/V2t0vhIBO1Khb9FQnFkjLSA XsFTvI6zlXndHuqcssqFsgSn3DcIsA1spfi7oC45NgI5mKvFcJ8m9Hr/JRCAZ5br f1RSMGpNhJcJMnm4zhUpjnPJRXprc461gD1yX1xgoC2dR2VRp/RvgZP0uqRTChSI K1qqrF3Ba5EPfgdTFrKgAVowSaIF9TKFsCTl7/SrjcRTZMzjscrBLjlHaXLPpY1A Kb4WDC+U0af3Mv1Vjjrrm440EUOo5decjgx7lEHMBdk8hXmCT7jytwZZDOH/83Pj Ji6aC036nlBKEo273Qg3E1jE1jRzp0vv6EUgzioLaW1USSJQNeNryTmcgjHVNeFZ 0GbSCqNh9BqqIn+/7endQzNIyiWSmzulJvKFPyufTjKk6GQg77XlQhuiEwLjphJZ AjCAr4MM6+341qhuy8/q =XQ2w -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4-Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
On Sun, May 10, 2015 at 3:39 PM, Sebastiaan Couwenberg sebas...@xs4all.nl wrote: On 05/10/2015 03:13 PM, Jürgen E. Fischer wrote: 2.8 can't be maintained w/o Qt4, Python2 and PyQt4. But when stretch is released, support for 2.8 is long gone. So I don't really see the urgency about this. There is indeed no urgency yet. Since Debian has just released the jessie stable release http://lists.osgeo.org/mailman/listinfo/qgis-developer Good, great that's settled! I think we should start educating (plugin) devs and power users that a switch to 3.0 will be necessary within a time frame of approx. 2 years (Please correct me if I misunderstood) so they can take this information into account when planning development. If you agree, I can write a short blog post as a first step. Best wishes, Anita ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4-Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
On 05/10/2015 05:02 PM, Anita Graser wrote: On Sun, May 10, 2015 at 3:39 PM, Sebastiaan Couwenberg sebas...@xs4all.nl wrote: On 05/10/2015 03:13 PM, Jürgen E. Fischer wrote: 2.8 can't be maintained w/o Qt4, Python2 and PyQt4. But when stretch is released, support for 2.8 is long gone. So I don't really see the urgency about this. There is indeed no urgency yet. Since Debian has just released the jessie stable release http://lists.osgeo.org/mailman/listinfo/qgis-developer Good, great that's settled! I think we should start educating (plugin) devs and power users that a switch to 3.0 will be necessary within a time frame of approx. 2 years (Please correct me if I misunderstood) so they can take this information into account when planning development. If you agree, I can write a short blog post as a first step. The time frame for the switch from Qt4 to Qt5 is the next two years, because in 2017 Qt upstream ends support. The time frame for the switch from Python 2 to Python 3 in the next 4-5 years (two Debian release cycles). The next stable release (stretch) will still have Python 2, the removal is planned for the release after that (buster). Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4-Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
On mobile devices we are already locked in a situation without QtWebkit (Partiallly due to vendor policies I believe). So I would very much enjoy to see the usage of it being kept to as little as possible. For those interested in the current state, that's what's required to compile QGIS 2.8 without webkit: https://github.com/m-kuhn/QGIS/commit/5a6168ea0f3f76c6a9809a5236943b3871096ec2 It's quite tedious to keep this patch up-to-date with master :-) Best Matthias On 05/10/2015 11:19 AM, Nyall Dawson wrote: On 10 May 2015 at 18:51, Matthias Kuhn matth...@opengis.ch wrote: The other issue is that there's a rather big dependency on QtWebkit currently. We are struggling already with that on Android. Alternatives * QtWebEngine is the future but only available starting from Qt 5.4. So this is not an option now. * QLabel/QML: Where it's only used for richtext, a QLabel can be used. Where there's javascript involved it may be worth investigating the use of QML. This change also affects composer in a big way, in that it's no longer possible to have a HTML composer item. QtWebEngine has no support for rendering using a QPainter, and without this ability we lose the possibility of vector rendering of HTML content. Hopefully this is addressed before QWebPage is removed from Qt5, but I honestly doubt it will be. I'm not sure what our alternatives are. We could fall back to using QLabel and it's limited subset of HTML, or ..? In the meantime, I'd suggest not relying too heavily on HTML content in compositions! Nyall signature.asc Description: OpenPGP digital signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4-Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
On 05/02/2015 10:19 AM, Luigi Pirelli wrote: basing of these info, timeline for transition is imposed by debian distribution http://perezmeyer.blogspot.com.es/2015/05/qt4s-status-and-qt4s-webkit-removal-in.html Triggered by this announcement, a recent bugreport about the Qt4WebKit removal [1], and the discussion on this list, I've investigated switching the qgis Debian package to Qt5. In Debian there are at least two missing dependencies before the qgis package can be switched to Qt5: python-qscintilla2 from the qscintilla2 source package, and libqwt-dev from the qwt source package. qwt is currently at version 6.0.0, which is not intended for Qt5 according to upstream, for Qt5 Qwt = 6.1 should be used. There is a bugreport requesting an update to Qwt 6.1 from 2013 [2]. Fortunately Ubuntu already has qwt 6.1.1 [3]. This packaging can be merged back into Debian, Lisandro Damián Nicanor Pérez Meyer said he might take a look at that. qscintilla2 only provides Python 3 bindings for Qt5, there doesn't seem to be a Qt5 equivalent for python-qscintilla2. So we may need to switch QGIS to Python 3 too. How feasible is switching to Python 3? The Python maintainers in Debian strive to move away from Python 2 in the next two development cycles (for stretch buster) as announced [4] earlier. The qgis package will need to switch in that time frame too. [1] https://bugs.debian.org/784514 [2] https://bugs.debian.org/733153 [3] https://launchpad.net/ubuntu/+source/qwt [4] https://lists.debian.org/debian-devel-announce/2015/04/msg5.html Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4-Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
Il 09/05/2015 12:38, Sebastiaan Couwenberg ha scritto: How feasible is switching to Python 3? I believe this would be a huge issue: most or all plugins will not work, both the internal and the external ones, so our qgis will be badly lame. Thanks for raising this point. -- Paolo Cavallini - www.faunalia.eu QGIS PostGIS courses: http://www.faunalia.eu/training.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt4-Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch
tank you for this analysis regards, Luigi Pirelli ** * LinkedIn: https://www.linkedin.com/in/luigipirelli * Elance: https://www.elance.com/s/edit/luigipirelli/ * GitHub: https://github.com/luipir * Stackexchange: http://gis.stackexchange.com/users/19667/luigi-pirelli * Mastering QGIS: https://www.packtpub.com/application-development/mastering-qgis ** On 9 May 2015 at 12:38, Sebastiaan Couwenberg sebas...@xs4all.nl wrote: On 05/02/2015 10:19 AM, Luigi Pirelli wrote: basing of these info, timeline for transition is imposed by debian distribution http://perezmeyer.blogspot.com.es/2015/05/qt4s-status-and-qt4s-webkit-removal-in.html Triggered by this announcement, a recent bugreport about the Qt4WebKit removal [1], and the discussion on this list, I've investigated switching the qgis Debian package to Qt5. In Debian there are at least two missing dependencies before the qgis package can be switched to Qt5: python-qscintilla2 from the qscintilla2 source package, and libqwt-dev from the qwt source package. qwt is currently at version 6.0.0, which is not intended for Qt5 according to upstream, for Qt5 Qwt = 6.1 should be used. There is a bugreport requesting an update to Qwt 6.1 from 2013 [2]. Fortunately Ubuntu already has qwt 6.1.1 [3]. This packaging can be merged back into Debian, Lisandro Damián Nicanor Pérez Meyer said he might take a look at that. qscintilla2 only provides Python 3 bindings for Qt5, there doesn't seem to be a Qt5 equivalent for python-qscintilla2. So we may need to switch QGIS to Python 3 too. How feasible is switching to Python 3? The Python maintainers in Debian strive to move away from Python 2 in the next two development cycles (for stretch buster) as announced [4] earlier. The qgis package will need to switch in that time frame too. [1] https://bugs.debian.org/784514 [2] https://bugs.debian.org/733153 [3] https://launchpad.net/ubuntu/+source/qwt [4] https://lists.debian.org/debian-devel-announce/2015/04/msg5.html Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
