Thanks for the report. Sure it is ok to add an issue for that because it sounds like a valid use case. :)
Am 26.10.2012 um 09:07 schrieb Dietrich Streifert <[email protected]>: > created enhancement bug with attached patch: > > http://bugzilla.qooxdoo.org/show_bug.cgi?id=6932 > > Regards > Dietrich > > > Am 25.10.2012 13:35, schrieb Dietrich Streifert: >> Hi Thomas, >> >> I think the best interface for my needs would be to have a method >> releaseChildControl which simply removes the childControl from the >> child control array. Quite the opposite what method >> qx.ui.coreWidget._createChildControl does. >> >> An additional parameter to remove would not fit here because the child >> control is not necessarily the direct child of the controlling widget. >> >> So the call stack to decouple the child (table) control from the >> control would be: >> >> control.releaseChildControl ('table'); >> control.remove(table); >> table.destroy(); >> >> I'm not quite shure about the method naming. >> >> What do you think? >> >> I'd like to create a patch along with the bug report. Is this OK? >> >> Mit freundlichen Grüßen >> Dietrich Streifert >> Visionet GmbH >> > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
