The Apache Flex PPMC would like to inform our community that Adobe Systems Inc. has assigned the Flex trademark to the Apache Software Foundation. This is an important milestone in our progress towards graduating and becoming a full-fledged Apache project.
Adobe will retain a limited license to use Flex for its current Flex products and web-sites so you will still see “Adobe Flex” out there, but Apache is now the official owner of the trademark.
-The Apache Flex PPMC
In case you were wondering, the Flex trademark has been assigned to Apache as mentioned here: http://markmail.org/message/vkwfmjkdjzpxrkke. As the email mentions, this is another step on the road to transitioning Flex to Apache as promised here http://www.adobe.com/devnet/flex/whitepapers/roadmap.html
The Apache Flex community is pleased to announce the release of Apache Flex 4.8.0-incubating!
Apache Flex is an application framework for easily building Flash Platform-based applications for mobile devices, the browser and desktop. This is the first release under the Incubator of the Apache Software Foundation and represents the initial donation of Adobe Flex 4.6 by Adobe System Inc.
Note that because Apache Flex is under “incubation”, Apache Flex is not an official Apache Project, and this is not an official Apache release. For more information see the DISCLAIMER file in the release. This release marks the start of a new era for Flex. The future of Flex is now driven by the community instead of a corporation. Users can have important bugs fixed or new features added by contributing the code themselves. Apache Flex is available in source form from the following download page: http://incubator.apache.org/flex/download.html When downloading from a mirror site, please remember to verify the downloads using signatures found on the Apache site: http://www.apache.org/dist/incubator/flex/KEYS Apache Flex release packages are different from Adobe release packages. For information on how to use Apache Flex with existing IDEs, see: http://incubator.apache.org/flex/packager.html For more information on Apache Flex, visit the project home page: http://incubator.apache.org/flex/ Thank you for using Apache Flex, The Apache Flex Community.
Apache Flex 4.8.0 ================= This is a parity release with Adobe Flex 4.6.0. The official Apache distribution is the source kit which can contain only source. Because of this, and various licensing constraints, there must be a few differences. ====> Please see the README, especially the "Install Prerequisites" section. <==== Differences: - BlazeDS integration is an optional feature (Adobe license) - Adobe embedded font support is an optional feature - the lib directory has been restructured -- lib (jars built from source) -- external (other Apache jars or ones with compatible licenses) -- optional (optional jars with incompatible licenses) - the default linkage is -static-link-runtime-shared-libraries=true - there are no longer Adobe signed RSLs (swz files) in frameworks/rsls - the frameworks/rsls directory contains unsigned RSL for libraries we build - the frameworks/osmf src is not included which means there is not an osmf RSL. - the frameworks/textLayout src is not included which means there is not a textLayout RSL. We expect this difference to be limited to this release. - the ASDoc in the asdoc package no longer has active links for Adobe Flash, Adobe Air, the Open Source Media Framework (OSMF) or Text Layout Format (TLF). We hope to correct this in a future release. Please report new issues to our bugbase at: https://issues.apache.org/jira/browse/FLEX The Apache Flex Project <http://incubator.apache.org/flex/>
Short answer: no. But I’m investing in HTML5.
Apache Flex is an application framework for easily building Flash-based applications for mobile devices, the browser and desktop. Summary: A large community is losing momentum as it waits for Adobe to complete the source code transition and infrastructure.
Here are the latest flex news from Apache Flex:
The Apache Flex Project has received the entire Flex Framework. This includes all components that were completed in Adobe’s 4.6.0 release and a few others. Essentially if you take the existing compiler to the frameworks code, you would get what amounts to the current Adobe release.
The automation framework that was a part of the Adobe Flex 4.6.0 framework is close to being donated, but has not been signed off yet. We expect this in the coming weeks.
The Apache Flex Project has received the “mxmlc Flex Compiler”. This means we can now make changes to the existing compiler that shipped with Adobe’s 4.6.0. This will allow us to make bug-fixes and small optimizations while we wait for the new “Falcon” compiler.
The testing framework that Adobe used known as Mustela has been donated. This will allow us to make changes to the compiler and framework while still maintaining compatibility with the previous versions. There are a series of tests that still need to be written, but at least the framework is there.
The Apache Flex team has created a set of build scripts so that anybody can easily build their own copy of the framework. Apache ANT scripts will be officially supported, but other developers have offered to make build scripts for Maven.
Pre-compiled builds have been created and posted. They are not the ‘official’ 4.8.0 version yet, but they are getting close. You can download them and put them in your Flash Builder or IntelliJ SDKs directory and see how they look with your existing projects today. This is a parity release to the current Adobe 4.6.0 release.
Apache committers have begun donating various components to the framework, including an FXGImage component, some collections classes, some major work around validation, busy indicators for non-mobile components, and some navigators. These components have not been integrated into the trunk (the main project), but you should expect to see some of them in the future.
Lots of work is happening around localization and internationalization. A bunch of new locales have been submitted with more on the way.
A team has formed to build what amounts to an automated installer for Apache Flex SDK. This is an AIR application that will allow a user to do a single-click install of the SDK, and integrate it into Flash Builder 4.6.0 (and possibly other IDEs).
Check-in tests and the button tests for Mustella are up and working. Jenkins Continuous Integration is up and running as well.
One of the first decisions that you must make when creating custom components is deciding whether to write
them in MXML or in ActionScript. Ultimately, it is the requirements of your application that determine how you
develop your custom component.
Some basic guidelines include the following:
•MXML components and ActionScript components both define new ActionScript classes.
•Almost anything that you can do in a custom ActionScript custom component, you can also do in a custom MXML component. However, for simple components, such as components that modify the behavior of an existing component or add a basic feature to an existing component, it is simpler and faster to create them in MXML.
•When your new component is a composite component that contains other components, and you can express the positions and sizes of those other components using one of the Flex layout containers, you should use MXML to define your component.
•To modify the behavior of the component, such as the way a container lays out its children, use ActionScript.
•To create a visual component by creating a subclass from UIComponent, use ActionScript.
•To create a nonvisual component, such as a formatter, validator, or effect, use ActionScript.
•To add logging support to your control, use ActionScript. For more information, see “Logging” on page 227 in Building and Deploying Adobe Flex 3 Applications.
Flex3 官方文档中如上释疑. 2010年我参加Flex Developer Day时, 有开发者提问国内是否有大型企业应用实例? 未得到正面回答. 倒是群硕的团队还上台张扬了一把, 他们的项目大约是奥运时CCTV直播网站.
07年底开始做的教育应用, 大致有120W行代码, 其中有60%+的为AS代码, 除了入口文件及部分复杂UI使用MXML之外, 清一色都是AS代码, 所有的UI都小心谨慎的创建, 销毁. 在10年的DevDay时, 坐在我旁边的某研发他们也是纯AS.
几年过去了, Flex贡献给了Apache, Flex也已经4.6了, 接触的代码多了, 习惯了清纯的AS代码, 当满篇都是MXML标签时, 我不淡定了.
思想斗争良久, 到底孰优孰劣? 在多数common的情况下, 几乎不分上下. 我觉得AS代码更优雅更易读, 可人家说了: 我们可以Design, 不用代码, 一眼就看出来了…:(
如上View, 假如我们只用MXML或只用AS来实现, 似乎看不出明显差异来, 其实相比选择编程方式, 可能对组件/Class的划分可能更加重要.
这样划分, 不论MXML还是AS都可以很好的降低耦合, 更可重用, 但不论如何, 我还是喜欢干净的AS代码.
// Proudly powered by Apache, PHP, MySQL, WordPress, Bootstrap, etc,.