View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0021831||mantisbt||plug-ins||public||2016-10-31 04:49||2016-10-31 07:33|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Summary||0021831: Include plugin classes in autoload|
For plugins that defines its own classes, it's useful to create an autoload procedure.
Deeper namespaces will locate in said dir:
With the corresponding documentation, plugin developers will be encouraged to namespace their plugin specific code. This avoids collisions between core functions, and even other plugins, which otherwise, are adding functions and classes to the global name space.
A plugin can then share its classes by applying the plugin-named namespace. Any other plugin can now use these classes which will be auto loaded. (The dependency was resolved if indicating "requires x plugin").
An alternative to the previous autoload strategy, is to also include non-namespaced classes from plugins.
For a namespaced class:
Still, for classes to be accesible by other plugins, they need to be namespaced with the plugin name, but requires an additional level in "classes" directory to account for this namespace.
|Tags||No tags attached.|