flex 4

Flex 3 had some language tags we are all familiar with like <fx:Binding>, <fx:metadata>, <fx:script> and <fx:style> to name a few.

Flex 4 introduces some new mxml tags you can use when writing mxml classes. They are <fx:Declarations>, <fx:Definition>, <fx:Library>, <fx:Private> and <fx:Reparent>.

 

sefi 14/05/2010 - 09:00

Now that Flex SDK 4 was released, I thought I'd do a series of posts on the differences between Flex 3 and Flex 4 SDKs that will hopefully help migrate your Flex 3 app to Flex 4 or make the transition from SDK 3 to SDK 4 easier. I will be assuming you already know Flex 3 and will concentrate on the new in Flex 4 compared to Flex 3.

This post will serve as the index of the series, and I will be adding links to the different posts to this one as they become available, so come back from time to time to get updated.

 

sefi 21/04/2010 - 07:33

 Over the past few months, I have heard that question many times.

 

Many think HTML5/JavaScript is going to replace it, and with Adobe releasing Edge it seemed to be a valid point.
Deepa Subramaniam, Senior PM for the Flex team, alleviates those concerns with her post (rather a post on the Flex team blog).

 

 It is a must read.

sefi 03/09/2011 - 14:43

The main incentive for the migration was to support RTL languages namely Hebrew and Japanese. Fact is that Flex 3 does not handle RTL writing properly – try writing Hebrew and English together.

 

After finalizing the long and fragmented process, I found that the migration had two main parts – handling the visual aspects (styling, skins etc) and handling the application logic (components and AS). I found a workaround that helped me to split the process into these two parts – i.e. set the styling to backward compatibility mode and handle the logic first. Then, once the application compiles and runs ‘properly’, disable the compatibility mode and go thru the styling issues.

 

So, to set the backward compatibility with Halo you should do the following:

 

charlie 18/07/2011 - 21:26

Flex 4 added some namespaces, while it still supports the Flex 3 namespaces. This can cause some confusion, more so since some classes are part of two namespaces.

 

While Flex3 used only one namespace (xmlns:mx="http://www.adobe.com/2006/mxml"), Flex4 uses 3 namespaces:
xmlns:fx="http://ns.adobe.com/mxml/2009"
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/mx"
Note, that while there's still a mx namespace, the URI is different.

 

Each namespaces defines a component set. The old Flex3 mx namespace is still active but if you use it Flex 4 features will not be available.

 

The fx:namespace includes top-level AS building blocks such as Object, Array etc. but does not include any of the mx or spark component sets. It also includes some mxml tags, like <fx:script>, <fx:style> and <fx:declarations>.

sefi 21/04/2010 - 07:35

Today, Adobe released the official version of the Flex 4 SDK as well as the new Flex IDE/eclipse plugin named Flash Builder 4.

As with Flex Builder 3, there are two versions of Flash Builder 4: Standard & Professional. The main difference is Profiling and network monitoring features.

 

Purchase/upgrade costs are described here.

You can download the free Flex 4 SDK here.

You can download a free trial of Flash Builder 4 here.

 

*** BONUS ***

If you are a student or faculty member with a valid id as proof, you can get the Flash Builder 4 Standard for free here (for non-commencial use).

 

 

sefi 22/03/2010 - 15:27
Syndicate content