________________________________________ From: Ranganath Rajiv (Nokia-DXM/SiliconValley) Sent: Wednesday, September 14, 2011 9:14 PM To: Vandonderen Casper (Nokia-MP-Qt/Oslo) Cc: <[email protected]> Subject: Re: [Qt5-feedback] Moving examples to a separate module
On 09/14/11 at 12:50P, ext [email protected] wrote: [...] >> What this means for the individual modules is that the /examples >> folder will disappear and will be put in the qtexamples module. Also >> most content from the /doc folder can be moved, since the text >> belonging with the examples should probably be in the qtdoc module. >> >Moving examples out of the module might have an affect on the Qt5 >release process. Thinking along those lines. I would say that the release process becomes simpler, since automatically only the examples that you have the modules for will be built, so if someone wants to do a release and does not want a specific module the examples for this module will not be built. [...] >> * We don't have examples all over the place, which makes it >> simpler for me to maintain, since I only have to look in the >> qtexamples repo. >> >Why can't we integrate the examples in qt-webkit-examples-and-demos >module into qt-webkit? They were there at some point, but now our qtwebkit repo only reflects upstream + our patches that have not gone upstream yet, since examples are not allowed upstream they are in a separate repository. >> * We get a place for examples that depend on multiple qt5 modules >> (e.g. QtWidgets and QtSvg). >> >At the moment, QtWidgets and QtSvg are add-on modules. This means that >eventually the release maintainer has the flexibility to decide if these >modules makes sense for their configuration. If not, they can drop it >from their release. > >However, if qt-examples, includes examples from QtCore + a number of >addons, the release maintainer will need to go thru' the hassle of >cleaning up qt-examples for every release and remove examples of addons >which doesn't belong in the release. See above and this can be solved by copying the examples that belong with the modules you have to a different folder (automatically using .pro files, since we do that already in some cases) >Additional disadvantages. > >- We now create a dependency between the module maintainer of any module > and the qt-examples module maintainer. Every time some change to the > example which could be because of a number of reasons - API change, > improving the example for additional clarity etc., the change needs to > be pushed into qt-examples. This dependency is there anyway, since there will probably be a specific maintainer for the examples. Since the maintainer of the other modules is also a contributor and an approver I hope he/she can make a conscious decision about putting the example in. >- If somebody decides to create a new addon module, their ability to > release the module is now dependent on their examples being integrated > into qt-examples. Some module maintainers might decide to keep their > examples in their own repo to avoid the hassle. This would mean that > we'll end up having our examples all over the place. I am wondering if this is a valid point, since if we don't put the examples in the qtexamples module we have the examples all over the place anyway. Casper _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
