Perhaps someone would like to develop a "error / debug" widget where it can display / store these messages. <br><br>Hmm didn't chameleon have this :) experiencing a "deJa vu" here<br><br>Cheers<br>
<br>Paul D. <br><br><div class="gmail_quote">On Mon, Jul 20, 2009 at 3:26 PM, Paul Spencer <span dir="ltr"><<a href="mailto:pspencer@dmsolutions.ca">pspencer@dmsolutions.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
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.<br>
<br>
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 :)<br><font color="#888888">
<br>
Paul</font><div><div></div><div class="h5"><br>
<br>
On 20-Jul-09, at 2:13 PM, Jason Birch wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
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.<br>
<br>
If it was called "extendedErrors" or something like that it might be better? Or if there were different debug levels (none, error, information)?<br>
<br>
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. :)<br>
<br>
Jason<br>
<br>
-----Original Message-----<br>
From: Paul Spencer<br>
Sent: Monday, July 20, 2009 10:56 AM<br>
Subject: Re: Ticket: Fusion reports unreadable error message<br>
<br>
Would a configurable option to run in 'debug' mode vs production mode<br>
be practical for this sort of this? It could be added to the existing<br>
config.json and used in various places for reporting problems vs<br>
either suppressing them or providing less ominous looking errors ...<br>
<br>
Paul<br>
</blockquote>
<br>
<br>
__________________________________________<br>
<br></div></div><div class="im">
Paul Spencer<br>
Chief Technology Officer<br>
DM Solutions Group Inc<br>
<a href="http://research.dmsolutions.ca/" target="_blank">http://research.dmsolutions.ca/</a><br>
<br>
_______________________________________________<br></div><div><div></div><div class="h5">
fusion-dev mailing list<br>
<a href="mailto:fusion-dev@lists.osgeo.org" target="_blank">fusion-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/fusion-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/fusion-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br> Paul Deschamps<br> Applications Specialist<br> DM Solutions Group Inc.<br><br> Office: (613) 565-5056 x28<br> <a href="mailto:pdeschamps@dmsolutions.ca">pdeschamps@dmsolutions.ca</a><br>
<a href="http://www.dmsolutions.ca">http://www.dmsolutions.ca</a><br> <a href="http://research.dmsolutions.ca">http://research.dmsolutions.ca</a><br> <br><br>