On Mar 4, 2008, at 9:36 PM, Ian Bicking wrote:
It's a rendering factory someone wrote. A little like Buffet, except noentry points, no standardized way to instantiate the object, and noparticular need to make the render callable have a completely consistentsignature.
Yet another level of obfuscation and misunderstanding, and yet another thing that will trip up those wanting to try and change how a template language is configured.
Putting a 15-line recipe into the pylons template seems really scrappy.
All of Pylons is a recipe. It's a recipe to configure Paste, a batch of middleware, and do some dispatching with Routes. The entire thing is no more scrappy than having a render function that uses the template engine.
I don't see this MakoRenderer being any less or more scrappy than a basic render function, but at least everyone I showed the render function to is 100% aware of what it does, and how they could change it. While MakoRenderer is another "what the heck is this? how come I can't just configure the template engine?".
MakeRenderer seems simpler than this, with no recipe stuff stuck in there.
I'm baffled that the hundreds of lines of code in the templateproposal, the setuptools entry points, the plugin hooks, the limiting render calls (which prevent you from accessing the Genshi stream object which some ppl want...).... is simpler than a 7 line render function. Even with TemplateProposal, 95% of the code I pasted is still needed in pylons.templating because it handles cache functionality and populating the template variables with the Pylons globals. I've written some extensive docs and committed them regarding how to use the render functions and write one:
http://pylonshq.com/project/pylonshq/browser/pylons/templating.py Let's ask the Pylons list, whether using this package: http://svn.pythonpaste.org/Paste/TemplateProposal/branches/TemplateProposal-MSO/Is easier than using the few lines of code needed for the render functions. Also, keep in mind that for someone to even start to override one of the plugins in templateproposal, first you get to explain setuptools entry points, how to extend them, how to register your own, then finally you get to write a render function... ick.
The point of Pylons is to try and make things easy through simplicity and elegance, so far Buffet and its abstraction ilk has been the exact opposite. After seeing how simple and short it is to just write a little render function that does *exactly* what you want, its hard to see the advantage in accepting template language limitations and abstractions.
Cheers, Ben
smime.p7s
Description: S/MIME cryptographic signature
