On 1/28/20, 1:01 AM, "Carlos Rovira" <[email protected]> wrote:
Hi again :),
I still didn't see the code, but was imagining how I'd like to use this
feature.
Some thoughts:
1.- Could be possible to have it as a bead for UIBase components a side of
the UIGraphicBase that could still be convenient for some cases?
Disclaimer: I haven't written the code or looked at it, so this is just a
high-level opinion: Regarding a bead for UIBase, I think it would depend on
how the "child 0" problem gets solved. My reason for posting is to remind
folks that in theory, the Basic Containers already support an internal
container. I haven't found a lightweight way of enabling internal containers,
mainly because I didn't want to mark the children and compute or track the set,
but also because since it is currently used for "chrome" (Panel TitleBar), it
is relatively simple to enable it the way it is.
Also, MXRoyale's UIComponent is essentially as heavy as a Basic Container, and
Spark Skinning emulation supports a separate child Skin. Other component sets
could just start out being heavier if they want to quickly enable this new
library via a bead.
Of course, I could be wrong...
-Alex
