The API looks ok to me, just one thing, since it's not a runtime operation
(in the sense that a php file is generated for the template),  I think it'll
be great if it used something along the lines of Zend_Loader_PluginLoader.

Which basically when setup with paths and class prefixes is able to find
"plugins" in several folders. This would allow to have a set of default
filters in PHPTAL distribution but override them and create new ones easily
just by placing the class files in a directory, not needing to register them
manually at runtime, which once the template is compiled, is of no use.

So -- phptal:filter="remove_whitespace" -- would automatically try to
include and instantiate a class for that filter.

While -- PHPTAL->addPreFilter("remove_whitespace") -- would just store the
name for when compiling the template and instantiate the class then.

Regarding the tutorials, creating documentation is always hard, specially
for OSS projects, perhaps we could use a simple wiki to collect information
(there is quite a bit of information scattered around, mainly from Zope's
By the way, DokuWiki is a great wiki for this kind of tasks.


On 9/16/09 10:55 AM, GRolf wrote:

I know it's an open project and you can't do everything. The reason I
was asking for this kind of documentation however is that I lack this
kind of knowledge. As such, I'm certainly not in the position to write
the documentation, I'm more in the target audience of it :)

Wednesday, September 16, 2009, 10:43:54 AM, you wrote:

 On 16-09-2009 at 08:14:31 GRolf <ger...@pictureparking.com>
<ger...@pictureparking.com> wrote:

    It sounds interesting and an improvement from previous versions.

However, I'd like to see some tutorials putting this to work. When do
you use those things, how can they be applied to improve your
templates and/or code etc...

What PHPTal lacks is this kind of documentation - the manual is fine,
but there are no hands-on-tutorials available.

    Would you write one?

    After all, it's an open project, and I can't do everything myself.

PHPTAL mailing 
PHPTAL mailing list

Reply via email to