MapTools.org

[Chameleon-dev] [Bug 112] New: [Chameleon]test template cwcwidget000.html?

bugzilla-daemon@www.maptools.org bugzilla-daemon@www.maptools.org
Thu, 13 Nov 2003 10:46:07 -0500
http://www.maptools.org/bugzilla/show_bug.cgi?id=112

           Summary: [Chameleon]test template cwcwidget000.html?
           Product: Chameleon
           Version: 1.1
          Platform: PC
        OS/Version: Windows 2000
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Widget
        AssignedTo: chameleon-dev@lists.maptools.org
        ReportedBy: thorne@dmsolutions.ca


cwcwidget000.html

1st Point:
This widget does not actually exist and cannot be tested. However, this dummy
test is acutally resulted in an important point. The result of the dummy widget
produces the red Text of the <CWC2/> tag, is this the result we want?

<CWC2 TYPE="cwcwidget" VISIBLE="TRUE" ENABLED="TRUE"/>

Whenever the "<CWC2/> text in red" pops up it proves that the service instance
is connected to Chameleon.php, and that chameleon is reading the <CWC2/> tags.
What it also shows is that there is something wrong with the widget/attributes.
 
The problem with this resulting error is that the red <CWC2/> tagged error
should really only be displayed if the Widget actually exists. It would be less
confusing for the user if they knew (with out checking the directory) that they
were actually having trouble with the widget and not just with the <CWC2/> tag.

Probably the simplest way to do this is to varify the widget exists is by the
TYPE="cwcwidget" attribute. First to check if the type attribute exists, then
check if the widget name is found. An error should reflect the failed result.


2nd Point (Documentation)
I am assuming this cwcwidget000.html template was created because it was found
in the documentation. This cwcwidget should be removed from the widget document
or have it in a separate introductory section and not within the main widget
list. This will remove confusion.



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


This archive was generated by Pipermail.