SYSTEM/Make loaders loadable in local

[djoproject]

Description

Addons are currently only loadable for the whole application. It could be interesting to have the possibilities to load an addon in a local context. So a procedure would be able to load an addon only for its execution.

Improve the existing "addon load" command and add some feature such:

• bool loadInLocal, default: False
• bool doNotLoadIfExist, default: True
• bool doNotLoadIfExistInLocal, default: False
• bool doNotLoadIfExistInGlobal, default: False

TODO to be loadable in local, an addon must be written following several rules, which one?

• commands of the addon must not try to access to parameter defined for the addon only in a global scope.
• or try to access to a complete manager or container
• ...

TODO create a method to check if an addon can be loader in local

Depends upon

• 109

Dependency for

• 110

[djoproject]

PRBLM 1: an addon can be loaded only once at at time, without caring about the scope. So if two thread try to load the same addon, one of them may have the message "addon already load". The import built-in will always returns the same addons object, with the lastest load or unload status.

• SOL 1.1: make addon cloneable and never load the addon coming from the module
• SOL 1.2: PRBLM 2: the loading system is not design against multithreading, if two thread try to load the same addon at the global scope, it could create a mess in the parameters
• SOL 2.1: add a good old lock on addon loading, yeah but at which place ?
• SOL 2.2