Re: Re: renderers and refactoring

Sam Liddicott wrote:

----- Original Message ----- From: "Alan Knowles" <alan@akbkhome.com> To: "Sam Liddicott" <sam@liddicott.com> Cc: "Pear Announce" <pear-dev@lists.php.net> Sent: Sunday, July 27, 2003 1:41 AM Subject: Re: [PEAR-DEV] Re: renderers and refactoring

Ok the base work of this is now done and in CVS I've not hooked it into the live code yet, but most of the basic logic and layout is there: New: HTML_Template_Flexy_Compiler : Factory and Interface for compilers HTML_Template_Flexy_Compiler_Standard : the existing general Token toString methods + the token build code. HTML_Template_Flexy_Compiler_Standard_Tag : The standard namespace html tag interpreter HTML_Template_Flexy_Compiler_Standard_???? : in theory support for tags <????:mytag ....> HTML_Template_Flexy_Compiler_Class should probably extend Standard HTML_Template_Flexy_Compiler_Simple should probably just extend Compiler. it might work by just replacing the ->_parse() call in flexy with $compiler = new HTML_Template_Flexy_Compiler($this->options); $compiler->compile(); although I still need to modify the code to compile text as well as files.

I've now finished my code in standalone mode using a lot of your ideas and am ready to implement it against the new flexy architecture. Where in CVS should I check my files in to? You may not want me to clutter up the Flexy stuff and want mine be a seperate package which depends on yours? HTML_Template_Flexy/HTMLClass ? HTML_Template_Flexy/Flexy ? HTML_Template_Flexy/Flexy/Compiler ? I'm guessing most of it should go in

HTML_Template_Flexy/Flexy/Compiler/Class.php HTML_Template_Flexy/Flexy/Compiler/Class/* It means rather long classnames.. - but thats the downside we have without namespaces :) Regards Alan

Sam