Maemo moving to Qt

Posted Jul 23, 2009 18:48 UTC (Thu) by KGranade (guest, #56052)
Parent article: Maemo moving to Qt

Have you noticed that the two factors cited as the reason for the migration actually cancel each other out?

"making it easier for application developers to use one tool chain and one API across a variety of platforms"

"...QtMobility project, which will develop entirely new APIs for mobile devices running Symbian, Maemo, or Windows CE."

So first you get the mobile developers to migrate to a set of APIs that are shared with desktop platforms, and then you get them to migrate to ANOTHER mobile-only API set? Perhaps the QtMobility APIs will be somehow compatible, but if so that should be made clear.

Maemo moving to Qt

Posted Jul 23, 2009 19:44 UTC (Thu) by halla (subscriber, #14185) [Link]

Er... Maybe the mobility apis are a sort of, you know, add-on, instead of a replacement? So, you've got what Qt offers (strings, data structures, push buttons, xml, threading, networking, concurrency, styling, whatever), and then you get additional finger-food widgets, addressbook, geolocation etc. api's. Sort of complementary, but all designed with the same fastidious api principles so the principle of least surprise holds through the sdk.