Chore: Applications addon decouple of logic #621
Merged
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.
Changelog Description
Moved some amount of applications logic to applications addon. Core still has to know some logic of applications addon but not all of it.
Additional info
The biggest disadvantage is that core addon has to know how to create action classes, their icons, labels if are enabled/disabled tc. which should be in charge of the applications addon. Applications addon is also providing the icons.
Selection object in launcher has support to get project settings.
Applications addon did not yet change the logic, only has it available, so old ayon core will still work, and new ayon-core can work with both new and old applications addon versions.
Because we're planning how applications addon work this is "must have" PR.
Testing notes: