Qt For Tizen Update Does Qt 5.2 Alpha, Wayland Happy
The open-source project aiming to bring the Qt tool-kit to the mobile Tizen Linux platform has now graduated to being a 1.0 Alpha 4 candidate. With this new development release, Qt for Tizen is powered by the latest Qt 5.2 Alpha build.
Qt 5.2 reached Alpha at the end of September with full support for Android and iOS, new modules, a built-in JavaScript engine for Qt QML, Qt Quick improvements, new Qt Quick Controls, and a wide-assortment of other work. Qt 5.2 is slated to ship as stable in late November or December and has already been pulled into the latest Qt for Tizen work.
Besides updating to Qt 5.2 Alpha, Qt for Tizen Alpha 4 also now delivers Tizen RPM packages in a dedicated repository, highly automized build scripts, improves handling of smartphone sensors, Qt Creator now takes on a bigger role as the integrated development environment for Qt Tizen development, and there's extended support for Tizen IVI 3.0. For Tizen In-Vehicle Infotainment 3.0, Wayland is now the preferred display server for these IVI purposes.
More details on the Qt for Tizen 1.0 Alpha 4 update can be found via today's project blog update.
Qt 5.2 reached Alpha at the end of September with full support for Android and iOS, new modules, a built-in JavaScript engine for Qt QML, Qt Quick improvements, new Qt Quick Controls, and a wide-assortment of other work. Qt 5.2 is slated to ship as stable in late November or December and has already been pulled into the latest Qt for Tizen work.
Besides updating to Qt 5.2 Alpha, Qt for Tizen Alpha 4 also now delivers Tizen RPM packages in a dedicated repository, highly automized build scripts, improves handling of smartphone sensors, Qt Creator now takes on a bigger role as the integrated development environment for Qt Tizen development, and there's extended support for Tizen IVI 3.0. For Tizen In-Vehicle Infotainment 3.0, Wayland is now the preferred display server for these IVI purposes.
More details on the Qt for Tizen 1.0 Alpha 4 update can be found via today's project blog update.
34 Comments