[Sugar-devel] [DESIGN] Messages notification

Gary Martin garycmartin at googlemail.com
Fri Dec 10 22:39:53 EST 2010


Hi Martin,

On 8 Dec 2010, at 05:11, Martin Abente wrote:

> The design looks great, and I like the fact that it attaches each notification to its real context when there is a visible one (i,e an activity, journal, battery device icon, etc). 
> 
> How would it work with notifications that are not related to an activity or with a visible context?

Notifications not related to an activity or existing visible context would pulse and add new icons in the same way that transfer to/from notifications are designed. Here's an example showing your schoolserver institutional broadcast message example:

	http://wiki.sugarlabs.org/go/Design_Team/Proposals/Notifications#School_server_messages

I am rather worried at the amount of use cases being raised, constant outside distractions and notifications are a productivity and deep thought killer. Hopefully you're just trying to make sure a design can cover all your possible base cases ;-)

I'd actually like to raise a possible 'simple' stepping stone approach:

- code is implemented to allow badging of frame icons
- existing activity alert code is updated so that when an activity alert strip is raised, it triggers the corner pulse and badges the activities icon (if the given activity is not currently front most).

This would allow existing activity alerts to be noticed at any time, switching to the activity with the badge would allow you read the actual text in the already implemented alert strip, and take any action necessary. Additional alerts (say for the Journal) could be used to notify of low storage space, backup failures.

Institutional broadcast messages (or any message from your schoolserver), is really a separate feature, much like the transfer to/from work, so could be added at any time.

Regards,
--Gary

> Possible use cases (examples):
> 
> * XS registration messages.
> * Automatic updater messages.
> * Sugar critical errors report.
> * Institutional broadcast messages.
> * Anything that simply requires displaying a message.
> 
> 
> On Tue, Dec 7, 2010 at 12:45 AM, Gary Martin <garycmartin at googlemail.com> wrote:
> Hi Martin,
> 
> On 23 Nov 2010, at 17:23, Martin Abente wrote:
> 
> > Awesome, let me know whenever you got something to share :)
> 
> Just wanted to pass on the wiki page I've been working on. I'd like to generate more example mockups covering the devices frame edge (easy), and the buddy frame edge (more complicated, though we could use this edge just for arrival/departure/buddy-event, but it might be possible to have it cover 'bubble chat' as per Eben's previous hopes):
> 
>        http://wiki.sugarlabs.org/go/Design_Team/Proposals/Notifications
> 
> Feedback/thoughts appreciated.
> 
> Regards,
> --Gary
> 
> > On Mon, Nov 22, 2010 at 5:36 PM, Gary C Martin <garycmartin at googlemail.com> wrote:
> > Hi Martin,
> >
> > Just wanted to give you a heads up that I have a slightly different design coming together for notifications.
> >
> > After further, more detailed, work the frame corner notification history palette idea is not coming together so well. I've switched to mockups that actually badge the existing icons in the frame, and add the notification messages to the end of their existing pop-up palettes. It holds truer (I think) to the original HIG and previous mockups of Eben's intent for notifications. I'll try and get the set of new images uploaded to the wiki later this week for folks to review.
> >
> > Regards,
> > --Gary
> >
> > On 17 Nov 2010, at 19:17, Martin Abente wrote:
> >
> > > Change the "want" for "need" and we have:
> > >
> > > "When there is something they _need_ to know"
> > >
> > > And that is exactly the same reason why we are already using the Icon notifications and the same reason why we are already using Alert widgets all over sugar (outside activities), and there are still more cases that we don't do because we simply don't have this feature fully implemented yet.
> > >
> > > That's all i got.
> > >
> > > Abrazos, :)
> > >
> > > On Wed, Nov 17, 2010 at 3:27 PM, Martin Langhoff <martin.langhoff at gmail.com> wrote:
> > > On Wed, Nov 17, 2010 at 1:10 PM, David Farning <dfarning at gmail.com> wrote:
> > > > This patch has a place in Dextrose.  Dextrose is looking at the
> > > > question, "How can we provide support staff the necessary information
> > > > to effectively fix and/or report problems to a higher level of service
> > > > and support?"
> > >
> > > Let's not jump to conclusions.
> > >
> > > Can this be limited to... when the user _wants_ it?
> > >
> > >
> > >
> > >
> > > m
> > > --
> > >  martin.langhoff at gmail.com
> > >  martin at laptop.org -- School Server Architect
> > >  - ask interesting questions
> > >  - don't get distracted with shiny stuff  - working code first
> > >  - http://wiki.laptop.org/go/User:Martinlanghoff
> > >
> > > _______________________________________________
> > > Sugar-devel mailing list
> > > Sugar-devel at lists.sugarlabs.org
> > > http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> >
> 
> 



More information about the Sugar-devel mailing list