Hi Jim,
I am not sure which version of qx you are using, but I experienced a
very similar problem a long while back with qx 0.6.x. My final
solution was to implement object pooling, and reuse pooled instances
rather than instantiating new ones all the time. I added my Pool
class to the contribute project, and (from memory -- must have been a
year ago now) I think Fabian migrated it to qx 0.7.x.
Simon
On Thu, Jul 3, 2008 at 10:52 AM, Jim Hunter <[EMAIL PROTECTED]> wrote:
> I am running into a troubling situation and am looking for a little help. My
> application re-uses 'tool windows' to display new information. It does so by
> removing all children (using a function I wrote to iterate through all
> children, destroy them (they iterate their children before destroying
> themselves). Then it destroys itself. Then I add the new contents to the
> tool window. In FireFox (all versions) I have no problems and the page
> renders in the same amount of time every time I bring it up. In IE (all
> versions 6-8), it takes longer and longer to render each time I bring up the
> tool window (I am using a qx.ui.layout.DockLayout as the main body of the
> tool window). And when I say longer, it goes from 2 seconds to 5 seconds to
> 9 seconds to 15 seconds to 25 seconds etc. It gets out of control very
> quickly.
> Has anyone come up with a way to manage this or even eliminate the problem?
> To me, it looks like the objects are not getting destroyed in memory and
> it's causing IE to start choking on them and doesn't release them as it
> should.
> Here is the function I use to clean out the tool before I add more objects
> to it:
>
> disposeChildren:function()
> {
> try{if(typeof this.hasChildren!='undefined')
> {
> if(this.hasChildren()==true)
> {
> this.forEachChild(function(chld)
> {
> chld.disposeChildren();
> chld.setParent(null);
> chld.dispose();
> qx.ui.core.Widget.flushGlobalQueues();
> });
> }
> }}
> catch(e)
> {
> try{this.setParent(null);
> this.dispose();
> }
> catch(e){}
> }
> }
>
>
>
> Any assistance would be greatly appreciated as we absolutely need to have IE
> working somewhat like FireFox. i know it's not going to work as fast, but we
> do need it to be consistant.
>
> Thanks,
> Jim
>
>
>
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
