Add ability to remove a plugin from within Protege

[rsgoncalves]

[ThomasThelen]

I ran across this issue while searching for a way to disable a particular plugin.

In terms of user interface, I think a fourth column next to Qualifier, named Enabled would be sensible placement. When selected, the plugin is enabled; when unselected, the plugin is disabled. Is anyone willing to provide insight on what the backing model is where the state of each plugin can be stored??

Here's my understanding of how this would function from a user's workflow

Not saving:

1. User enables/disables plugins
2. User clicks 'Cancel'
3. Plugin state is not changed
4. User closes & opens Protege
5. User sees that their plugin changes haven't been saved

Saving:

1. User enables/disables plugins
2. User clicks 'OK'
3. Plugin state is saved globally
4. User closes & opens Protege
5. User sees their plugin changes have persisted

Things to do:

1. Add the new column; make sure it correctly reflects the state of the backing model
2. Correct checkbox state when user selects/deselects & clicks OK/Cancel
3. Modify the backing model to support the state of each plugin
4. Persist the new changes to the model on disk
5. Load the states on disk (while also loading previous formats without the state)

Questions:

1. What happens when the user clicks 'reset defaults'? Disable all the plugins?

[rpgoldman]

In the short term, just telling us where to find the plugin files so that we can remove them would be a huge help. This could be done just by adding a sentence to the Plugins preference pane for Protege.