Hi Stefan, thanks for sharing your considerations.
Cheers, Fritz On Mon, 4 Oct 2010, Stefan Andersson wrote: > > Fritz, > > Thanks! > >> are qx.core.Init.getApplication().getRoot() or qx.bom.Document of any help? > > both insist that you have to know the children of "root" or "document" and > that is the problem of walking downwards the hierarchy. The other way > which we have used, walking upwards the hierarchy generates the many > getLayoutParent's but we don't need to know more than the level where the > app root layout is located so it does not work if parts of the widgets > move around and the level changes thereby.... > > It seems that the best way is to create a static variable in the > Application class containing our app layout root and this would remove the > upward traversing getLayoutParent calls in the layout children. > > What we were looking for was a way to delegate and broadcast calls within > the layout hierarchy, not in the class/object hierarchy. That would have > solved this in a better way. A message bus is intended for, as an event > listener system, listen to messages coming all over from and act upon it, > while we wanted the upward or downward layout hierarchy starting from one > or more layouted widgets at the same level. > > Stefan -- Oetiker+Partner AG tel: +41 62 775 9903 (direct) Fritz Zaucker +41 62 775 9900 (switch board) Aarweg 15 +41 79 675 0630 (mobile) CH-4600 Olten fax: +41 62 775 9905 Schweiz web: www.oetiker.ch ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
