I would love to see a more modular approach to the DynAPI as well.
For instance I like Pascal's DynObject for which DynLayer and
DynDocument belong since they share common functionality.  The same
could also be done for events (mouse and keyevents, etc all have some
common functionality).  I think the much of the dynlayer/dyndocument
stuff could be moved out of the DynAPI.js so that the DynAPI can be
used to support more than just dynlayers.

I don't really like the idea of OO in JS. The problem is Javascript
does not support OO. The DynAPI as it is now uses an Object-oriented
approach. There is no standard for trying to make javascript use OO
and their are lots of problems trying to do this in JS. As it stands
now, the widgets use proper subclassing, atleast as close as possible
in Javascript. I don't see why the next gener. couldn't use the same
approach. Its not really and OO issue, but a DynAPI design issue.

Maybe people can make some proposals to the list as to how to design
the next version.

However, the current version still needs to be improved with
Mozilla/NS 6 support (as well as other fixes) before any thoughts of
starting the next version begins.


-- 
// Robert Rainwater

On 1/28/2001, 8:23:31 AM EST, Eytan wrote about "[Dynapi-Dev] Next Generation":

> Hi,
> Since recent discussion has led to the reorganization of the code, and
> basically rewriting it I wanted to know what you guys think about a serious
> redo and not only a face lift. Then (yes I know I'm bugging you about this
> again but hey maybe someone will get convinced) we can at least implement
> some of the real OO code. Is there any way I can convince some of you. There
> are many reasons I want to do this but mainly stability. And also changing
> the amount of DynLayers used for everything and the weight of dynlayers. I
> have an example (will try to get it on a public server so you can see the
> bug too) that when you add more and more dynlayers suddenly some of them
> start to disappear and then appear out of the blue.

> all rocks will be accepted,
> 8an


> _______________________________________________
> Dynapi-Dev mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev


----------------------
DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/
DynAPI Homepage: http://dynapi.sourceforge.net/



_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev

Reply via email to