+1 from me.
On 4/11/06, Alberto Valverde <[EMAIL PROTECTED]> wrote:
>
>
> On Apr 11, 2006, at 9:40 AM, Andrey Lebedev wrote:
> > I'm fully aware of this feature and I'm not proposing to remove it. I
> > am proposing to add another feature to be able to display flash by not
> > issuing redirect. This way, when program issues redirect after setting
> > flash, it (flash) will be loaded from cookies. When program renders
> > template after setting flash, it will be loaded from cherrypy.response
> > or cherrypy.request.
>
> I agree with this, flash should behave more or less like this IMO:
>
> 1)
> def method(...):
> ....
> flash("bang")
> return dict(...)
>
> (Display message on current request passing message via CP.request)
>
> 2)
> def method(...)
> ...
> flash("bong")
> redirect(...)
>
> (Display flash in next request passing message via cookie)
>
> This is something that has bugged me before too... I think flash
> should be a uniform interface to display status messages, regardless
> if we're redirectig to another page (after a save, for example) or not.
>
> My .2€
>
> Regards,
> Alberto
> >
>
--
cheers
elvelind grandin
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears Trunk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears-trunk
-~----------~----~----~----~------~----~------~--~---
