There have been some questions over the last few days on the status of the Flex data visualization components and I wanted to make sure everyone knows our intentions.
First of all, you may notice that the 3.4 downloads page has an updated copy of the data visualization components (charts and the Advanced DataGrid and OLAPDataGrid). While we have made it easier to view the source (you don’t have to run the DMV-source.jar anymore), we still consider these components to be under the Flex Builder license, and the source to be considered “Professional Component Source Files” as described in the Flex 3 SDK EULA. So I hope that clears up the licensing question.
The other concern I’ve heard raised is that Flex 4 is not seeing many changes to the data visualization components, and therefore folks are worried that Adobe is not investing in them. Data visualization remains a “core competency” of Flex, and we absolutely plan on further development of these components along with supporting partners who have expanded upon them like the ILOG team at IBM. In the Flex 4 time frame we plan on making some improvements to the GroupingCollection, a fundamental piece of the ADG in the hopes of addressing one of the larger performance bottlenecks. However, we chose to take on 2 significant agendas that preempted doing significant work in the data visualization components.
The first is the data connectivity features in Flash Builder; the way we’re making it even easier to connect your data from the back end into the data visualization components in the front. We hope that this will make the data visualization components even more accessible for developers, making it simple to get up and running and build powerful data-driven applications.
The other agenda is the introduction of the Spark architecture. As everyone knows, this is a significant improvement to the fundamental component architecture in Flex, but it is too much to bring every component forward into the new model in a single release. While the charting components do not need to be modified significantly to fit well with Spark, the DataGrid (and therefore the AdvancedDataGrid) will take significant effort, and that is work we intend to do in the following release. Knowing that a fundamental re-architecture of the DataGrid is coming, we decided not to make significant investment in the current one for this release other than addressing the most important bugs.
So that’s the status and we hope you’ll understand and agree with our prioritization. If you’ve got any questions, feel free to comment here or post to the forums!