I looked at Xelig a few months ago, and frankly this guy comes off as arrogant and rude. The POD for that module contains the following:

AVOID

XSLT, Template::Toolkit, Mason, HTML::Template, PHP, JSP, ASP, PageKit, EmbPerl, ePerl, ZPT, TAL &c.

That's pretty obnoxious, especially considering that the documentation for Xelig is almost non-existent and the module is sorely lacking in features compared to some of those other systems. It's especially odd since Xelig seems closer to TAL than to XMLC, which is referred to as the inspiration for this. And what's with calling the template processing method MVC? As far as I can see from the docs, there's nothing there but the V part.

XMLC always sounded like a bad idea to me because it adds an extra compile step every time you change any of the HTML templates and because it only supports explicit manipulation through a DOM tree (at least that was the story last time I looked). Xelig appears much more similar to Petal, but I would recommend Petal over Xelig since it has documentation, a mailing list, and an active base of users.

This guy may have a lot to offer to the Perl community, but a little more humility would go a long way here.

In reply to Re: DBI database connection support and more by perrin
in thread DBI database connection support and more by princepawn

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.