> My main frustrations so far have been with modularity & reusability, > expressive power (ugly kludges to make up for lack of statements) and > performance, in this order of importance. I don't think I have grokked > yet what match templates (py:match) can do that can't be done with > functions (py:def), or how to use them effectively for non-trivial > examples. Same for using XInclude to include anything more complex > than a single master file, or making sure that a template is included > *exactly* once. > > Perhaps there are solutions and workarounds to these issues that I am > still missing but at the end of the day it comes down to the > philosophy of whether a template language should be a real programming > language or crippled by design. I understand that in some real world > cases the latter is preferable or even required, but so far in this > projects it seems it's more of a hindrance. >
I would not call genshi crippled, just a different syntax. I made recursive menu building functions in genshi and managed to greatly simplify my TG widget code that way. Genshi gets only the data structure and the genshi functions build the xml tree. Give it a second look and you might be pleasantly surprised. That said, I'm sure Mako is great if you need the speed, given the author! Iain --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
