On the NetTuts.com (Plus) site there's a new tutorial focusing on aspect-oriented programming in PHP, a shift from the usual methods of development with the goal of "crosscutting" your classes/objects by weaving in extra functionality. Their examples of this method use the FLOW3 framework.

All modern frameworks (including FLOW3) push a lot of patterns into the software stack that do a great job at separating the concerns of your business logic; among them the famous MVC that is separating your logic into different layers. However, an application is not only built on business logic alone. As it grows, you may want to implement additional services, features, plugins or plugins of plugins. You surely don’t want this stuff in your business logic! But what are your options?

For their example, they show how to implement a logger across your classes, taking it out of the actual code and implementing it in an aspect (at the "pointcut") by "weaving" it into a DocBlock comment with special annotations. They help you get the FLOW3 framework set up and show you how to "kickstart" a new project and work with its controllers and resources. They show you how to implement the Logging aspect and how to define it in your code (and where it caches the requests).

Lorenzo Alberton has posted a review of a book from Packt Publishing covering the development of extensions for the Typo3 CMS.

A couple of months ago I started working on a Typo3 project for a client, and at about the same time I was asked by the folks at Packt Publishing to review a book, so the choice fell naturally on "Typo3 Extension Development" by Dmitry Dulepov. The book, published in September 2008, covers the entire extension development life cycle, from planning to uploading it to the Typo3 Extension Repository (TER).

Starting with the table of contents, he goes through the book and shares opinions about each step of the way. He liked the book for its simplicity and straight forward content and loves the "immediate head-start" it gives to the reader. The only thing lacking was the term index that didn't seem to add much to the content due to its small size.

In a new post today, Lukas Smith asks the community, "where are all of the PHP5 CMS?"

We have tons of very mature PHP4 CMS. And yes some of them even work on PHP5, but honestly those for the most started in the days where code design in the PHP scene was not well established yet. Unit testing was only for the paranoid and coding styles were optional.

He goes on to talk about why reimplementing them in PHP5 would be such a hassle (bad coding practices?) but that there's a light at the end of the tunnel - CMSes like Flux CMS and MODx. Oh, and Java fans will be happy to see his mention of the talk about various CMSes implementing JSR-170 as well.

In a new post today, Lukas Smith asks the community, "where are all of the PHP5 CMS?"

We have tons of very mature PHP4 CMS. And yes some of them even work on PHP5, but honestly those for the most started in the days where code design in the PHP scene was not well established yet. Unit testing was only for the paranoid and coding styles were optional.

He goes on to talk about why reimplementing them in PHP5 would be such a hassle (bad coding practices?) but that there's a light at the end of the tunnel - CMSes like Flux CMS and MODx. Oh, and Java fans will be happy to see his mention of the talk about various CMSes implementing JSR-170 as well.