Oh my this would need to be one subtle alert... It's one thing for testers/developers (I.e. fantastic) but quite another for spamming our target age range users! It would definitely need to be a control panel so folks can switch it on/off.
Question: is this for Activities, Sugar, or both? 'Simple' proposal (from the UI side), how about an insect bug shaped icon notification that pulses for a few cycles in a corner (activity corner?) when a traceback hits. That could be enough so interested parties can go use Log, and the other 99.99% of users to at least recognised 'something just went wrong'. Regards, --Gary On 1 Jul 2010, at 10:52, Tomeu Vizoso <to...@sugarlabs.org> wrote: > Any ideas about how it would look like? > > Regards, > > Tomeu > > ---------- Forwarded message ---------- > From: Sugar Labs Bugs <bugtracker-nore...@sugarlabs.org> > Date: Sun, Jun 27, 2010 at 20:20 > Subject: #2063 UNSP: Sugar should bring up an alert when an unhandled > Python exception occurs > To: > Cc: b...@lists.sugarlabs.org > > > #2063: Sugar should bring up an alert when an unhandled Python exception > occurs > ------------------------------------------+--------------------------------- > Reporter: bernie | Owner: tomeu > Type: defect | Status: new > Priority: Unspecified by Maintainer | Milestone: > Unspecified by Release Team > Component: sugar | Version: Git as of bugdate > Severity: Unspecified | Keywords: > Distribution: Unspecified | Status_field: Unconfirmed > ------------------------------------------+--------------------------------- > Many UX designers abhor the idea that the computer would scare off users > with incomprehensible error messages. Ideally, we would have a 100% bug > free system in which this never happens, but current today's is very > different. > > Currently, users and are left wondering why some operation isn't doing > anything and have no way to tell that their log is full of tracebacks. > > To keep things simple, I would suggest to print the exception message in a > notification alert, and suggest users to open the Log activity for further > details. > > -- > Ticket URL: <http://bugs.sugarlabs.org/ticket/2063> > Sugar Labs <http://sugarlabs.org/> > Sugar Labs bug tracking system _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
