David Deraedt

UPDATE: The slides and samples are now available for download. Thanks to everyone who attended the session!

So you've built a great app, and of course you want it to be used by everyone and their mother, probably by taking advantage of the new multiscreen capabilities of the Flash platform?

Then remember: having your application running on every device does not mean much if your users simply can't understand it. If you're truly committed to reach as many users as possible, you want to internationalize your application.

Updated on June 1st to add a SparkSkin description given by Ely Greenfield

I noticed that the new spark and Flex4 architectures can confuse developers coming from Flex3, so I decided to create some very simple class diagrams to help them get the big picture.

Please note that these diagrams are by no means exhaustive, and probably not even 100% accurate: they're just meant to provide an overview in three simple steps. I hope it can be useful to some of you.

So here we go:

Besides the still existing mx components architecture, we now have the spark architecture with two main branches: SkinnableComponent which is the super class for the new spark components, and Skin, which is the super class for the components skins, ie the class which defines the look of the component.

This project was discontinued.

You can grab the source here.

*** *** *** *** *** *** *** *** *** *** 

Lupo is a set of tools designed to help localizing Adobe® Flex® and Adobe AIR® applications.

As of today, lupo is comprised of three parts :

Lupo Manager, an Adobe AIR application, helps developers extract strings from their source code, manage resource bundles and implement i18n logic in their Adobe Flex / Adobe AIR applications, in a very productive way.

It's about 10 days late, but it's here. I'm proud to announce that lupo manager is now available for download. You can now start internationalizing and localizing your flex apps in a much more productive way ;)

Lupo manager is the first (and main) part of the lupo localization studio: it's the tool which helps Flex developers extract strings from their code, manage resource bundles, and implement i18n features in their apps. Lupo Translator, the second part of the lupo localization studio which is aimed at translators, should follow very soon.

 This project was discontinued.

You can grab the source here.

*** *** *** *** *** *** *** *** *** *** 

With lupo manager, an Adobe® AIR® application, easily extract strings from your source code, manage resource bundles and implement i18n logic in your Adobe Flex® / Adobe AIR applications, in a very productive way.

Following the sneak peek video, I wanted to give you a better, in-depth overview of my new toy, Lupo Flex application Localization Studio. So here's a pseudo real-time video demo of me localizing a Flex app using Lupo Manager, and a feature list.

Real Time Demo

This video shows a case study : I use Lupo to translate a sample Flex ecommerce application in "real time" (not including the actual translation job). The video lasts about 8 minutes, but, presentation constrains aside, internationalizing such a small app shouldn't take more than 2 minutes with Lupo.