Bug 96 - [Chameleon] Loading Widgets Expectations
: [Chameleon] Loading Widgets Expectations
Status: NEW
: Chameleon
Widget
: 1.99
: PC Windows 2000
: P2 normal
: FUTURE
Assigned To:
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2003-11-07 12:47 by
Modified: 2004-08-10 16:04 (History)


Attachments


Note

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


Description From 2003-11-07 12:47:07
Many widgets do not display unless the widget is actually functioning. This was
shown by Norms One Widget for One HTML template.

For example:
1) CompassPoint Widget
compasspointwidget000.html to  compasspointwidget008.html

When this widget loads, the button should be displayed, or if the image path for
the button is invalid the broken image icon should be there. If the user selects
the button an Error or Warning should popup stating that there is no MapDHTML
widget found in the template, which mean the widget is inactive.

2)CursorPos Widget
cursorposwidget000.html
If the there is no Map then only the Label marker of this widget should be
displayed with a possible default value of "0" in the box. No error, Maybe a
Warning logged, but the application will still function.


Most Widgets are like this where either an error pops up 
eg.1
  Fatal error: Cannot instantiate non-existent class: cwclabel in
C:\ms4w\apps\chameleon\htdocs\widgets\Cursorpos.widget.php on line 58

eg.2
  Fatal error: Cannot instantiate non-existent class: mapnavigator in
C:\ms4w\apps\chameleon\htdocs\widgets\BoundingBoxPopup.widget.php on line 95

OR NOTHING IS DISPLAYED AT ALL IN THE BROWSER.

This is very confusing to the Chameleon Web Mapping Template Developer,
something should be displayed for the user to see that Chameleon.php is being
loaded, and that it is reading the template, but it is the widget configuration
that is the problem.
------- Comment #1 From 2004-04-06 11:50:56 -------
agreed in general, I will start taking a look at this after the 1.99 release
because using one widget per template in this way is not the intended use of
chameleon ... i.e. you would not build most applications this way.
------- Comment #2 From 2004-04-08 08:36:22 -------
updated version to 1.99
------- Comment #3 From 2004-07-07 17:19:44 -------
Changed target to 2.1.
------- Comment #4 From 2004-08-10 16:04:42 -------
Changed Target Milestone to FUTURE. (Enhancements may be moved from this target 
to specific "versioned" targets after product design review cycles.)