View Single Post
qgil's Avatar
Posts: 3,105 | Thanked: 11,088 times | Joined on Jul 2007 @ Mountain View (CA, USA)
#32
Originally Posted by qwazix View Post
New apps @ store: We could make a wiki page, each participant can point to one application that is out in the wild and not in Nokia Store and write a small text describing it. Then we could form a commitee that will decide about usefulness/innovation/difficulty/interface and give a grade for each one of these aspects. The average (or weighted average) can be used to determine who gets a device and who doesn't.
I'm proposing a lighter process at http://talk.maemo.org/showpost.php?p...45&postcount=5 Any specific reason why we should go for the wiki page & committee instead? I'm hapopy evolving or changing the initial proposal - for a known and good reason.

Qt5 mobile projects: Is there a special goal that Nokia/QtProject want to achieve with this activity? Are there any special new features in Qt5 that developers should be encouraged to use?
The main motivations are mixture of:

- Helping testing Qt 5 itself and providing feedback while it's alpha/beta.

- Helping testing the Qt 5 libraries for the N9.

- Getting stories of real apps ported from Qt 4 to Qt 5. Trivial? Horrible? What are the pain points? And what about Qt Creator and the documentation available?

- Getting developers to play with the new toys: Qt Quick 2, textures, transitions, graphics / video effects, raw OpenGL ES stuff, post-Mobility APIs, the new Qt WebKit, JSON DB, ongoing R&D on PhoneGap own JQuery based experiments...

This is the same motivation we have for the QtonPi program, but for mobile development the N9 provides a touch display and many more sensors and hardware features that a bare bones board is missing.

Good question and I have posted this explanation at http://wiki.maemo.org/Summer%2712_De...obile_Projects

If yes these should be stated clearly and made a prerequisite. If not, seeing that updates and ports are probably being downplayed in the maemo coding competition this year maybe it's a good idea to give the awards to porting Qt4 applications to Qt5.
I would leave Qt 5 apps from the Code Competition. Qt 5 can cause a lot of frustration to someone jumping in unaware of its status and the reasons why things are the way they are. It will be different when it's final and stable.

In the meantime there are some dudes that are in the opposite situation: following Qt 5 development, growing appetite watching demo videos and examples, and lazily looking for an excuse to get started on something. This is an attempt for becoming that excuse.
 

The Following 4 Users Say Thank You to qgil For This Useful Post: