#610 closed enhancement (wontfix)
XSLT as templating engine.
| Reported by: | anonymous | Owned by: | Adrian Holovaty |
|---|---|---|---|
| Component: | contrib.admin | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
It would be great to have XSLT as an optional template engine. It would require some sort of model -> XML conversion first.
The reasons to use XSLT are:
- it's XML (easy to verify that the templates are in workding condition using DTD or Schema)
- it's a widely accepted standard (higher interoperability between different frameworks)
- it is extremely versatile and extensible
- it's very fast (using libxslt from xmlsoft.org or other fast implementations)
Note:
See TracTickets
for help on using tickets.
There's nothing stopping you from doing this; you can use whatever template language you want with Django. Chances are this won't be a core feature; the goal for Django's built-in template language is to be accessible to designers and others with HTML experience but limited programming skills.
FWIW, #115 will include a standard XML vocabulary for describing ORM'd objects and lists of objects.