Download the PHP package hongyukeji/plugin without Composer
On this page you can find all versions of the php package hongyukeji/plugin. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download hongyukeji/plugin
More information about hongyukeji/plugin
Files in hongyukeji/plugin
Package plugin
Short Description A plugin system for PHP, with cascading events.
License MIT
Homepage http://www.hongyuvip.com
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package plugin
Hongyukeji PHP Plugin system
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
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, Events and Results
- Plugin packages
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.
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:
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:
Get more info about plugins.
