Adobe Flex

Adobe Flex Learning Paths… now available

Adobe has published a new sub-site, Adobe Flex Learning Paths, to provide an easy way to get started with Adobe Flex.

They have divided the paths into 4 distinct sub-paths according to roles:


Each path is an easily accessible way to acquire more knowledge about Adobe Flex which is custom tailored to each specific role.

To study the path relevant for your role is a must if you are starting with Flex or are considering to get started.


If you are feeling adventurous, Adobe has even created a Flex version of the HTML sub-site… however it’s still in BETA, so its full of wet paint and wrinkles that need to be ironed out.

Check it out…

Adobe Flex

Localized Adobe Flex Applications… introducing BabelFlex

As you probably already know, the Flex SDK only contains English and Japanese locales, now some guys in the Adobe community have created BabelFlex which is a set of translated locale sources.

At the time of writing this there were locale sources for Spanish, French, Danish, German, Finnish, Italian, Korean, Norwegian, Dutch, Portuguese, Swedish and traditional Chinese.

Check it out…

Adobe Flex

RIA Architecture, the technology agnostic perspective

In the midst of the ongoing (and escalating) technology war between Adobe Flex and Microsoft Silverlight, it’s nice to see that foes can get together and solve common problems for the greater benefit.

It has managed James Ward and Josh Holmes to get together during JAOO in the Danish city of Aarhus (Søren, as you are reading this, are you regretful because you didn’t go and instead decided to go to TechEd in Barcelona? I guess not, hugh? )

Anyways… check it out…

This might be a groundbreaking event… you should probably make a note of it.

Adobe Flex

Adobe Flex cookbook

Adobe has started the cookbook initiatives, it’s meant to be a source for resources for developers when looking for solutions to problems they have or problems they didn’t know they had (yet). In that sense it could be a valuable tool in creating better Flex developers.

I have taken the liberty of taking one of my old posts and adding to the Adobe Flex cookbook.

Check it out..

Adobe Flex

Adobe Flex Data Visualization Watermark

Once in a while even the most professional individual finds themselves forced into a corner by circumstances over which they don’t have control… and on rare occasions it happens even though the individual do everything right…

…one such situation recently happened to me when I had to deploy an Adobe Flex solution using undigested Runtime Shared Libraries, Flex Modules and Data Visualization in one cool cocktail… after having been unable to rid myself and the solution for the annoying Flex watermark declaring that the chart was shown with a graph compiled with non-registered version of the Adobe Flex SDK, I consulted good ol’ Uncle Google for an answer…

If you don’t know what I am talking about… this is the watermark I am talking about… displayed in grayed out letters displaying “Flex Data Visualization Trial”…

Quickly I came to the JIRA entry for the problem stating that it was not a bug if you remembered to load the Framework RSL prior to loading the Visualization RSL…

However, this didn’t change a thing as I was already loading the framework prior to data visualization – I did however try, and yes, it wasn’t the solution…

Left with no official solution and a deadline I didn’t want to break for no one, I quickly had to become innovative and ingenious… I therefore dived down into the source code of the Adobe Flex SDK and eventually found my way to the sources for the data visualization components… once I had created an Adobe Flex Class library for the sources, compiling a SWC and referencing it from my application was easy.

To my great satisfaction, the homebrewed SWC proved to have no watermark when loaded as undigested RSL from a Flex module !

This solution not only solves the problem with the watermark, but it also allows me full control of which classes to include in the library allowing me to effectively cut the size of the visualization library in half based on the classes necessary for this particular application.

I have read the EULA from Adobe, and I don’t think I am in conflict when doing this… however, if anyone at Adobe reads this, please advice otherwise in case.

Please don’t hesitate to write me if you problems getting this solution to work for you…

PS… off course I have a licensed edition of Adobe Flex Builder, so this is not the issue here.

Adobe Flex

Enterprise Resource Management for Adobe Flex

One of the major challenges with building localized enterprise systems on Adobe Flex is to decide how to manage the resources and properties for the application.

The initial way we did this was to compile the resource bundles into distinct localized SWF’s that would be loaded at runtime depending on which locale the application was set to. This approach has some benefits, but definitely also has some drawbacks as the number of resources grow.

As a response to an ever increasing number of resources we need to support our ever increasing complex applications, we have at Hello created a resource management application that delivers the resources through a set of REST services that serves XML to the client that eventually are loaded into the resource manager.

Besides of facilitating editorial staff and text-writers to maintain the “static” texts in an application easier than through the use of the ordinary SWF based resource bundle sets, it has proved to reduce the development cycle with a couple of steps as well reducing the effort required by the developers to create the texts in the first place.

Through a set of search and simple filter-functions, it’s made possible for the editorial staff to find a certain resource easily and hence modify the texts without any knowledge of the inner layout and structure of the application, but merely by observing it…

I’m going to be writing more about this killer-app which makes the development and maintenance of localized enterprise applications much easier than it’s the case with the build-in localization support in Adobe Flex.

Adobe Flex

Danish Adobe Flex Campaign Site

Adobe Denmark has recently launched a Danish Adobe Flex Campaign site…

It’s not all that clear what the idea is, but besides the misspelling of Flec (sorry, I mean “Flex”) the coloring scheme is bold… on the edge of challenging… and the message is not that clear… I was hoping to have a Danish site to direct Danish clients to so that Adobe Flex could become more clear for the average business decision-maker out there… however, this site is just not going to cut it… we need good information to be able to deliver the message, but this is not that useful as it makes Flex look unserious and flaky.

Check it out yourself…