#2380: Refactor template plugin options loading in view.load_engines
-------------------------+--------------------------------------------------
Reporter: Chris Arndt | Owner: Chris Arndt
Type: enhancement | Status: new
Priority: normal | Milestone: 1.1
Component: View | Version: 1.1 HEAD
Severity: normal | Keywords: view, template options
-------------------------+--------------------------------------------------
Currently, we only pass a fixed set of options, which is defined in
`view.base.load_engines`, to template engine plugins and we pass all
options to each plugin, whether it is meant for that particular plugin or
not.
This is bad because:
* If a template plugin adds a new option, it can not be set through the
!TurboGears configuration, unless support for it is added in
`load_engines`.
* Badly written templates may choke when we pass options to them they do
not recognize.
--
Ticket URL: <http://trac.turbogears.org/ticket/2380>
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
-~----------~----~----~----~------~----~------~--~---
