On Friday 28 November 2014 05:08:43 Kevin Kofler wrote:
> Thiago Macieira wrote:
> > Since Qt doesn't use V8 anymore, there should not be any clashes at all.
>
> Be warned though that QtWebEngine does use V8 through Chromium.
Which means that lots of archs will not be able to have QtWebEngine.
-
Thiago Macieira wrote:
> Since Qt doesn't use V8 anymore, there should not be any clashes at all.
Be warned though that QtWebEngine does use V8 through Chromium.
Kevin Kofler
___
Development mailing list
Development@qt-project.org
http://lists.
On Wednesday 26 November 2014 19:59:55 N. N. wrote:
> > On Wednesday, 26 November 2014, 14:15, Hausmann Simon
wrote:
> > > Hi,
> >
> > You are right, we need to add a few more features to QJSEngine.
> >
> > I'm not so much in favor of the default prototype for meta type api
> > anymore, as it p
> On Wednesday, 26 November 2014, 14:15, Hausmann Simon
> wrote:
> > Hi,
>
> You are right, we need to add a few more features to QJSEngine.
>
> I'm not so much in favor of the default prototype for meta type api anymore,
> as it promotes the creation of slow conversion code I think. If you
19:51
To: development@qt-project.org
Reply To: N. N.
Subject: [Development] Clarification needed for Qt Script's future over
QJSEngine/Value
I was looking at using QtScript for a project and noticed that all work has
been "ABANDONED" for using the new java script engine V8 as noted in
I was looking at using QtScript for a project and noticed that all work has
been "ABANDONED" for using the new java script engine V8 as noted in
http://qt-project.org/wiki/V8_Port and
then pouring over other bug reports & the mailing list about QtScript and how
QtScript won't be updated to use
