Currently, the plugin manager loads (=activates) a plugin as soon as a plugin item is requested by the system. This takes time, because the plugin's dll file(s) have to be loaded.
This leads to a behavior we want to avoid:
If the plugin exposes resources (strings, skinfiles) as well as code (dlls), its dll files have to be loaded at startup, because the string- and skin-resources have to be loaded by the laguage system and skin engine.
We'll add another plugin state "Accessed", which is halfway between "Enabled" and "Activated". Accessed plugins have to be signed off from their item users, but their own state tracker instance isn't loaded yet.