On May 26, 11:27 am, Sam Kuper <sampabloku...@googlemail.com> wrote:
> 2009/5/26 Bojan Mihelac <bmihe...@gmail.com>
>
> > is there a way to pass result of a template filter to some tag for
> > further processing?
>
> > {% some_tag content|textile %}
>
> > The best I came so far is something like:
>
> > {% textile content as content2 %}
> > {% some_tag content2 %}
>
> > With this textile, or any other filter should be rewritten as a tag
> > which does not seem DRY.
>
> I haven't used Django with Textile before, but mightn't it be reasonable to
> do the textile processing in the view before handing over to the template?
I am not sure if this would be right way, there are also other filters
like urlize, linebreaks and so on... I think their place should be in
template and not controller.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
