MapTools.org

[Chameleon-dev] [Bug 97] New: [Chameleon] Widget Golden Rules

bugzilla-daemon@www.maptools.org bugzilla-daemon@www.maptools.org
Fri, 7 Nov 2003 12:50:46 -0500
http://www.maptools.org/bugzilla/show_bug.cgi?id=97

           Summary: [Chameleon] Widget Golden Rules
           Product: Chameleon
           Version: 1.1
          Platform: PC
        OS/Version: Windows 2000
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Widget
        AssignedTo: chameleon-dev@lists.maptools.org
        ReportedBy: thorne@dmsolutions.ca


Talking with Norm here are some Rules that all Widgets should be able to handle,
or be configured to do. This will help in developing a standard development
widget standard. I realize that all these are separate bugs, but I wanted a
general discussion first to hammer it out. I will then create new individual
bugs form the results.

General Widget Rules:

1) All Widgets Should work/ display independent from other resources, widgets,
other scripts. 
http://www.maptools.org/bugzilla/show_bug.cgi?id=96


2) If an error occurs with one of the widgets the other widgets found in the
HTML template should still be loaded. Maybe there should be a setting for this
to allow the app to either stop loading once an error occurs vs. keep loading
until all widgets have been attempted to load. If there is a major mapserver,
mapfile error this should be treated separately. 

3) If a Widget is dependent on another widget/ resource, *.php file this should
be checked and message displayed if error occurs with respect to this issue.

4) If a widget needs curtain resources, widgets, other *.php files than this
should be found in the documentation.

5) Standardized CWC attributes between widgets example of this problem is the
compass point widget.

http://www.maptools.org/bugzilla/show_bug.cgi?id=28


If you guys think of anything other rules, please add them.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


This archive was generated by Pipermail.