Policy regarding QtWebKit and QtScript

[Lisandro Damián Nicanor Pérez Meyer]

On Tuesday 22 December 2015 19:50:43 Allan Sandfeld Jensen wrote:
> 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.

And should be compilable for some time, indeed.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20151222/e994deef/attachment.sig>