On Tuesday, 10 de May de 2011 10:42:06 Michael Hasselmann wrote: > On Tue, 2011-05-10 at 11:29 +0300, Sakari Poussa wrote: > > That (Qt5) is a vision with timeline. It's not 10 years, it is 1+ year > > as you can read from the blog. > > > > These are big and complex things which need long cycles to be planned > > and communicated correctly. That's what we (MeeGo) are doing now. And > > not saying do MTF apps now and then say year later that use something > > else. > > > > So yes, we need to start the preparation now. > > Again, nothing has been mentioned in that document that either QWidget > or QGraphicsView are or will be deprecated with Qt 5.
They aren't deprecated. They are "Done" (I'll announce this tomorrow). See the definition at: http://labs.qt.nokia.com/2011/05/03/qt-modules-maturity-level/ Unless someone takes them up and moves them back to Maintained. > Qt 5 probably will be released next year. The ABI promise then would > demand a new major release for Qt before QGraphicsView could be > removed/marked as deprecated, and that next version (Qt 6) will > certainly *not* happen in 2012. Indeed. Graphics View and the widgets will not be removed in Qt 5, so they'll be around for a number of years to come. > With the upcoming Open Governance, deprecation of modules is not > decision of the Qt team alone, but outside maintainers could step in (if > they realize they are heavily invested in a certain module) and take > over. Indeed. Someone has been paying attention to what I've been saying :-) > If we already plan for the removal of QGraphicsView (which, by the way, > is far more mature than what QML2 will be upon its release, simply > because it takes time to mature software), then I think we are planning > too far ahead here. We can plan ahead. And Arjan's point is that we want to remove libmeegotouch eventually. For that to happen, we need to know *how* we'll go about it: what is obsoleted by newer technology elsewhere, what should move to other libraries because they are very useful, what needs research and development to be replaced. This is independent of there being a Qt 5 release. This is something MeeGo has decided it wants to do anyway. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Senior Product Manager - Nokia, Qt Development Frameworks PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
