Princepawn has come up with his own framework, Seamstress, though I'm not sure how serious he is about it

Thank you for your balanced assessment of templating systems. My first question would be: have you looked at the docs and philosophy behind HTML::Seamstress? Would you agree that Seamstress is a rather unique beast in the jungle HTML templating systems? The only thing similar to it is XML::LibXML, which is based on XHTML and hence requires better structured documents. It also is not based on HTML::Tree which means that you cannot get the magnificent table-building abilities of HTML::ElementExtended

Now on to your question about my seriousness.

• Seamstress originally contained HTML templating subroutines and support for preparing HTML documents for templating via a command-line tool. All subroutines for templating have been moved out to a separate tested and documented distribution, HTML::Element::Library. Seamstress is now simply compiler support for a large collection of generic tree manipulation routines, which includes HTML::Element::Library, HTML::ElementExtended and the root class HTML::Element (which is part of HTML::Tree).
• I recently developed a database-driven website in CGI::Prototype (merlyn'stool), Data::FormValidator, Class::DBI, and HTML::Seamstress. If you click on any page, at the bottom is a "View source" link which gives you an idea of how Seamstress works.

  I can report that I was pleased with my ability to create common look and feel by normal object-oriented programming as opposed to something like a Mason autohandler.

• I am very happy with my tool and responsive to input on it's improvement. It is not a popular tool. It was well-received at the Thousand Oaks Perl Mongers meeting recently. I meant to give a talk on DFV but they got interested in Seamstress so I explained how it worked and they liked it. That being said, HTML::Template and Template, Mason, Embperl are much more popular and have much longer track records in critical corporate situations. Using Seamstress is a commitment to improving it as you need it - much as I do.

HTML::Formvalidator

I think the most popular validation module is Data::FormValidator and I am happy with its performance. You might take a look at that.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.