On Monday 24 April 2006 13:20, Robin Haswell wrote: > Since we only do xHTML, this means we're extremely used to writing > well-formed XML.
My CMS successfully uses KID to template all sorts of XML - a Google Sitemap being one important one, RSS feeds another. Surprisingly enough I have also been using KID to template plain text CSV and XML database exports! (CSV may be more abuse than use. ;) My sitetemplate.kid file is around 160+ lines, while my display templates are 15-30 lines. Forms are, of course, much larger. (But I'll be fixing that with widgets once I can figure them out.) On Monday 24 April 2006 13:51, Karl Guertin wrote: > Kid's main problems are the opaque error messages... After modifying a template we run it through kidc with --source enabled. This produces very nice backtraces (as the source code actually exists for introspection and debugging), and warns us ahead of time about syntax errors. (Just run Python across the source file!) - Matthew --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
