I've been trying to push for PHPTAL use in several projects in the
last years but I haven't been very successful. I ended up writing my
own version from scratch a couple of months ago, leveraging new PHP
5.3 features and the bundled XML parsers + Tidy for legacy templates.

The main point in implementing my own version was to make it extremely
modular to support custom storage (file, string, pdo...), easily
extendable namespaces, tales modifiers, pre/post filters and code
generation in other languages besides PHP (Javascript). While PHPTAL
supports most of that stuff it's showing its age and doesn't makes use
of modern PHP's OO features. That's why I target 5.3, so I can tell
management that the library is using 'latests technology' and is
easily hookable into existing frameworks like ZF or Symfony. Using a
BSD like license was also required in some projects.

As for integration with IDEs, being an XML format I guess the only
thing needed is to implement a DTD and a RelaxNG schema to cover most

I also agree on that it needs to be more 'marketting friendly', the
home page is an invaluable resource given that the manual is quite
complete but it does not sale the product. And a section with tips and
tricks (zebra rows, working with javascript, ...) would also help a
lot newcomers.


On Fri, May 30, 2008 at 5:33 PM, Patrick Burke <[EMAIL PROTECTED]> wrote:
> Anton, yes I am a developer of PHPTAL but I'm not on the PHTPAL
> developer list.  My modifications have been specific to the company I
> was implementing it for but I've made more general modifications along
> the way, like some memcached/compiled templates trickery I used at the
> last place I did a gig for, and I'm ready to make a formal
> contribution so the PHPTAL Developers can tell me what's up/what they
> think.  But even if my own contributions get shot down I'd like to see
> development of PHPTAL geared towards the people I have to pitch to:
> CTOs, IT Managers, Directors/Producers of Internet Programming, etc.
> Just for a while anyways, just until there's undeniable awareness of
> PHPTAL in that segment of IT personnel.  I think it's only a matter of
> adding and promoting a few more "enterprise" features to the project
> (I really, reeeeally hate that "enterprise" term but...you probably
> know what I mean when I say it so that's why I'm using it).
> I've probably got another couple of months before I get up to speed on
> the latest version of PHPTAL and then implement the memcached thingy I
> did.  Hopefully I'm an "official" PHPTAL developer at that point.
> But do you get what I'm saying about the direction of development in
> the short term?  It's just that I know too many CTO types that have
> actually heard of Smarty but are baffled by this new-fangled PHPTAL
> stuff, and they aren't even keen on hearing about it until I start
> sneaking in comments like, "See, that problem just simply doesn't ever
> happen when you use PHPTAL", or "We wouldn't worry about that
> bottleneck if we had something like PHPTAL's system".
> Know what I mean?
> Hew

PHPTAL mailing list

Reply via email to