{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 啃猪蹄的小仙女 的问题《Migrating to Flex 4》','https://www.manongdao.com/q-886039.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
How much of an impact will migrating to Flex 4 have on our code base? We have about 40k LOC written in Flex 3. I'm hoping that there are no breaking changes in the Flex SDK, and that we can smoothly transition to the new features of Flex 4 while minimizing any disruption. From what I've read Adobe is developing a new set of GUI components called 'Spark' but I'm hoping our existing stuff can co-exist with the new components.
相关问题
- How to load flex swf from flash?
- Converting Date with Time in PST into UTC format
- Is older version of flex SDK really required?
- Setting Page Title from a SWF
- How to handle right to left languages in Flash (pr
相关文章
- Trace on Chrome/Browser console
- Is building separate .swc allow a faster loading o
- Assigning an array of objects to a DataGrid
- Libraries for text animation in Flex / Actionscrip
- Flex 4 - Create states and add elements at runtime
- changin the default width and height of the dropdo
- How can I copy an ArrayCollection of transfer obje
- Optionally use Flash 10.2 cursors, while still bei
Spark and MX components can co-exist within the same application (and even within the same MXML files). There are some changes to how CSS works because CSS namespaces are now supported, and you will encounter a small migration step there.
In terms of choosing Spark versus MX, Adobe recommends keeping your existing code that already uses MX components the same. There's no need to make everything Spark immediately. You can make incremental changes as the need arises. For new development, you should use Spark when possible. However, the Spark components in Flex 4 will not have 100% feature-parity with MX, so you will likely encounter some situations where you need to continue MX components for the time being.
You can move to Flex 4 without adopting any of the new stuff. You can keep the 2006 namespace so that you don't have to update your MXML files. Also you can optionally use the Spark components. The only major benefit of doing this is the faster compiler. It will also allow you to progressively move to the 2009 namespace and Spark.