February 24, 2011 by Kent Hansen | Comments
The status of the V8-based back-end is that we still have some QtScript API that's not implemented, and there are autotests failing (QTBUG-17640), but several of the QtScript and QML examples and demos run. Aside from behavorial compatibility with current Qt, we also need to ensure that there aren't any performance gaps in the C++/JS layer before a V8-powered Qt can become a viable solution. As I mentioned in a previous post, we're simultaneously looking to trim the fat of our current APIs to make a switch feasible.
Subscribe to our newsletter
Try Qt 6.4 Now!
Download the latest release here: www.qt.io/download.
Qt 6 is the productivity platform for the future, with next-gen 2D & 3D UX and limitless scalability.
Explore Qt World
Check our Qt demos and case studies in the virtual Qt World
Check out all our open positions here and follow us on Instagram to see what it's like to be #QtPeople.
Näytä tämä julkaisu Instagramissa.
Want to build something for tomorrow, join #QtPeople today! We have loads of cool jobs you don't want to miss! http://qt.io/careers #builtwithQt #software #developers #coding #framework #tool #tooling #C++ #QML #engineers #sales #tech #technology #UI #UX #CX #Qt #Qtdev #global #openpositions #careers #job
Henkilön Qt (@theqtcompany) jakama julkaisu