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. And as
far as I understand, the difference is that in the old dynapi, all the divs
and their content were generated inside the body, and the objects were created
on these existing divs, like the inline layers in the new dynapi. The
exception is that you could ask the "old widgets" their html as soon as you
created them, so it was possible to nest custon content and widgets. With
dynapi 2, it's only after the widgets received oncreate that it's guaranteed
that they fill their html instance variable, and you can't add them as child
to an inline layer.
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.
I posted an issue I had with Netscape and Kanji characters which are lost if
you write to a div after the document is loaded. I found a way to hack dynapi
for netscape so that I manually call create() on the top objects inside a
function in the body tag, and re construct the hierarchy in the regular onload
method, and that way I got the divs of widgets generated in the body, and re
initialized as expected after.
Would see a way to do that for IE on the current code base ? based on my
experience, it does make a difference in the limit/performances.
Benoit Marchant
Pascal Bestebroer wrote:
> > The test scenario I had a couple of days ago with 1000 layers
> > took only
> > about 8MB memory. The creation took a couple of seconds with my 600MHz
> > Pentium. Each contained some text but nothing else. It would
> > be nice to know
> > what is a reasonable amount of "real world" layers, though.
> >
>
> try the same test, but insert table and "real" contents in each layer..
>
> and although I don't understand it there are still alot of people that work
> with 200mhz pentiums and 64mb memory.. those systems can be crashed
> very easily.
>
> There's no "real world" limit (at least I don't know it) but I think having
> 64 layers should be enough for any page...if you need 100+, you might wanna
> look for other solutions or do some thinking about
> your site's design issues (just my opinion though).
>
> 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
_______________________________________________
Dynapi-Help mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-help
