Hi, Just a little question about the way qooxdoo manage widgets and layouts at dom level.
Everything (container, content, decorator) is always expressed in terms of pixels for the widths and heights. Is there any good reason about this choice ? I mean... if we resize a widget (a qx window for instance), there is a recomputation of the size for the container and then we must affect the new size to all the container's children. I don't know if affecting the new width or height this way is really expensive in terms of performance but I wonder why not use percentages (=100%) for the children. If we apply this kind of computation generally to an whole qx app, it could explain why resizing the browser's window is so slow (it must be applied to all "layouted items"). Could someone shed light on it ? Best, BenoƮt -- View this message in context: http://qooxdoo.678.n2.nabble.com/general-question-about-widgets-and-layouting-at-dom-level-tp5291840p5291840.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
