On 4 mai 09, at 23:36, Malcolm Tredinnick
wrote:
> On Mon, 2009-05-04 at 15:41 +0200, Masklinn wrote:
>> On 4 May 2009, at 14:55 , pbzRPA wrote:
>>> On May 4, 1:24 pm, Masklinn wrote:
>
> [...]
>
FWIW the `'app.views.showItems'` isn't even necessary, you can just
pass the view functi
On 4 mai 09, at 23:36, Malcolm Tredinnick
wrote:
> On Mon, 2009-05-04 at 15:41 +0200, Masklinn wrote:
>> On 4 May 2009, at 14:55 , pbzRPA wrote:
>>> On May 4, 1:24 pm, Masklinn wrote:
>
> [...]
>
FWIW the `'app.views.showItems'` isn't even necessary, you can just
pass the view functi
On Mon, 2009-05-04 at 15:41 +0200, Masklinn wrote:
> On 4 May 2009, at 14:55 , pbzRPA wrote:
> > On May 4, 1:24 pm, Masklinn wrote:
[...]
> >> FWIW the `'app.views.showItems'` isn't even necessary, you can just
> >> pass the view function and reverse will figure out the rest, so
> >>
> >>
I'm not saying that the original OP code didn't work, just that it felt
sloppy to have this lists/delete/item1 url lingering out there. Just looking
for a better way. :)
John Crawford-14 wrote:
>
>
> Okay, I'm not sure why the OP code didn't work - it seems like going
> to the URL 'lists/show
Okay, I'm not sure why the OP code didn't work - it seems like going
to the URL 'lists/show', with the updated list, would work. So my
*guess* is that since it's a page the browser already saw and cached,
that the page just isn't getting refreshed. In other words, if he hit
the browser-refresh but
You guys are awesome, it's always great to find a great new framework and
then find out it has a great community as well. I can't wait to try this
tonight. Thanks again!
Masklinn wrote:
>
>
> On 4 May 2009, at 14:55 , pbzRPA wrote:
>> On May 4, 1:24 pm, Masklinn wrote:
>>> On 4 May 2009, at
On 4 May 2009, at 14:55 , pbzRPA wrote:
> On May 4, 1:24 pm, Masklinn wrote:
>> On 4 May 2009, at 12:47 , pbzRPA wrote:
>>
>>> I would do the following.
>>
>>> from django.http import HttpResponseRedirect
>>> from django.core.urlresolvers import reverse
>>
>>> def deleteItems(request, item):
>>
>
On May 4, 1:24 pm, Masklinn wrote:
> On 4 May 2009, at 12:47 , pbzRPA wrote:
>
> > I would do the following.
>
> > from django.http import HttpResponseRedirect
> > from django.core.urlresolvers import reverse
>
> > def deleteItems(request, item):
>
> > return HttpResponseRedirect(reverse('ap
On 4 May 2009, at 12:47 , pbzRPA wrote:
> I would do the following.
>
> from django.http import HttpResponseRedirect
> from django.core.urlresolvers import reverse
>
> def deleteItems(request, item):
>
>return HttpResponseRedirect(reverse('app.views.showItems'))
FWIW the `'app.views.showItems
I would do the following.
from django.http import HttpResponseRedirect
from django.core.urlresolvers import reverse
def deleteItems(request, item):
return HttpResponseRedirect(reverse('app.views.showItems'))
--~--~-~--~~~---~--~~
You received this message bec
On 4 mai 09, at 06:54, scott212 wrote:
> I'm reading through the djangobook and trying to build a small app as
> I go. The app is just a list that I can add to and delete entries
> from. Deleting is easy, but I'm not sure how the url/view portion
> should be handled.
>
> http://127.0.0.1:8080/lis
On 5/3/2009 9:54 PM, scott212 wrote:
> I'm reading through the djangobook and trying to build a small app as
> I go. The app is just a list that I can add to and delete entries
> from. Deleting is easy, but I'm not sure how the url/view portion
> should be handled.
>
> http://127.0.0.1:8080/lists
I'm reading through the djangobook and trying to build a small app as
I go. The app is just a list that I can add to and delete entries
from. Deleting is easy, but I'm not sure how the url/view portion
should be handled.
http://127.0.0.1:8080/lists/show/
list item 1 - [delete]
list item 2 - [del
13 matches
Mail list logo
