Just a though (unless there is another way?
If I have something like (sudo code)-
Tags
People
Badges
Help
<window id="outerDiv" apply="pfactory.ComposerFactory" >
<label id="outer_label"></label>
<div id="innerDiv">
<label id="inner_label"></label>
</div>
</window>
all is fine and it is easy to access "outerlabel" or "innerlabel" in ComposerFactory but if I have (sudo code) -
<window id="outerDiv" apply="pfactory.ComposerFactory" >
<label id="outer_label"></label>
<window id="innerWin">
<label id="inner_label"></label>
</window>
</window>
I have to use (sudo code) to access "inner_label" -
label = innerWin.getFellow("inner_label")
It is not a major problem, just an annoyance. The reason of course is that the Window component creates a new idspace.
perhaps it would be a nice idea to have something like "newIdspace="false" as an option of the window component?
Or am I missing something?
Hey there,
I'd say it depends why you need the window for?
If you want an object that can be moved around, resized, etc, you can consider using a Panel or a Groupbox, both of which have window-ish features without implementing IDSpace.
If you just want a logical container, then good old Div might be a better choice since it's lightweight and all that.
Did you have specific features you want to use on that container?
Regarding the initial annoyance: if you are using a SelectorComposer, you can still @Wire components located inside a window. You can do that by chaining the selectors in the wire annotation. For example: @Wire("#myWin #myComp") will wire the component id="myComp" inside of the window "#myWin".
MDuchemin ( 2021-06-10 11:20:36 +0800 )editAsked: 2021-06-09 16:51:24 +0800
Seen: 3 times
Last updated: Jun 09 '21
