There is a whole universe of XML based tools, a lot more than the number
of tools that support Python directly. XML interoperability is much more
than just a checklist item -- it's essential. If you're going to invent
a new language that's not compatible with XML, then PLEASE make it look
completely different than XML (say, s-expressions), so it doesn't
confuse people and computers.
One of the most important features of Kid is that it's 100% XML
compatible (not 99 44/100'ths percent pure, but absolutely 100%), which
makes it much better than all those half-baked templating languages that
invent all kinds of quirky incompatible syntax, like ASP, JSP, Cold
Fusion, DTML, etc.
It makes sense for Microsoft to use mutant forms of XML, because then it
forces you to use their tools that support it, because it makes regular
XML editors barf, but that's because Microsoft wants to lock you into
their proprietary languages so you have to buy their tools. But unless
you have a staff of thousands of programmers and billions of dollars to
pay them to develop your own tools and editors and debuggers, using pure
XML with open source and off-the-shelf tools makes a lot more sense.
I've been using XMLBuddy and <oXygen/> to edit Kid templates and other
XML documents, and I've been writing Relax NG schemas to describe and
document the XML formats I'm using, which the tools read and understand,
to provide validation and high power editing features. Not only can
other tools read my XML, but they can also read my Relax NG schemas,
which are compatible between different tools, and can be translated to
other schema languages. It works wonderfully! I'd hate to give up all
that power and interoperability, just so I didn't have to quote
less-than signs.
-Don
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]
On Behalf Of Brian Beck
Sent: Tuesday, December 13, 2005 12:33 PM
To: TurboGears
Subject: [TurboGears] Re: Comparison operators in a Kid template
David Stanek wrote:
> On 12/10/05, Kevi
> But I am not sure how good of an idea this would be. I'll bring it up
on the
> Kid mailing list after I think about it for a bit.
I brought it up on there a few days ago, and I think the developers
value the "always-valid-XML" feature quite highly. Personally I think
that's just a checklist feature and doesn't actually help developers.
The "able to write actual Python in your templates" is a much more
valuable feature to me, so I'd like to see it changed...
