Re: git commit: [flex-asjs] [refs/heads/develop] - Created IChrome interface which helps Container (and others in the future) identify children that should be treated as part of its chrome and kept distinct from content children. TitleBar and ControlBa...

[Alex Harui]

On 7/25/13 3:32 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote:
>>
>This would be a confusing API to the user, isn't it?
Funny, we debated a couple of ideas and I thought it would be less
confusing to not have both addElementAt and addChromeElementAt in the API
documentation and instead mark what is being added and handle it
internally in a single addElementAt call.  My thinking was that the
component developer can learn to mark things, but the app developer won't
have to worry about that.

>Can we split it up
>into two methods: addElementAt(o:Object,i:int) and
>addChromeElementAt(o:IChrome,i:int)  ?
Sure, let's see if others have opinions and go with the majority.  I
really could go either way.
>
>Thanks,
>Om