将 Flex3 应用程序迁移到 Flex4 的优势 [英] Advantages of Migrating Flex3 App to Flex4

问题描述

将 Flex 3 应用(Java 后端、BlazeDS、Spring、Hibernate)迁移到 Flex 4 有哪些优势?

What are the advantages of migrating a Flex 3 app (Java backend, BlazeDS, Spring, Hibernate) to Flex 4?

Flex 4 的最大优势之一是设计.假设与性能相比，设计/用户界面目前不是业务的主要驱动力，那么我们还可以强调哪些其他因素?

One of the biggest advantages of Flex 4 is design. Assuming that design / UI isn't a big driver for the business right now as compared to performance, what are the other factors we can highlight?

我们已在应用中实施了 Cairngorm 和 Swiz(计划在未来逐步推出"Cairngorm).

We have implemented Cairngorm and Swiz on the App (with a gradual "roll out" of Cairngorm planned for the future).

有什么意见吗?

谢谢，斯里

推荐答案

Swiz 和恼人的汽车喇叭?我绝对喜欢 Swiz，但我认为逐步推出 Cairngorm"是指长期、缓慢且不有趣的 Cairngorm 推出".:-)

Swiz AND the annoying car-horn? I absolutely love Swiz, but I assume that by 'gradual roll-out of cairngorm' you meant, 'long, slow and not fun roll-out of cairngorm.' :-)

Flex3 非常可靠——如果你已经有了一个代码库，那么几乎没有理由改用 flex4:pez 说的是轻量级组件"，但真正的负载差异如果不是不存在的话，可能可以忽略不计大多数应用程序的需求.(无论哪种方式，我认为他的意思是架构良好的类似 openFlux 的组件.)

Flex3 is very solid -- if you already have a code-base, there are few reasons to change over to flex4: pez said 'lightweight components', but the true load difference is probably negligible if not non-existant for the needs of most applications. (Either way, I assume he meant well-architected openFlux-like components.)

你在开发什么类型的应用?具有大量表单字段的应用不是大跌的理由(除非您当前的代码库相对较小).

What kind of app are you building? An app with a bunch of form fields isn't a reason to make the plunge (unless your current code-base is relatively small).

Vector 类非常棒，但您可以使用 flex3 完成所需的一切.

The Vector class is great and all, but you can do everything you need with flex3.

这篇关于将 Flex3 应用程序迁移到 Flex4 的优势的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！