isaac wrote: > Hi, > > just a thought... > > What if every time you called flash, it _collected_ the messages, and > then returned them to the template or JSON as a list? > > As it stands, if you call flash more than once, the view will only > see the last message (right?). > > Is this something worth pursuing? Or is there an easy way to just > append to the existing message? I'm just thinking of situations where > a request sets off multiple actions the user should know about. > > -i
tg_flash is implemented by storing the string in a cookie, so it shouldn't be too hard to encode multiple messages in there however you like. I wonder if storing that in a cookie is really such a good idea? Well, at least without telling people that it is stored in a cookie. Although now that I think about it, how else would you do such a thing in TG? The only other option I can think of would require identity, and I am not even sure what I am thinking is correct. Mostly though I am worried that people will rely on tg_flash for notifications and forget to tell people that they need cookies turned on for that to work. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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 -~----------~----~----~----~------~----~------~--~---
