Enable or disable plugins on a per-project basis

[elisee]

No description provided.

[florentpoujol]

Some though :

So we should have a settings editor, probably part of the common settings tool which edit a resource.
That resource should reference the inactive plugins, so that plugins are activated by default.

The UI is basically a list of plugins and a checkbox to turn them on/off (+ fancy style/color-code, alphabetical/per autor/per statut triage or stuffs like that).

Assets/tools/actor components/TS definitions of deactivated plugins shouldn't show-up in the client nor in the builds.

Should the plugins themselves be notified and do something when they are turned on/off ?
Also a plugin itself shouldn't make so that it couldn't be undeactivable (except the settings one).

I feel it should be something passive that has effect only on the project/client.

For assets we shouldn't be able to deactivate a plugin if an asset of that type is already in use in the project.

For resources, I think we should keep the file when the plugin is deactivated but allow to delete unused resources (like for trashed assets).
(I don't think there is plugins that used resources from other plugins.)

When plugins are turned on/off, should the client update automatically (in order .to reload the asses/components/definitions) ?
Forcing to reload the project seems acceptable to me, at least for a first step.