#395 closed enhancement (wontfix)
Add a system for plugging in additional directives
Reported by: | Carsten Klein <carsten.klein@…> | Owned by: | cmlenz |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | General | Version: | 0.6 |
Keywords: | Pluggable Directives | Cc: |
Description
See wiki page WorkInProgress/PluggableDirectivesLibraries for more information on this.
Change History (3)
comment:1 Changed 14 years ago by anonymous
- Resolution set to wontfix
- Status changed from new to closed
comment:2 Changed 14 years ago by carsten.klein@…
The issue was closed by me of course.
comment:3 Changed 14 years ago by Carsten Klein <carsten.klein@…>
The code initially developed for this can be found under git://github.com/axnsoftware/genshi-bugs-n-features.git in the genshi-issue-395 branch.
Note: See
TracTickets for help on using
tickets.
I reviewed the existing genshi code and even managed to implement a few tags that could just be plugged in and used.
However, the system for arbitrating the tags and also for prioritizing them, that is currently implemented into genshi, makes it hard to provide a unified approach.
This is mainly due to the fact, that genshi markup can be used as both elements and namespaced attributes to existing other elements.
In order to become independent of the order of tags in a given document, one must rewrite genshi so that it gets rid of genshi markup that utilizes attributes for performing genshi magic.
E.g.
would have to be removed from the templating language, as py:for and py:if are order dependent.
Instead, everything would have to be noted just like
for which nearly all existing templates would have to be reimplemented in small to large parts.
Closing as wontfix, as the benefit would be too small since a major rewrite of genshi would be required. And, given the current feelings to genshi as a whole, and whether trac should continue supporting it, it seems even more unlike that such a thing will happen.