Thank you for your help, we finally decided to use the third solution : - mako component that are called in our templates - mako component that call plain python modules, presents in the lib/ dir
It works well, and we're not stuck anymore. Have a nice day > > 3rd Idea: > Mako (or others template systems) allow you create "functions". Mini > templates in your templates for reuse generation parts. You can use it > for your purpose. > > There are more possible ideas (I think). Witch one is better is a very > hard question for me ;-) > 1st is speedy in execution (slow in development) solution. 2nd one is > dirtier (example: what about of headers changes in functions?), but > can be useful in some conditions. 3rd one is a standard an easy form > to do it, but a designer gets templates harder to interpret. > > Regards, > > Javi --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
