Hi Alex, El mar., 25 dic. 2018 a las 18:19, Alex Harui (<[email protected]>) escribió:
> Ideally, there won't be any Royale components that are "MXML-only", > meaning they can only be used in MXML. Right, this component should be used in AS, maybe I was mixing my use case in the explanation, but I always think in components and not if they are used in AS3 or MXML. It sounds like there is "one set of children" for this component, No. The components declared are part of what we call "Chrome" in components like Panel you referred. > so folks will be tempted to call addElement to add children from AS. Yes. doing "component.addElement(childComponent)" must add childComponent to the right subelement in component like in Panel. > Basic Panel already has code that redirects the actual parent to an > internal container. Maybe that's what you want. > > Yes, I already worked with Panel. And Jewel Wizard really follows Panel way of doing things. But I wasn't trying to create a complex royale component with various files (strand, beads, with model, controller, view, and so on...). Maybe the difference is that Panel is a more elaborated component and I was searching for some basic way of doing things. But maybe the only approach is go the Panel approach, since I must use addElement for the initial components as well. I'm not sure if we have a component that has multiple sets of children, but > it is certainly possible. I really don't look for multiple sets por children. I think that would be somewhat problematic for the end user. Ok, so I'll follow Panel convention for this case too. Thanks! -- Carlos Rovira http://about.me/carlosrovira
