mugle-dev team mailing list archive

[Scott Ritchie <s.ritchie73@xxxxxxxxx>]

I am inclined to agree but when i spoke to Matt a month or so about it, he
said experience with IVLE had taught them it was better to show the full
stack trace.  Maybe we could have a button that popped up a window with the
stack trace or something like that?

On Thu, May 19, 2011 at 10:27 PM, Jens Pfau <jens.pfau@xxxxxxxxx> wrote:

> I think we should shield the user from that detail but we should actually
> make sure that more information is logged somewhere.
>
>
> On Thu, May 19, 2011 at 10:22 PM, Scott Ritchie <s.ritchie73@xxxxxxxxx>wrote:
>
>> Hi im just going through and chaning the existing onFailure error messages
>> to use this new error display.  Just a design question;
>> Do we want to show the stack trace in the panel below the error's message?
>>
>> On Thu, May 19, 2011 at 2:30 AM, Prageeth Silva <prageethsilva@xxxxxxxxx>wrote:
>>
>>>  Displaying error messages added.
>>> Use:
>>>
>>> Mugle.showError(String);
>>> Mugle.hideError();
>>>
>>> Also noticed that, KeyValuePair test works after I cleaned the database.
>>> It's using Blob type (serialized=true) and can someone please confirm
>>> this.
>>> This can be checked in stderr (System.err) output.
>>>
>>> --
>>> *Prageeth Silva*
>>>
>>> --
>>> Mailing list: https://launchpad.net/~mugle-dev
>>> Post to     : mugle-dev@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~mugle-dev
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>