MapTools.org

[Chameleon-dev] [Bug 311] [chameleon 1.99] TextButton shared resource: borders enhancement

bugzilla-daemon@www.maptools.org bugzilla-daemon@www.maptools.org
Thu, 1 Apr 2004 18:27:50 -0500
http://www.maptools.org/bugzilla/show_bug.cgi?id=311





------- Additional Comments From warnock@dmsolutions.ca  2004-04-01 18:27 -------
After discussing this with dean over MSN...

1) Be able to shortcircuit buttonizer by specifying an image and no button
resource... it's not clear right now that you can do that.

Technically we can already do that, but I need to make a full clean set of basic
buttons so you can do it out of the box.  I would use the basic set of button
resources to achieve this.

2) Need ability to just specify width, style and colour for borders

This, as paul says is no small thing.  It means a complete redesign of the
button resource.  I think we should model this completely on the way CSS works.
 with CSS you can specify width, style and colour, and the coolest thing about
CSS syntax is the shorthand.

border: #ffffff, 1px, solid;

is also

border-color: #ffffff;
border-width: 1px;
border-style: solid;

is also

top-border-color: #ffffff;
top-border-width: 1px;
top-border-style: solid;
etc... for left bottom and right

of course to suport the images, border-image is also needed

Note: other parameters would need to be shortened or changed to reflect this
methodology.  

background-image
background-color

icon-src
icon-width
icon-height

label-value
label-font
label-color
label-size

I think also that something deeds to be done about padding and nudge, like
depricate and replace with position properties

icon-horizontal-position (could be left right center, or px value)
icon-vertical-position

label-horizontal-position
label-vertical-position

if we keep nudge and padding they should be

icon-padding
label-padding

or

icon-top-padding etc...

The other thing that needs to be considered is defaut values so that buttons can
be made without specifying all these parameters.



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


This archive was generated by Pipermail.