Naming advice for a templating module
Hi all,
yes, yes, a templating module. Shush.
This one differs because it’s a pure-XML approach. The templates
must be well-formed XML, and the design of the template language
is built to ensure, as best as possible, that the output is
well-formed at all times as well.
Much to my dismay, the obvious XML::Template choice is taken;
particularly to my dismay, that module there follows a really
terrible design that I find impossible to use. (That was one of
the reasons I set out to write another templating module at all.)
The design of mine is very much like Text::Template in a lot of
ways, if you disregard the strong XML slant.
So now I’ve got to come up with a name. It’s going to be a
variation on XML::Template, obviously. The differentiating point
that the name should convey is that the templating language is
designed to be both more Perlish and more XMLish than that of
XML::Template. (Another criterion is that I must not feel silly
whenever I mention being the author of that module. :^) )
I briefly considered XML::Template::Native, but in retrospect,
that is rather vacuous (and would likely fail the silliness
criterion in the long term). It may also be confused as having to
do with XML::Template, so I believe it’s better to aim for a name
of the form XML::FooTemplate.
Anyone have suggestions?
TIA,
--
#Aristotle
*AUTOLOAD=*_;sub _{s/(.*)::(.*)/print$2,(,$\/, )[defined wantarray]/e;$1};
Just-another-Perl-hacker;
Re: Naming advice for a templating module
Hi Lincoln, * Lincoln A. Baxter [EMAIL PROTECTED] [2006-02-25 23:30]: Usually superior designs can be used to wrap infrerior ones in a way that provide backwards compatibility... If the problem is a data file format one, then you could perhaps detect the older format, and drop down to the older routines... I disagree. Perl is not a wrapper around awk+sed+shell. Have you thought about asking the author of the XML::Template, to give it over to you? That would be pointless. I have no interesting in supporting the approach that XML::Template takes, and the one I want to follow doesn’t lend itself to that at all. BTW: I don't really like XML::XMLTemplate... *What* about it do you dislike? Any objective reason, or is it just a matter of taste? Regards, -- Aristotle Pagaltzis // http://plasmasturm.org/
Re: Naming advice for a templating module
On Sun, Feb 26, 2006 at 12:22:55AM +0100, A. Pagaltzis wrote: BTW: I don't really like XML::XMLTemplate... *What* about it do you dislike? Any objective reason, or is it just a matter of taste? I don't like the repetition. Repeating XML adds no value to the name for me. Why not go shopping among the many HTML::Template variations? I'll suggest XML::Template::Strict, since your approach seems to be stricter about validness than XML::Template. Mark
Re: Naming advice for a templating module
* Mark Stosberg [EMAIL PROTECTED] [2006-02-26 01:40]: I don't like the repetition. Repeating XML adds no value to the name for me. Well, taken versus the XML::Template approach, it makes some amount of sense. With XML::Template you don’t actually write templates so much as grammars and instances of them; with my module, you write an template XML file. I'll suggest XML::Template::Strict, since your approach seems to be stricter about validness than XML::Template. Careful: well-formed != valid. I don’t do anything about validation; in terms of well-formedness, XML::Template is even stricter than the approach I’m following. I expect that my module will be capable of producing malformed markup if you try to coerce it hard enough – just not in any common scenario. Also, if anything, it would have to be XML::StrictTemplate, since XML::Template::Strict sounds like it has some sort of commonality with XML::Template, of which there is absolutely none. Any way to express “idiomatic” in a short word that’s suitable for a descriptive name? Maybe I should give up and just try to generically differentiate from XML::Template, like maybe XML::ExTemplate? Regards, -- Aristotle Pagaltzis // http://plasmasturm.org/
Re: Naming advice for a templating module
Can you give some usage examples of your approach to XML templating? I'm curious to see what you need that XML::DOM, XML::LibXML, XML::LibXSLT, and PeTaL and XML::Twig cannot do for you.-- http://slowchess.com/ http://www.moneycoop.org http://www.osogd.org http://www.metaperl.com http://www.livingcosmos.org
