A little over a year ago the Flash Builder 4.5 plug-in for SAP NetWeaver Gateway was published as a beta on Adobe Labs (at http://labs.adobe.com/technologies/flashbuilder_sap). As a research beta, the plug-in only works with older versions of Flash Builder (4.5 and 4.6). The plug-in was never shipped as an official product, and isn’t going to be developed further – we’ve discussed open-sourcing the project with the code owners but this is unfortunately not going to be possible.
If you still rely on this research project, please grab the bits now – as part of routine cleanup it will be disappearing off of Labs in April 2013.
We’re also planning to visit some European Flex User Groups. We hope that you’ll be able to join one of these meetings. We’ll be in Europe for two weeks only but we believe that this tour will be an unique opportunity to discuss the future of Flex, the role of Apache, the Flash roadmap and answer your questions.
I am pleased to announce that Flex as been accepted into the Apache Incubator. With weekends and holidays, I suspect that it will still be several days before we get up and running with mailing lists, bug base, source control, etc, so we continue to appreciate your patience. However, I’m really looking forward to 2012 and beyond, and I hope you are too.
We received a whopping 65 requests to be on the initial committers list for the proposal to become a Podling in the Apache Incubator! It is great to see such enthusiasm from the community.
We are discussing with Apache experts as to how many folks we can put on the list. I think it will be at least 24. Initial committers also form the Podling’s Project Management Committee and can vote in other committers who establish a track record by submitting patches that get accepted. I am not looking forward to having to deny so many of these requests. Once we pick a number, I will send each of you an email of whether your request was accepted or denied.
If you requested to be a committer and are not chosen to be on the initial list, please continue to show your support by contributing patches via the JIRA bug base that will be set up. That way you can be promoted to committer as soon as possible.
Thank you to all who requested to be a committer. I look forward to working with you on Flex.
One of the requirements for a proposal to incubate a new project in the Apache Software Foundation is to have an initial set of committers. A committer has to sign a license agreement with Apache in order to obtain write access to the source code repository. A committer’s responsibilities are listed at http://www.apache.org/dev/committers.html#committer-responsibilities.
As we announced at the Flex Community Summit earlier this week, we are looking to identify the initial committers for the Flex SDK incubation proposal. If you want to be on this list of initial committers, please email me at firstname.lastname@example.org by noon PST Friday, December 16, 2011. We may limit the initial set to around 12, but you can still become a committer after that by following the process outlined by Apache. And remember, if you don’t want to be a committer, you can still contribute in many ways.
We are excited to be engaging the community in the shaping of Flex, and look forward to your future contributions.
Flex SDK Team
Adobe Systems, Inc.
The Flex team is thrilled that 360Flex Denver is right around the corner! This is going to be a fantastic event with a stellar lineup of speakers and sessions, including engineering and product management representatives from the Adobe Flex, Flash Builder and Flash Catalyst teams. We will demonstrate the Flash Builder and Flex SDK 4.5 features and workflows for building mobile applications for deployment on Android, iOS and RIM devices, as well highlight the dozens of new coding productivity enhancements in Flash Builder that will significantly speed up ActionScript and MXML coding. Additionally, we will be showcasing the enhanced design workflows in Flash Catalyst ‘Panini’ including roundtripping with Flash Builder.
It doesn’t stop there….we have some new announcements to share about mobile platform support as well as publicly discussing the new (and improved) open source contribution model for the Flex SDK. Additionally, we will have sneaks of upcoming features slated for the next versions of the Flex product family.
Check out the 360Flex Denver schedule to make sure you know when Adobe members are speaking. Below are some must-see sessions that I’d highly recommend attending before they fill up:
- What’s New in Flash Builder 4.5, Andrew Shorten
- What’s New in Flex SDK 4.5, Deepa Subramaniam & Steven Shongrunden
- Multi-Density & Multi-Platform Development with Flex SDK 4.5, Narciso (NJ) Jaramillo
- Flash Builder Tips & Tricks, Sreenivas Ramaswamy
- Flex Performance Tips & Tricks, Evtim Georgiev
- Whats New in Flash Catalyst ‘Panini’, Jacob Surber & Peter Flynn
So, if you haven’t registered yet – get on it! You can get a special 20% discount by entering ‘AdobeRocks’ when you register. And, don’t forget, registration includes 4 hands-on sessions on Sunday which will deep dive into Flex 4 development, mobile development for Android and Blackberry Tablet OS as well as an introduction to Away3D.
See you in Denver!
Last year we announced that a number of positions on the Flex Product Management team were open – whilst we still have one position available, I wanted to confirm that the core team is now in place and that we’re actively planning for future releases of Flex SDK, Flash Builder and Flash Catalyst.
New additions to the team are Adam Lehman, who joins as Flash Builder Product Manager and Jacob Surber, who has taken on responsibility for Flash Catalyst.
Many folks will know Adam as the Product Manager for ColdFusion – readers of Adam’s blog will be aware that he announced last week that he is moving to a new role at Adobe, and I’m happy to confirm that he brings his experience and passion to Flash Builder. In addition to blogging, you can also follow Adam on Twitter where he’s @adrocknaphobia.
Jacob has moved across from the XD team at Adobe, where he has spent the last couple of years using Flash Catalyst and Flash Builder to prototype and implement user interface elements in a number of Adobe’s products, including the recently launched Acrobat X. Jacob truly understands and represents both the designer and developer viewpoint, which will be a big asset as we continue to refine the workflow between Catalyst and Builder. Follow him on Twitter where he’s @jacobsurber.
Regular readers need not fear about Deepa and myself – we’re still here, with Deepa leading Product Management for Flex SDK, whilst I take on a Group Product Manager role overseeing both Flash Catalyst and Flash Builder.
The entire team is heading out to user group meetings and upcoming events over the next couple of months (including FITC in Amsterdam and 360 Flex in Denver), as well as meeting with specific customers so as to get feedback on our plans for Flex for 2012 and beyond. If we don’t manage to meet with you in person then we’re always interested in your feedback and thoughts – you can get in touch with the team by sending us a comment on this blog or by joining our pre-release program.
Some of you may have noticed that Adobe Open Source has been down for some time. The service is currently unavailable as we investigate a critical issue with our server infrastructure. We currently do not have an ETA on restoring service, but I will share more information as it becomes available. I sincerely apologize for this inconvenience.
Thank you for your patience,
Senior Product Manager, Flex SDK
UPDATE: Service to opensource.adobe.com was reinstated Friday, 10/22 at 5 PM PST.
We are very excited to share with the ActionScript community an ActionScript Code Coverage Plugin for Flash Builder 4. This plugin provides an Eclipse perspective that allows you to start/stop the code coverage tool, view generated code-coverage reports, examine source code and save/load reports. Typically developers will use the code coverage tool to see which areas of code have not been exercised during execution so that additional testing requirements can be identified.
The tool provides detailed line coverage and method coverage reporting, as well as highlighting classes that are not linked into the application. You can use the ActionScript Code Coverage Plug-in for Flash Builder with applications developed in ActionScript 3, optionally using either Flex SDK 3.x or Flex SDK 4.x, targeting both Adobe Flash Player and Adobe AIR®. A trial or licensed version of Adobe Flash Builder 4 Premium is required to use the ActionScript Code Coverage Plug-in.
You can access the plugin on Adobe Labs here, read documentation around using and configuring the code-coverage tool, and provide feedback via the code-coverage forum.
The Flash Platform tooling team would like the community’s help in shaping the product roadmaps for the Flex SDK, Flash Builder, Flash Catalyst, and Flash Professional.
We would like you to complete a 15-20 minute online survey. In the survey, you’ll get an opportunity to help us understand how you are using Adobe tools currently, and we’ll also ask you where we should take the products by helping us prioritize potential areas of investment.
The product management team takes these surveys very seriously and the results figure heavily into the decisions that we make about feature prioritization.
Please, take the opportunity to give feedback.
Thanks so much for your time!
Flash Platform Tools Product Management team