Good that it is known to the developers ;-) ... this should definitely be documented!
Introducing a destroy method would be a good idea - and also a good place to document the differences to a simple dispose. I think that 'interims-disposes' as you call it are quite common, when creating 'single-paged' qooxdoo apps, aren't they ? Maybe even dispose should be overridden to create a special comment for widgets. I think otherwise it's not really obvious that parents have to be reset before disposal ? >> The DOM node issue would remain though. If you call setParent(null) the DOM-node is correctly removed. Circular references between widget and DOM are reset in the destructor of Widget. Otherwise the leak after introducing setParent() would be much bigger. So from my point of view, there is no problem with the latest 0.7.x-branch currently (if you know that setParent will do the trick). Anyway - in 0.7.3 the other important changes regarding theme-management are missing. Without a 0.7.4 noone has a chance to write a memory-sensible single-paged qooxdoo-app right now. Since RAP-applications are always single-paged, this is quite a big problem for us. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
