On Thu, Jun 23, 2011 at 1:07 PM, Till Harbaum / Lists <[email protected]> wrote:
> My problem here is that i don't see any path to the future. The fact that > there's no roadmap for future hardware makes it very dangerous to > explicitely code for MeeGo handsets. The way I see it, you would explicitly code for N9 / Symbian (or other future devices with QML support) and coincidentally the stuff will work on MeeGo Handset (until handsets with real meego become available). Or non-handsets like tablets. > Without apps there won't be users. Without users no other vendor will replace > nokia. Exclusively focussing on a brand new tool chain like qml/qtquick would > only then be an option if there'd actually be a roadmap. But it looks like > there isn't. Qt Quick is not MeeGo specific by any means, so I don't see the risk. > I personally think that MeeGo handset is now orphaned and i think it would be > very useful to find ways to connect to it's ancestors to get some intial > broad set of software support which in turn might help it find a new home. To > achieve this, some very basic projects are needed: I'd rather see new broad set of software emerge around QML. > - But imho way more important requirement is some nice integration of plain > qt apps. Until a few days ago there has been some half-done themeing for > plain qt apps that made those to mimic the look and feel of meegotouch apps. > Without such theming plain qt apps look exactly like their desktop > counterparts (they e.g. have a tiny ordinary menu bar on top and always run > in landscape, see and example here: > http://www.harbaum.org/till/harmattan.jpeg). I'd really like to see the mtf > theming to get some caring attention. Qt really is a great basis for both > desktop and handset apps and the Maemo5 qt integration impressively shows how > well the handset integration can be done. The degree of mobile functionality you get with maemo5 is nice (some custom components like QMaemo5ValueButton, kinetic scrolling in lists, nice menus), but the deal is that similar UI's are trivial to do in QML. And that QML version will work well outside maemo5 as well. > I really think a solid foundation to port apps from previous Maemo versions > will be crucial to get a solid application based for the MeeGo handset. And > this in turn is required to pave a persistent road for meego handset. Persistent road should be based on technology with a future promise (QML), not something that's considered deprecated/dead on mobile devices. Upcoming performance improvements like Qt Scene Graph are targeted to improve QML performance, promoting a non-QML solution will create a legacy of slow apps. I don't want to act as stop energy for someone wanting to improve the MTF QWidget style, but it should remain a "niche" solution that we'll warn developers from touching unless absolutely necessary. _______________________________________________ MeeGo-community mailing list [email protected] http://lists.meego.com/listinfo/meego-community http://wiki.meego.com/Mailing_list_guidelines
