Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Hmmm, I appear to be having this rant quite a lot recently. Anyway, here we go:

    Everyone seems to write their own template system with slightly different syntax / features and then upload it to the CPAN. Far be it from me to dissuade you doing the same.

    Have you read Choosing a Templating System [perl.com]?

    What does TAL provide that, say the Template Toolkit or AxKit does not? Wouldn't it be better to rely on a module that has had years of testing, complete documentation, an active support group and many users tha

    • I think this templating system is well justified because it would allow Zope and Python users to migrate to perl.

      More importantly it means that Zope-Compatible or Competitive CMS can be written in perl.

      One of the great things about Open Source is the level of competition and also the way in which many components are fairly easy to interchange.

      --

      @JAPH = qw(Hacker Perl Another Just);
      print reverse @JAPH;
      • I think that it is important to note that Zope-Tal/Petal interopability is not a goal of the Petal project. I asked about Zope-Tal/Petal interopability on the Petal mailing list. Here's Mr. Hiver's response:
        >> Is keeping things in sync between Tal and Petal a goal of the project?

        No it isn't. The goal of the project is to make a useful library to template any kind of XML and XHTML. The TAL spec was a good place to start, it has plenty of really good ideas.

        Now I had my own good ideas as well that I needed to integrate in this library :-)

        However, wherever I can, I try to make the library as TAL-compliant as I
        can because it's good practice.

        > What problems would there be in having language neutral templates?

        Unfortunately TAL is not that neutral, it's been designed for Zope. I you limit yourself to the intersection of features between TAL and Petal, you could very well write templates that run on both engines, but you'll loose functionality for either side.

        A grand unification between Zope and Perl does seem interesting, but I wonder how realistic this is.