I want to make a templating language for internal use that has less features and different syntax.
I don't know what pylons expects of a templating language like genshi, kid, myghty or mako so it's hard to know if I have done everything. I don't know what to expect in the arguments to render. Is that documented? - Nate On Dec 17, 6:14 pm, "Mike Orr" <[EMAIL PROTECTED]> wrote: > On Dec 17, 2007 3:49 PM, hagna <[EMAIL PROTECTED]> wrote: > > > > > What does __init__ do in this object? > > >http://pylonshq.com/project/pylonshq/browser/pylons/templating.py#L237 > > > Is that a requirement for any template language? > > > Interestingly I use similar code to this and there is no > > info['_global_args'] object passed in the render method when I make a > > request. > > > Is there any more information on writing template languages for pylons > > or the pylons fork of buffet. Is it really forked or not? > > Buffet was never designed or properly documented. It just grew like a > weed to satisfy TurboGears' immediate needs at the time. Pylons had > to fork it to get something usable. The plugins are also a mess due > to dotted notation and haphazard template options. (TurboKid uses > "directory.mytemplate" syntax as if templates were imported, which > they aren't, and TurboCheetah and Genshi emulate this.) > > There's an ongoing project to write a successor to Buffet (Buffet2?), > which would reunite the forks and be scalable. The latest code is Ian > Bicking's > TemplateProposal:http://svn.pythonpaste.org/Paste/TemplateProposal/trunk > > I'm currently working on cleaning this up and writing a Pylons patch > to use it. So far I have renderers (=plugins) for Mako and Genshi and > a test suite for them. But no Pylons interface and no template > options yet. It won't be ready for Pylons 0.9.7 but maybe 0.9.8. > > If you need to write a Buffet plugin for a new template engine now, > and you can't wait for Buffet 2, I'd follow the example of > mako.ext.turbogears.TGPlugin,because it has less legacy cruft. > > http://www.makotemplates.org/docs/usage.html#usage_common_turbogears/... > > Myghty requires a lot more template options than other the plugins do. > You'll find that the Mako plugin hardly requires any. So unless your > template engine requires certain options, I wouldn't worry about them. > > What engine are you making a plugin for? > > More information is in the following mailing list archives. Search > for "buffet", "smorgasbord", and "TemplateProposal". > > http://groups.google.com/group/pylons-develhttp://groups.google.com/group/pytemplateshttp://groups.google.com/group/pylons-discuss > > -- > 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 -~----------~----~----~----~------~----~------~--~---
