|
Here are some things I would like to see addressed
as far as a GUI component standard.
Defaults: All arguments for all components should
have default values. This way a user can pass as many or as few values as they
choose and not have the component fail.
Colors: shuould we define the default color scemes
to be used with any GUI component so as to have some sort
of comon look and feel?
Parameters: (and I am guilty of this myself) some
parameters, such as the background and foground colors of
a component are not always accessable as methods.
(for instance, the FG color of the scrollbar)
Should we insist (in our standard) that any passed
parameter can also be set and read after rendering the component? I.E.
myScroll.setButtonColor() myScroll.getButtonColor()
Fonts: back to a common look-and-feel. If we want a
common look-and-feel to our gui comonents when used in default mode, we should
include default font family, font size, font color, ect. (maybe with a css
sheet..)
What else am I missing? Let's here it.
A side note:
I know I can be loud obnoxious an agressive, but I
do this with the best of intentions.
I see here (again) an oportunity to build something
great, and sometimes I get a little over-excited about that.
I also sometimes take things personally. That's
simply my nature.
You need to understand. I built the light scrollbar
as a light scrollbar because of the voiced concerns over the 'heavyness ' of
past widgets. I even stated specifically that this is ment as a light component
and that I would produce a more classical skinned one as well. Yet when I
released it, I get a three page report on why my scrollbar sucks (that is simply
how it seemed to me until I had a chance to
cool-off).
|
- Re: [Dynapi-Dev] GUI component standard. Doug Melvin
- Re: [Dynapi-Dev] GUI component standard. Raymond Irving
- Re: [Dynapi-Dev] GUI component standard. Doug Melvin
- Re: [Dynapi-Dev] GUI component standard. Benoit Marchant
