Sorry, my wording was unclear. I was NOT talking about getting rid of the mx namespace from the Flex SDK. I dont want to start a war here :-)
My point is that if we are going to create a s:Spacer class, it should support the same functionalities that mx:Spacer currently supports. We can add functionality, but not remove. This will help developers smoothly migrate their existing apps to the spark architecture and reduce the confusion while doing so. Om On Thu, Mar 1, 2012 at 12:44 PM, Jonathan Campos <jonbcam...@gmail.com>wrote: > On Thu, Mar 1, 2012 at 2:37 PM, Om <bigosma...@gmail.com> wrote: > > > I see the performance argument, but we want to also make sure that > existing > > apps can easily get rid of mx namespace as easy as possible. > > > > Why do we need to get rid of the mx namespace? If it ain't broke don't fix > it. While I can understand personal preference to see s: instead of mx: I > don't really think that this is a huge necessity. > > -- > Jonathan Campos >
