Summary: | [Chameleon -Widget] Keymap attribute IMAGE rename. | ||
---|---|---|---|
Product: | Chameleon | Reporter: | Chris Thorne <cthorne@dmsolutions.ca> |
Component: | Widget | Assignee: | chameleon-dev <chameleon-dev@lists.maptools.org> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | 1.99 | ||
Target Milestone: | 2.0 Final | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Changed target to 1.99 Final.
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.
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.
I can see both sides to this but I still want to stick with IMAGE for the keymap. Marking as wontfix