Ticket #2864 (closed defect: fixed)

Opened 7 years ago

Last modified 6 years ago

Need design for sugar notification system

Reported by: crschmidt Owned by: Eben
Priority: normal Milestone: Future Release
Component: interface-design Version: Build 542
Keywords: Cc:
Action Needed: Verified: no
Deployments affected: Blocked By:


When using the OLPC, a number of events can occur which change state in a way that the user is interested in. (Especially in the case of wireless access.) Having a running message log which is accessible to the user for messages like "Connecting to Wireless network Atlas 'failed'" would be useful.

The equivalent in the OS X world would be 'growl', which shows short-term message displays.

These displays would not be necessarily be re-displayed ever -- just let the user know what is going on as it is going on.

(SJ encouraged me to open this)

Change History

Changed 7 years ago by kimquirk

  • milestone changed from Untriaged to Trial-3

Changed 7 years ago by marco

  • owner changed from dcbw to Eben
  • component changed from sugar to interface-design

Eben, how do you see this done in the UI?

It seem like Journal, notifications (whenever we figure out a design for them) and advanced informations in rollovers already covers the possible use cases.

Changed 7 years ago by Eben

  • summary changed from Running 'message log' -- alerts from various services to Need design for sugar notification system

Right, this is in my mind the notification system we've been toying with all along. We still don't have a final design for that yet, but it would cover exactly the types of things that this ticket mentions.

Changed 7 years ago by Eben

  • milestone changed from Trial-3 to First Deployment, V1.0

This requires an entirely new service and API.

Changed 7 years ago by jg

  • milestone changed from First Deployment, V1.0 to V1.1

Changed 6 years ago by Eben

  • status changed from new to closed
  • resolution set to fixed

The preliminary designs appear in the screenshots posted to wiki.laptop.org/go/Designs/Frame. Additional details should be addressed in separate tickets, as needed.

Note: See TracTickets for help on using tickets.