Migrating fx3tofx4
by Jonathan Campos on May 21, 2010
- 2,623 views
TechWed presentation to help Flex Developers move between Flex 3 to Flex 4.
TechWed presentation to help Flex Developers move between Flex 3 to Flex 4.
Accessibility
Categories
Tags
Upload Details
Uploaded via SlideShare as Apple Keynote
Usage Rights
© All Rights Reserved
Statistics
- Favorites
- 2
- Downloads
- 80
- Comments
- 0
- Embed Views
- Views on SlideShare
- 2,145
- Total Views
- 2,623
While there are MANY details that we could focus on, I’ve picked specific points that I feel most Flex developers would hit right from the get-go.
As you can see from my subtitle, the main point I’m going to keep reiterating is how easy it is to make the change from Flex 3 to Flex 4. You’re not going to lose lots of development time making the switch, instead you’ll just add the your own list of capabilities.
Lots of care was taken on the part of the Flex Development team to make sure that the movement from Flex 3 to Flex 4 would be as seamless as possible.
As you can see from the graphic Flex 4 contains everything that ever was or is Flex 3 and adds to it. What does this mean? You can start making “Flex 4” apps while still just using everything you’ve known and built with Flex 3. And there are some Flex 4 benefits you will still be receiving by making this shift, but ultimately it isn’t a “true” Flex 4 app, so let’s continue by looking at how exactly Flex 4 extends Flex 3.
2. Enhancements
3. New Concepts
4. Common Migration Pitfalls
5. Bonus, Flex 4 Component Lifecycle
2. Enhancements
3. New Concepts
4. Common Migration Pitfalls
5. Bonus, Flex 4 Component Lifecycle
2. Enhancements
3. New Concepts
4. Common Migration Pitfalls
5. Bonus, Flex 4 Component Lifecycle
findSkinPart: used in attach skin, don’t use directly
clearSkinParts: used in detachSkin
detachSkin: destroys and removes a skin part
partAdded: called when a skin part is being attached. Don’t call this directly. Do override it.
partRemoved: called when a skin part is being removed. Don’t call this directly. Do override it.
- everywhere?
2. Is Flex 4 compiler faster for apps written in Flex 3
- yes, as discussed earlier. Many compiler improvements are provided for you when using the Flex 4 SDK. You don’t need to do anything to receive these benefits
3. Why is Flash Builder not available on Linux? It's the most voted-for feature request in the Adobe JIRA.
The issue is with the design view working with Linux.
4. What are some use cases for Flex that might be good for instructional design projects, project management teams, community building, etc.?
At Dedo:
Scrum management software
project management software
Hudson reporting
5. If you could summarize in 3 steps the process of becoming as cool as Jonathan Campos, what would they be?
Um... what?
6. What happened to the Import Web Service code generator in Flex 4? The new code it generates is not as strongly typed as the code from Flex 3. It went from ArrayOfDataType to just a plain Array..
File a feature request.
7. Do I have to learn Eclipse to some degree before I tackle Flex?
Yes and no. Understanding the basic layout can take about 5 minutes and that would be all you need. To get into adding plug-ins etc, that would require more understanding of the eclipse IDE, though not extremely difficult.
8. Where is the best place to go for training on Flex 4?
New to Flex? Flex in a Week http://www.adobe.com/devnet/flex/videotraining/
Not new to Flex? Pick a topic and go to the web.
9. What are the issues with mixed IDE environments? e.g. some developers on Flex Builder 3 and others on Flash Builder. Just want to verify
There is a compiler change, so you would want you compiling standardized. Also Flex 4 specifically targets FP10. Yes you can set this up in Fx3, but if you haven’t you may get errors without expecting it. Also, Fx3 and Flash Builder can’t live in the same install of Eclipse, I’ve had issues with that.
10. Status of completing the migration of the remaining MX components to Spark. This really needs to be a priority. Also, an update on the issues in JIRA related to enabling additional compiler hooks to allow for compiler extensions to support custom metadata would be extremely useful.
I “believe” they are shooting for full polarity in 2011, don’t quote me on that, I don’t think it’s official. I think it is meant for the Flex 4.5 release is what was said in the past.
Update on JIRA, additional compiler hooks, conditional compiling, etc. They know of these issues, and no official plan has been laid out but it has been remarked as very important.