flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Reicher <danreic...@gmail.com>
Subject Re: s:Spacer (was Re: Missing Spark components)
Date Thu, 01 Mar 2012 21:04:15 GMT
> 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.

The "RSL tax" for me is the most obvious reason. Admittedly, using
mx:Spacer alone doesn't invoke it, but things like DateChooser,
ProgressBar, ColorPicker, etc. do. Secondarily, again ignoring Spacer, but
the hybrid mx/s approach adds weight of having to double embed fonts in a
lot of cases (cff / non-cff) because mx controls don't use FTE. With the
digested RSLs going away, simply adding an mx control incurs an additional
1/2 meg download for every user. If you're having to double embed fonts
that can get sizable very quickly as well. I see the value in keeping the
SDK extremely tight; however, there is something to be said for keeping the
resulting output tight as well.

I don't think mx needs to go away, but it would be nice for developers to
be able to hit the "Spark Only" radio button in Flash Builder and not have
to worry about paying the download tax. Once you open the door to the
hybrid approach, it puts the burden on the developer to navigate and know
the implications of everything they do. That's fine, but shouldn't an SDK
do what it can to mitigate those things from happening and make the hybrid
approach the exception and not the rule.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message