Having templates in a DB is nice indeed but IMO you need a compile phase so
that performance do not hit the wall ...
Dear all,
I use Naoki's class with a database to generate static files. I agree a template systems needs to handle both static/dynamic information. It shall work from file/database templates. The turnkey is an object oriented structure not based on value replacement.
I bought recently a license of
http://www.phplens.com. If you are looking for a working solution now, go for it and buy a license. It is a really good product I recommend to create application models (before programming).
Phplens needs very little information to build a list/page view. Basically, it can generate an application without templates. All you need are SQL queries. Everything seems to be done with abstract builders (???).
Similarly, I would be in favour of merging abstract builders with database/file templates to:
- define (left, upper, down, right) recursive panes,
- link panes/items to SQL queries,
- place components inside panes (New, Delete, Next, Previous and Last buttons),
- apply styles.
This would be a killer-application for PEAR. With such a template system, it would take just a few days (weeks?) to program an application like Phorum or PhpMyAdmin. This would open the door to PHP on-line programming.
I will be free to work on such a system in December and January if the community needs my help. What do you think? Don't forget I am new to PEAR, therefore I am not completely sure of my technical analysis.
Best regards,
Jean-Michel POURE, Paris, France