Flash removal very clumsy

[dreamingmind]

Flash removal was simple for the new f_success and f_error mesages. But the needs of the cart pallet when the last item is being removed added logic into the app.js method that clears the message.

This is super lame and overly coupled.

I could use different, special flash messages that carry a different close-button binding...

[curlyjason]

You're considering multiple flash message types? I have been thinking a bit about 'internal messaging' in apps. It seems like there may be a reason to try to scaffold a system (at least conceptually). Features like:

• Flexible types
  • Current error & success
  • Could be warning... can't think of any others right now
• Consistent css. All hooks the same for all dialogs, all css in app.css (I know that doesn't exist, you know what I mean).
• Cascading / non-cascading closure
• Handling of multiple messages
  • Handle up to x messages as normal messages
  • Handle more than x messages differently
  • Messages stack, with each one behind the last
  • Messages cascade, with a toggling behavior
  • Also need to handle closure of multiple messages
  • Perhaps a messaging center separate from primary UI if messages get out of control
• As I think about all of the multiples, it occurs to me that we should never allow this level of messaging to occur. If we need to deliver this level of messages, maybe we need to rethink program flow