Thanks for the write up!

I just want to address one point because it is one important thing that 
I really *like* about TG.

KID's insistance on receiving a valid document format to process is not 
just a great feature.  It's the only right way to do it.

html and xhtml are document formats.  rtf is a document format.  
Wordperfect has a document format.  MS comes out with a different set of 
formats every couple of years.

And when a file is written in these formats, it needs to be right. If it 
isn't it will either fail to load or not look right when someone loads 
it.  The format unambiguously describes the document and the document 
must be described correctly or it is *wrong* and that seems perfectly 
reasonable and expected to most everyone... except when it comes to 
html.  When it comes to html, some people, for some weird reason beyond 
my ken, think it is perfectly reasonable to think that you should be 
able to slop any old thing out there to the document file and expect the 
document reader (aka browser, and sadly too often aka IE) to figure it out.

In my way of thinking, your templates are part of your program, and if 
you don't follow the rules, the template is wrong and KID would be 
remiss not to complain about it.  If the python interpreter one day 
started making guesses about what the programmer really meant and acted 
accordingly it would be considered a serious bug.  And so it should be 
with a templating engine.

That said, people trying to port apps that were written in systems that 
allowed erroneous html through do have a hard time porting them to TG, 
and that's unfortunate.  But for new projects there is no excuse.

Personally, when I finish writing a template and kid says its OK, it 
gives me the warm fuzzies, because I *know* my w3c validation is going 
to pass. (Well, unless I used XML()... but hey!)

-Steve

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---

Reply via email to