On 06/06/2016 11:00 AM, Tom Chadwin wrote: > It's a question of timing. I understand that testing is not a commonly used > environment. However, it indicates that QtWebkit's end is getting closer. > And with QWebEngine not yet here, it's just a bit of a concern as to when I > should start looking at replacing the former with the latter.
Right now is too early - it's not available for any platform with Qt4, so for 2.x it's out of reach. As long as someone wants to maintain a 2.x compatible version of his plugin, just stick to QtWebKit. For plugins developed against only QGIS 3.x it will be an option if it suits the needs for the particular purpose. But we should neither recommend (let alone require) replacing QtWebKit with QtWebEngine for now. Once we have collected enough knowledge about QtWebEngine and QtWebKit really starts to disappear from supported platforms we can start recommend porting code. I don't know when that will be but I don't expect this to happen in the next year. 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
