Hi Alex,
2018-06-30 8:06 GMT+02:00 Alex Harui :
>
>
> On 6/29/18, 11:29 AM, "carlos.rov...@gmail.com on behalf of Carlos
> Rovira"
> wrote:
>
> Hi Alex,
>
> thanks for the explanation I think finaly understand the main
> difference
> between Group and Container. Although, I see
On 6/29/18, 11:29 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
wrote:
Hi Alex,
thanks for the explanation I think finaly understand the main difference
between Group and Container. Although, I see Group seems to have many
things already setup to be able to do
Hi Alex,
thanks for the explanation I think finaly understand the main difference
between Group and Container. Although, I see Group seems to have many
things already setup to be able to do have this feature. Don't know if
having two separate components make sense, or there's more differences?
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
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
