On 15/02/13 21:23, Zoltán Balogh wrote: > On 02/15/2013 12:43 PM, Stephen Kelly wrote: >> On Friday, February 15, 2013 12:28:32 Timo Jyrinki wrote: >>> At least qtpim, qtsystems, qtconnectivity, qtfeedback >>> and qtwayland will follow later, and I'll be filing change proposals >>> for them at that time as part of the process. >> I don't know why you're packaging those. >> >> You understand that they are not 'part of Qt 5', right? >> >> And you understand that they are not stable in any way and their API will >> likely change, and they will not be part of Qt 5.1, and they may never be >> part >> of a Qt release? >> > > Few days ago there was a question about the qt3d what is not released in > Qt 5.0.0 and not planned for the 5.1 either. Lars wrote then that the > module will require more work to make it suitable for an official > release. I take the same for all modules not released with Qt 5.0.0 > > The same way the qtsensors, qtlocations (even mentioned in the marketing > video http://www.youtube.com/watch?v=FIs5YqzS4Bc) are left out and still > they can be used for experimenting, demonstrating the strengths of Qt5 > > So I see a definite value in packaging all available Qt modules and > distribute them.
+1 > > Yes, API changes and missing/broken features are are expected, but that > is normal with unstable or experimental libraries. As far as QtSensors is concerned, the base API is not changing and has been stable since QtMobility. Only that new sensor types keep being added. :) I'm looking at you RIM^H^H^HBlackberry! > > Packaging in Ubuntu all the available Qt modules means distributing the > Qt to a wider audience. I guess it can be considered as a good thing :) > and never know somebody might get excited and interested to contribute > and push forward the modules left out from the release. I would agree here too. Making the unloved modules invisible is not a good thing. Lots of people put lots of work into them, and IMHO that shouldn't be wasted. -- Lorn Potter Senior Software Engineer, QtSensors/QtSensorGestures/QtSystemInfo _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
