Ok, first: totally respect your work, but I guess it's just because I was
against the whole idea of changing stuff that I'm making some negative
comments again :)
First of all, I don't see the big differences here Object wise. The only
difference I see is that in your case the adding is done by the child and
not by the parent.
The current DynAPI code uses a method of the parent to add the child, your
code is using a method of the child to add it to the parent. But again,
that's all I see done differently.
It might be way to early to comment on this by me, but I guess I'm just not
seeing the bigger changes and ideas behind
this, and you did ask for "anything else" :-)
Pascal Bestebroer ([EMAIL PROTECTED])
Software ontwikkelaar
Oberon Informatiesystemen b.v.
http://www.oibv.com
> -----Oorspronkelijk bericht-----
> Van: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]Namens Eytan
> Heidingsfeld
> Verzonden: dinsdag 6 februari 2001 15:30
> Aan: Dynapi-Dev
> Onderwerp: [Dynapi-Dev] TCanvas
>
>
> Got working on it. Have it working. I'd appreciate it if you
> test it, fix
> it, have idea or anything else. A lot of the code is borrowed from the
> DynAPI(although most of the borrowed code there is only one
> way to write).
>
> It works like this.
> myCanvas = new Canvas(owner);
> myCanvas.create();
> if owner is ommited it is created in the document itself.
> Currently working
> on events. About to add destroy.
> Supported methods:
> * setHTML
> * moveTo, setX, setY, getX, getY
> * setVisible, getVisible
> * setSize, setWidth, setHeight, getWidth, getHeight
> * setBgColor
>
> Will have all the other methods ported.
> you have to also include the browser.js file.
>
>
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
