[Qgis-developer] QtWebKit 2.3

Tom Chadwin tom.chadwin at nnpa.org.uk
Thu Feb 25 03:10:09 PST 2016


OpenLayers is moving away from the Closure library. This is A Good Thing, as
abandoning Closure will decrease OpenLayers' filesize considerably.

However, it means that OpenLayers now doesn't work on older browsers. While
not a big deal for end-users' desktop browsers, as very few are affected,
it's a problem for QGIS plugin developers.

Qt4.8 uses QtWebKit 2.2 (I believe), and this *is* affected. It can be fixed
by adding two polyfills (likely to increase in number in the future).

qgis2web uses QtWebKit for its preview, so I've had to add the polyfills. I
don't like doing this, as it adds bloat, and at the moment (unless I
redesign the code), the polyfills are added to exported maps as well, which
really don't need them.

QtWebKit 2.3 was developed and released as a community project, outwith the
Qt project. 2.3 includes an up-to-date WebKit version, so it would fix these
problems. Can anyone give an opinion on whether it would be possible to
package QtWebKit 2.3 with qgis2web?

I obviously realize that QGIS3 will remove this issue, with Qt5. However,
QGIS3 is a while off yet - there will be several OL3 releases until then -
and QGIS2 is likely to remain in use for a long time.

Does anyone have an opinion, or any expertise in this area?



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/QtWebKit-2-3-tp5252791.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.


More information about the Qgis-developer mailing list