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
------------------------------------------------------------------------------
Virtualization is moving to the mainstream and overtaking non-virtualized
environment for deploying applications. Does it make network security
easier or more difficult to achieve? Read this whitepaper to separate the
two and get a better understanding.
http://p.sf.net/sfu/hp-phase2-d2d
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
