>> This is interesting. I have dome something similar: I have added a unit
>> test class, which asserts for each widget that it leaks no objects and >> no event listeners. Unfortunataly I won't be able to do any more work on this this week, but I think the 'Leakfinder' could just be added to this testcases (good to hear, that such testcases exist :D). Actually my approach is just a bit more exact as your approach as it searches the whole JS-tree and not 'just' checks some choosen registries. Thus it is able to spot any unwanted reference wich keeps an object alive. ------------------------------------------------------------------------- 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 qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
