Have you modified the framework source for your own purposes on a production Flex application? If so I’d like to hear from you as we’re currently trying to understand where folks are making changes and the kind of impact they could have on applications with relation to our new cached framework strategy.
Please let me know the following:
1) What files (or at least what areas) have you patched
2) Is SWF size an important consideration for your app
3) Was patching really the only solution available to you
4) Are you comfortable creating RSLs
You can comment here or mail me: mchotin AT adobe DOT com.
For most of our customers the general expectation is that all SWFs in your Flex application (including modules, runtime CSS and sub-applications) are all compiled against the same version of Flex. When you upgrade your 2.0.1 application to 3.0, all SWFs used in the application should be upgraded at the same time.
Technically it is possible, in certain circumstances, to allow a 3.0 application to load modules, runtime CSS and sub-applications that were compiled in 2.0.1. We are interested in getting feedback from developers for whom recompilation of existing 2.0.1 SWFs is impossible or impractical and must try to use these 2.0.1 SWFs in their 3.0 applications. There will likely be many rules and restrictions on how both the 2.0.1 SWFs and 3.0 SWFs should be designed and written.
If you fall into this latter category please contact me ASAP (mchotin AT adobe DOT com) so we can gather your requirements. We are making some last-minute decisions as to how this can work.