Summary: | Size of Buttons (e.g. close button) | ||
---|---|---|---|
Product: | Chameleon | Reporter: | Schnider Markus <msr@sourcepole.ch> |
Component: | Core | Assignee: | chameleon-dev <chameleon-dev@lists.maptools.org> |
Status: | NEW | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | 1.99 | ||
Target Milestone: | FUTURE | ||
Hardware: | Other | ||
OS: | Linux | ||
Whiteboard: |
Good point. We talked about a change to the buttonizer that would allow sizes to be declared as variable, as in width="75*" which would create a button a minimum of 75 pixels wide, but which could expand to accomodate longer text. Similarly width="*" would make a button just wide enough for the text. I have not implemented this yet, but it seems like a reasonable change. Alternately, we could enable expansion by default and provide a mechanism to set a fixed width regardless of text length . Alternately, we could put the sizes of the various buttons into the language dbf files and then get the values based on language. This would have the advantage of allowing the designers to set up pre-determined sizes for each language and ensure that they can be accomodated in the design. One thing that worries me with variable size buttons is breaking the careful HTML design of many of our layouts. Not sure if this would happen or not, it is just a point of concern.
Changed target to FUTURE.
Instead of "75*", perhaps the following would give more control: - "75+": 75 pixels or more: minimum of 75 pixels, or more if text won't fit - "75-": 75 pixels or less: use automatic size based on label size, up to a max of 75 pixels - "*": make button just wide enough for the text
I think that most popups can accomodate buttons of various sizes. there are a few popups that have columns of buttons that may look a little odd with duttons of different sizes. I'm thinking about the search widget specifically.