README

A very complete plugin system to let you claim that your application supports plugins!

You will need PHP 5.4 for this to work.

Components

php artisan vendor:publish --provider="Hongyukeji\Plugin\PluginServiceProvider"

Components

Hooks

Place them in your code to execute events. Unlike several other packages, these Hooks allow interacting with the data and can hold the scope of the class.
Events

The events happen when a Hook with the same key is encountered. Events accept static methods and Closures, as well as a priority, because you can stack them and have them passing variables to each other.
Result

The object that Hooks and Events share, and return. They keep your code clean from mysterious function parameters and even more confusing return values.
Plugin

The internal package handler. Plugins are actually Composer packages. Use the bootstrap file to create new events and use the install/uninstall/upgrade hooks.
Loader

The packages utility. It looks into the folders you tell it to, finds plugins, loads them and give you the arrays.
PlugSuit (trait)

Add plugins automatically to your classes. It adds a before and after hook, and lets you override the parameters passed to the methods.

What will you have to do? You must use the Loader class to create your own administration panel and run the plugins you choose to run. Since it doesn't have any database bind (or any dependency at all), you must create an enabled/disabled system yourself.

Some examples follow.

You can go in-depth with these explanations with the following pages:

Hooks and Events

The most basic part of the package. You can use Hook and Event anywhere in your code, not only in the plugins.

<?php

use \Hongyukeji\Plugin\Hook as Hook;
use \Hongyukeji\Plugin\Event as Event;

// define an Event
Event::forge('triggerOnThis')->setCall(function($result){
	$result->set(123);
})->priority(2);

// the Hook triggers it
$result = Hook::forge('triggerOnThis')->execute();

// echoes 123
echo $result->get();

Result

We coded the result package to avoid confusion with cascading Events. This is why Events only get one parameter, that we use to call $result.

As this is where most of the mistakes are made, any unset parameter or unset result without explicit fallback will cause an exception.

Example:

<?php

// define an Event
Event::forge('triggerOnThis')->setCall(function($result){
	$increment = $result->getParam('increment')
	$increment++;
	$result->setParam($increment);
	$result->set($increment);
});

// define another Event editing the parameters with lower priority (lower number is higher priority, default is 5)
Event::forge('triggerOnThis')->setCall(function($result){
	$increment = $result->getParam('increment')
	$increment++;
	$result->set($increment);
})->priority(8);

// the Hook triggers it
$result = Hook::forge('triggerOnThis')
	->setParam('increment', 0)
	->execute();

// echoes 2 (we increased the number in each event)
echo $result->get();

// echoes 1 (we edited the parameter only in the first event)
echo $result->getParam('increment');

Plugins

We have two classes for dealing with plugin packages: Plugin and Loader.

Here's an example of how would you load the plugins you choose to run:

<?php

$loader = Loader::forge()->setDir('main', '/path/to/plugins/');

$enabled_plugins = array('hongyukeji/fake', 'hongyukeji/kynet');

foreach ($loader->getPlugins('main') as $plugin)
{
	if (in_array($plugin->getConfig('name'), $enabled_plugins))
	{
		$plugin->execute();
	}
}

Get more info about plugins.

hongyukeji / plugin

Maintainers

Details

README

Components

Components

Hooks and Events

Result

Plugins