On 09/14/2016 09:28 AM, Nyall Dawson wrote: > On 14 September 2016 at 17:26, Matthias Kuhn <[email protected]> wrote: >> On 09/14/2016 09:14 AM, Nyall Dawson wrote: >>> On 14 September 2016 at 16:26, Matthias Kuhn <[email protected]> wrote: >>>> QtWebKit is not removed, is it? >>>> >>> >>> Eventually it is. I'm not sure on the timeframe for various platforms >>> but sooner or later we'll hit this. I think it'd be easier for plugin >>> devs/packagers if we address this before QGIS 3.0 release. >> >> I think there was an initiative to revive QtWebKit. >> >> https://www.phoronix.com/scan.php?page=news_item&px=QtWebKit-Next-Gen >> >> So I'm really not sure it's worth the trouble with (at least my) current >> state of knowledge. > > Yeah - that's this one > http://qtwebkit.blogspot.com.au/2016/08/qtwebkit-im-back.html > > I'm just not sure if distros will embrace and package this.
Just like we don't know if QtWebEngine will be in a good-enough state soon enough :) If I'm not mistaken, QtWebEngine mainly misses functionality for vectors, so it's a problem for map canvas items. Anything else (plugin manager etc) could be switched over to web engine. For plugin devs, QtWebEngine can be made available in parallel to QtWebKit. In general I think our API doesn't directly offer much (any?) webkit related things. So we can just switch the engine for map canvas/print composer items under the hood when/if QtWebEngine fully supports our requirements? Matthias _______________________________________________ Qgis-developer mailing list [email protected] List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
