[Dextrose] Fwd: [Sugar-devel] [DESIGN] Messages notification

Martin Abente martin.abente.lahaye at gmail.com
Sun Nov 7 20:13:48 EST 2010

On Sun, Nov 7, 2010 at 5:05 PM, David Farning <dfarning at gmail.com> wrote:

> Martin,
> In theory this not needed because Sugar is perfect and all users are
> hackers:-/
> In practice, it could be very useful as teachers, onsite techs, and
> developers try to figure out what is happening when something goes
> wrong.

> It is not worth the fight to get this into upstream but it could be a
> great value add to dextros.
Well, even though it seems that I am fighting, I am not, Is just the way I
talk in this foreign language hehe :). I am reading the HIG and comparing it
to what is actually implemented (in the reality). And of course I will
implement this in dextrose anyway. Just wanted to ask the community for
ideas to do it better as possible.

> ---------- Forwarded message ----------
> From: Martin Abente <martin.abente.lahaye at gmail.com>
> Date: Fri, Nov 5, 2010 at 4:02 PM
> Subject: [Sugar-devel] [DESIGN] Messages notification
> To: sugar-devel at lists.sugarlabs.org
> Hello amigos,
> Recently I encountered many situations where a system-wide
> notification-messages system is required as a basis for many bug fixes
> or enhancements. I am not talking about the messages that are related
> to an specific activity or its context, in many of those cases the
> current alert widgets are effective and proper methods. Currently,
> Sugar does not have a mechanism to communicate to users different kind
> of information about sugar itself. For example:
> 1. Important system events (automatic backup running, new update
> available, journal being almost full,etc)
> 2. Connectivity status changes or errors (connecting to a wifi network or
> 3G)
> 3. Critical sugar errors, right now most of those errors are invisible
> to users (this make testing process very difficult)
> 4. I am sure others can imagine more use cases.
> So I would like to list two extensions to the current notification
> system. Basically what we need is:
> 1. Simple text messages display.
> 2. Messages manager, this would help the user to see what messages
> have been delivered in the current session, so they could react to
> those events (for example, reporting bugs).
> I believe this feature could be a huge plus to dextrose and and sugar
> mainstream, therefore I invite everyone to share their ideas on how
> this feature could work and look.
> Saludos
> Martin (tch) Abente
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
> _______________________________________________
> Dextrose mailing list
> Dextrose at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/dextrose
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/dextrose/attachments/20101107/ad1935ce/attachment.html>

More information about the Dextrose mailing list