RE: [Dynapi-Dev] Next Generation

[Pascal <pb...@oi...>]

Object Oriented indeed, as Dann mentioned, embraces both Class and
Prototyping.

Your stating that prototyping doesn't exist, but then you should take a
better look at what where doing with the DynAPI.. correct: Prototyping.
There might not be much info on prototyping out there on the net, but
javascript is actually using prototyping, not class-based.

Both class and prototyping fall under Object Oriented development. I don't
know what the definition of OO is, but I think it's just a global definition
of developing things using reusable-object code, under which both
class-based and prototype-based fall.

Also your previous mail stated "OO in JS or ECMA script is documented. If
you read carefully you will notice
that JS was designed as a Class Oriented language".. I'm pretty sure the
original Netscape implementation of javascript was build on Prototype-based
(as stated in there documentation)

And coming back to that ever lasting quest of mine, redoing inheritence, or
creating functions for it is not needed.. the way we are currently doing
widgets is how Javascript handles inheriting (with prototyping).. the same
structure and idea can be implemented to the DynLayer and DynDocument
objects (see Dynacore on howto).


Pascal Bestebroer (pb...@oi...)
Software ontwikkelaar
Oberon Informatiesystemen b.v.
http://www.oibv.com

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Eytan
> Heidingsfeld
> Verzonden: maandag 29 januari 2001 14:14
> Aan: dyn...@li...
> Onderwerp: RE: [Dynapi-Dev] Next Generation
>
>
> Lets really get the terms straight.
>
> Class-Oriented: You develop classes. You do this be using the
> prototype of
> an object. Then this object becomes basically a prototype, a
> class and then
> for inheritance an object says use this objects prototype and
> add these
> members.
> Object-Oriented: You develop classes by defining an interface and then
> implementing this interface. To use this object you create a
> new object
> based on this class. Inheritance is dealt with by saying I
> want to inherit
> this and this class. Then your new object has the same
> members as those
> classes with pointers to their implementation.
>
> There is no PO only CO and OO the difference is inheritance and memory
> management but since there is no memory management in JS there is no
> difference but inheritance.
> 8an
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>