What I miss in the feedback I got from my previous post was people acually using VCL/PHP for enterprise applications and how that is working. From what I can tell the usage of Exceptions is still limited to the 3rd party libs such as Zend Framework which are included with VCL/PHP. That's a bit interesting.

He mentions one big issue that several people pointed out with the VLC implementation - the class name prefixing (or lack there of) and the problems it could cause in the future. Prado uses naming conventions that keep its classes out of the move generally named realm. He also touches on the quality of the code behind the VLC implementation, noting that while it might work well for smaller projects, there's more of a potential for failure on enterprise-level usage.

As of now, we are moving through the era of web application frameworks. That's the landscape we are surrounded with. Plenty of frameworks have been built during these years broadly categorized under software frameworks, web application frameworks and JavaScript frameworks (or libraries), and plenty more are being developed.

He starts with these frameworks:

• CakePHP
• CodeIgniter
• Symfony
• Prado
• Django
• Ruby on Rails

He looks at the non-PHP frameworks first to see how difficult they'd be to get into. Despite reservations about the different language structure, he shows favoritism towards Ruby on Rails. He has reviewed the PHP frameworks yet, so it's not a final decision.

I've been asked on the forum about my preferences in frameworks and I wrote a few thoughts about it.

These comments include the fact that eighty percent of his code is not in frameworks, that the Zend Framework is the more flexible of the group and that the right tools, methods and language structure is the real key to making for successful software development.

My favorite PHP framework just got a new release, adding several new components and fixing 30-ish bugs. The bundled JavaScript libs (Prototype / script.aculo.us) have also been upgraded, so that should help lots of people struggling with the old versions.

You can download the framework from its website and, if you're new to it, check out the tutorial to get you started. Prado is a free PHP5-based rapid application development framework that doesn't go with the usual MVC format of most frameworks. It opts instead for "logic be stored in classes and presentation in templates".

The December issue of International PHP Magazine includes my latest article "Seamless AJAX with PRADO - An introduction to ActiveControls". In this article I discuss some AJAX design patterns and show you how to make use of them in AJAX enabled components that ships with the PRADO framework.

More information about this issue (and subscribing to the International PHP Magazine) can be found on this page of their site and details on the PRADO framework are over on the project's website.

This kind of tool is something that ASP.net has had for a long time (ie Visual Studio.net). Not only does it make the development process easier when it comes to building applications, but it also handles setup of applications, default configs etc. [...] My impression is that most PHP developers (at least above hobby level) works on Linux based workstations, so I imagine getting a strong user base could prove to be difficult.

That said, he has his reasons for why Prado should have been the framework of choice including the exception handling gap between the two (Prado on top), validation controls, how they use global variables and the rendering of HTML/XHTML by each.

From te post by javalizard:

I've been wanting to share with all you something new and special. I've needed to use Wordpress Multiuser as blogging software (it's supported and has new releases once in a while and people know how to use it) with PRADO. Auxiliary is the integration of BBPress too. Basically, it's a single login system for prado, blogs, and forums.

This setup lets you manage user information (roles, permissions, abilities) for WordPress through PRADO, handles user authentication and applies WordPress code libraries (actions/filters) and plugins.

Originally, the story came from a forum post where Timani describes his application as "80% finished" with things like optimization, meta tags and more content to still be added.

In the interview they find out a bit about Timani, what he was using CakePHP for and why he made the choice to go with PRADO over Cake. Also included are some of the differences/things he misses about using Cake over PRADO.

PHP frameworks is the newest buzz word that is spreading the PHP community due to the threat posed by the famous Ruby on rails. Now everyone seems to look like working on such frameworks. The problem with this there is so many frameworks out there with different pros and cons that it is a hectic job to choose the right one.

They have a short list of frameworks, five of them - Symfony, Prado, CakePHP, the Zend Framework and CodeIgniter - and for each list out a few quick pros and cons for their use. Be sure to check out the comments for lots of other great framework-related comments as well.

PRADO is a component-based and event-driven framework for rapid Web programming in PHP 5. PRADO reconceptualizes Web application development in terms of components, events and properties instead of procedures, URLs and query parameters.

Recent updates to the blog include an interview with Dario Rigolin of foxcoverplay.com and several Prado Watch editions. Keep checking back for the latest updates on this great framework.