Policy regarding QtWebKit and QtScript

[Allan Sandfeld Jensen]

On Tuesday 22 December 2015, Thomas Lübking wrote:
> On Dienstag, 22. Dezember 2015 19:05:23 CEST, Ivan Čukić wrote:
> > So, using Kross would mean implementing the kjs backend for it that we
> > had in 4.x times?
> 
> Isn't the designated successor for QtScript QJSEngine (I even assumed there
> should be some porting tools?)
> 
> About QtWebkit - what exactly does "disappear" mean in this context?
> Will it be impossible to link QtWebKit 5.5 to Qt 5.6 ?
> For if it would, that would be one giant ABI break and the answer would be
> to fork Qt... :-P
> 
No, probably not, it uses private Qt modules, so it cases the version mismatch 
assert. But currently it looks like there will be a source-only qtwebkit 5.6, 
but not as part of the official release.

Best regards
`Allan