将Flex3 App迁移到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的最大优点之一就是设计.假设与性能相比，设计/UI目前不是业务的主要推动力，那么我们还能强调哪些其他因素?

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?

我们已经在App上实现了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 App迁移到Flex4的优势的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！