Most of the problems with the web today besides ie vrs netscape wars, come from non-std compliant code.

about unit testing TG uses nose.

On the other hand, yes kid is hard to learn/use/etc and Cheetah is simplier but the reason for Kid is to stop the bad practices, your code is most likely to work on all browsers with kid templates then with Cheetah, and pass the validators :)

about the last comment, of course Guido hates XML :) so he probably has never use kid

On 3/14/06, dberger < [EMAIL PROTECTED]> wrote:

Early on I was bit by a Kid bug (since fixed) not recognizing some
&code;s, Maybe its the doco and maybe it's me, but I've had a lot of
trouble getting Kid's behavior match what I read.  Finally, trying to
create unit test with webunit's DOM parser, I had some admittedly
unreproducible problems getting parsable code with input that I'm
pretty sure was valid (as I said, I couldn't go back and recreate the
error, so I can't point to a specific problem).

Cheetah, OTOH, I've found much easier to ramp up with and does exactly
--~--~---------~--~----~------------~-------~--~----~
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