What are the downsides to using Spark over Halo in Flex?

Is there more work, or source code files required to customize your look and feel (skins)? How maintainable and readabl开发者_JAVA技巧e is Spark relative to Halo? Is it more productive and easier to customize overall than Halo, about the same, less?

If you're an SDK user who was 99% happy with Halo's appearance (maybe just a few CSS tweaks), is switching to Spark creating more work for you? Do we now need to employ designers to get a reasonably complete look and feel?

Having done quite a bit of skinning with both halo and spark, I can say I find spark to be much more flexible (no pun intended). With halo, I used to spend a lot of time writing ActionScript to draw programmatic skins. Flex 4 introduced the new states model and FXG, which allows you to create your skins with MXML. Less code, more readable, much more maintainable in my experience. The separation of form and function is also much more clean with spark. It took my a good amount of time to really get my head around the spark way of doing things, but in the end it was worth the effort. On the downside, I'm finding the spark control set to be incomplete (no Tree, DataGrid, DividedBox, DatePicker, ColorPicker, icon Button, to name a few), and the new spark controls have their quirks (why doesn't the DropDownList size itself to its content like its halo counterpart?!), but overall I'm happy.

IMHO you have more possibilities with Spark skins. Therefore it requires in some cases more work but because of that the skins are maintainable, depending on the developer as well of course. I haven't modified Halo skins, so I started working with skins with Spark. I'm not the skin expert and there are just a few skins I worked on. The difficulty was ok. Creating new skins seems to be hard but to extend an existing skin is quite easy.

If you're (99%) happy and you don't see the advantage of switching to Spark, then you should'nt do it.

Some things changed while using Spark components e.g. the possibility to use an icon in a Button control dosn't exist in a Spark Button. Of course you can write your own skin and have more possibilities to do that, but this takes time. Except the Button, I don't regret that we switched to Spark.