On Fri, 2010-10-08 at 02:43 +0200, ext Sivan Greenberg wrote:
> According to Kate, Qt Components which as I understand it is building
> specialized reusable components through QML, is the most probably
> cross platform way, maybe because they are built in runtime through
> generic ECMAScript like language, where you make it run on a different
> platform (namely, Symbian) you just need to replace the runtime with
> runtime for S{3,4} that uses the underlying look and feel of the
> native widgets.I agree, Qt Quick (including the new Components) is raising high interest among mobile developers. It will be used for developers targeting multiple MeeGo UXs thanks to its clean separation between logics and UX and it is well positioned to be popular among developers targeting MeeGo and Symbian. About the Components, see http://labs.qt.nokia.com/2010/09/10/building-the-future-reintroducing-the-qt-quick-components/ The 1.2 release cycle will be probably the one bringing Qt Quick to the developer awareness. If the task "Qt across MeeGo & Symbian" can contribute analysis, documentation and examples before the 1.2 release that would be great. > My feeling is that QWRT is somewhat similar, so going with > "Components" seem wise, given QML's promises in tems of UX and > designer incorporation. What would ol' Qt mean in this context? By ol' Qt I mean QWidget. :) Qt WebRuntime and the corresponding SDK are appearing in the surface (Forum Nokia users can check the recent technology preview at ww.forum.nokia.com/Develop/Web/ ). If someone else is interested in concentrating on WRT across MeeGo & Symbian great, but otherwise it is perhaps better to concentrate on Qt Quick first? -- Quim _______________________________________________ MeeGo-community mailing list [email protected] http://lists.meego.com/listinfo/meego-community
