On Thursday 15 April 2010, ezjd wrote: > Thanks for sharing these important KDE information! > > As a long time KDE user (not developer though :( ), I have been hoping we > can see places of KDE on embedded device and I even talked with KDE guys > about it when KDE 4.0 was just released. Although KDE team was busy shaping > up KDE 4.X at that time, it seems KDE team have more time working on mobile > world now. > > I really like the way KDE is doing UI framework: one framework fitting all,
thanks :) > but 1st question is how streamline KDE (or KDE SC :) ) can be? Actually it > is also a question for MeeGo as the "core platform" already has >300MiB > rootfs. well, i can answer for the KDE side: our goal is to make possible a build of Plasma with a minimum amount of KDElibs. since some pieces of KDElibs (and its dependencies) are specifically useful just in a desktop scenario. in the kde-core-devel mailinglist there a discussion right now on what ro remove and how. > > Seems MeeGo will do something different according to architecture as each > UX will have its own UI framework, i.e., my understanding is that an > application specific to one UX will need some kind of porting (UI rewrite?) > to work on another unless it is plain Qt application. i didn't exactly understood if those are exactly the plans, but, that's what we really would like to avoid, because there is a lot more to share than just the Qt libraries > Another question for both KDE and MeeGo is how QML (Qt Quick) fits in the > whole picture? Will it be just another supported "program language" like > python or javascript? Or will it be the primary way to develop MeeGo > application (probably it won't for KDE)? I do like the way QML handles UI > design after trying out Qt 4.7/Qt Creator 2.0 TP, btw. Ah, qml, that's an interesting part i forgotten in my original email :) In the end, QML generates items that will go in a QGraphicsview, so we already started to look at an itegration with the existing Plasma library. actually, the Plasma Mobile shell that can be seen in some of the videos i linked already usues QML to manage soe of its animations. it's really easy to mix part of the ui written in qml with other parts r even better, bind a previously existent widget set as elements in QML (and some modifications in qml are being done expliitly to make this easier), this will ensure while maintaining the coherent look and feel of an already done widget set and theme look, you have the ease of use of designing the ui with QML Chees, Marco Martin _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
