If you like me want to try Flash 10 features in Flex or AIR 1.5 in Flex Builder, I would recommend installing the Flex Builder 3.0.2 update using the update mechanism in Flex Builder (Help>Search for Flex Builder updates) and get the Flex SDK 3.2 installed that way. When I followed the instructions for the manual installation, I realized that dataVisualization.swc was not included in the download. So my projects with Charts were not compiling.
For targeting Flash 10, you still have to remove the default playerGlobal.swc and re-add the one that targets Flash 10 as explained in the instructions. But at least you do not have to manually add (actually borrow from Flex SDK 3.1 ) the dataVisualization.swc. Again, you only need this if you are using Charts or the Advanced Datagrid in your project.
Also make sure to also regenerate your HTML template folder after changing the require Flash Player version to 10.0.0 ( Project>Properties>Flex Compiler>Require Flash Player). That includes the correct version detection scripts for Flash 10.
I did not see the bugs that some people are reporting about missing code hinting for the some Flash APIs ( Graphics and Bitmap). These were bugs that according to Adobe were fixed for the Flex 3.0.2 release, and the fixes are working for me in FB 3.0.2. I guess, you just need to make sure that you have upgraded to Flex Builder 3.0.2, have replaced the playerGlobal.swc that targets Flash 10 and have regenerated your HTML template folder.
I will be speaking about Building Mashups with Adobe Flex and AIR at Flex Camp Boston this December 12th at Bentley University. A Flex camp is a great opportunity to advance your Adobe Flex and AIR skills and network with other fellow Flex developers. Last year, we had a blast and this year looks really promising as well. Speakers include members of the Adobe Flex Team as well as experts from several companies.
Allen Manning is a colleague at Brightcove and a talented Adobe Flex developer. He has a great insight about best development practices and is now writing about them in his blog
The Presidential election in the U.S. is today and millions of Americans are making this a historic moment. For the first time an African-American runs for president, a woman is nominated to run for Vice-President and earlier in the primaries a woman was head to head to the presidential nomination in the Democratic party. For many, this is a life time opportunity to write history.
This is also a presidential election where technology has played a role like never before. Four years ago there was no YouTube, no Facebook, no Twitter and there were not thousands of influential blogs. Opinion has been created and spread faster than ever, and people have held their own political debates in this cloud of Web 2.0 artifacts. The Internet has been fundamental in mobilizing volunteers and raising funds.
Something else that is also new in the scene are "Rich Experiences". Not only in the Internet as Rich Internet Applications but also other forms. I am taking specifically about a technology that caught my attention early in the primaries: The "Magic Wall", an electronic multi-touch board that CNN introduced early this year that displays an electoral map and that "magically" changes views as John King clicks, drags and drops, and zooms in and out sections of screen with a touch of his fingers. I immediately started thinking about the parallels between the "Magic Wall" and the RIA apps that we build with Adobe Flex and other technologies.
On the one hand, the input is the same for both, data which changes continuously, and on the other hand, the challenge is the same, this information needs to be organized and presented to the user with the detail to be understood. The latter one, a main and mandatory feature of RIA applications. That is, it is not enough to use shiny components or effects, they must align with the nature of the information. For example, the Magic Wall uses a map metaphor to present electoral results and from there with a touch of a finger or fingers you can zoom in a specific geographical area. The audience can actually analyze the results on the screen even before John King can explain it.
For me the Magic Wall has accomplished things that RIA apps should do as well:
Provide competitive advantage. I believe CNN has accomplished that. They have not only accomplished a "Wow" effect, but their competitors are still showing static screens. Everyone's attention is set in the general election, not only in the US but internationally, and it is a good time for News organizations who compete for audiences eager for information. RIA apps should facilitate user's interaction with data and apply information architecture best practices to find and understand data as clear as possible. This can make a big difference between one RIA application and another.
Organizes and presents information faster and in different dimensions (geographical and time) in the same screen real state. RIA applications should move from the page and pop-up dialogs paradigms and re-use screen real state dynamically following the direction of what the user is looking for.
Places this technology in the path to mainstream and raises expectations from users. CNN has provided the Magic Wall with huge visibility and people are noticing it. Since RIA is still an emerging technology, RIA apps should strive for setting a new standard and raising user's expectations.
I think the Magic Wall is providing a collateral benefit for RIA developers. People who are watching this technology on TV will be looking for the same rich experience in the Internet from now on. The challenge for us, RIA developers, is to provide that same magic in our applications.
