On Thu, Oct 14, 2010 at 5:59 AM, <fors...@ozonline.com.au> wrote: > Hi > > Sorry if I do not fully understand this. The proposal is that an ErrorAlert > will be created which must be dismissed by its OK button. Is there any > possibility that a large number of errors can be created, each needing to be > manually dismissed? >
Good question. Yes, this can surely happen, and we do need to take care of this use-case. > > > We can improve the helpfulness of this message. For example, we can tell > > people which file to open in the log. I would like to give some > recommended > > steps to help get problems fixed, but I haven't included it here. Also, > if > > they don't have the log viewer activity, then they may feel helpless > > Option 1, example > Operation could not be performed > Please check the logviewer activity for details > > Option 2 example > Sorry, something went wrong > Please check the file shell.log for details. > The last line of that file is: > TypeError: integer expected got float > > It is very unlikely that primary school students will be able to make any > sense of the log and not much better for secondary school students. Anybody > who could interpret the log would probably know about the Log activity. So I > wouldn't ask them with "please check" but rather offer it as a possibility. > > My suggested rewording: > Sorry, something went wrong. > For more information, use the Log Activity > to view the file shell.log. > The last line of that file is: > TypeError: integer expected got float > Thank you for the pointer. Indeed very helpful. Yes, context and delivery of the exception message is indeed the key here. Any further inputs? Kindly share. Manu > _______________________________________________ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel >
_______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel