[EMAIL PROTECTED] schrieb:
> Good that it is known to the developers ;-) ... this should definitely be 
> documented!

Yeah sure. Many things are better with more documentation. But we are 
quite busy with 0.8 right now :)

> 
> 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 ?

The GMX web mail application works without nearly any dispose(). We have 
a massive use of pooled widgets there. One reason for the superior 
performance.

> 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 ?

Mhh, I do not like to modify dispose() directly. Better add a destroy 
method which does exactly the parent removal and dispose and document 
this in code and wiki.

> 
>>> 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.

This is not the case in my opinion. The node is only removed after the 
layout queues etc. have been flushed which never happens for widgets 
which are disposed already.

> Otherwise the leak after introducing setParent() would be much bigger.

DOM nodes to not leak that massively. The links to the JS objects are 
gone. It's just the generated markup.

> 
> 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. 

We are aware of this and plan to release a 0.7.4 some time after 0.8 is 
out. It's just that 0.8 has the focus at the moment.

> Since RAP-applications are always single-paged, this is quite a big 
> problem for us.

We have already heart your and others feedback on this :)

Sebastian

> 
> 
> 
> 
> 
> 
> -------------------------------------------------------------------------
> 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


-------------------------------------------------------------------------
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

Reply via email to