Re: Re: renderers and refactoring

Then you have to get all the different template maintainers to agree to use that model which I would imagine could prove to be difficult. It is a good idea though. -D On Wednesday, July 23, 2003, at 06:26 PM, Joshua Eichorn wrote:

Just a thought but wouldn't it make sense to create something like HTML_Template_Model while your refactoring and then move to all templates in PEAR to use this same model for loading the variables into, so that templates can at least have alarge portion of shared api. -joshua eichorn Sam Liddicott wrote:

Alan Knowles wrote:

Flexy: HTML_Template_Flexy_Compiler_Full <-- the current compiler engine (a mix of whats in Tokens and Flexy compiler() calls. HTML_Template_Flexy_Compiler_Class <-- sams Code to generate classes - as an extension of Compiler_Full

The structure and the factories all seem fine, I would also want a simple interface suhch as this: class_from_html($htmlfile); $page=new $mypage(); $page->output(); class_from_html would wrap the caching, the factory calls, etc, and just cause the class to be declared. Like a more clever kind of reqiure_once() Is this acceptable? Sam

-- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

-- Darrell Brogdon Brogdon Internet Services, LLC Phone: 770-918-9042 Email: dbrogdon@brogdon.biz http://brogdon.biz 1024D/D7FB6981 3CB8 A14D 1662 8351 11F6 40C1 D205 2D97 D7FB 6981