Hi, I've been wrestling with Container all day. I was working on the Flex layouts, but then went down the rabbit hole of Containers while trying to get the layouts to look right.
The issue really isn't the HTML/JS side. That's pretty easy really (in concept). A FlexJS Container's element is a <div> that gets its display style set to flex and then a couple of other properties. The problem comes from the SWF-side which creates several structures: The Container itself, its inner content area, and a viewport. All of this is to support padding, chrome pieces, and scrolling. The Container's content area appears on the HTML side, too, because of the potential chrome elements. Most times you want to use a Container you aren't going to need chrome elements, so I'd like to do away with that for Container. Maybe make a ChromeContainer later to support Panel or make Panel be a special-case Container that has chrome. QUESTION: In your Flex apps, do you need to place chrome elements besides using a Panel? Scrolling, to me, is a different issue, even though scrollbars could be considered chrome elements. What I'd like to do here is create a ScrollableContainer that will add in scrollbars on the SWF side and just set the overlay style appropriately on the HTML/JS side (again, the JS side is simple). I'm getting hung up with the nesting of the containing elements and I think most of the time it isn't necessary, especially on the JS side. Grouping elements together is a fundamental thing in UI frameworks and I'm just not feeling that this is being handling correctly. Thanks, Peter
