> I want a methodology for creating custom Component subclasses using BXML > markup. I want to be able to place such a component into other components, > sometimes by markup (bxml:include), sometimes programmatically (by > deserializing the bxml, which as I described earlier, I hide by a static > factory method on my component's class).
This makes sense. > Seems like I need to subclass a container, since otherwise how does the bxml > serializer interpret the child of the root element? Why not simply use the child element as the root? Is there any reason to add another level to the hierarchy? > Panel is certainly not what I want. I do want my component to undergo layout. So again, it really depends on what kind of layout you want to use. The layout containers provided by the platform cover a pretty large number of use cases. If you find that they aren't sufficient for your needs, it really isn't tough to create your own container. It also isn't that difficult to create a completely custom component. A concrete example would probably help here. G
