Hi Benco, Am 14.07.2010 12:01, schrieb benco: > 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. This computation is deeply incorporated into the layout engine of qooxdoo. The resize (and all other computation) is done in javascript meaning that the browser does not need to render it directly - only after the layout computation is done. Using absolute pixel has one big advantage: there is very little (if any) space left which the browser can doing something wrong.
> 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. There are layouts which support percentage values - if you mean this with percentage values. > 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"). Do you have an example for this? Is this valid for a specific browser or are all browsers affected? cheers, Alex ------------------------------------------------------------------------------ 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
