Nymbl, I definitly agree that something like that would be ideal and is
important if developers are able to get the full power out of generic
views.
On Nov 14, 8:38 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> I have an idea. Instead of a 'message' parameter, there could be a
> on_success
I have an idea. Instead of a 'message' parameter, there could be a
on_success, on_error callable parameter in the function. I don't know
what the parameters to the callback would be, but this is the rough
idea:
def on_error(request, ?other parameters?):
request.session['message] = "Not saved
You are correct Collin. :)
I noticed that myself but couldn't go back and edit it or anything.
James, also I noticed that the messages system even with authenticated
users won't work properly with generic views because again, there is no
way to know whether the update/creation was a success or n
Point of clarification, it'd be a GET param, since you can't add POST
in a redirect ;-)
--
I do not fear computers. I fear the lack of them.
-- Isaac Asimov
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
James, I discussed with you some on IRC earlier my situation, but I'll
bring it up here so others can read it.
The problem with your suggestion is it will only work for authenticated
users. If you have anonymous users, using messages like that simply
won't work. The Django docs suggest using the
On 11/13/06, jp <[EMAIL PROTECTED]> wrote:
> Something that is fairly common in web applications are indicator
> messages. For example, after you've posted an article, the site should
> echo back to you 'Article x created'. This is important because it
> let's the user know what is going on.
You
Something that is fairly common in web applications are indicator
messages. For example, after you've posted an article, the site should
echo back to you 'Article x created'. This is important because it
let's the user know what is going on.
Unfortunately with Django generic views, particularly t
