Bug 807 - [Chameleon -Widget] Keymap attribute IMAGE rename.
: [Chameleon -Widget] Keymap attribute IMAGE rename.
Status: RESOLVED WONTFIX
: Chameleon
Widget
: 1.99
: PC Windows 2000
: P2 normal
: 2.0 Final
Assigned To:
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2004-11-01 14:18 by
Modified: 2005-01-11 11:33 (History)


Attachments


Note

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


Description From 2004-11-01 14:18:58
The IMAGE attribute of the Keymap Widget should be renamed. I think it should be
renamed to MAPIMAGE or KEYMAPPATH because there is already a defined attribute
called IMAGE inside the attribute group button. 

Any attribute that is maybe used in several widget through the attribute group
mechanism of chameleon should be a reserved attribute name. That the name should
not be defined in any other specific widget or attribute group.

To add to this if an attribute is only defined within a widget. Than the
attribute name can be reused in others.

This is my thought on this and should be incorporated within the Widget
Developers Golden Rules.
------- Comment #1 From 2004-11-01 16:37:31 -------
Changed target to 1.99 Final.
------- Comment #2 From 2004-11-01 20:04:09 -------
Personally, I think IMAGE is very descriptive of what the attribute is.  I
disagree with having 'reserved' attribute names, that is too restrictive.  I
think that attribute names should reflect what they are.  In this case, exactly
as with the buttons, the image is a URL or path to an image that the widget will
use.  Just because it is going to be used in a slightly different way doesn't
change the fact that it is exactly the same attribute.
------- Comment #3 From 2004-11-01 22:19:57 -------
I am not argueing the fact the the IMAGE attribute used exactly the same way as
the IMAGE in Button attribute group.

I was trying to look at the bigger scope of these attributes and try to identify
a general rule that could be applied to attribute naming.

In the hopes of preventing widget development issues. It seems there is a
balance to be made between everything that effect how widgets are written vs.
the tools and utilities trying to manage the widgets. I think maybe this is
really the issue, to be solved first.


------- Comment #4 From 2005-01-11 11:33:25 -------
I can see both sides to this but I still want to stick with IMAGE for the
keymap.  Marking as wontfix