__construct()
__construct(\Pico $pico)
Constructs a new instance of a Pico plugin
Parameters
\Pico | $pico | current instance of Pico |
Common interface for Pico plugins
For a list of supported events see DummyPlugin; you can use DummyPlugin as template for new plugins. For a list of deprecated events see \PicoDeprecated.
You SHOULD NOT use deprecated events when implementing this interface. Deprecated events are triggered by the \PicoDeprecated plugin, if plugins which don't implement this interface are loaded. You can take advantage from this behaviour if you want to do something only when old plugins are loaded. Consequently the old events are never triggered when your plugin is implementing this interface and no old plugins are present.
If you're developing a new plugin, you MUST implement this interface. If you're the developer of an old plugin, it is STRONGLY RECOMMENDED to use the events introduced in Pico 1.0 when releasing a new version of your plugin. If you want to use any of the new events, you MUST implement this interface and update all other events you use.
__construct(\Pico $pico)
Constructs a new instance of a Pico plugin
\Pico | $pico | current instance of Pico |
setEnabled(boolean $enabled, boolean $recursive = true, boolean $auto = false) : void
Enables or disables this plugin
boolean | $enabled | enable (true) or disable (false) this plugin |
boolean | $recursive | when true, enable or disable recursively In other words, if you enable a plugin, all required plugins are enabled, too. When disabling a plugin, all depending plugins are disabled likewise. Recursive operations are only performed as long as a plugin wasn't enabled/disabled manually. This parameter is optional and defaults to true. |
boolean | $auto | enable or disable to fulfill a dependency This parameter is optional and defaults to false. |
thrown when a dependency fails
getPico() : \Pico
Returns the plugins instance of Pico
the plugins instance of Pico