View Single Post
qgil's Avatar
Posts: 3,105 | Thanked: 11,088 times | Joined on Jul 2007 @ Mountain View (CA, USA)
#326
Originally Posted by javispedro View Post
I have to wonder what will happen when we end in a setup where all the system apps directly use underlying APIs, each with its own set of quirks, while all the third party apps are suggested to use the extra abstraction layer in order to keep source compatibility.

Example: native calendar application APIs:
MeeGoTouch -- KCal (possibly?)
MeeGoNetbook -- Evolution
Maemo5 -- calendar-backend

Will Nokia succeed in unifying all of those under a Qt Mobility "Calendar" API? Will it be encompassing enough and at the same time stable and consistent, so that most developers do not feel compelled to use the native APIs to get more features/avoid bugs?
Dince you ask, javispedro and other developer with real concrete questions like this one: it is more useful to wonder and ask at the places where the related developers can be found.

Qt Calendar API appears as planned for 2H 2010 - http://qt.nokia.com/developer/qt-roadmap/ . meego-dev is a good list to ask and discuss about the availability of this API in MeeGo, current development status, maintainers, plans to support this API in Maemo 5...
 

The Following User Says Thank You to qgil For This Useful Post: