reload on fastcgi + lighttpd

2006-07-05 Thread imbunche
Hi all, I finnally settled on lighttpd + django runfastcgi as my devel environment. It's just wonderful mainly becausse I run the httpd server as myself, no need root permissions or anything and fastcgi is the only thing I get from my ISP. But how can I force a server reload when I change m

Re: help with custom tag plus custom filter

2006-01-22 Thread imbunche
akaihola wrote: > I don't see why you couldn't use compile_string (from > django.core.template) or your own parser to resolve variables in your > template tag. A custom parser might be faster, but then again with > compile_string you get more features. Using compile_strings {{a}} = 'c' {{d}} = '

Re: help with custom tag plus custom filter

2006-01-21 Thread imbunche
Thanks for your reply, that means my tag implementation is wrong :-( ... Then, how can I resolve the variable name inside the tag implementation?? I'd like to invoke the tag like: {% imgpath /static/images/ %} ... and are variables. It looks like it can not be supported ... I hope I'm wrong.

Re: filter are not inherited [BUG??]

2006-01-21 Thread imbunche
> This is a feature -- each template that uses custom tags or filters > needs to load them explicitly. > > Adrian Thanks a lot for the prompt response. I think this feature is a bit counterintuitive may be it should be noted in the documentation. thx again. Saludos, IvO

help with custom tag plus custom filter

2006-01-21 Thread imbunche
Hi, I have a tag (called imgpath) which creates the renders the tag with the image passed as argument and verifies the file exists or provides some defaults ... that works fine. Notice that the argument to {%imgpath%} can be a template variable, e.g. {% imgpath {{baseurl}}/images/{{myimage}} %}

filter are not inherited [BUG??]

2006-01-21 Thread imbunche
Hi, I notice that if I load my set of filters in my base view (base.html) and then try to use any of those filter in any template that {% extends %} base the filter are not available (not recognized) leading to the error page. I would have imagine that an inherited template has access to the sam