This repository was archived by the owner on Jun 3, 2024. It is now read-only.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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… 😄