flex 3 sdk

In previous posts in the series we discussed new features in Flex 4 that are basic in nature (namespaces, an introduction to the new Spark components architecture and the new mxml tags to name a few).

In the next few posts we will discuss the more interesting stuff new with Flex 4 like FXG, states, layouts, effects and skinning.
So, without further ado, View States!

 

sefi 29/06/2010 - 08:56

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

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

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

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

In previous posts in the series we discussed namespaces, an introduction to the new Spark components architecture and the new mxml tags introduced with Flex 4.
This post is all about data binding, and two-way data binding new to Flex 4 specifically.

Basically, data binding is like taking a piece of string and tying each end to an object, so that when the data in one object is modified, the modified data also applies to the other object. The benefits are obvious – an easy way to pass data between different layers of the application or an easy way to catch an event with a single handler and have that handler update more than one object are a few examples.

sefi 30/05/2010 - 23:07
Syndicate content