| | 1 | = Add Support for the Jinja2 Template Engine |
| | 2 | |
| | 3 | We've decided some time ago to remove support for the ClearSilver template engine, in 0.12, but this didn't happen yet. Clearsilver had its share of inconveniences, enough that we decided to switch to the nicer Genshi template engine in 0.12, but it was **very** fast and memory lenient. While we managed to keep Genshi memory usage somewhat in control (remember #6614), the speed was never really adequate, especially for big changesets and for displaying source files over a few thousand lines of code (see TracDev/Performance#Genshi for details). |
| | 4 | |
| | 5 | So one solution would be to switch once again, to a template engine that would combine the advantages of Genshi (pure Python, nice templates, flexible) and ClearSilver (speed!). Such a beast seems to exist now: **[http://jinja.pocoo.org/2/documentation/ Jinja2]**. |
| | 6 | |
| | 7 | The switch can happen progressively, instead of removing support for ClearSilver we could substitute that code by the support for Jinja2 (well, maybe, remains to be seen if that still makes sense while coding it). |
| | 8 | |
| | 9 | Several points remain to be clarified: what will be the upgrade path for plugins that came to rely on `IStreamFilter`s, how to handle themeing, should we rewrite tag builders or use lightweight string templates, etc. |
| | 10 | |
| | 11 | See also: googlegroups:trac-dev:fc8d8c0447140110 |
| | 12 | |
| | 13 | == Status |
| | 14 | |
| | 15 | Nothing started yet, and the urgency has dropped now that we have a good Genshi 0.6 release available |
