Finally, I made render_string() as following, http://d.hatena.ne.jp/pyxis-dev/20080219
---- Junya Hayashi On 2月14日, 午前8:45, junya <[EMAIL PROTECTED]> wrote: > Hi, > > Thanks Mike. I took things too seriously, and missed the meaning of > Buffet. > I'll define custom render() without Buffet. > > I was thinking of providing same configuration to db stored templates > as one of in file system. > Inheritances and includes are also required. > But configure options are avairable in pylons.config or environ, so > I'll use them. > > Thanks a lot ! > > ---- > Junya Hayashi > > > There's no reason you have to use Buffet. Its purpose is to hide the > > differences between template engines for simple cases. But if you > > want to use extra features of a particular engine, you can just use > > the engine in its native manner, or write your own render function. > > The latter would be more convenient. You can define render() in > > environment.py to get the options, and import it into your > > controllers, or stick it into pylons.g. Since you're getting the > > templates from a database you won't need TemplateLookup except for > > inheritance and includes. You can create your own TemplateLookup with > > whatever options you want, or look through pylons.templating and > > pylons.wsgiapp and imitate how it discovers options for Mako. > > > The next version of Buffet and its plugins will change significantly, > > so I wouldn't spend much time looking closely at the code or calling > > internal methods, because those will all change. > > > -- > > Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
