Alan wrote: > 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?
There seems to be consensus at least on keeping the simple examples together with the code, so I suppose this is the conclusion :) On a related note, I think that should be written " $repository_name/examples"... The difference between modules such as Qt Gui and Qt Service Framework and repositories such as qtsystems, qtbase is a bit confusing. Based on a discussion with Rajiv, Marius, and Lars, I believe we should use the term module to refer to libraries, so qtbase, qtsystems and qtpim are not modules but repositories. The repo structure shows in the Qt source code but it should be otherwise invisible to the user of Qt. These repositories and the fact that several modules share a repo should mostly remain an internal implementation detail. I added a section about this in the Qt5 product definition: http://developer.qt.nokia.com/groups/qt_contributors_summit/wiki/Qt5ProductDefinition#db5a1972d9a39488e9f1b10a3d958b8f The page also documents a recommended way to structure a repository: repository/ README LICENSE bin/ include/ src/ doc/ examples/ tests/ modules/ qt_<module1>.pri qt_<module2>.pri repository.pro sync.profile Comments? We could add a note about the more complex examples or demos in that document as well. Best regards, Henry _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
