Bug 643 - [Chameleon - MapTitle] Widget should be using Label Attribute group
: [Chameleon - MapTitle] Widget should be using Label Attribute group
Status: NEW
: Chameleon
Widget
: 1.99
: PC Windows 2000
: P5 enhancement
: FUTURE
Assigned To:
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2004-08-26 14:46 by
Modified: 2004-10-12 22:42 (History)


Attachments


Note

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


Description From 2004-08-26 14:46:32
The MapTitle is a Label widget and should be using the Label Attribute Group.
Currently the MapTitle widget defines two attributes: WidgetClass and WidgetStyle. 

Issues with this:

1) These attribute names do not define what the attributes do.
2) The attribute names are used else where to define different things eg.
defined in CursorPos. 
3) The LabelStyle and LabelClass do the same thing as what WidgetClass and
WidgetStyle does for MapTitle.

This mean once the MapTitle widget uses Label.php attribute group than there is
no more use for WidgetClass and WidgetStyle.
------- Comment #1 From 2004-10-12 22:42:58 -------
Actually I am in favour of eliminating the Label group entirely but this is not
feasible right now.

The use of WidgetStyle and WidgetClass may not be clear, but to a web designer,
these are the attributes that they can best use to control the appearance of
widgets.

The current implementations normally reserve WidgetStyle and WidgetClass for use
with the HTML representation of the widget, and add LabelStyle and LabelClass
for use with additional labels surrounding the main representation of the widget.

From this point of view, the MapTitle widget is using these attributes correctly
since the 'label' is the actual HTML representation of the widget.  If the
widget output 'title: <Map Title>' then it would be appropriate to provide
LabelStyle and LabelClass to style the 'title: ' part.

I believe Fred may have some input on this, but I believe that his opinion was
that just WidgetClass would be sufficient for most users.

In any case, this is an issue to be discussed for a future release.