On Oct 10, 2011, at 11:27 PM, ext Ville M. Vainio wrote: > Master branch. It's an optional dependency. Just try and build it. > > You may learn somehing useful here: > > http://developers.nokia.com/Community/Blogs/blog/kate-alholas-forum-nokia-blog/2011/06/23/nokia-meego-1.2-harmattan-qt-quick-components > > We are also working on freely distributable graphics (still, it's a > slow process), now you need to "hack" and copy the graphics manually > from SDK/device. >
We have already freely distributable graphics, the package is based on public MeegoTouch development theme graphics. This public graphics is distributed for MeeGo N900 CE and fn ppa for Ubuntu. There is more about porting components in http://www.developer.nokia.com/Community/Blogs/blog/kate-alholas-forum-nokia-blog/2011/07/08/porting-meego-1.2-harmattan-qt-quick-components As my opinion Harmattan components are very flexible for any touch based devices, I got it working with minor hacks even in Android Kate > > On Mon, Oct 10, 2011 at 10:53 PM, Marco Martin <notm...@gmail.com> wrote: >> On Monday 10 October 2011, Ville M. Vainio wrote: >>> Yes, src/MeeGo. >>> >>>> i still think that probably in the end what is wanted is a separed >>>> compatible set, even if it would end up sharing a large amount of code, >>>> since we need it themed with plasma and not depending from libmeegotouch >>> >>> Harmattan components don't depend on libmeegotough, just QML, graphics >>> and a bit of C++. People are even running them on Android. >> >> uhm, master branch? to me is still linking to it (and uses mthemedaemon too) >> or is it a build time optional dependency? >> >> Cheers, >> Marco Martin >> > _______________________________________________ > Qt-components mailing list > Qt-components@qt.nokia.com > http://lists.qt.nokia.com/mailman/listinfo/qt-components _______________________________________________ Qt-components mailing list Qt-components@qt.nokia.com http://lists.qt.nokia.com/mailman/listinfo/qt-components
