Flashes / notifications in Backbone about ghost HOT 8 CLOSED

Need to wait until backbone is present. Currently the {{>flashes}} is compiled on pageload using pre-existing data. Saving, editing, etc is done async though.

from ghost.

Where are we on this, and can it be pushed to 0.3?

from ghost.

Working on this, expect a PR today - tomorrow.

from ghost.

Because notifications will be async, and client generated, a couple of questions:

• If I do something that generates a notification, and then do something else that generates another notification, do I end up with 2 flashes?
• Should notifications auto-clear?
• Should new notifications replace the previous one?

from ghost.

Notifications should have multiple states - passive, or persistent. Passive should disappear on the next pageload or user action, persistent should remain until manually dismissed by the user, with the "x".

Eg:

Your post was successfully published! - Passive
Ghost 0.3.1 is available, please upgrade! - Persistent

Multiple persistent notifications should stack, until dismissed.

There may be some UI / display issues with this. I'm thinking about a "notifications" wrapper that might solve a few problems, but for now let's just get it working functionally and then see here we are.

from ghost.

I've added a div just after the <main> tag to accommodate the notifications and keep them in their separate world.

from ghost.

Just an update. Passive notifications are working perfectly. Working on persistent ones. Basically I need to replace the flashes module with something else, plop the persistent ones on the ghost instance, and have logic to remove on user action. Hence PR is still not present.

from ghost.

Please resubmit this PR against the 'notifications' branch. Apologies I realise this will require some work due to the restructure :(

from ghost.