Quim, I think we're (well, I am) about getting involved in the now-open code of the Handset UX itself: running it on primary development machines, playing with the code and submitting patches - rather than developing apps for the Handset UX.
Cheers, Andrew On 01/07/2010, [email protected] <[email protected]> wrote: > Hi, > > Andrew Flegg wrote: >> What's the development environment of those working on the Handset UX; >> how are they managing to do development; and how do they get new >> employees up to speed quickly? > > > Even if you might be targeting the Handset UX, the idea is that you can and > will want to recycle as much work as possible for other UXs. For this reason > the default starting point is Qt and the corresponding Qt SDK. > > Regular unstable MeeGo SDK builds are on its way, just not ready yet. In the > meantime, those willing to get familiar with the environment can try the > Nokia Qt SDK and have a look at the Qt 4.7 novelties. The architecture and > the components are the same, it's only the targets that differ. > > If you want to speed up quickly then Qt Quick is a good choice. See > http://qt.nokia.com/developer/qt-qtcreator-prerelease/ > > Note though that all these pieces are being integrated and polished as we > speak. MeeGo 1.1 is not yet ready for application developers just looking > for a stable and reliable environment. > > -- > Quim Gil > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev > -- Andrew Flegg -- mailto:[email protected] | http://www.bleb.org/ Maemo Community Council chair _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
