Thanks again, i can't maintain a docbook documentation, the only format
i can write/read/think on is plain text. I've done yesterday a dirty
text=>docbook converter based on an uggly text=>html library i wrote a long time ago to identify titles, paragraph, examples, etc... but it will never be as clean as a manually written docbook :)
I have some code based around XML transformer, that converts Openoffice files to HTML (paginated), It's plausible that I may get time to modify it to generate docbook (although I thought somebody had tryied that already)
I think you will find that the package will get used alot more if there is good documentation - in the manual - while phpdoc comments/text files are nice.. - nothing beats a good manual.
HTML_Template_PHPTAL is wrong
XHTML_Template_PHPTAL is not entirely right
XML_Template_PHPTAL is not entirely right but my prefered
This was kind of gone through before - I use flexy as a template engine to parse/output xml,html,emails,rtf,csv.. (as do people with most of the other engines) however the feedback I got was that nobody could really see why we needed more than one template category - I have to agree more now - it would be confusing for the end users. - hunting all over the manual/cvs/web site for template engines.
I don't know which one to choose and i don't have other ideas right now :)
- concerning class naming convention, as there shouldn't be any conflict with the PHPTAL name, i'd like to keep PHPTAL class name shortcut instead of XXX_Template_PHPTAL class. Same for interfaces : PHPTAL_Cache,
PHPTAL_SourceResolver and PHPTAL_SourceLocator.
That is for users, they don't like to type 128 characters class names
(neither do i).
That makes locating source file difficult (which is one of the beautys of pear) - we have to live with the current standard until you start using PHP5 in which case name spaces should solve this.
Regards
Alan