Henrik has posted the second part of his look at using Doctrine, this time in combining it with Smarty. (Check out part one here).

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.

On the ProDevTips blog, there's a quick post with an example of a Zend Framework/jQuery and Smarty combination he came across while working up a CMS system:

The result is an interface where an administrator can settle money transfers. It will start with displaying a list of all requested transfers, when the administrator has manually finished transferring cash to each recipient's account he can use this interface to update the database.

He briefly explains the code, a combination of a jQuery function run on page load, a Smarty template for each transfer's information and the backend code through the Zend Framework to handle the requests issued from the button click.

Jordi Boggiano has blogged about a new PHP5 templating engine called Dwoo that's just been released for download.

Early this year I wanted to rebuild my template engine to have something stronger to work with, so I started thinking about it and then asked myself why I didn't use one of the available engines out there. The fact is that - and I guess I will lose many of my few readers here - I am not fond of using php itself as a template engine (with Savant or similar).

Features of the templating engine include a striking similarity to Smarty's methods, the fact that its code is scope aware, it has template inheritance and comes with a plugin system that can be extended as you see fit.

You can get complete information about the engine from the Dwoo homepage.

The PHPEveryDay.com website has posted more tutorials recently - this time about working with Smarty.

• Smarty Template: Introduction
• Smarty Template: Installation
• Smarty Template: My First Smarty
• Smarty Template: Basics That You Must Know
• Smarty Variable: Associative Arrays
• Smarty Variable: Array Index
• Smarty Variable: Object
• Smarty Variable: Variable at Configuration File
• Smarty Variable: Reversed Variable

Check out PHPEveryDay.com for more great PHP articles and tutorials.

On the phpRiot blog, Quentin Zervaas has posted a quick tutorial about using the Iterator interface (part of the Standard PHP Library) together with Smarty to loop through some objects:

The PHP 5 Iterator interface is very useful for defining custom behaviour for looping over objects, however I just noticed that looping over such objects in Smarty will not work correctly. Smarty will in fact cast an object back to an array.

He includes code examples of his problem to illustrate and shows how he got around the problem - a getData() function he defined that just returns the array from the object.

In a new post to the Zend Developer Zone, Brett Zamir has posted a new tutorial that talks about using the Smarty templating system to create what he calls the HYSOCAMTT templating approach ("Have-Your-Separation-Of-Concerns-And-Mix-Them-Too".

This article aims to highlight a approach which allows one to separate everything from one's business logic to one's design logic, to XHTML from CSS, one's Javascript from the page structure, etc., while at the same time being able to be lazy and include, for example, CSS information within the same document (template) as one's XHTML

The tutorial uses an extension for Smarty called SmartyDocB that makes the documentation side much easier. He works through the templating process and includes some of the code for the .tpl files to get you started.

He also includes some future goals for his idea, a mention of XSL templating, XQuery and the potential for templating across programming languages to make your site even more flexible.

Scott Klarr has pulled together a listing of the top cheat sheets that he's found out there relating to PHP (and things surrounding it) like:

• this one from blueshoes.org
• a sheet covering filtering and escaping
• a Smarty cheat sheet
• a few covering WordPress
• and ones covering CakePHP and Drupal

Check out his page for more (and thumbnails for each).

On the {H{Riot.com site today, there's a new tutorial talking about how to customize your site's Smarty templates a bit more using external plug-ins, specifically one for making those "code block" sections seen all over the web.

We will first learn how block plug-ins can be used in your templates, and then learn how to create our own. Once we know how to create a block plug-in, we will cover a practical example that will show you how block plug-ins can effectively be used in your own web sites.

The tutorial assumes that you already have Smarty installed and that you're familiar enough with it to know how to work with the plug-in system right away. They include some samples of how it can be used (a default block, formatting it with HTML) and, of course, how to integrate this (PHP code and all) into your template and push your content into it.

On the PHP in Action blog today, there's a quick new post that talks about not only using the Smarty templating system but also a method for testing it to check for any kind of possible failure.

As I mentioned in my blog post on Paparrazzi testing, Uncle Bob (Robert C. Martin) has discussed how to test web templates or server pages. Since I'm currently working with Smarty templates, I wanted a simple way to run tests on them without needing to deal with a web server and the page navigation in a full web application.

Thankfully, he's found a nice, simple method for running tests against the Smarty engine (and includes that in the post - an interface to Smarty and the example test case to run against it).

ProDevTips.com has posted part nine of their long-running series about using the Zend Framework (and Smarty) to create a CMS/Community website.

This piece covers creating a proper folder structure so that we can have a skin system. I've also created a folder for the admin section which is fully contained with it's own controllers folder and so on. Another unrelated change that has happened since the last part is sub menu logic which we will also take a look at.

They make updates to the bootstrap file to introduce another controller directory and, inside of that, create the Administrator controller and integrate it with a Smarty template to show different menu items if an admin user is logged in.