The problem with having PHPTAL generate the documentation is that some templates might not be used often, for example one for a obscure feature of the site, so the documentation might not be uptodate.
If you think this is what you actually need, you can use PHPTAL::setPreFilter() to register a callback which parses the template looking for comments and stores them wherever you wish. Iván On Fri, May 30, 2008 at 11:16 AM, Anton Andrievskij <[EMAIL PROTECTED]> wrote: > No I think the right idea is to have this documentation in XML format > directly inside template and to have PHP tal to output this documentation. > So why not to allow PHPTAL to output this documentation just like it outputs > other contents? Then developers may have access to the documentation to > always latest version of template. > > Anton > > On Fri, May 30, 2008 at 12:09 PM, Kornel Lesinski > <[EMAIL PROTECTED]> wrote: >> >> On Thu, 29 May 2008 20:25:51 +0100, Jason - USL >> <[EMAIL PROTECTED]> wrote: >> >>> For example, if my template designer creates something like >>> tal:repeat="option options", my php developer would see a corresponding >>> line in the documentation saying that the variable 'options' needs to be >>> set, and it needs to implement the iterable interface... >> >> This could be useful indeed. >> >> But you don't need to change PHPTAL itself - templates are supposed to be >> XML after all. You could try to implement this with XSLT or XPath + PHP. >> >> -- >> regards, Kornel >> >> _______________________________________________ >> PHPTAL mailing list >> PHPTAL@lists.motion-twin.com >> http://lists.motion-twin.com/mailman/listinfo/phptal > > > _______________________________________________ > PHPTAL mailing list > PHPTAL@lists.motion-twin.com > http://lists.motion-twin.com/mailman/listinfo/phptal > > _______________________________________________ PHPTAL mailing list PHPTAL@lists.motion-twin.com http://lists.motion-twin.com/mailman/listinfo/phptal
