Should I write a new application in Flex4/Spark if performance is a bigger consideration than skinning?
I've worked extensively with MX and Spark frameworks and both work fine for me. I am about to start a very large project in Flex where speed and fi开发者_如何学Pythonle size are going to be critical factors. I am not going to use Adobe Catalyst.
Is there any reason I should use Spark for this application rather than MX?
Is there any reason I should use Spark for this application rather than MX?
Adobe has stated that Spark is the future. The MX line is receiving no new components; and many expect to the be deprecated at some future point.
Spark also provides a significantly more flexible skinning architecture.
Spark components are architected in a way that is supposed to be more light weight; sort of like a "Pay As You Go" architecture, so you aren't dragging lots of functionality along that you don't need. A good example of this is that scrollbars are separate from containers.
Spark also provides you with greater Flexibility for deployments. Only spark components are supported on Mobile devices, for example.
If speed and file size are critical factors, you may want to reconsider your use of Flex, though. There are a bunch of alternate ActionScript frameworks such as Reflex, that are written for simplicity and performance.
精彩评论