Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is there more work, or source code files required to customize your look and feel (skins)? How maintainable and readable 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?
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.