Yes, Dynlayer and dyndocument use the same base class to inherit from.
dynobject contains all parent-child relations (adding,removing,deleting,
etc)
Also events are extending the dynobject, so dynlayer and dyndocument also
share that same extension (no differences between the code).. should make
developing things easier (having one object that contains the code, others
simply use it)
it looks like its working great (the release has been out for a while now,
haven't heard of big problems or found myself.. all Dynapi examples work
correctly with dynacore)
Pascal Bestebroer ([EMAIL PROTECTED])
Software ontwikkelaar
Oberon Informatiesystemen b.v.
http://www.oibv.com
> -----Oorspronkelijk bericht-----
> Van: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]Namens Michael
> Pemberton
> Verzonden: vrijdag 16 februari 2001 14:43
> Aan: [EMAIL PROTECTED]
> Onderwerp: Re: [Dynapi-Dev] TCanvas vs. DynLayer
>
>
> do you mean dynlayer+dyndocument both inheriting from dynobject?
>
> Pascal wrote:
>
> > I already did some of these split ups in dynacore.. and it
> works ok, but is
> > not such a big speed increase (maybe a small increase when
> creating many
> > layers at initialisation)
> >
> > I split up things like sethtml, setx+sety, so you might
> want to look at that
> > before having to code it yourself :)
> >
> > I want to introduce all those changes to DynAPI aswell, but
> I think we
> > should first make sure NS6 works correctl aswell (not sure
> how many problems
> > there still are though).
> >
> > If you and Robert find it ok (main developers) I will try
> to include these
> > optimisations, and also add the dyndocument idea
> (dynlayer+dyndocument both
> > inheriting from dyndocument)
> >
> > cya,
> >
> > Pascal Bestebroer ([EMAIL PROTECTED])
> > Software ontwikkelaar
> > Oberon Informatiesystemen b.v.
> > http://www.oibv.com
> >
> > > -----Oorspronkelijk bericht-----
> > > Van: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED]]Namens Jordi -
> > > IlMaestro
> > > - Ministral
> > > Verzonden: vrijdag 16 februari 2001 14:21
> > > Aan: [EMAIL PROTECTED]
> > > Onderwerp: Re: [Dynapi-Dev] TCanvas vs. DynLayer
> > >
> > >
> > > Speed optimization can always be introduced. In fact, the
> > > latest precreation
> > > code that caused some old bugs to reappear and some people to
> > > complain about the
> > > API going backwards was introduced in order to speed up layer
> > > creation,
> > > something that was not a problem until people started wanting
> > > hundreds, even
> > > thousands of layers onscreen.
> > >
> > > I've been tempted to suggest this many times but I didn't
> > > want to spawn another
> > > "code split-up" argument. Some critical methods like, say,
> > > moveTo or setSize
> > > might speed up by doing.:
> > >
> > > if(is.ns) DynLayer.prototype.moveTo = function A
> > > else DynLayer.prototype.moveTo = function B
> > >
> > > I'll try myself in see what happens
> > >
> > > Pascal wrote:
> > >
> > > > me again :)
> > > >
> > > > I don't think this test is really useable.
> > > > Your current Tcanvas code misses ALOT of things DynLayer
> > > takes care of.
> > > >
> > > > DynLayer sets sizes, z-index,clipping,bgimages in
> > > initialisation (and also a
> > > > few other style properties.. note that setting a style
> > > property is what
> > > > slows everything down) I once did some optimization tricks
> > > to the dynlayer,
> > > > by removing sizes/clipping etc.. this speeds up things BIG
> > > TIME, but also
> > > > brakes useability for a large amount of widgets, and is
> > > less flexible.
> > > >
> > > > DynLayer has code included for fast child-creation.. even
> > > though there are
> > > > no child layers in your test, this code is still called
> > > (function calls).
> > > > This could be made faster in dynlayer, but for now is more
> > > readable for
> > > > developers. Do another test with layers containing a large
> > > amount child
> > > > layers.. Dynlayer's precreation will probably be faster.
> > > >
> > > > shreded enough? ;)
> > > >
> > > > 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: vrijdag 16 februari 2001 13:19
> > > > > Aan: Dynapi-Dev
> > > > > Onderwerp: [Dynapi-Dev] TCanvas vs. DynLayer
> > > > >
> > > > >
> > > > > I'd love to test performance one against the other. The only
> > > > > test I did was
> > > > > create 100 layers and check the times. In IE TCanvas was 200
> > > > > ms faster and
> > > > > in NS it was 1300(canvas) to 10000(dynlayer).
> > > > >
> > > > > I'd love you guys to start tearing my canvas to shreds.
> > > > >
> > > > > Included in the zip are:
> > > > > tcanvas.js
> > > > > browser.js
> > > > >
> > > > > they need to be included in the document(working on
> > > adding .include)
> > > > >
> > > > > 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
> > >
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>
> --
> Michael Pemberton
> [EMAIL PROTECTED]
> ICQ: 12107010
>
>
>
>
> _______________________________________________
> 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
