Flex3.0 & AIR 1.0 release and some goodies

Every blog I look around on announces the coming of the new Era of Flex3.0 & AIR. Yesterday, I was at the Flex User Group Meeting at Adobe Bangalore Office and I could see the excitement in the eyes of all who were present. Check out these “Flex Behind The Scenes” videos by Matt Chotin, our Product Manager…

There are some more news in conjunction with this…

1. 30onair.com – What is 30onair?
2. opensource.adobe.com – Here is what we promised. The new opensource.adobe.com site is going live and will serve as a hub for Adobe open source projects, news and more. For open source projects like the Flex SDK and BlazeDS, the site has related content,a subversion source control tree that anyone can use, and links to the bugs base and forums. We are also linking to other open source projects, and related events. The site currently has 9 projects running.
3. developer.adobe.com – developer.adobe.com spots an improved look, with better navigation & search facilities.
4. Kick A** Live Docs – I personally was not a big fan of the Flex 2 live docs. But Flex 3 live-docs rocks. Check it out !

More to follow 🙂

How to apply the Data Visualization license on command-line in Flex 3 !

In the last post, I talked about the various licensing changes in Flex 3 & FB3. I said that the way to create charting applications n Flex3, is to get a FB Pro license (as charting is not a separate product anymore) and enter the serial number in FB3 and then develop as usual. I also mentioned that the license.properties file has now been moved to a global location in Flex3from its usual “/frameworks” path in Flex 2.

Now, what if you are one of those IDE haters or prefer VI, EMACS, TextPad over any IDE then this causes a problem for you. You might have the FB Pro license number which includes the Charting & Data Visualization component license, but you might not have FB installed. Then the license.properties file does not exist and so you will get a Trial-Watermark on your chart as below, despite having the license key. This will not happen in Flex2, as the license.properties file resides in the SDK directory itself.

DV Watermark

The way to go, is to use the flex-config.xml file. flex-config.xml is the configuration file contains most of the default compiler settings for the application and component compilers. In Flex3, we have added a license tag, where you can specify the compiler option for your Flex serial number.

<licenses>
<license>
<product>flexbuilder3</product>
<serial-number>your serial number here</serial-number>
</license>
</licenses>

So, the compiler will now pick up the options from the config file, even though license.properties file does not exist.

The good news for those who have FB installed and still want to use the command-line compiler is that the compiler also checks for the existence of the license.properties file, so you may not have to do the above steps and it would work as is for you without problems…

Update (04/23/2008):

The path to find the licence.properties file on various OS’s in the final Flex3 release is as below:

OS	Location
Windows XP	C:\Documents and Settings\All Users\Application Data\Adobe\Flex\license.properties
Windows Vista	C:\ProgramData\Adobe\Flex\license.properties
Mac OSX	/Library/Application Support/Adobe/Flex/license.properties
Linux	~/.adobe/Flex/license.properties

You can get more details on this article in the livedocs…

Changes in Flex 3 licensing model

There have been several changes from Flex2.0.1 to Flex 3. In this post, I’ll discuss about the packaging changes in Flex Builder(FB) and the changes in licensing for the product.

Packaging changes in Flex 3

In Flex 2, we had the following types of packaging…

• Flex Builder 2
• Flex Builder 2 with Charting
• Flex Charting 2

In Flex 3, it has become as below…

• Flex Builder Standard
• Flex Builder Professional

This means that the Flex Charting product that existed in 2.0.1, no longer exists as a standalone buy in Flex 3. Instead, it is packaged in the Data Visualization package (which includes Charts & its enhancements, AdvancedDataGrid, OLAPGrid… etc) which is available only with the Flex Builder Pro.

Over and above the standard edition, the professional edition will provide premium features like Charting and Visualization components, the Profiler, and the Flex Test Automation Framework. If you need more info about prices and stuff, you can check out this post by Ted. A thing to note here is that the Automated Testing Framework is available only with the FB Pro & also that this would be the only way of buying the Automation framework of rhe product…

FB & Data Visualization Licensing and the “licenses.properties” file

Now, let’s talk about the licensing. In Flex2, if you had the charts.swc then you could write applications using the charting framework. But this would lead to a trial watermark to be displayed on the chart as below, which would make it useless for production applications.

Charting Watermark

The way to get rid of this was to get a Flex Charting license and then add it in the “Manage Flex Licenses” tab in Flex Builder 2 or add it in the license.properties file in the “\sdk\frameworks” directory.But with FB3, a whole new set of work flows emerge.

1. If you need to use charting in FB3 using Flex3 SDK, things are a breeze. You can install FB Pro, and enter the serial no in the “Manage Flex Licenses” tab in the “Help” Menu and you are ready to roll.

2. But, FB3 also supports multiple-sdks in it. It comes pre-installed with Flex 3 & Flex 2.0.1 sdks (you can find it in the “\sdks” directory). So you may want to still continue working with Flex 2.0.1 project in FB3. If that project has charting, you will still see the watermark, even if you enter the FB3 Pro serial. This is because the Flex 2.0.1 SDK takes the charting serial from the licence.properties file in its SDK directory (“\sdks\2.0.1\frameworks”). So the way to work around this is to enter your Flex 2 charting license in the file.

Also, another thing to note is that if you want to manually enter the FB license in the license.properties file in Flex3, the file is now stored in a global location in the OS and not in the frameworks directory in the SDK path. The path to the license.properties file for various OS’ are given below.

• “../Documents and Settings/All Users/Application Data/Adobe/Flex” directory on Windows
• “Library/Application Support/Adobe/Flex” directory on MAC
• “$HOME/.adobe/Flex” on Linux