问题描述
是否需要更多工作或源代码文件来自定义您的外观(皮肤)?Spark 相对于 Halo 的可维护性和可读性如何?与 Halo 相比，整体定制是否更高效、更容易，大致相同，但更少?
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?
如果您是一位对 Halo 的外观 99% 满意的 SDK 用户(也许只是一些 CSS 调整)，那么切换到 Spark 是否会为您创造更多的工作?我们现在是否需要聘请设计师来获得相当完整的外观和感觉?
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?
推荐答案
恕我直言，Spark 皮肤有更多的可能性.因此，在某些情况下它需要更多的工作，但由于皮肤是可维护的，当然也取决于开发人员.我没有修改过 Halo 皮肤，所以我开始使用 Spark 处理皮肤.我不是皮肤专家，我只研究了一些皮肤.难度还可以.创建新皮肤似乎很难，但扩展现有皮肤却很容易.
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.
如果您 (99%) 很高兴，并且没有看到改用 Spark 的优势，那么您不应该这样做.
If you're (99%) happy and you don't see the advantage of switching to Spark, then you should'nt do it.
一些事情在使用 Spark 组件时发生了变化，例如在 Spark Button 中不存在在 Button 控件中使用图标的可能性.当然，您可以编写自己的皮肤并有更多的可能性来做到这一点，但这需要时间.除了 Button，我不后悔我们改用 Spark.
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 而不是 Halo 的缺点是什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！