在Flex中使用Spark over Halo有什么缺点？ [英] What are the downsides to using Spark over Halo in Flex?

问题描述

是否有更多的工作或源代码文件需要定制你的外观（皮肤）？如何维护和可读性相对于光晕的火花？如果你是一个SDK用户，对Halo的外观感到满意（可能是99％）只是一些CSS的调整），是切换到Spark为您创造更多的工作？我们现在需要聘请设计师来获得一个合理的完整的外观和感觉吗？
解决方案

恕我直言，你有更多的可能性与Spark皮肤。因此，在某些情况下需要更多的工作，但是因为皮肤是可维护的，当然也取决于开发者。我没有修改光晕皮肤，所以我开始与Spark的皮肤工作。
我不是皮肤专家，只有几个皮肤我工作。困难是好的。创建新的皮肤似乎很难，但扩展现有的皮肤是相当容易的。

如果你（99％）高兴，你没有看到切换到Spark，那么你不应该这样做。

使用Spark组件时有些事情发生了变化，例如在Spark按钮中不存在使用按钮控件中的图标的可能性。当然，你可以写自己的皮肤，并有更多的可能性，但这需要时间。
除了按钮，我不后悔我们切换到了Spark。

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.

这篇关于在Flex中使用Spark over Halo有什么缺点？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！