Community
Participate
Working Groups
http://www.instantiations.com/forum/viewtopic.php?f=1&t=2346&p=8905#p8905 We can add support for something like this in future. When I say "something like this", I mean that we will use same style as for "lazy creation" in Swing - each container method creates also children components (invokes corresponding methods). In contrast, in your example hierarchy is build in single method, i.e. all single methods are invoked from single one. I think that Swing approach is better for structuring source. This is not so easy to support however, so this will require some time.
Probably better approach: each widget should be in field and in each parent method we just call createSomeChild() methods. Or getSomeChild() methods, but without using result of "get", just to allow to change later its modifier from "private" to "public" and allow its displaying in VI.
There was also idea was that we can always call getSomeChild(parent), but "parent" is used only first time, during UI construction.
Closing. Please reopen if this is still an issue.
