#2054: [PATCH] Mechanism to programatically choose an expose decorator in a
method
-------------------------+--------------------------------------------------
Reporter: splee | Owner: faide
Type: enhancement | Status: new
Priority: normal | Milestone: 1.9.7a5
Component: TurboGears | Version: trunk
Severity: normal | Resolution:
Keywords: |
-------------------------+--------------------------------------------------
Changes (by splee):
* summary: Mechanism to programatically choose an expose decorator in a
method => [PATCH] Mechanism to programatically
choose an expose decorator in a method
Old description:
> See patch for details
New description:
Docstring from register_custom_template_engine in patch:
{{{
"""Registers a custom engine on the controller.
Mulitple engines can be registered, but only one engine per
custom_format.
The engine is registered when @expose is used with the
custom_format parameter and controllers render using this
engine when the use_custom_format() function is called
with the corresponding custom_format.
exclude_names keeps track of a list of keys which will be
removed from the controller's dictionary before it is loaded
into the template. This allows you to exclude some information
from JSONification, and other 'automatic' engines which don't
require a template.
"""
}}}
--
Ticket URL: <http://trac.turbogears.org/ticket/2054#comment:1>
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
-~----------~----~----~----~------~----~------~--~---
