|
From: Raymond I. <xw...@ya...> - 2003-07-30 14:10:12
|
Hello Everyone,
I've been doing some thinking and came up with a
solution that I think is able to give us more speedy
layers than what we currently have.
The solution employs a StyleManager that will enable
us to be able to change the look, feel and behavior of
DynLayers and widgets.
With this in mind I would like to make a proposal that
we change the 7th argument in DynLayer to use the
"style" argument instead of image.
IMO background image in rarely used by developers and
could be easily changed with the use of setBgImage or
dictionary object ({}) in those rare cases. I think
the "style" argument will be used much more frequently
than bgimage.
Possible usage of styles:
// create a plain DynLayer
var l = new
DynLayer(null,0,0,10,10,null,'PlainLayer');
// creates an html container
var l = new
DynLayer('Hello',0,0,null,null,null,'HTMLLayer');
var l = new DynLayer(null,0,0,0,0,null,'CoverLayer');
The above layers will use customize code found in the
Style object to improve the creation speed of the
layers.
What do you think? If it's a no, then I guess we'll
just have to use setStyle() and keep the image
argument.
--
Raymond Irving
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
|
|
From: Kevin <ke...@ke...> - 2003-07-30 19:07:13
|
Hello,
As I have used bgImage as the 7th param'. I would
prefer not to change. Don't we have a setClass('style')
or are you using the new parameter as a hard coded
string to integrate with HTMLcomponents? Which
seems to have css as the first param' and is set to null?
With an established interface it is preferable to add to,
rather than change and break backward compatibility
-
Kevin
----- Original Message -----
From: "Raymond Irving" <xw...@ya...>
To: "DynAPI-Dev" <dyn...@li...>
Sent: Wednesday, July 30, 2003 3:10 PM
Subject: [Dynapi-Dev] The 7th argument in DynLayer - Introducing the StyleManager
> Hello Everyone,
>
> I've been doing some thinking and came up with a
> solution that I think is able to give us more speedy
> layers than what we currently have.
>
> The solution employs a StyleManager that will enable
> us to be able to change the look, feel and behavior of
> DynLayers and widgets.
>
> With this in mind I would like to make a proposal that
> we change the 7th argument in DynLayer to use the
> "style" argument instead of image.
>
> IMO background image in rarely used by developers and
> could be easily changed with the use of setBgImage or
> dictionary object ({}) in those rare cases. I think
> the "style" argument will be used much more frequently
> than bgimage.
>
> Possible usage of styles:
>
> // create a plain DynLayer
> var l = new
> DynLayer(null,0,0,10,10,null,'PlainLayer');
>
> // creates an html container
> var l = new
> DynLayer('Hello',0,0,null,null,null,'HTMLLayer');
>
> var l = new DynLayer(null,0,0,0,0,null,'CoverLayer');
>
> The above layers will use customize code found in the
> Style object to improve the creation speed of the
> layers.
>
> What do you think? If it's a no, then I guess we'll
> just have to use setStyle() and keep the image
> argument.
>
>
>
> --
> Raymond Irving
>
>
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../
|
|
From: Raymond I. <xw...@ya...> - 2003-07-30 20:32:07
|
See below:
--- Kevin <ke...@ke...> wrote:
> Hello,
>
> As I have used bgImage as the 7th param'. I would
> prefer not to change. Don't we have a
> setClass('style')
> or are you using the new parameter as a hard coded
> string to integrate with HTMLcomponents? Which
> seems to have css as the first param' and is set to
> null?
The StyleManager is not about CSS. It's about being
able to apply javascript functions to an exiting
widget to modify it's functions, change it's look and
it's behavior.
For example you can use the StyleManager to convert an
ordinary DynLayer into a button widget by just
applying the "ButtonStyle". Later you could then
change that layer into a ProgressBar by just applying
the "ProgressBarStyle".
IMO it's a completely modular and fashionable way to
design DynAPI widgets. With StyleManager a basic
widget can be morphed into another widget by just
simply changing the style.
> With an established interface it is preferable to
> add to,
> rather than change and break backward compatibility
Ok, I guess we'll just keep the 7th argument and use
setStyle() to change styles on DynLayers.
--
Raymond Irving
>
> -
> Kevin
>
> ----- Original Message -----
> From: "Raymond Irving" <xw...@ya...>
> To: "DynAPI-Dev" <dyn...@li...>
> Sent: Wednesday, July 30, 2003 3:10 PM
> Subject: [Dynapi-Dev] The 7th argument in DynLayer -
> Introducing the StyleManager
>
>
> > Hello Everyone,
> >
> > I've been doing some thinking and came up with a
> > solution that I think is able to give us more
> speedy
> > layers than what we currently have.
> >
> > The solution employs a StyleManager that will
> enable
> > us to be able to change the look, feel and
> behavior of
> > DynLayers and widgets.
> >
> > With this in mind I would like to make a proposal
> that
> > we change the 7th argument in DynLayer to use the
> > "style" argument instead of image.
> >
> > IMO background image in rarely used by developers
> and
> > could be easily changed with the use of setBgImage
> or
> > dictionary object ({}) in those rare cases. I
> think
> > the "style" argument will be used much more
> frequently
> > than bgimage.
> >
> > Possible usage of styles:
> >
> > // create a plain DynLayer
> > var l = new
> > DynLayer(null,0,0,10,10,null,'PlainLayer');
> >
> > // creates an html container
> > var l = new
> > DynLayer('Hello',0,0,null,null,null,'HTMLLayer');
> >
> > var l = new
> DynLayer(null,0,0,0,0,null,'CoverLayer');
> >
> > The above layers will use customize code found in
> the
> > Style object to improve the creation speed of the
> > layers.
> >
> > What do you think? If it's a no, then I guess
> we'll
> > just have to use setStyle() and keep the image
> > argument.
> >
> >
> >
> > --
> > Raymond Irving
> >
> >
> >
> >
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! SiteBuilder - Free, easy-to-use web site
> design software
> > http://sitebuilder.yahoo.com
> >
> >
> >
>
-------------------------------------------------------
> > This SF.Net email sponsored by: Free pre-built
> ASP.NET sites including
> > Data Reports, E-commerce, Portals, and Forums are
> available now.
> > Download today and enter to win an XBOX or Visual
> Studio .NET.
> >
>
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> >
>
http://www.mail-archive.com/dyn...@li.../
>
>
>
-------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built
> ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are
> available now.
> Download today and enter to win an XBOX or Visual
> Studio .NET.
>
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
>
http://www.mail-archive.com/dyn...@li.../
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
|
|
From: Kevin <ke...@ke...> - 2003-08-07 17:06:30
|
Raymond wrote: > The StyleManager is not about CSS. It's about being > able to apply javascript functions to an exiting > widget to modify it's functions, change it's look and > it's behavior. > > For example you can use the StyleManager to convert an > ordinary DynLayer into a button widget by just > applying the "ButtonStyle". Later you could then > change that layer into a ProgressBar by just applying > the "ProgressBarStyle". > > IMO it's a completely modular and fashionable way to > design DynAPI widgets. With StyleManager a basic > widget can be morphed into another widget by just > simply changing the style. My thinking is: button1=new Button() button1.setHighLight(...) progressbar1=new ProgressBar() progressbar1.setScale(...) ... Morph button1 to a progressbar ... button1.setScale(..) ? How would we know button1 has new methods as setScale() was before meaningless for a button? button1 and progessbar1 are instances of their own class with separate attributes and methods. Morphing button1 to a progressbar? Ok fine, but morphing 'setStyle(...) or maybe setMorph(...)' is not a method of either class but more a method of a management class not related to (or inherited from) a DynLayer. Perhaps an example would help in understanding what is intended in an OOP context. Thanks. - Kevin. > > With an established interface it is preferable to > > add to, > > rather than change and break backward compatibility > > Ok, I guess we'll just keep the 7th argument and use > setStyle() to change styles on DynLayers. > > -- > Raymond Irving > |
|
From: Raymond I. <xw...@ya...> - 2003-08-07 23:47:23
|
Hi, Once I'm done with a simple example I'll post it to the list. -- Raymond Irving --- Kevin <ke...@ke...> wrote: > > Raymond wrote: > > > The StyleManager is not about CSS. It's about > being > > able to apply javascript functions to an exiting > > widget to modify it's functions, change it's look > and > > it's behavior. > > > > For example you can use the StyleManager to > convert an > > ordinary DynLayer into a button widget by just > > applying the "ButtonStyle". Later you could then > > change that layer into a ProgressBar by just > applying > > the "ProgressBarStyle". > > > > IMO it's a completely modular and fashionable way > to > > design DynAPI widgets. With StyleManager a basic > > widget can be morphed into another widget by just > > simply changing the style. > > My thinking is: > > button1=new Button() > button1.setHighLight(...) > progressbar1=new ProgressBar() > progressbar1.setScale(...) > ... > Morph button1 to a progressbar > ... > button1.setScale(..) ? > > How would we know button1 has new methods as > setScale() was before meaningless for a button? > > button1 and progessbar1 are instances of their own > class > with separate attributes and methods. Morphing > button1 > to a progressbar? Ok fine, but morphing > 'setStyle(...) or > maybe setMorph(...)' is not a method of either class > but > more a method of a management class not related to > (or > inherited from) a DynLayer. > > Perhaps an example would help in understanding what > is > intended in an OOP context. Thanks. > > - > Kevin. > > > > With an established interface it is preferable > to > > > add to, > > > rather than change and break backward > compatibility > > > > Ok, I guess we'll just keep the 7th argument and > use > > setStyle() to change styles on DynLayers. > > > > -- > > Raymond Irving > > > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built > ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are > available now. > Download today and enter to win an XBOX or Visual > Studio .NET. > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://www.mail-archive.com/dyn...@li.../ __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com |