Do not worry. There is no plan to change the template system. If some users want to use other engines (and I understand that they may have legacy templates they may want to use with web2py) that can be done by calling the rendering engine in the action ad returning the html as a string.
It is also possible to make another engine default since all actions are wrapped by a function called response._caller=lambda x: x() One can redefine this is in the controller (or a model) so that if x() returns a dict, it calls the one's favorite template engine. For example: def use_my_engine(a,b): use_genshi(a.view,b) if isinstance(b,dict) else b response._caller=lambda x: use_my_engine(response,x()) Massimo On Oct 13, 9:16 am, BBi <[EMAIL PROTECTED]> wrote: > Massimo, > > I like the way web2py is templating, and I hope you keep it very > simple and very pythonic. In its current version, it is easy to learn > and to use. It's OK. > > IMHO, complex processing should be in nothing else than python, so the > "pipe like" syntax seems to me totally exotic. > However, complex processing can be coded in a module outside of the > view and expose a clean python API called from the view. That's also > style, but more about how we understand and apply the MVC pattern. > > Regards, > Bruno --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
