Since IE is way more popular I started with it. I was wrong with my
assumption that nullifying objects (not even talking about html
elements(layers)) does the whole thing. Let me tell you what I discovered:
if you create 10000 small object and then nullify them nothing happens but
when you recreate them still the memory stays stable. I want to test replace
"= null" with "= [];" maybe that will help.
Identified positive freeing of memory when changing url. Now you all may
say: "so what this sux we can't force them to change url!!" it might be ok
if we design such a system(this design fits well with the talks about a new
API"
We create a framed page
one called RAM and one regular one where you place your project.
In the RAM page there is a method called createObject which does the
following:
* takes the type of object expected
* adds a new object of that type to an array called mem
* returns the index
then on the regular page we say
i = createObject(DynLayer);
myDynLayer = parent.frames[0].mem[i];
(there will be a shortcut to parent.frames[0]).
Then when we want to free mem we pass the mem array to the main frame change
the url to an empty page and reassign the mem array.
Not even sure if this system works. Gonna try it now anyone else got ideas?
8an
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
