Hi Devs, Do we have some guiding docs about the preferred/ideal (future) project/code structure of QGIS?
To be able to move some ui/gui components out of src/core to src/gui I got stuck because of my lack of C++ CMakeLists.txt knowledge [0] But while moving around the ui and gui files I wondered if there was some shared idea of the project tree structure (espcially if this was documented somewhere). Thinking about some docs answering questions like: - should the code/dir/tree structure of the ui part of providers ideally mimick the providers tree? Like providers/foo/faa have it's ui stuff in gui/foo/faa - should ui files be separated from it's accompanying gui h/cpp buddies? If not, again: should the tree structure mimic the src structure? - remembering some discussion's about moving to a core and a gui lib, maybe move the ui part into gui? - what would be the benefit of splitting up in core/gui? I know these things are: never ideal, not easy to do, both practically and with dev's all have a different opinion about a 'proper project structure', but.... just asking :-) Regards, Richard Duivenvoorde [0] https://github.com/qgis/QGIS/pull/44879#issuecomment-910988820 _______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
