On Thu, 15 Sep 2011 17:53:01 Pasion Jerome (Nokia-MP-Qt/Oslo) wrote: > Hello, > > Why not have both? > > A Qt example is essentially a demo, where you are free to use multiple > module dependencies. The individual repositories can keep the current code > samples and snippets in their own repositories. > > The problem is that we need to have the freedom to include examples that > have dependencies and they do not belong to the individual repositories. > > So, let's say we have a Media Player example. It depends on core, > declarative, components, multimediakit, etc. This example cannot be in the > qtbase, qtdeclarative, qtcomponents, qtmultimediakit, and so on. Since > it's not documentation either, it shouldn't be in qtdoc. Hence, it should > be in some sort of repository where it and others can exist. > > Just to note, we receive many of these examples and they are needed in the > overall Qt 5 landscape. One Qt story is the "porting" story whose content > is quite anemic. We receive Qt+SymbianAPI examples which we cannot put > into the main Qt 5 repo. We simply ignore them, which is a shame, really. > > I would like to keep the trivial code into the submodule repository for > these reasons: -any bugs on these code will be filed against the module > and module maintainers and not the doc team. Developers make them, so they > should be responsible for them. There are simply too many to manage in too > many repos. The module maintainer should have control of these issues and > not the QtDoc or Qt Examples maintainers. -any Qt examples are put into a > separate repo, where its maintainer (ie. Casper) can handle the bugs and > act like a proper maintainer. > > The any qt5 module maintainer can simply ignore the Qt examples and they > will still have their API, API listing, and their snippets. But the > overall Qt 5 product pages and the Qt examples should be separate as they > do have multiple dependencies. > > > With regards to definition: > Qt Example: "demos" and any other code samples, etc. > snippet code: trivial code, code samples. > The overlap is intentional. *Don't be afraid of overlap* > > About the sugar comment. Sugar is good, it attracts people. A product > without fluff is not a product. >
I like this idea - though I still have my own opinions on the naming ;) . Does this mean that $module_name/examples would be split up? The bigger 'examples' becoming Qt Examples and moving to qtexamples and the smaller ones becoming snippets (but staying in $module_name/examples)? Who would be making this decision? -- Alan Alpert Senior Engineer Nokia, Qt Development Frameworks _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
