I vote for a 'modified' 'object model.
My main concern is for an object that can delete itself effectively.
Also, the base Layer Object should be just that,
BASIC. A small and simple as possible.
An icon in the top left corner of you web page.
Which does nothing more than just sit at the top left corner of your webpage
uses a very small fraction of the functionality currently built into the
DynLayer object.
----- Original Message -----
From: "Eytan Heidingsfeld" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 30, 2001 12:31 AM
Subject: [Dynapi-Dev] Next Generation part II
> Ok, so now we have all discussed and recommended and finished throwing
> stones. After we all got in-depth about OO and prototypes and classes
where
> are we going. My recommendation of how to act is as such:
> * Create a DynLayer(mayber change it's name) that is totally seprate and
> stand alone. It includes only methods to affect the layer and events that
> are triggered from the outside(mouse and keyboard events).
> * Create the basic objects: Application, Object, Component
> Application:
> Manages the DynLayers focus and events
> Object:
> Basic object with create and destroy
> Component:
> Basic object with dynlayer.
>
> I'd be glad to change the model if anyone has new and improved ideas.
>
> Now except for the actual model I want to know if we have enough ppl who
> want a next generation to continue.
>
> 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
