#2407: Support Genshi in TG widget templates
--------------------------------+-------------------------------------------
 Reporter:  chrisz              |        Owner:     
     Type:  task                |       Status:  new
 Priority:  normal              |    Milestone:  1.5
Component:  TurboGears          |      Version:  1.1
 Severity:  normal              |   Resolution:     
 Keywords:  genshi kid widgets  |  
--------------------------------+-------------------------------------------
Comment (by chrisz):

 After a larger clean-up operation in the widgets package in r6949, the
 main work has now been accomplished in r6954.

 Still to be done:

  * Convert templates for all widgets included with TG from Kid to Genshi
  * Switch the `default_engine` for TG widgets from Kid to Genshi
  * Shall we make the `default_engine` configurable?
  * Add some more test, e.g. for displaying a Genshi widget with Kid
 subwidgets
    on a Kid page, and displaying a Kid widget with Genshi subwidgets on a
 Genshi page
  * Add some documentation, particularly for the new `engine_name`
 attribute
  * Should we set `engine_name` by default to None (i.e. try to derive the
 engine
    from the template), or to `'genshi'`? The former will be a bit more
 backward
    compatible: Pld widgets with Kid templates and no `engine_name`
 attribute would
    inherit the `engine_name='genshi'` setting, i.e. try to render the Kid
 template
    with Genshi.

-- 
Ticket URL: <http://trac.turbogears.org/ticket/2407#comment:2>
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to