[fusion-dev] Re: Ticket: Fusion reports unreadable error message

Paul Deschamps pdeschamps at dmsolutions.ca
Mon Jul 20 17:15:09 EDT 2009


Perhaps someone would like to develop a "error / debug" widget where it can
display / store these messages.

Hmm didn't chameleon have this :) experiencing a "deJa vu" here

Cheers

Paul D.

On Mon, Jul 20, 2009 at 3:26 PM, Paul Spencer <pspencer at dmsolutions.ca>wrote:

> This sounds more application-specific than I am willing to put into the
> library as core functionality.  So to accommodate this, I would prefer that
> we expose 'extended' error conditions through event notifications that
> developers can use to implement their own handling system.  In this case,
> Fusion would never alert an error but rather would trigger error events
> (some of this happens already) and pass both basic and extended information.
>
> In this case, Christine's patch should be modified to fire an error event
> instead of an alert.  Perhaps that is beyond the scope of the current change
> :)
>
> Paul
>
>
> On 20-Jul-09, at 2:13 PM, Jason Birch wrote:
>
>  I'm not sure.  I was initially going to suggest that, but I often don't
>> get trouble reports until after an application has been signed off, moved to
>> production, etc...  I'd hate to leave a debug flag turned on in production
>> if it had performance implications made the interface totally
>> developer-centric, and I'd be concerned that calling the config option
>> "debug" would lead to this.
>>
>> If it was called "extendedErrors" or something like that it might be
>> better?  Or if there were different debug levels (none, error, information)?
>>
>> Another option would be a link that says "Email Problem Report" where user
>> can fill in information about what they were doing, and all debug info is
>> automatically added to the report. :)
>>
>> Jason
>>
>> -----Original Message-----
>> From: Paul Spencer
>> Sent: Monday, July 20, 2009 10:56 AM
>> Subject: Re: Ticket: Fusion reports unreadable error message
>>
>> Would a configurable option to run in 'debug' mode vs production mode
>> be practical for this sort of this?  It could be added to the existing
>> config.json and used in various places for reporting problems vs
>> either suppressing them or providing less ominous looking errors ...
>>
>> Paul
>>
>
>
> __________________________________________
>
>   Paul Spencer
>   Chief Technology Officer
>   DM Solutions Group Inc
>   http://research.dmsolutions.ca/
>
> _______________________________________________
> fusion-dev mailing list
> fusion-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fusion-dev
>



-- 
   Paul Deschamps
   Applications Specialist
   DM Solutions Group Inc.

   Office: (613) 565-5056 x28
   pdeschamps at dmsolutions.ca
   http://www.dmsolutions.ca
   http://research.dmsolutions.ca
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/fusion-dev/attachments/20090720/c6746f2e/attachment.html


More information about the fusion-dev mailing list