And see the API part, this means not just for making things work
cross-browser, but also make the underlying code transparent and as easy to
use as possible.
So the difference:
myWidget.moveTo(50,50)
or
myWidget.DynLayer.moveTo(50,50)
would
1. add more code in general
2. not as transparent as wanted.
A DynLayer and Widget can now be controlled in exactly the same way, but if
every widget needs to be accessed thru it's dynlayer object, a dynlayer and
widget won't be controlled in the same way.
The only thing you gain with this is the fact that any deletion code we
might create (a single function probably) would be easier, yet all other
code created by users would be larger and more "difficult to understand" for
users.
Pascal Bestebroer
[EMAIL PROTECTED]
http://www.dynamic-core.net
> -----Oorspronkelijk bericht-----
> Van: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]Namens Eytan Heidingsfeld
> Verzonden: zondag 25 februari 2001 9:54
> Aan: [EMAIL PROTECTED]
> Onderwerp: Re: [Dynapi-Dev] a few hours for only 2 lines of code.. damn!
>
>
> It HURTS!
> My My The Rocks fell like rain!!
> (And Feb 24th is even my birthday ;-)
> There will be no difference in memory if you place it as an
> object but it is
> just better programming. Straight out! The problem is that you think of
> DynLayer as a widget instead of an interface remember it is Dyn - API
> (Interface is the I)
> 8an
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
