Good morning,
There is again new snapshot(2013-06-25-65/) available in
http://download.qt-project.org/snapshots/qt/5.1/5.1.0-rc2/backups/. It is
already quite near of rc2 but some changes are still missing. Below is listed
new changes since my previous mail:
Qtsdk:
·Fix warnings during
On segunda-feira, 24 de junho de 2013 15.50.17, Knoll Lars wrote:
> On 6/24/13 5:32 PM, "Giuseppe D'Angelo" wrote:
> >On 24 June 2013 17:20, Markus Goetz wrote:
> >> Hi,
> >>
> >> I remember that gooling for "QWidget" or "QNetworkAccessManager" gave
> >> you the documentation page (usually of th
[Upfront: I am _really_ happy to see V8 and the glue code its service
required to be on its way out. But...]
On Mon, Jun 24, 2013 at 01:30:18PM +0200, Simon Hausmann wrote:
> > This confuses me a bit. Why isn't the implementation tuned specifically
> > for QML, instead of being a fully-compliant
Simon sayeth:
>
Chris replied:
> > This is really exciting news! Good stuff!
>
+1
> > I wonder how much performance delta there is between JIT and pure
> > interpretted, with a tight enough interpreter loop, if you make some
> > simplifying assumptions (eg, types can't change at runtime / e
Hi,
This is really exciting news! Good stuff!
> Hi,
> >
> > Does that include to get rid of v8 as an JS engine option for QML2?
>
> Yes, that's exactly the proposed change.
>
> > I have not tested it yet, but it would be interesting to know if the new
> > engine also uses just in time compilatio
Hi,
Does that include to get rid of v8 as an JS engine option for QML2?
I have not tested it yet, but it would be interesting to know if the new
engine also uses just in time compilation, as we had quite some work done
to get v8 running on WinCE due to wrong ARM abis for Windows CE among other
thi
