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
- Re: [Dynapi-Dev] Next Genera... Doug Melvin
- Re: [Dynapi-Dev] Next Generation .:: OCB ::.
- RE: [Dynapi-Dev] Next Generation Matthew Alan Shirey
- RE: [Dynapi-Dev] Next Generation Michael Ellis
- Re: [Dynapi-Dev] Next Generation Raymond Smith
- RE: [Dynapi-Dev] Next Generation Cameron Hart
- Re: [Dynapi-Dev] Next Generation Michael Pemberton
- Re: [Dynapi-Dev] Next Generation Doug Melvin
- RE: [Dynapi-Dev] Next Generation Cameron Hart
- RE: [Dynapi-Dev] Next Generation GORTSILAS ANDREAS
- Re: [Dynapi-Dev] Next Generation part II Eytan Heidingsfeld
- Re: [Dynapi-Dev] Next Generation part II Doug Melvin
- RE: [Dynapi-Dev] Next Generation Henrik Våglin
- RE: [Dynapi-Dev] Next Generation Michael Ellis
- RE: [Dynapi-Dev] Next Generation Michael Ellis
- Re: [Dynapi-Dev] Next Generation Raymond Smith
- Re: [Dynapi-Dev] Next Generation Raymond Smith
- Re: [Dynapi-Dev] Next Generation Richard Bennett
- Stats (WAS Re: [Dynapi-Dev] Next Generation) Doug Melvin
- RE: [Dynapi-Dev] Next Generation Michael Ellis