Re: variable tag / filter

Write one base template, and have as many as you need extend from it, overriding whatever blocks you need. The "child" templates could be as simple as one or two lines. There's no harm in having more, smaller templates--in fact, it makes it more flexible and easier to change in the future.

Re: variable tag / filter

I wanted to write one all purpose generic template.. Now I have split that and extended multiple specific templates.. :( Thanks, ~ramyak/ On Oct 23, 6:34 pm, Jeff FW <[EMAIL PROTECTED]> wrote: > To my knowledge, no, it's not possible to do that. Even if it was, > however, I would strongly

Re: variable tag / filter

I wanted to write one all purpose generic template.. Now I have split that and extended multiple specific templates.. :( Thanks, ~ramyak/ On Oct 23, 6:34 pm, Jeff FW <[EMAIL PROTECTED]> wrote: > To my knowledge, no, it's not possible to do that. Even if it was, > however, I would strongly

Re: variable tag / filter

I wanted to write one all purpose generic template.. Now I have split that and extended multiple specific templates.. :( Thanks, ~ramyak/ On Oct 23, 6:34 pm, Jeff FW <[EMAIL PROTECTED]> wrote: > To my knowledge, no, it's not possible to do that. Even if it was, > however, I would strongly

Re: variable tag / filter

To my knowledge, no, it's not possible to do that. Even if it was, however, I would strongly argue against it, as it would make your templates unreadable--how would you know what filter/tag would be called without mucking through the rest of your code? Maybe there's a better way to get the

variable tag / filter

Is it possible to have variable tags / filters {{ my_value | my_filter }} where c['my_filter'] = 'formatDateTime' formatDateTime is the actual filter function defined in templatetags similarly {{ my_tag my_filter }} where c['my_tag'] = 'formatDateTime' formatDateTime is the actual tag