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? Possible use cases (examples): * XS registration messages. * Automatic updater messages. * Sugar critical errors report. * Institutional broadcast messages. * Anything that simply requires displaying a message. <div class="gmail_quote">On Tue, Dec 7, 2010 at 12:45 AM, Gary Martin <<a href="mailto:garycmartin@googlemail.com">garycmartin@googlemail.com</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> Hi Martin, <div class="im"> On 23 Nov 2010, at 17:23, Martin Abente wrote: > Awesome, let me know whenever you got something to share :) </div>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): <a href="http://wiki.sugarlabs.org/go/Design_Team/Proposals/Notifications" target="_blank">http://wiki.sugarlabs.org/go/Design_Team/Proposals/Notifications</a> Feedback/thoughts appreciated. Regards, --Gary <div><div></div><div class="h5"> > On Mon, Nov 22, 2010 at 5:36 PM, Gary C Martin <<a href="mailto:garycmartin@googlemail.com">garycmartin@googlemail.com</a>> 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 <<a href="mailto:martin.langhoff@gmail.com">martin.langhoff@gmail.com</a>> wrote: > > On Wed, Nov 17, 2010 at 1:10 PM, David Farning <<a href="mailto:dfarning@gmail.com">dfarning@gmail.com</a>> 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 > > -- > > <a href="mailto:martin.langhoff@gmail.com">martin.langhoff@gmail.com</a> > > <a href="mailto:martin@laptop.org">martin@laptop.org</a> -- School Server Architect > > - ask interesting questions > > - don't get distracted with shiny stuff - working code first > > - <a href="http://wiki.laptop.org/go/User:Martinlanghoff" target="_blank">http://wiki.laptop.org/go/User:Martinlanghoff</a> > > > > _______________________________________________ > > Sugar-devel mailing list > > <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> > > <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > > </div></div></blockquote></div>