On Thu, Mar 1, 2012 at 1:18 PM, Alex Harui <aha...@adobe.com> wrote: > > > > On 3/1/12 12:37 PM, "Om" <bigosma...@gmail.com> wrote: > > > It might not be a very common use case, but it is a valid use case > > nevertheless. > I would prefer that we don't try to serve the uncommon use case. Why make > everyone pay for a full UIComponent just for space? You are welcome to > create a sample "SpacerWithToolTip" component. >
How about we create a s:SpacerLightWeight (switched order of words to help during autocomplete) that extends off of s:Rect. And make s:Spacer work just like mx:Spacer. This way we achieve both goals :-) > > > mx:Spacer supports everything that UIComponent supports. > Shooting for 100% parity with MX is not a good idea, IMHO. > See, I have a problem with this. Why would we not want to do that? The ideal scenario is keep the interface same/similar but support everything. Internally, we can do things efficiently. That said, we can build new components with an eye for performance. I am completely for this! > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > >
