任何 Flex 4 迁移经验? [英] Any Flex 4 migration experience?
问题描述
我目前的开发栈是 MySQL + iBatis + Spring + Spring BlazeDS Integration 1.01 + BlazeDS 3.2 和 Flex 3 with Mate 0.8.9 框架.现在 Flash Builder 4 beta 2 出来了.有一些很酷的功能，如数据中心开发 (DCD)、表单生成等......你知道 Spring Blazeds 集成如何与 BlazeDS 4 一起工作吗?马特呢?Flex 4 有什么问题吗?DCD 如何与 mate eventmaps 配合使用.我知道最好自己尝试一下，但我只想检查是否有人尝试过迁移 Flex 4.如果是这样，有什么问题?您是否注意到任何生产力加速?谢谢.
My current development stack is MySQL + iBatis + Spring + Spring BlazeDS Integration 1.01 + BlazeDS 3.2 and Flex 3 with Mate 0.8.9 framework. Now Flash Builder 4 beta 2 is out. There are cool features like Data Centric Development (DCD), form generation etc... Do you know how Spring Blazeds Integration works with BlazeDS 4? What about Mate? Is there any issues with Flex 4 ? How DCD suits with mate eventmaps. I know it is better to try it out myself but I just want to check if somebody ever tried to migrate Flex 4. If so what are the issues? Did you notice any productivity speed up? Thanks.
推荐答案
我无法告诉您有关迁移第三方组件的任何信息.我不使用你提到的那些.
I can't tell you anything about migrating your third-party components. I don't use the ones you've mentioned.
但是，我可以告诉您，您无法简单地将现有项目加载到 Flash Builder 4 中，将 SDK 更改为 4.0，并期望它重新编译.Flex 4 中发生了大量变化，通常不兼容.
I can tell you, however, that you won't be able to simply load your existing project up into Flash Builder 4, change the SDK to 4.0, and expect it to recompile. A huge number of things have changed in Flex 4, often incompatibly.
以下是我目前遇到的:
您现在拥有两个并行组件库，Spark 和 MX.MX 是旧的 Flex 3 组件库，有时称为 Halo，尽管从技术上讲这只是默认皮肤的名称.Spark 是新的 Flex 4 组件库，仅部分替代了 MX.
You now have two parallel component libraries, Spark and MX. MX is the old Flex 3 component library, sometimes called Halo, though that's technically just the name of the default skin. Spark is the new Flex 4 component library, which only partially replaces MX.
它们确实可以互操作.您可以在单个应用程序中同时使用两者，并且您可以执行诸如将 Spark 组件放入 ViewStack 等 MX 布局容器中的操作.在应用程序中也有自然的划分，其中一侧使用 Spark，另一侧使用 MX，无需担心出现问题，因为它们不在 GUI 级别进行互操作.例如，对话框就是这样.
They do interoperate. You're allowed to use both in a single app, and you can do things like put Spark components in MX layout containers like ViewStack. There are also natural divisions in an application where it's possible to have one side using Spark, the other MX, with no worry about trouble because they don't interoperate at a GUI level. Dialog boxes are like that, for instance.
他们做这一切的原因是为了支持您听说过的这种新皮肤:Flash催化剂、FXG等等.如果你使用 Halo 原版皮肤，除了它是未来这一事实之外，我认为 Spark 对你来说并不重要.
The reason they did all this is to support this new skinning stuff you've been hearing about: Flash Catalyst, FXG, and all that. If you use the stock Halo skin, I don't see that Spark matters to you, other than the fact that it's The Future.
(旁白:获得绿野仙踪回声效果的 Markdown 语法是什么?)
(Aside: What's the Markdown syntax to get the Wizard-of-Oz boomy echo effect?)
Joan Lafferty(Flex SDK 质量主管)有一篇很有价值的文章，Flex 之间的差异3 和 Flex 4.在 第 4 页 上，她有一张表格，列出了 Flex 3 MX 组件在 Flex 4 中还没有被 Spark 组件取代.其中大部分没有自己的外观，比如 Accordion，所以你不需要给它们换皮肤，或者像对话框一样的东西，比如 <代码>警报.(你应该通读那篇文章的其余部分.它涵盖了我不知道的东西，因为我还没有遇到所有的差异.)
Joan Lafferty (Flex SDK Quality Lead) has a valuable article, Differences between Flex 3 and Flex 4. On page 4, she has a table listing the Flex 3 MX components that have not been replaced by Spark components in Flex 4. Most of these have no appearance of their own, like Accordion, so you don't need to skin them, or are things like dialog boxes, like Alert. (You should read through the rest of that article. It covers things I don't, because I haven't run into all of the differences yet.)
说到皮肤，Flex 4 中只支持 Flex 3 中的两个 MX 皮肤.色彩更丰富的 MX 皮肤已经消失，尽管有一组新的基于 Spark 的彩色皮肤炫耀一些您可以使用 FXG 等进行的操作.如果您真的喜欢他们删除的其中一个，您无疑可以在 Spark 上重新创建它们，但它不是开箱即用的.
Speaking of skins, only two of the MX skins from Flex 3 are still supported in Flex 4. The more colorful MX skins are gone, though there is a new set of colorful Spark-based skins that show off some of the things you can do with FXG and such. If you really liked one of the ones they removed, you can doubtless recreate them atop Spark, but it's not available out of the box.
许多内容已经重命名，还有一些 SparkMX 组件的替代品具有不同的接口，因此具有不同的名称.例如，要完全迁移到 Spark，您必须将 VBoxes 更改为 VGroups.有很多类似的令人讨厌的小差异.
Many things have been renamed, and some Spark replacements for MX components have different interfaces and so have different names. For instance, to move entirely to Spark, you'll have to change your VBoxes to VGroups. There are lots of annoying little differences like that.
由于整个双 GUI 库的问题，Adobe 发现自己有一堆 MXML 标签，例如
