FOREWORD

The world is full of programming languages and development tools. Some languages can be designed for embedded devices, others for ease of development. Each of them has its own distinct syntax and its own distinct tools, and is suitable for a distinct purpose. This has been a dilemma for a long time, especially in the mobile arena. Companies have their own development tools, programming paradigms and selected programming languages, and the same code can rarely be reused between different segments, from mobile terminals to desktop environments. Since the beginning of this century, Nokia has had three active software platforms: S60 (Symbian), S40 (proprietary) and Maemo (Linux). Each of these platforms has its own set of software components and applications. No matter what the application was, whether for a calculator or browser, Nokia had at least three different solutions for it. Each of these applications needed its own localization, tools and testing teams. Thus, it was self-evident that the overall dvelopment model was very expensive How then could this be reduced? How could a development model be created that the developers would love? How could a better return on software investments be provided? How could open source innovations be leveraged? The answer to this last question is very simple, but hard to actualize. First, you just create an environment or system where you can share code or applications between software platforms and then you do not implement everything ...

Get Qt for Symbian now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.