Bug 112 - [Chameleon]test template cwcwidget000.html?
: [Chameleon]test template cwcwidget000.html?
Status: RESOLVED FIXED
: Chameleon
Widget
: 1.99
: PC Windows 2000
: P4 normal
: 1.99 beta 4
Assigned To:
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2003-11-13 10:46 by
Modified: 2004-12-02 21:26 (History)


Attachments


Note

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


Description From 2003-11-13 10:46:06
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.
------- Comment #1 From 2003-11-13 12:24:03 -------
The tag appears in red because the type="" attribute refers to a widget that
cannot be found.  If a widget can be found that matches the type, then you will
not see the tag in red.

CWCWidget is not a valid widget.  It is the parent of all other widgets, but it
cannot ever itself be created.

I think that this widget test can be dropped entirely, at least from this type
of testing.
------- Comment #2 From 2004-04-06 12:11:59 -------
the base Widget class is in the documentation so that we can describe the core
attributes.  The documentation should reflect that this is not actually a widget
that can be created in the template.

The appearance of the widget tag in red in the template is as we have designed
it.  It appears when anything is wrong with the tag, either the widget type or
any of the attributes.  Changes to how this works should be proposed as an
enhancement, but I am unlikely to modify it because I think it is important that
the application designer see what tags are not correct when building an
application, regardless of why the tag is wrong.

Jeff, please update the documentation of CWCWidget appropriately and close this bug.
------- Comment #3 From 2004-04-06 13:30:10 -------
accepting bug
------- Comment #4 From 2004-04-08 08:35:28 -------
updated version to 1.99
------- Comment #5 From 2004-05-03 10:37:10 -------
Changed Target Milestone to 1.99 RC
------- Comment #6 From 2004-11-04 18:28:56 -------
is this an issue in the new docbuilder?
------- Comment #7 From 2004-11-04 22:21:11 -------
No, this is not an issue in the latest version of the doc builder because the
doc builder only lists widgets it finds based on filename ending in ".widget.php".
------- Comment #8 From 2004-11-05 08:35:34 -------
What bill is saying is that the Type="cwcwidget" is not documented at all within
the widget docs. However the base attribute group (Widget.php) is documented as
such which represents the same thing.

This has a widget xml doc
/htdocs/help/attributegroup/Base_attribute_group.en-ca.doc.xml

Setting to fixed.