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. [...] > * 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? > * 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. > * The SDK has only one place to look for examples. This can still be done by looking into the examples directory in the module and providing one picture to the SDK user. So, to me it doesn't seem like a major advantage. > > Disadvantages: > > * People have to clone the whole repo for just a few > examples. (People that compile Qt from source will have to live > with this, if you use the SDK this should not impact these > people) > * If the API of a module changes and an example breaks it will not > be caught by the CI system the moment the change is going into > mainline. 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. - 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. Best, Rajiv _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
