R – Changing Flex Components Language

apache-flexflex3flexbuilder

When we are building a application in Flex the components that we add are in English.

Lets say that i want to change then to French, Spanish or Portuguese.

How could i do that??

I've google a bit about it, but nothing good.

I didn't look too much, because you guys always now things, and here in SO its more faster to ask than search for it

😀

Thanks for any help.

EDIT:

I think i didn't expressed my self correctly.

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute" width="408" height="332">

    <mx:DateChooser x="117" y="83"/>

</mx:Application>

This creates a calendar where you can choose a date, as default shows the present date.
If you take a look the Months he shows "January, February, …" they are in English, lets say i want then in French or any other language.

How can i do that?

Best Answer

Adobe has a good article on the ResourceManager. This lets you store different languages, currency formats, etc, and access them based on the current locale the application is running in(runtime configurable).

In practice please remember to check the sizing of your Labels and Buttons! In one language a label may be well placed and the appropriate size, in another language the label may be too small and your whole layout will look bad. It's better to think of that upfront instead of at the end.... like I did....

EDIT:

I haven't followed this guideline, but it seems to match your Datechooser edit. I don't use Datechooser in either of the apps I maintain, so I can't provide help with it unfortunately.

Related Solutions

R – Where to begin learning Flex and Flash

It depends on where you want to go.

If you're aimed towards making "application"-like content - that is, buttons, pulldown menus, tab and accordion frames and so on, then probably you should keep on with the Flex tutorials. Flex is a framework, remember - it will spare you more of the gritty details if what you want to do is aligned with it.

If you want to make more generally expressive content - games, unique menus, highly interactive experiences and the like, then learning Flex would probably be a sidetrack. You'd be better off focusing on ActionScript itself.

Since you're starting from zero, you should also consider how far you plan on going. If you hope to eventually be able to handle complicated, heavily script-driven content, then you'd be better off learning ActionScript 3 and pretending AS2 doesn't exist. However, if you need to learn "enough" scripting to get the job done, but you don't plan on getting married to it, then you might prefer to do the reverse. AS2 is much more ad-hoc, and less strict. It has more whippituppitude, as they say. But for complex work AS3 is far better.

As for learning other languages, I'd say not so much. AS2 is very similar to JavaScript, and AS3 is very similar to Java, but you'll understand much better how to make good Flash content if you learn the scripting together with the authoring tool, and you'll come away more able to grok Flash's internal structure and the attendant possibilities and limitations.

Apache – ‘Pre-measuring’ Flex Components

I studied the framework code a bit, and if initial results are an indication, this isn't as painful as I feared. The guts of it:

var renderer:IListItemRenderer = getRenderer();
renderer.initialize();
for each (var cell:Object in cells) {
    renderer.data = cell;
    renderer.validateProperties();
    renderer.validateSize(true);
    // Access renderer's size properties here
}

Passing the 'recursive = true' flag to validateSize is the key that I was missing previously. Unfortunately there's no equivalent flag for validateProperties, so I'll probably have to implement that myself to make it reliable for arbitrary ItemRenderers.

Best Answer

Related Solutions

R – Where to begin learning Flex and Flash

Apache – ‘Pre-measuring’ Flex Components

Related Topic