Maybe a icon (with number of unread notifications) and a window with a list of unread notifications that pops up when we click that icon. Kinda like in social media or smartphones.
Use websocket pubsub service on server. Let various parts of app create callbacks on various notifications (from server, from client, from other clients? From APRS?) . There may be different types of notifications. Icon may handle just one of the types....
This could be used when implementing messaging, chat, etc.. And possibly geographical feature notifications that do not fit into the websocket interface for map-overlays.
Maybe a icon (with number of unread notifications) and a window with a list of unread notifications that pops up when we click that icon. Kinda like in social media or smartphones.
Use websocket pubsub service on server. Let various parts of app create callbacks on various notifications (from server, from client, from other clients? From APRS?) . There may be different types of notifications. Icon may handle just one of the types....
This could be used when implementing messaging, chat, etc.. And possibly geographical feature notifications that do not fit into the websocket interface for map-overlays.