This is why Gordon and Darrell are probably better suited to answer these questions. mx:Container is probably special-cased as I don’t see metadata for it either. IIRC, the compiler generates these things called UIComponentDescriptors for mx containers. For Spark and FlexJS, we are using [DefaultProperty]. Spark also uses [ArrayElementType] and we should add the right ArrayElementType values to the FlexJS code.
On 10/14/14, 2:44 PM, "Neverbirth" <neverbi...@gmail.com> wrote: >Thanks for your replies. > >My doubt comes from containers and the like, for example, how does an IDE >know the direct child of <mx:Container> can be objects inheriting from, >eg, >a GraphicElement? I'm a bit familiar with DefaultProperty (and >ArrayElementType), but I didn't see it in that case, did I overlook it? or >is it a special case? And if it's a special case, which are the proper >interfaces and/or classes to check depending of each framework? > >The failing cases I've seen come from custom implementations that define a >DefaultProperty, but I'd like to cover every case possible correctly. > > > >-- >View this message in context: >http://apache-flex-development.2333347.n4.nabble.com/Determining-which-MXM >L-elements-are-containers-tp41370p41381.html >Sent from the Apache Flex Development mailing list archive at Nabble.com.
