Container creates a ContainerContentArea as its child and then all children become children of the ContainerContentArea. Group does not do that. The concept of having an inner content area forms the basis of complex containers with "chrome" around it, such as Panel. I'm not sure how your requirements about positioner are different from what Container and Panel do, so you might need to provide more detail about the differences.
HTH, -Alex On 6/29/18, 8:17 AM, "[email protected] on behalf of Carlos Rovira" <[email protected] on behalf of [email protected]> wrote: Hi, I trying to find the best route to have a container component that has some nested html tag structure and adding child elements will be added to the inner element, but the rest of normal behavior (id, listeners, etc..) will be referencing the positioner. What's the best way to do this? Use Group or Container? what I should override? get host() method in BeadViewBase should be override? how? Hope you could point to the best way of doing this thanks -- Carlos Rovira https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cbef963261fdf463682d308d5ddd37182%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636658822573164461&sdata=kLJNuz8V8r46O6YvTUm5TuQHx78VXnrPSbAbp2p%2BOLg%3D&reserved=0
