Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generic solution for enabling/disabling plugins #309

Open
klues opened this issue Apr 12, 2019 · 0 comments
Open

Generic solution for enabling/disabling plugins #309

klues opened this issue Apr 12, 2019 · 0 comments
Labels
enhancement Priority 3 The issue is nice but only has low priority

Comments

@klues
Copy link
Contributor

klues commented Apr 12, 2019

Often it makes sense to be able to enable or disable plugins at model runtime, e.g. enabling the ComPort plugin only if it is needed and preventing error messages at startup if the COM port is not available.

#295 implements enabling/disabling for the COM port plugin, #294 for the Averager plugin.

It would be great to implement a generic solution for enabling/disabling plugins so that it isn't necessary to implement it multiple times in multiple plugins. Some solutions could be:

  1. A complex solution for this could be to implement composition of bundle descriptors, so we could define generic functionality.
  2. A simple solution could be to create a plugin which allows to control the lifecycle and properties of any other plugin.
  3. define some generic functionality for enabling/disabling a plugin in a superclass DeactivatablePlugin and Plugins can derive from this class
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Priority 3 The issue is nice but only has low priority
Projects
None yet
Development

No branches or pull requests

1 participant