Download the PHP package weew/eventer without Composer
On this page you can find all versions of the php package weew/eventer. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 eventer
Simple event system
Table of contents
- Installation
- Usage
- Simple subscription
- Attaching data to an event
- Creating custom events
- Unsubscribing from events
- Event subscribers
- Existing container integrations
Installation
composer install weew/eventer
Usage
This event system allows you to easily subscribe to certain events and get notified as soon as one occurs. The most simple way to subscribe to an event is by using a string as the event name.
Simple subscription
The easiest way to create a subscription is to use callback function.
Attaching data to an event
Mostly you want to throw an event with particular data attached. The quickest way to achieve this is to use the generic events.
Creating custom events
In more complex applications I would suggest to roll your own events. This makes the code much more easier to understand since you'll never have to guess what the event name might be. It also allows you to extend your events with more complex behaviour.
Unsubscribing from events
To unsubscribe from an event you can simply pass the subscription object to the unsubscribe method on the event dispatcher.
Event subscribers
Using callbacks in your events might not always be an optimal solution. Therefore you can create event subscriber classes that get called whenever an event occurs. The class must have the handle(IEvent $event) method, but there is no specific interface that you are forced to implement.
Existing container integrations
There is an integration for the weew/container. See eventer-container-aware.
