Bug 87 - [Chameleon] Delayed Error logging
: [Chameleon] Delayed Error logging
Status: NEW
: Chameleon
Core
: 1.0
: PC Windows 2000
: P3 enhancement
: FUTURE
Assigned To:
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2003-10-30 10:58 by
Modified: 2004-11-03 10:24 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2003-10-30 10:58:00
Better error logging should be presented to the user at the write time an
current example of this is with the new demo http://www.mapsherpa.com/gom_viewer/

The MassGIS WMS layers being called are producing intermittent failed requests
if the zoom level causes an expensive request on the ArcIMS WMS Connector. 

With respect to Chameleon, the errors can only be shown within the error popup
widget. These errors can then only be displayed after the application is unstuck.

The error's found in the mapscript error log should be displayed immediately
within the map view, instead of waiting until you think the app has actually failed.

This problem is better explained. in bug:

http://www2.dmsolutions.ca/bugzilla/show_bug.cgi?id=2217
------- Comment #1 From 2003-10-31 16:08:16 -------
the problem is that chameleon loads but delays drawing the map image so that the
application will appear more responsive.  The error only happens after the page
has loaded (i.e. when requesting the map image).  So it is impossible (well,
very difficult) to determine that an error has occurred and display it
immediately.  In reality, the code to draw the map registers the error in the
session but it is not until something causes the page to reload that you will
see the error in the error widget.  This is not something that I can (easily)
change.

Possible solutions:

1. use the javascript API.  It has a mechanism for talking to the server after
the image is loaded and checking to see if errors occurred.

2. modify map widgets to provide onerror handlers so if the map image fails to
load, the errors can be displayed immediately.  This won't necessarily work all
the time.
------- Comment #2 From 2003-11-13 16:52:51 -------
New Attribute parameter Type="string"

The Attribute definition section requires and additional parameter within
<attribute>
Currently there is: 
<attribute name=”VISIBLE” required=”false”>
There need a parameter to hold the parameter value type eg. Boolean, Char,
Integer, Array, Color (RGB|HEX), Image path.

<attribute name=”VISIBLE” required=”false” type=”Boolean”>

For Image Path is required what relative path is from eg. Relative to template,
chameleon.php, or others like drawmap.php ;)  
------- Comment #3 From 2003-11-14 09:46:15 -------
I'm not sure the comment #2 should appear into this bug or do I missed
something.
------- Comment #4 From 2003-11-14 11:02:38 -------
Please ignore comment #2 I placed this in the wrong bug. It was suppose to be
Bug 74. Maptools.org did something funny that I did not notice until after that
when you commit a bug that has a dependency, rather than showing the current bug
page you are working on it displays the dependency bug 87. 

I did not notice and place my comments into this bug rather than bug 74.
------- Comment #5 From 2004-04-05 14:42:10 -------
Maybe we can check for the image onload event as part of MapDHTML (or
ErrorReport) widget every second until the map is loaded and display error if
any ? Not sure it's a clean solution but at least I'm bringing ideas ;)
------- Comment #6 From 2004-04-05 17:52:36 -------
not for 1.99 unless we have nothing else to do ...
------- Comment #7 From 2004-07-07 17:16:11 -------
Changed target to 1.99 Final. If there is no time, it can be moved to 2.1.

Also changed priority to 3.
------- Comment #8 From 2004-11-03 10:24:07 -------
future enhancement.