On Fri, May 28, 2010 at 8:06 PM, JD Zheng <[email protected]> wrote: > I was looking for the answer to "to Qt or not to Qt" for all MeeGo UX and > seems I am unable to get consistent answer. > I was calling for community involvement for non-Qt app porting, seems it is > just "wasting time", which implies the current GTK app will stay there as > MeeGo core app and it basically says NO to my original question. > Why wasn't moving to rpm "wasting time"? We followed the decision even if we > disagreed, why decision can easily be reverted now for other reasons? Or > maybe we shouldn't discuss decision in the first place?
As Paul points out.. A lot of the applications in MeeGo Netbook at least are either directly from- or working with upstream. Putting work into porting something that already works essentially for religious work, and then putting the required effort into maintaining that consistently (as it's probably unlikely to be upstreamed, quite honestly) is a big commitment. This is very different to the choice of rpm vs deb, which is a downstream choice affecting MeeGo only. Now, I'm not saying that we (as in the wider MeeGo community) couldn't probably do this, but two things: - why should it be done? honestly, even with my bias (I love Qt, I hack on it when I can, and I work with it on a daily basis) - it's essentially a religious choice. "if it ain't broke, don't fix it" applies to some extent here. - you don't really *gain* anything through this port process, apart from a longer still time before you have usable software With these two in mind, you're unlikely to gain commercial backing from this, unless you have demonstrable gains and reasons to do so. > Sounds like the things left to any outsider is some applications to be done > if no one is coding for that (well, I have no idea what is being > developing). I'm not sure what you're asking here, but I'll guess that you're asking what the point of Qt is if nobody uses it. Well: remember first that you're only seeing half the picture. The handset UX isn't out yet, and from signs from Nokia[1] suggest that Qt will have a much larger influence there. Then remember that the application SDK for MeeGo has been announced to be based on Qt, meaning that people writing applications for MeeGo are recommended to use it, so the influence will grow. > What does MeeGo really expect from community? (unfortunately so many emails > distinguished "We(MeeGo?)" and community and I follow that). I was expecting > the answer after 1.0 release and now it is the right time to ask. Honestly not sure how to answer this. I don't think anyone is, yet. I suspect the picture is becoming growingly clear as more parts of the puzzle (like the meego-arm team) come to work and collaborate in the open. > Thanks. > JD Zheng I hope this helps you some. ;) Robin Burchell mob: +447702671419 msn: [email protected] irc: w00t @ irc.freenode.net twr: http://twitter.com/w00teh lac: http://identi.ca/w00t _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
