Ticket #1533 (Closed: invalid)

I can see why you are suggesting smarty.

Some reasons against it: Smarty is not as good as the campsite template language which is well designed for the job, although smarty is more popular.

Here to blow my own trumpet and suggest using straight php and slightly marked up html. I have a template system which renders tagged html into php classes so they can be subclassed and superclassed and pass parameters etc.

If you are interested read up here: http://www.liddicott.com/templates.html

I'm due a new release which fixes some bugs and allows the ability to replace <object> tags at runtime with target-browser-specific content instead, but anyway...

The reason I suggest this template mechanism is that it avoids embedding logic into the design, but leaves that in the php. The designers html (which gets converted to php) and the programmers php sit side by side but can each be revised independently.

Sam