Symfony Blog

In the last part, we have seen how to move code from the Controller to the Model. The principle is quite simple, you want thin controllers and fat models. Today, we will see how the new form framework can help us keep this clean separation of concerns.

Today, we will start by refactoring some actions from the product module. As symfony is modeled after the MVC design pattern, Vince was pretty confident that he did the separation of concerns pretty well. The Controller role is to get data from the Model and pass them to the View. Pretty simple, no?

Refactoring implies a lot of changes in the code. It means that you need a way to check that you don't break anything during the process. So, before beginning the refactoring session, I asked Vince about its unit and functional test suite. But Vince had no unit or functional tests. So, we decided to write some functional tests before starting the refactoring.

Read release notes

Some time ago, Vince, a seasoned PHP developer, asked me to have a look at his very first symfony project, a product store. As the mistakes he did were quite common, I decided to tell you the story of this refactoring session in the hope you will learn as much as Vince did.

Today, Doctrine gained its citizenship in symfony 1.2.

I provided a training session at the Symfony Camp 2008, and after having talked with some of the attendees it looks that it can be difficult to find symfony trainings in every country.

This week, the second edition of the symfony camp was held, with more than 80 attendees. In the technical talks, the great new features of symfony 1.2 were shown and the future of symfony 2 was outlined. Besides, the Symfony community showed this week its strength with a massive support for symfony inclusion in NetBeans.

The second and last conference day of symfony Camp was today.

symfony Camp started yesterday with a symfony 1.1 training but today is the first conference day.