I am yet to write the last article of the Yii Session series. I just decided to write something about the scenarios in the Validation feature of Yii framework. Scenarios are a very useful tool for adding different validations rules for different cases on the same model. In a real life situation, you would require one validation rule for user registration but the same rule might not be applicable to the User login. Scenarios help you define validation rules for different situations within same model.

He shows you how to set up a "rules()" method in your model and a few validation configurations inside it - ensuring the password and email are set, checking the length of the password, etc. Then, by calling the "validate()" method on the model, you can easily apply these rules and check the pass/fail status.

Finally we figure out the basics of Yii. While working on basic of Yii, I want to rewrite the url to SEO friendly. So I started to search on google, forum got useful information here http://www.yiiframework.com/doc/guide/1.1/en/topics.url To hide the index.php from url I did changes in config/main.php [...] and I created new .htaccess file in the same directory as my index.php file.

The changes are pretty simple - it's mostly a change to the "urlManager" setting to provide some rules for mapping controller and actions to the right place. The .htaccess file uses Apache's mod_rewrite functionality to grab the requested URL and remap it back to lay on top of the "index.php" front controller for the request.

A behavior, as it is called in Yii, is a manner of combining objects at runtime to extend an object's functionality. Behaviors are an excellent way to decouple code and keep ever expanding systems maintainable. [...] We can not reuse our code effectively because PHP doesn't support multiple inheritance. The Yii behavior system is a way of achieving multiple inheritance by implementing mixins.

He gives an example of working with a user that's connecting to your application just to get to a third-party billing system. They show how to take this functionality our of your generic "User" class and make a behavior out of it. This functionality can then be attached to the User object (via an attachBehavior call) and used directly. He gets into how Yii does this magic, showing how it appends it to a special value in the class and the __call method checks the method call to see if it exists in one of these special classes.

An application event is something that occurs which might be of interest to other bits of code. A standard event in most GUI applications would be a "click" event, but the sky's the limit and what events you define is really up to you. [...] The details can be provided by application-specific modules allowing you to keep individual requirements separate from your reusable code. Events allow you to attach a potentially unlimited amount of functionality without changing your core modules and components.

In his example, he shows how to create an event handler that is triggered when the user registers on the site. This event (CEvent) is then registered with the system and is attached via a call in the controller's "init" method.

There's been a lot of buzz surrounding the use of frameworks for quite a while now and there are many great PHP frameworks to choose from. I was blown away by the simplicity and power of the base CComponent class in the Yii framework. [...] Every class in the framework extends from the CComponent class, which means that all subclasses work as components and can raise and handle events as well as be reusable and configurable. This packs a lot of punch for such a little class!

In this first post of the series, he looks at how this base class lets you work with class properties using the magic getters and setters. He includes some code showing how to set them up and how to use it to configure your object by passing in other component and their configuration.

Now you could run [your] tests manually after each change by typing 'phpunit ', but we were looking for something a little more comfortable. We want to decrease the transactional cost of running the tests as much as possible to make the lives of our engineers more pleasant. Making testing easy is the only way the engineers will run the tests frequently.

Instead they opted for Watchr, a tool that keeps an eye on a list of files looking for a change. When one happens, a process is fired off - in this case a PHPUnit run. To make it even easier to see feedback, they integrated it with Growl to show pass or fail results. He includes the source for his Watchr script to help you get started.

Frameworks have been the topic du jour here at PHPBuilder.com, with numerous recent articles covering DooPHP and Fat-free. In this latest stop on the framework tour, we'll check out Yii, a relatively new framework (less than three years old) that boasts an impressive array of features and an equally impressive array of users, among them the enormously popular Stay.com.

He walks you through the install (downloading the latest version) and shows how to use the command-line tool to automatically generate the basic website structure. He continues on showing how to update the main page and template, how to get it connected to a MySQL database and how to use the Gii tool to create basic admin forms for working with the tables.

Ext4Yii is essentially a bridge between these two projects, which aims to integrate Ext JS as an extension for Yii. Ext4Yii is implemented as a templating system, which consumes XML models where you define widget elements like buttons or handlers (in embedded JavaScript code which can take advantage of Ext-powered methods and objects).

This templating system integrates directly with the Yii framework's structure and gives you access to a lot of the ExtJS objects without the need for multiple calls to .js files. The tool also comes with a bundled plugin for Netbeans that can help you get started quickly (rather than having to work out the syntax by hand from the start).

Fabien Potencier released Symfony 2.0.0alpha1 last week, along with some benchmarks showing its performance. I am glad to see that Fabien used my benchmarking system and methodology, and am happy to see that he is paying attention to the performance of his framework. I take this as an acceptance on his part that my methodology is legitimate and valid, and that it has value when comparing framework responsiveness.

Paul points out that Fabien's reporting is a bit inaccurate and goes on to talk about how his numbers are off and what a more correct version of the benchmarks would look like. He takes the testing methodology that Fabien used in his process and reapplies it to his benchmarking process using clean Amazon EC2 instances and Siege to run some response/request testing on software running on each framework. Numbers are run for three different comparisons and results are found...but you'll have to read the rest of the post to find those out.

It was over a year ago that I wrote the article that compares CodeIgniter and Kohana. Since then both CodeIgniter and Kohana have seen major progress with the release of CodeIgniter 1.7.0 and Kohana 2.3. [...] Let's see how they compare with each other.

He judges on a list of criteria including licensing, supported databases, community, documentation and modularity. Ratings are gives for each framework (like "Excellent" or "Good") on each item with over twenty aspects considered.