This PR restructures and removes MGV's "over-modularisation" - taking away complexity where it makes sense. After this is finished, the basic repository stuff should be working "as usual" again.
[x] Move former RepositoryModule to "Ui" directory, to later compile it into main app.
[ ] To solve: Why don't files show in project tree?
Screenhot:
@scunz
I'm currently moving the application modules into a central "Ui" folder (we can rename that later, but IMO it fits best). Please help: I don't understand, why the "new" source/header files don't show up in QtCreator yet (see screenshot). Could you have a look into Ui/Repository/CMakeLists.txt? Other than that, I'll stick with the RepositoryModule as the first module to "merge" into the main application's source tree as a non-optional component. Later, this should provide all the user interface actions to interact with the yet-to-come repository concept, located in RepoMan… at least I got something started… :smile:
Long time, but finally back to work… :)
This PR restructures and removes MGV's "over-modularisation" - taking away complexity where it makes sense. After this is finished, the basic repository stuff should be working "as usual" again.
RepositoryModuleto "Ui" directory, to later compile it into main app.@scunz I'm currently moving the application modules into a central "Ui" folder (we can rename that later, but IMO it fits best). Please help: I don't understand, why the "new" source/header files don't show up in QtCreator yet (see screenshot). Could you have a look into
Ui/Repository/CMakeLists.txt? Other than that, I'll stick with theRepositoryModuleas the first module to "merge" into the main application's source tree as a non-optional component. Later, this should provide all the user interface actions to interact with the yet-to-come repository concept, located in RepoMan… at least I got something started… :smile: