> The interresting thing is that I have an implementation using
> the original
> dynapi, it was faster and I had no troubles like the one I
> described.
That is quite possibly because of DynAPI2 's size (term bloated is well
known by DynAPI2 :)
Old dynapi created divs, and far less code linking to that div. A normal
DynLayer object
in DynAPI2 contains a lot of methods, functions and parent objects of which
it inherits. I think
this all causes the speed and memory problems when using many layers.
> I don't have the need to move objects around the hierachy
> after the page is
> loaded, but I need to nest widgets in layers with custom html.
Then you might reconsider the use of DynAPI2.. not sure what your target
browser is
but you could create simple widgets without the use of any api.. they will
work alot faster
and require alot less resources.. sadly those tricks only work on IE5+ and
DOM compatible
browsers (ie4 might be so kind to run it aswell). Maybe there's a smarter
way to nest
those widgets without using so many layers "around it".
Pascal Bestebroer ([EMAIL PROTECTED])
Software ontwikkelaar
Oberon Informatiesystemen b.v.
http://www.oibv.com
_______________________________________________
Dynapi-Help mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-help
