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 <[email protected]> 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 [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
