Hi Andreas (nice name btw ;-)) ,
Below you'll find my suggestions to your points.
- Does it make any difference if we add the window to qx.ui.core.queue.Dispose?
This wouldn't make any difference because that's exactly what
qx.ui.core.Widget.destroy() does.
- I stumbled over a blog post [3] where a solution is given, maybe this would
be a nice feature for qooxdoo disposing process?
What do you think?
This could indeed be a workaround for your problem but I don't think it would
be a good generic behavior for every use-case, because it would simply slow
down every object-disposing, no matter if the browser actually stumbles or not.
I think it would
- Any other ideas are really welcome! :)
I see two possible ways how to solve the issue:
1. Instead of destroying the whole window at once, you could group the forms
inside the win into smaller chunks and destroy them one after another.
2. You could reuse the forms as you already mentioned. Also ake a look at the
helper-class qx.util.ObjectPool which offers some convenience for exactly this
purpose.
Hope this helps!
Andreas Parusel
Software Developer
Applications & Integration
1&1 Internet AG
Ernst-Frey-Straße 10
DE-76135 Karlsruhe
Telefon: +49 721 91374-6184
E-Mail: andreas.paru...@1und1.de<mailto:andreas.paru...@1und1.de>
Web: www.1und1.de<http://www.1und1.de>
------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
