What’s up with Qt and the future of Cascades?

Cascades

Some of you may have been reading about Nokia’s decision surrounding their investments in Qt and wondering what exactly this may mean for BlackBerry® 10 and the Cascades™ application framework. As many of you know, RIM provides a port of Qt to run on the BlackBerry® PlayBook™ as well as BlackBerry 10 smartphones. Qt is also one of the foundational pieces for the Cascades application framework contributing both the UI declaration in QML as well as many C++ APIs.

We believe that Qt has many great qualities, which is why we have adopted it as part of the core Cascades app framework. The fact that Qt is an open source project has allowed us to both embed it as a core technology layered on top of the POSIX compliant QNX RTOS, as well as contribute changes back to the project. We want to make sure that everyone understands that the BlackBerry 10 platform, and our Cascades application framework, is not tied to the future of Qt in Nokia.

RIM continues to support the Qt community and we are committed to supporting Qt on the BlackBerry platform, including tight collaboration with the Qt community outside of Nokia and with Digia as new potential owner of Qt. We also welcome all Qt developers to bring both their talents and applications to the BlackBerry platform.

While the formal side of the future of Qt is a little foggy right now, we want our community to rest assured that Qt on BlackBerry is here to stay and that Cascades has a bright and long term future with QML.

Cascades, Qt and open source links:

About Tim N.

Tim leads Application Platform & Tools Product Management at Research In Motion. This includes APIs, Frameworks and Tools for the BlackBerry Platform. He can be found hanging out in the development forums or Twitter (@brcewane) trying to help out where he can and to bring your feedback into the next releases of BlackBerry tooling. You’ll also see Tim presenting various topics at the BlackBerry Developer Conferences and BlackBerry World so be sure to stop by and say hi. Just don’t start talking about cars or Batman or you won’t be able to get rid of him.

Join the conversation

Show comments Hide comments
+ -
  • http://www.bbnews.pl/2012/08/research-in-motion-deklaruje-dalsze-wsparcie-dla-qt/ Research In Motion deklaruje dalsze wsparcie dla Qt | BBNews

    […] via: devblog.blackberry Categories: Programiści […]

  • http://www.blackberryordie.com/?p=3676 What’s up with Qt and the future of Cascades? | Blackberry or Die™

    […] post: What’s up with Qt and the future of Cascades? Posted in Apps, Blackberry Playbook, Devices, Editorial, Media, Mobile, Personal, Super Apps, […]

  • http://genteblackberry.wordpress.com/2012/08/23/rim-reafirma-compromiso-con-qt-y-cascades-como-digia-termine-la-adquisicion-de-nokia/ RIM reafirma compromiso con Qt y Cascades como Digia termine la adquisición de Nokia | News Channel

    […] Echa un vistazo a los detalles sobre la devblog […]

  • http://www.sdknews.com/blackberry/whats-up-with-qt-and-the-future-of-cascades What’s up with Qt and the future of Cascades? | SDK News

    […] What’s up with Qt and the future of Cascades? […]

  • http://devblog.blackberry.com/2012/11/porting-qt-apps-to-blackberry-10/ Porting Qt Applications to BlackBerry 10 is Easier than Ever! | BlackBerry Developer Blog

    […] YouTube: BlackBerry Jam Session (JAM12): Porting Qt Applications to BlackBerry 10 Developing in Cascades What’s up with Qt and the future of Cascades? […]

  • http://blackberryphoneshop.info/2012/11/14/porting-qt-applications-to-blackberry-10-is-easier-than-ever/ Porting Qt Applications to BlackBerry 10 is Easier than Ever! | BlackBerry and Phone Shop

    […] YouTube: BlackBerry Jam Session (JAM12): Porting Qt Applications to BlackBerry 10 Developing in Cascades What’s up with Qt and the future of Cascades? […]

  • http://devblog.blackberry.com/2012/11/writing-qt-apps-blackberry-10/ Writing Qt apps for the BlackBerry 10 platform | BlackBerry Developer Blog

    […] What’s up with Qt and the future of Cascades? […]

blog comments powered by Disqus