Re: [Dynapi-Dev] TCanvas vs. DynLayer

[Eytan H. <ey...@tr...>]

You just don't get it.
It's not that I use different code and the version I tested with has a
children list. (uses my TList so didn't include it).
The reason it's faster is such. When browsers parse js code and create
objects they create actual objects in their application. That means that for
every dynlayer there is an object inside Netscape or IE with actual objects
in them. In your method of creation you:
Create new DynLayer()
Call add child to the parent
Parent does the following
static Create the virtual object
static Create the actual element
static Assign the element
This means that the browser has to
Get Parent object in browsers memory
Call addchild
Call static line and create js object
Call static line and create js element
Call staticassignment where you have to get obj1 and obj2 and assign
and more of this type of thing
It slows down the process by a whole lot
What my create does is:
Create new Canvas()
myCanvas.create does this:
Check who the parent is
if null create in the actual document
if Canvas create under it
No passing of object between methods, not assigning no static methods.

8an