In this post, I will discuss 5 tips and tools that the php community has provided to speed up development time and improve code quality. These should help you out if you don't already know them, but if you do I would like to hear what you use to speed up your development time.

Their five tips/tools are:

• Framework with the Model View Controller (MVC)
• AJAX Frameworks
• Integrated Development Environment (IDE)
• Database Creation/Management Software
• Object Relational Mapping (ORM)

Included for each is his personal preference and recommendation.

With the basic structure for our Framework in place, it is time to start adding functionality to it. In this tutorial we will create a template manager and database handler, bringing us a step closer to a powerful Framework fit for use for almost any project. If you haven't already, be sure to review Part 1 of this series first!

This time they look at a few different parts of the framework, namely the database handler, the template manager and loading data into the framework. The end it with an example of the simple framework in action - pulling a list of members from a database and displaying them to the page.

We are creating an MVC setup where M is Doctrine, V is Smarty and C is our own stuff we do here. The Zend Framework has been reduced to just another component library for me now, I will pick goodies when I need them.

He shows how to be "empowered, not stifled" by the framework and to combine the two technologies in a flexible, lightweight platform. His example is a simple signup form that, on submit, saves the information to the database via the Doctrine layer.

Before we begin our exploration of the architecture of the Zend Framework (ZF), it is important to discuss how a typical MVC application is built. Examining and understanding the architecture of an MVC Web application allows you to make more contextually sound choices when building your application.

He starts with a look at a three-tier architecture (presentation, application, data) and compares that to the MVC used in the Zend Framework. He talks about how ZF is a hybrid component and infrastructure framework and the coupling that it provides between its components. He also has a few criticisms namely some performance issues from this style and the lack of a module to handle model/controller dependencies.

In part one we saw how to setup our Zend_Acl instance and how to attach it to the MVC environment (by using the Front Controller Plugin), but what about setting another action for the denied access, or how does an article be edited only by its owner?, this, and some more is what we are going to see in the following examples.

This second part is broken up into a few parts:

• Using Modules
• Using Roles
• Setting the denied error action
• Using the action helper

These two tutorials are based on this proposal for the integration of Zend_Acl into the current framework is currently pending.

A design pattern is a general reusable solution to a recurring design problem in object-oriented systems. Design patterns are essentially blueprints that suggest how to solve a particular set of OO design problems while adhering to OO best good-practices (which I've recounted in my Object Oriented part of this series).

He talks about one of the most popular examples - the Model/View/Controller design pattern that is used in many rapid development frameworks for PHP (including CodeIgniter and the Zend Framework). He also briefly mentions a few others like the composite, singleton and decorator patterns.

Other parts of this series include looks at testing, refactoring and coding standards.

Last Thursday, during the Open Nordic Conference 2008 eZ Systems handed out its annual awards again. For the eZ Components award, there were four nominees, which are all recognised for their support of the eZ Components project.

Nominees included Stefan Marr and Falko Menge, James Pic, Andreas Schamberger and Freddie Witherden. The winner was James Pic for his work with the upcoming MVC additions to the component framework.

So, what is wrong with Zend_Acl and the current MVC implementation in the Zend Framework? there is nothing wrong, it is just that it gets not too obvious for developers how to achieve an optimal integration between these two important parts of the framework.

He talks about the proposal that's out for a potential update to the component, the two key points being the front controller plugin and a new action helper. He includes some sample code showing how to set it all up including a "denied" controller to handle the failures.

ActiveRecord is fine. It is a tool that does just what it's designed to do. What sucks is when developers try to make it do other things than what it's intended to do.

He cites his work with the Zend_Db component and how Mike Seth gets it right when he says that the pattern shouldn't be "ActiveRecord-View-Controller". He compares the ideas of a true Model in an MVC application with the incorrect ideas that many developers seem to hold.

A Model is a class that provides a logical component of your application domain. Models are products of OO design, which is a development activity I see get very little attention in the developer blogosphere or the developer tools market.

Models can reference one or many (or no) database tables and are not where the hard work is being done. That's saved for the ORM (or ActiveRecord) to do.

Finally, I found some time to take CakePHP for a spin. I've heard some really good things about it, and I've been trying to get some time to try it out. I installed the framework and went through the tutorial on building a simple blog application. I have to say I'm quite impressed.

The post briefly introduces the Model-View-Controller method the framework follows and shows some of the features/benefits it brings with it - the low entry level, its speed, and whether or not it makes for a good "first framework" for other developers.