You are viewing revision #2 of this wiki article.
This version may not be up to date with the latest version.
You may want to view the differences to the latest version or see the changes made in this revision.
These features provide endless possibilities and unbelievable flexibility, but as current documentation does not give more than a few examples, it might be difficult to fully understand their internals and requirements.
It should be noted that they do mostly the same thing. You can attach behaviors and event handlers to components to modify the components' behavior.
Events ¶
It is useful when you want to interrupt the normal application flow without extending base classes.
For example, enabling gzip compression on the output could be done via extending CWebApplication. But because there are entry points for event handlers, one can do this:
Yii::app()->onbeginRequest = create_function('$event', 'return ob_start("ob_gzhandler");'),
Yii::app()->onendRequest = create_function('$event', 'return ob_end_flush();'),
You can create an event handler -- which is simply a method in some class with a specific signature -- and attach it to the event of an object. You can add as many event handlers as you wish, from as many objects as you wish. If the event handler is, effectively static, then you can create the object as you assign it:
$test_comp->onSomethingGoesOn = array(new SomeClass, 'eventHandler1');
$test_comp->onSomethingGoesOn = array(new SomeOtherClass, 'eventHandler2');
$test_comp->onSomethingGoesOn = array(new YetAnotherClass, 'eventHandler3');
As long as you have a handle on the object, then you can add an event handler to it.
At some point, you can then raise the event with something like one of these:
$test_comp->onSomethingGoesOn(new CEvent($this));
$test_comp->onSomethingGoesOn(new CEvent());
So, basically, it allows you build a list of function calls that can later be executed, in the order they were added. It can save you passing around a lot of object refs and building conditional code, since you can still raise the event, even if it doesn't do anything.
Behaviors ¶
Behaviors are simply a way of adding methods to an object. In an OO language like Ruby, it's quite possible to start with an completely empty object and simply build its behavior as you go along. Yii provides this behavior with a little magic. The key is that the class you wish to add the behavior from must extend Cbehavior.
class SomeClass extends CBehavior
{
public function add($x, $y) { return $x + $y; }
}
Then use with:
$test_comp = new TestComponent();
$test_comp->attachbehavior('blah', new SomeClass);
$test_comp->add(2, 5);
So, in this case, you are extending the functionality of an object with functionality of another object.
After studying this cookbook page it is encouraged to reread the corresponding guide page as it contains advanced information (for example, if you are familiar with interfaces, you might find it enough to implement IBehavior before extending CBehavior).
Events in real life
I've looked anywhere to find a real life example of events but nothing... finally with help of google the examples found in a really useful blog (http://blog.mbischof.de/kategorie/yii/). it was not in English but again google helped me (+ some manual edits), have a try:
After a user registration can happen many things:
Actions are executed when certain events occur (Observer Pattern)
When a user registers, I want to execute certain actions.
I define a new event onNewUser in User-model:
public function onNewUser($event) { $this->raiseEvent('onNewUser', $event); }
which is executed after the record has been created:
public function afterSave() { if ($this->isNewRecord) { if ($this->hasEventHandler('onNewUser')) { $event = new CModelEvent($this); $this->onNewUser($event); } } parent::afterSave(); }
in my controller, I can define actions to be executed then:
public function hello($event) { $user = $event->sender; var_dump($user->firstname, $user->lastname); } public function hello2($event) { $user = $event->sender; var_dump($user->email); exit; }
and yet I need to attach these two actions to my onNewUser event:
public function actionCreate() { $model = new User; if(isset($_POST['User'])) { $model->attributes = $_POST['User']; $model->onNewUser = array($this, 'hello'); $model->onNewUser = array($this, 'hello2'); if ($model->save()) { $this->redirect(array('show','id' => $model->id)); } } $this->render('create', array('model' => $model)); }
As my friend mentioned in another comment in your projects you should use Events in a way that helps you make thing clean and faster. here we have seen just a simple example :)
What about adding properties in a behavior?
The article makes it seem as if a behavior is only for adding methods. Is this the case?
Behaviors add both properties and methods to objects
Behaviors add both properties and methods to objects. They support getters and setters as well.
@myView
You my friend deserve a medal :)
addition to "Events in real life"
This is an addition to Events in real life comment.
First of all, I think this practical example is the best one I could find (thanks to http://blog.mbischof.de/yiiframework-events).
I'd like to add a couple of clarifications.
$model->onNewUser = array(new TestObserver(), 'hello'); $model->onNewUser = array(new TestObserver(), 'hello2');
in your controller (the last piece of code in "Events in real life")
Events & Behaviors : Under the hood
Hey guys,
If you want to really be an expert in this "events & behaviors" stuff then I recommend you to read this useful, 3-part article, from PHP-Master:
Under the hood of Yii's component architecture
easy :)
@RKK
How I wish I saw you comment 3hrs ago. Best explanation on the web. thanks
Under the Hood of Yii’s Component Architecture, Part 1
@RKK
Thanks for the example and the link. I would like to say the link is now a 3 part series and has a new URL Under the Hood of Yii’s Component Architecture, Part 1. If you are a newbie like I am it is very helpful.
Alternate tutorial
If anybody is confused by this tutorial but still wants to learn more about events, I will give you the following example presented as a single file. The example is taken from the forums.
The summary of this example: You initiate an action on your controller to get a typical web page. In the controller, you use a custom component class that was created (Data in this example) with methods to do whatever it was that needed to be done (add in this example). But you want to modify or extend the ability of the component to do other things without physically touching the file or making a copy of it, but by adding random functions while using the component in your code just for that one instance of use. You want the function to be executed at a certain moment in the component's operation, plus you want the function to have access to whatever variables are available at that moment.
So you create the controller with an action, use a component (Data), create/use a function that uses component's internal variables, and add the function to the component.
On the component side, you bookmark a place where you want the custom functions to be executed and make variables available to that bookmark.
class Data extends CComponent // our component is Data { public $id; public function add($var1) { // insert variables into new object. Object will be made available to other functions $variables = new CEvent($this, array('var1'=>&$var1,'var2'=>&$this->id)); $this->onAdd($variables); // bookmark to insert custom functions // and avail variables to custom functions //statements that will add the data } public function onAdd($variables) // the bookmark must execute raiseEvent { $this->raiseEvent('onAdd',$variables); // all custom functions are executed here } } class SiteController extends CController { public function actionIndex() // when page site/index is launched { $data=new Data; // initiate component $data->id=$id; $data->onAdd = 'checkWhatItIs'; // add custom function $data->add('hello'); } }
For more info: http://www.yiiframework.com/forum/index.php/topic/3739-request-for-component-event-example/
Confused!!!
where to write the code below i.e. to attach the event to a handler
$test_comp->onSomethingGoesOn = array(new SomeClass, 'eventHandler1');
If you have any questions, please ask in the forum instead.
Signup or Login in order to comment.