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. 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. Also, if you followed a strict deprecation cycle (where modules first need to be marked as deprecated before they can be removed in the next version), then QGraphicsView can only go away with Qt 7. 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. 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. regards, Michael _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
