The only thing that was changed in the DynAPIX is now the NS6 is using
the precreation. NS4 is the only browser that doesnt support the
creation of all the children at once.
--
Robert Rainwater
On 3/27/2001, 11:31:18 AM EST, Eytan wrote about "[Dynapi-Dev] DynAPIX":
> Is it m
Thats the whole point of the new code. If you look carefully, it is
using the dom, but it only does one insert, instead of inserting all
of the children separately.
Creating an element with createElement may be faster, but try creating
an element and its 50 children with createElement. Thats 5
So with all this talk of DOM this and DOM that we don't take advantage of
DOM. And btw I think that creating elements in IE5 with createElement should
be faster. I'll have to test.
8an
___
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourcef
The layer's HTML tag, as well as those of its children are converted into a big
HTML string that is inserted as a block of text. Then elements are assigned for
those created. This is the precreation stuff Dan introduced several months ago.
BEfore that each children was created as a node, being muc
Is it my imagination or does DynAPIX not use createElement for IE5 and NN6?
8an
___
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
Some more on this, in DynObject.prototype.addChild there is a line:
if(this.created) c.create();
however the first line of DynLayer basically says if(this.created)return,
So in addition to my suggestion below should the line in
DynObject.prototype.addChild be changed to:
if(!this.created) c.cr
Trying to make myself useful, so I'm having a go at migrating LoadPanel to
DynAPIX. Out of the box it doesn't work, I think I've tracked down the
reason why. LoadPanel has a method called reload, which basically removes
itself from its parent then adds itself again (I'm not sure why, I didn't
writ
