Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What are the advantages of migrating a Flex 3 app (Java backend, BlazeDS, Spring, Hibernate) to 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?
We have implemented Cairngorm and Swiz on the App (with a gradual “roll out” of Cairngorm planned for the future).
Any opinions?
Thanks,
Sri
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 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).
The Vector class is great and all, but you can do everything you need with flex3.