Hi Alex, Thanks for your reply.
Alexander Steitz wrote: > > 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 agree with it all. But I wonder if it is efficient for complex layouts (as you said, all the resizing operations are done in javascript but not by the browser directly) and so, I'm thinking about replacing most of my full ui applications in inline ones to decrease recomputing operations. And if we consider widgets like windows for instance, it would be simpler to affect to the content element a width of 100% - so the update is done automatically when the container element is resized. Alexander Steitz wrote: > > There are layouts which support percentage values - if you mean this > with percentage values. > I know but I'm afraid the percentage values are transformed in their "pixel" equivalent at running (at least for the canvas layout). So, the problem stay the same. In other cases, the flow layout use absolute positioning towards float divs - but as you said earlier, absolute positioning is the best in managing browsers rendering differences. Alexander Steitz wrote: > > Do you have an example for this? Is this valid for a specific browser or > are all browsers affected? > It's downright the case with FF. I haven't tested with other browsers but I guess it's the same. Launch the demobrowser app and resize the browser window, the operation is clearly slower than using percent values because of all the width and height recomputations and/or reassignements. That's why I was wondering if it was possible to optimize it by specifying some containers with "percentage layouts"... Best, Benoît. -- View this message in context: http://qooxdoo.678.n2.nabble.com/general-question-about-widgets-and-layouting-at-dom-level-tp5291840p5293291.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
