You need to log in before you can comment on or make changes to this bug.
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.
Golden Widget Rule: 6) When a widget is dependent on working with respect to another widget(s) an error popup. This popup should only occur when an action is being requested by the user.
eg. of Rule # 6 is bug 124
Golden Widget Rule #7: Widget Parameters that deal with paths should always be relative to the template the user is building. eg. "./images/icon_*.png Otherwise if it is an image that is found under the chameleon application eg /htdocs/images/icon_*.png this should be a url. This is even if it is on the same server. To many times the image path causes the biggest confusion for users, and varies greatly from widget to widget is located.... I am expecting a stink about the above comment from the developers, but I only wish to get feed back on this major limitation to the usability of this technology. Thanks Please make all comments to this specific Golden Rule #7 to: bug 127.
we'll take a look at this and try to set up some guidelines for widget development but it will be post 1.99
updated version to 1.99
The widget golden rules have been moved out of this bug and reviewed under the QA Manger for Chameleon. The golden rules are using in Phase 0 of the Chameleon Test plan. https://www.lan.dmsolutions.ca/dminternal/wiki/index.php?pagename=Chameleon%20Tests%20Scope
Changed target to 2.1.
Changed Target Milestone to FUTURE. (Enhancements may be moved from this target to specific "versioned" targets after product design review cycles.)
