dynapi-dev

[Dynapi-Dev] GUI component standard.

[Doug M. <do...@cr...>]

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.=20

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.

[Raymond I. <xw...@ya...>]

--- Doug Melvin <do...@cr...> wrote:
> 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.

How would this be done?

> 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?

Yes. Something like: foreColor, backColor, Highlight,
Shadow, outline, textColor, selectColor, etc.

> 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..)

Default font-family and font-size. Font-color should
go inside the color section.
 
> 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).

lol - It's always good to get feedback from others.
This way we can improve on what we have.


--
Raymond Irving

__________________________________________________
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
http://platinum.yahoo.com

Re: [Dynapi-Dev] GUI component standard.

[Doug M. <do...@cr...>]

See below:

> > 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.
>
> How would this be done?

function myObject(arg1,arg2,arg3){
    this.var1 = arg1||null;
    this.var2 = arg2||0;
    this.var3 = arg3||"#999999";
}

You test for null. if the argument waxs not passed you assignt he 'default'
value.
If you look into the scrollbar you will notice that autoknob is on by
default (if you do not pass that value)
You will notice also that the backcolor and forcolor are set by default to
appear "windows-like"
if you do not explicitly pass colors..

>
> > 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?
>
> Yes. Something like: foreColor, backColor, Highlight,
> Shadow, outline, textColor, selectColor, etc.
>
> > 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..)
>
> Default font-family and font-size. Font-color should
> go inside the color section.
>
> > 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).
>
> lol - It's always good to get feedback from others.
> This way we can improve on what we have.
>
>
> --
> Raymond Irving
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
> http://platinum.yahoo.com
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by:
> The Definitive IT and Networking Event. Be There!
> NetWorld+Interop Las Vegas 2003 -- Register today!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../
>

Re: [Dynapi-Dev] GUI component standard.

[Benoit M. <mar...@ma...>]

On Tuesday, March 25, 2003, at 10:45  PM, Doug Melvin wrote:

> Here are some things I would like to see addressed as far as a GUI=20
> component standard.
> =A0
> Defaults: All arguments for all components should have default values.=20=

> This way a user can pass as many or as few values as they choose and=20=

> not have the component fail.
I agree. The defaults should be so that the component still looks like=20=

what it should, even if that's not how the user want it, but then, a=20
user will right away understand that it needs to be configured a little=20=

more, compare to a first impression where, because an argument is=20
missing, the thing is completly screwed up, which is really=20
discouraging.

> =A0
> Colors: shuould we define the default color scemes to be used with any=20=

> GUI component so as to have some sort
> of comon look and feel?
I guess we should.

> =A0
> Parameters: (and I am guilty of this myself) some parameters, such as=20=

> the background and foground colors of
> a component are not always accessable as methods. (for instance, the=20=

> FG color of the scrollbar)
> Should we insist (in our standard) that any passed parameter can also=20=

> be set and read after rendering the component? I.E.=20
> myScroll.setButtonColor() myScroll.getButtonColor()
I agree we should.

> =A0
> Fonts: back to a common look-and-feel. If we want a common=20
> look-and-feel to our gui comonents when used in default mode, we=20
> should include default font family, font size, font color, ect. (maybe=20=

> with a css sheet..)
This reminds me that Raymond has almost done a DynCSSStyle :-) So, if=20
we had this beats, it would be very handy to use for skinning. After=20
all a style definition defines location, size, colors and fonts ! We=20
would get as well to change the style of multiple layers in one=20
operation !
> =A0
> What else am I missing? Let's here it.
> =A0
> A side note:
> I know I can be loud obnoxious an agressive, but I do this with the=20
> best of intentions.
> I see here (again) an oportunity to build something great, and=20
> sometimes I get a little over-excited about that.
> I also sometimes take things personally. That's simply my nature.
> =A0
> You need to understand. I built the light scrollbar as a light=20
> scrollbar because of the voiced concerns over the 'heavyness ' of past=20=

> widgets. I even stated specifically that this is ment as a light=20
> component and that I would produce a more classical skinned one as=20
> well. Yet when I released it, I get a three page report on why my=20
> scrollbar sucks (that is simply how it seemed to me until I had a=20
> chance to cool-off).
I'm glad you realized it wasn't meant this way. At all. I'm usually=20
pushing the envelope. I was really happy about your scroller, first of=20=

all because it's proportional, the one I'm using right now isn't ! And=20=

my comments were made in a constructive spirit. My writing may not have=20=

conveyed it enough !

Thanks,

Benoit