View Single Post
Posts: 3,319 | Thanked: 5,610 times | Joined on Aug 2008 @ Finland
#49
Originally Posted by gerbick View Post
That's not being addressed in regards to these updates in Qt. To my knowledge (and I might be fully wrong here) but Qt 4.7 will not be on the Nokia N810. Qt Mobility will never make it to Maemo 4.1 (Diablo) either. What does Qt offer in those situations once a device is old enough to not be supported by the new features?

It's all fine and dandy at this moment. Not so in the future. I think that part needs to be confirmed about how forward reaching these updates will be.
Okay, as much as we're used to yell Nokia-abandonware, Qt had and still has a very strict policy about that.

http://doc.qt.nokia.com/qtmobility-1...-compatibility

See these platforms (note the S60 ones). Those platform are guaranteed to be supported in the next version, with a worst case deprecation in the release after that (so in the very worst case scenario, the very oldest S60 3rd FP1 can drop out in Qt 4.8, which would be around 2011Q4, 2012Q1). And that's 2007-8 hardware officially supported till 2012 as a WORST case scenario.

In the case of Diablo, it might not be that much further.
Yes, that ship has already sailed. Diablo never was an official Qt platform, sadly (it didn't even get the 4.6 update yet). Now, the good part is that Qt (and QtMobility) are *fully* GPL, so there is absolutely nothing preventing anyone from backporting it to Diablo. Ditto for 4.7, 4.8, etc (this also applies to S60 should it one day lose official support).
__________________
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
 

The Following 5 Users Say Thank You to attila77 For This Useful Post: