Re: Policy regarding QtWebKit and QtScript

On Tuesday 22 December 2015 20:03:22 Thomas Lübking wrote: > On Dienstag, 22. Dezember 2015 19:44:21 CEST, Aleix Pol wrote: > > compiling for some time, but that's not a reason to rely on it on our > > side. > > Sure, getting rid of it is mandatory. > What worries me is that this *break* happens

Re: Policy regarding QtWebKit and QtScript

> Isn't the designated successor for QtScript QJSEngine > (I even assumed there should be some porting tools?) That's what I meant under 'qml engines'. :) A relevant mail by Frederik: http://lists.qt-project.org/pipermail/interest/2015-June/017446.html Cheers, Ivan -- KDE, ivan.cu...@kde.org,

Re: Policy regarding QtWebKit and QtScript

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 >

Re: Policy regarding QtWebKit and QtScript

On Dienstag, 22. Dezember 2015 19:44:21 CEST, Aleix Pol wrote: compiling for some time, but that's not a reason to rely on it on our side. Sure, getting rid of it is mandatory. What worries me is that this *break* happens in a *minor* Qt release. Should generally not happen. Period. It

Re: Policy regarding QtWebKit and QtScript

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? > > > >

Re: Policy regarding QtWebKit and QtScript

Pau Garcia i Quiles ha scritto: > > > On Tue, Dec 22, 2015 at 11:02 PM, Albert Astals Cid > wrote: > > > > Soon Qt 5.6 will be released and with it, 2 quite widely used > > frameworks will disappear: QtWebKit and QtScript. Also QtQuick 1, but >

Re: Policy regarding QtWebKit and QtScript

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

Re: Policy regarding QtWebKit and QtScript

> QtScript support in Kross depends on Qt's QtScript. Meant to reimplement the scripting mechanisms we have to use Kross instead of QtScript - to expose the scriptable objects to Kross. IIRC (haven't checked Kross for a long time) it supported accessing Qt objects and properties/methods, was

Re: Policy regarding QtWebKit and QtScript

El Tuesday 22 December 2015, a les 18:10:44, Aleix Pol va escriure: > Hi, > Soon Qt 5.6 will be released and with it, 2 quite widely used > frameworks will disappear: QtWebKit and QtScript. Also QtQuick 1, but > I think this is much less of a problem. As far as I understand they are just going to

Re: Policy regarding QtWebKit and QtScript

On Tue, Dec 22, 2015 at 11:02 PM, Albert Astals Cid wrote: > > > Soon Qt 5.6 will be released and with it, 2 quite widely used > > frameworks will disappear: QtWebKit and QtScript. Also QtQuick 1, but > > I think this is much less of a problem. > > As far as I understand they are

Re: Policy regarding QtWebKit and QtScript

On Wed, Dec 23, 2015 at 12:06 AM, Luigi Toscano wrote: > > Shouldn't it be the other way around? Workable solution first and drop the > old > one later? > > That's exactly what people said when plans to drop QtWebKit and QtScript were first announced. As people

Re: Policy regarding QtWebKit and QtScript

2015-12-22 20:21 GMT+03:00 Ivan Čukić : > As for QtScript, I see two approaches: > - kross (what is the state of it?) > - qml engines Hi Ivan, I don't get what you are suggesting. QtScript support in Kross depends on Qt's QtScript. -- Alexander Potashev

Policy regarding QtWebKit and QtScript

Hi, Soon Qt 5.6 will be released and with it, 2 quite widely used frameworks will disappear: QtWebKit and QtScript. Also QtQuick 1, but I think this is much less of a problem. I'd say we need a plan to figure out what to do with these dependencies. I don't think assuming that they will stay

Re: Policy regarding QtWebKit and QtScript

http://blog.qt.io/blog/2015/12/18/qt-5-6-beta-released/ > Webkit and Qt Quick 1 Removed > > We have removed WebKit and Qt Quick 1 from Qt 5.6 release content. > The source code is still available in the repositories, but these are not > packaged with Qt 5.6 any more. **Qt Script remains