- January 2014 (1)
- October 2013 (3)
- September 2013 (4)
- August 2013 (6)
- July 2013 (1)
- June 2013 (4)
- May 2013 (6)
- April 2013 (2)
- March 2013 (3)
- February 2013 (1)
- January 2013 (3)
- December 2012 (2)
- November 2012 (1)
- October 2012 (3)
- September 2012 (2)
- August 2012 (3)
- July 2012 (1)
- June 2012 (1)
- May 2012 (3)
- March 2012 (2)
- February 2012 (1)
- January 2012 (1)
Yet another good checkpoint for the Apache Flex project. As I’ve mentioned earlier, getting Adobe Flex fully contributed to Apache involved quite a bit of legal footwork; much more I imagine than anyone imagined, other than legal itself perhaps. From an outsider’s standpoint is easy to wonder what could be so difficult? Just zip up the code and send it over. Unfortunately, it’s not so easy.
Wow! What a huge milestone for the Apache Flex community. The legal trials and tribulations are over. The code transfers are complete. The votes are in, and the Apache Flex community has truly come together to produce the first official release of Apache Flex, Apache Flex 4.8.0-incubating.
You can find the official announcement here. The announcement includes all the details you need to get started with the release.
I don’t think anyone anticipated how much work would be involved getting us to this point, but we’re finally here. Kudos to everyone involved in the process.
As those of you following this know, the Apache Flex podling is still in the incubating stage. However, having an official release is a huge milestone on the road to a top level Apache project. A lot has been learned along the way. Fortunately, future releases won’t have the same legal overhead to go through so should go much smoother.
Now don’t expect anything new and fancy out of this release. The major goal of this was to produce a parity release with Adobe Flex 4.6. Many folks have bug fixes and features that they’re dying to put into Apache Flex, but held off for now, to ensure that no new problems were introduced into the code during this initial release.
I urge you all to try it out, and get involved with the community. If something’s not to your liking, well then just go fix it!
Now the fun begins…
I just registered as a speaker for 360|Flex 2012 in Denver, CO – April 15 – 18, 2012. You can find more details at the conference website: http://360flex.com. Should be a great conference. Tickets are cheaper on a first come, first serve basis, so buy your tickets asap at http://360flex.eventbrite.com to get the best possible price. See you there.
I’ve been using Apache software in one form or another for about 15 years. But it’s only recently, with the advent of Apache Flex that I’ve started to actually understand what Apache is all about. I’m not referring to the Apache web server here, which in some circles is synonymous with ‘Apache’. I’m talking about the Apache Software Foundation (ASF), its history and how it works, as well as the Apache-specific projects, and how those projects are developed and maintained.
This is just a quick note to point out that Adobe has recently published two very important white papers.
The first is a white paper detailing Adobe’s view of Flex and its commitment to Flex in the future. This is a must read if you are at all involved directly or indirectly with Flex.
Following quickly on the Flex white paper is the Adobe Roadmap for the Flash Runtimes. This document provides an overview of the Flash runtimes and a roadmap for their development. Obviously, this has implications for both Flash and Flex.
It has occurred to me recently that there is actually a lot of confusion when talking about maps and adding mapping functionality to a Flex application, be it a web application or a mobile application. When talking about mapping, it’s important to first differentiate between straight ‘mapping’ and ‘GIS’. As well, you also need to differentiate between mapping frameworks & apis and map data sources. Things can get very confusing otherwise. I’ll go through the various options I know about below and try to explain and differentiate where possible.