#2287: [PATCH] No simple way to make TurboGears 2 produce HTML
-------------------------+--------------------------------------------------
Reporter: chrisz | Owner:
Type: enhancement | Status: new
Priority: high | Milestone: 2.1a1
Component: TurboGears | Version: 2.0rc1
Severity: normal | Resolution:
Keywords: html patch |
-------------------------+--------------------------------------------------
Comment (by jorge.vargas):
Replying to [comment:7 Twey]:
> Why can't the Genshi renderer (and other renderers, for that matter)
take a dictionary of options as in Buffet? Is there some serious defect
in this configuration model? Using it, it would be possible to pass
whatever options to Genshi one desired. It's even easy to tie into the
INI file. Why was the templating API crippled in this way?
The main reason why buffet was removed is because template APIs aren't
really that flexible. TG1.x used to need a special class to coerce each
templating engine into using it. Specialized renderers prove to be a saner
design. I think the current implementation by chrisz seems to be best. As
I said in my previous comment the Genshi API can be made as powerful as we
want without needing to call down on the pylons implementation.
--
Ticket URL: <http://trac.turbogears.org/ticket/2287#comment:9>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---
