>>>>> "Chris" == Chris Josephes <[EMAIL PROTECTED]> writes:
Chris> 1. Create a template language specification that was easy to Chris> read and write. People using the language should not be Chris> required to have strong programming skills. Template Toolkit - check. Chris> 2. The template language should not follow Perl syntax rules, Chris> or be designed with preference towards Perl users or Chris> programmers. It should also not be used as a system to simply Chris> merge perl code in a document. Template Toolkit - check. Chris> 3. The parser needs to have a simple interface for module Chris> authors to add their own code without requiring extensive Chris> rewrites of an existing codebase. Template Toolkit - check. Chris> 4. The parser needs to understand the order and structure of Chris> the document data. The information needs to be made available Chris> to programmers writing code to interact with the parser. Template Toolkit - check. I think. Since I don't understand this one. Chris> 5. The template language should use multiple namespaces, so Chris> object code using the system don't create overlapping commands. Chris> For example, if two different objects created a tag named Chris> "address", the parser should understand which object the tag is Chris> associated with. Template Toolkit - check. Chris> Given the high number of template systems out there, it is easy Chris> to understand the reluctance or hesitation in adding another Chris> one to CPAN. But I would like to briefly cover some of the Chris> other systems out there. It is not my intention to criticize Chris> other works, but to discuss why I felt these systems didn't Chris> meet all of the requirements I wanted. OK, here we go... Chris> 5. Template Toolkit Chris> The closest match to Text::UberText is the Template Toolkit. It allows Chris> for template commands to be matched against variables or subroutines, Chris> and it has a large plug-in library which indicates that it is Chris> easy to expand. And the reason it's not suitable is... ? -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <[EMAIL PROTECTED]> <URL:http://www.stonehenge.com/merlyn/> Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
