yes, but you won't like it. :)

It's use one of the many template systems, especially for HTML.

You can role your own, but at the end you will reinvent the wheel.

Personally I'm stuck with a system at $work where I have to roll my own :/

Another best practice is MVC ... well separation of code and templates at least.

yes, but you won't like it. :)

You know me too well - LoL
Seriously - It's not so much a question of not liking it...I have tried creating a template and found it more difficult to maintain than not doing so. Although as explained in Re^4: Here documents in blocks I know how to improve it thanks to the Monastery and that alone may be sufficient to revisit this. Add an existing templating system and this option is becoming more attractive.

Part of the problem is that I don't usually have the luxury of time to learn a new way to do things. We have a business need and I have to find a solution. Speed is often more important than elegance. Incremental learning I can do but finding the time to learn a whole new methodology or framework is mostly just not possible.

> I don't usually have the luxury of time to learn a new way to do things.

well, yeah.

But you have enough time to ask how to improve the old ways you do things? ;-)

shrug! :)

Cheers Rolf
_{(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery}