You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been reviewing the PluginManager code and noticed it currently supports one project plugin per project (matching the project filename).
What are your thoughts on extending this to support multiple project plugins per project (e.g., plugin1.qml, plugin2.qml)?
While the technical implementation seems straightforward, the more difficult part might be the lifecycle management of multiple plugins - when and how they should be loaded, unloaded, and how they interact with each other? Any other reasons that I do not see why only a single plugin is supported?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I've been reviewing the PluginManager code and noticed it currently supports one project plugin per project (matching the project filename).
What are your thoughts on extending this to support multiple project plugins per project (e.g., plugin1.qml, plugin2.qml)?
While the technical implementation seems straightforward, the more difficult part might be the lifecycle management of multiple plugins - when and how they should be loaded, unloaded, and how they interact with each other? Any other reasons that I do not see why only a single plugin is supported?
Beta Was this translation helpful? Give feedback.
All reactions