Gotcha, you are filtering the QuerySet in Django, returning to client, and
further filtering with jQuery. Makes sense now. :-)
Happy Coding!
Furbee
On Wed, Mar 14, 2012 at 2:11 PM, Larry Martell wrote:
> On Tue, Mar 13, 2012 at 4:26 PM, Furbee wrote:
> > Oh, you are filtering in the template,
On Tue, Mar 13, 2012 at 4:26 PM, Furbee wrote:
> Oh, you are filtering in the template, using Django, sorry. I thought you
> meant you pass it to the template and use jQuery to filter. My bad. :-)
I am filtering in the template using jQuery.
>
> Cheers
>
>
> On Tue, Mar 13, 2012 at 3:25 PM, Furb
On Tue, Mar 13, 2012 at 4:25 PM, Furbee wrote:
> Aha! Very nice. As a sidebar, you said you pass the filter string back to
> the template so it can apply filtering on the new data set. This makes me
> think that filtering is being done on the entire data set from the browser,
> instead of the serv
Oh, you are filtering in the template, using Django, sorry. I thought you
meant you pass it to the template and use jQuery to filter. My bad. :-)
Cheers
On Tue, Mar 13, 2012 at 3:25 PM, Furbee wrote:
> Aha! Very nice. As a sidebar, you said you pass the filter string back to
> the template so i
Aha! Very nice. As a sidebar, you said you pass the filter string back to
the template so it can apply filtering on the new data set. This makes me
think that filtering is being done on the entire data set from the browser,
instead of the server. Maybe I misunderstood, but if so, I would suggest
fi
On Tue, Mar 13, 2012 at 3:53 PM, Furbee wrote:
> Gotcha, I was unclear. You can have jQuery modify the URL without actually
> requesting the page from the webserver, I thought that was what you meant.
> This comes in handy when you want to use javascript to update the URL
> without requesting a ne
Gotcha, I was unclear. You can have jQuery modify the URL without actually
requesting the page from the webserver, I thought that was what you meant.
This comes in handy when you want to use javascript to update the URL
without requesting a new page from the server in case the user hits F5 or
refre
On Tue, Mar 13, 2012 at 3:33 PM, Furbee wrote:
> Good deal, but if you send the page to the client, then jQuery updates the
> URL, the {{ request.get_full_path }} is still only able to have the original
> URL that was requested. Once the page is sent to the client, Django/Python
> is done and cann
Good deal, but if you send the page to the client, then jQuery updates the
URL, the {{ request.get_full_path }} is still only able to have the
original URL that was requested. Once the page is sent to the client,
Django/Python is done and cannot manipulate the page, unless you are using
AJAX to get
On Tue, Mar 13, 2012 at 2:19 PM, Furbee wrote:
> Hi Larry,
>
> render_to_response is one of many ways to return an HttpResponse to send to
> the client. Wherever your view does the return, you can pass these GET
> variables.
>
> However, if they are being generated by jQuery, dynamically, you shou
Hi Larry,
render_to_response is one of many ways to return an HttpResponse to send to
the client. Wherever your view does the return, you can pass these GET
variables.
However, if they are being generated by jQuery, dynamically, you should be
using jQuery/javascript to read them and deal with the
On Tue, Mar 13, 2012 at 12:38 PM, Furbee wrote:
> I think you want to actually get these in the view code and pass them to
the
> template as named variables. For example:
>
> return render_to_response('page.htm',
> {'date_time': request.GET['date_time'], 'submit_preview':
> request.GET['submit
I think you want to actually get these in the view code and pass them to
the template as named variables. For example:
return render_to_response('page.htm',
{'date_time': request.GET['date_time'], 'submit_preview':
request.GET['submit_preview'], 'event_type': request.GET['event_type'],
'filter
On Tue, Mar 13, 2012 at 11:58 AM, Xavier Ordoquy wrote:
>
> Le 13 mars 2012 à 18:40, Larry Martell a écrit :
>
>> On Tue, Mar 13, 2012 at 11:26 AM, Xavier Ordoquy
>> wrote:
>>> Hi
>>>
>>> Le 13 mars 2012 à 18:11, larry.mart...@gmail.com a écrit :
>>>
From within a template can I find out th
Le 13 mars 2012 à 18:40, Larry Martell a écrit :
> On Tue, Mar 13, 2012 at 11:26 AM, Xavier Ordoquy wrote:
>> Hi
>>
>> Le 13 mars 2012 à 18:11, larry.mart...@gmail.com a écrit :
>>
>>> From within a template can I find out the URL that caused the template
>>> to be invoked?
>>
>> You usually
On Tue, Mar 13, 2012 at 11:26 AM, Xavier Ordoquy wrote:
> Hi
>
> Le 13 mars 2012 à 18:11, larry.mart...@gmail.com a écrit :
>
>> From within a template can I find out the URL that caused the template
>> to be invoked?
>
> You usually should have the request object in your template. See
> https://
Hi
Le 13 mars 2012 à 18:11, larry.mart...@gmail.com a écrit :
> From within a template can I find out the URL that caused the template
> to be invoked?
You usually should have the request object in your template. See
https://docs.djangoproject.com/en/dev/ref/request-response/#django.http.HttpRe
>From within a template can I find out the URL that caused the template
to be invoked?
--
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
18 matches
Mail list logo
