flex 3

Flex 3 SDK Vs. Flex 4 SDK

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
comparison, flex, Flex, flex 3, flex 4, MX, namespace, sdk 3, sdk 4, Spark
Migrating Flex 3.x application to Flex 4.5 – Tip No. 4

The next tip refers to fonts embedded either with CSS or style tag.

 

The format we know and used in Flex 3.x was:

 

sefi 11/07/2011 - 13:56
embed font, embed-as-cff, embedAsCFF, flash text engine, Flex, flex, flex 3, flex 3 sdk, Flex 4.5, Flex 4.5 SDK, font, migration, Spark
Migrating Flex 3.x application to Flex 4.5 – Tip No. 3

The next few posts will be dedicated to common errors that arise from moving to Flex 4.5 SDK and Spark Theme.

 

First, let me explain why those errors arise. When changing the compiler SDK to Flex 4.5 some errors arise and are easily fixed.
When you change the theme to Spark Theme, some styles are no longer supported for mx components.

 

If you plan a complete migration, you will replace those with Spark equivalents and all will be good.
If, however, you only plan a partial migration, then you won’t necessarily replace all components but you will have to handle those errors.

 

The first one will be borderThickness and backgroundAlpha styles, which are no longer available for some mx compoments under the spark theme.
Let’s review an example (code was modified to protect customer code):

 

sefi 11/07/2011 - 13:50
flash variables, flash vars, flashvars, Flex, flex, flex 3, flex 3 sdk, Flex 4.5, Flex 4.5 SDK, html-wrapper, migration, swfobject.js
Migrating Flex 3.x application to Flex 4.5 – Tip No. 2

As described in a previous post, I am currently doing some migration work for a client, migrating their Flex 3.5 application to Flex 4.5.

 

I needed to pass a set of variables to the main application using flashvars.

 

In Flex 3, it was pretty straight forward – you’d use the html-template file and modify it’s object tag to include those variables.

This has changed somewhat with Flex 4.5.

 

First, the template itself has changed. It uses a different js file, and runs differently.
Second, the way you supply the flashvars has also changed, since it is no longer a string but rather an Object with each flashvar is a property on that object.

sefi 04/07/2011 - 16:56
flash variables, flash vars, flashvars, flex, Flex, flex 3, flex 3 sdk, Flex 4.5, Flex 4.5 SDK, html-wrapper, migration, swfobject.js
Migrating Flex 3.x application to Flex 4.5 – Tip No. 1

I am currently doing some migration work for a client, migrating their Flex 3.5 application to Flex 4.5.

 

Occasionally, I will undoubtedly encounter bumpers…
This will be an account of those bumpers, and how I came to resolve them. This is not guaranteed to be the best solution, just the one that worked for me, usual caveats apply.

 

The application I am migrating is built of modules, and every time I ran the app I got an exception on UIComponent’s getStyle method. Nothing I did fixed this, until I found this link.

It describes a compiler flag, namely ‘isolate-styles’ which, when set to false, you can prevent merging of styles between the modules and the main application.

 

sefi 04/07/2011 - 15:24
compiler flag, flex, Flex, flex 3, flex 3 sdk, Flex 4.5, Flex 4.5 SDK, isolate-styles, migration
Flex SDK 3 Vs. 4 - Part 1 - Namespaces

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
comparison, flex, Flex, flex 3, flex 4, MX, namespace, Spark
Syndicate content