Re-do the way to do Internalization

[GoogleCodeExporter]

I will look into re-doing the way we localize the project.
I feel that we should follow the "Flex" way ... instead of inventing our own.

References:
---------
- Localizing Flex Applications
 http://livedocs.adobe.com/flex/3/html/help.html?content=l10n_2.html

- Video training: "Localization using resource bundles".
http://www.adobe.com/devnet/flex/videotraining/xml/vid46.html

- Localization using resource bundles.
http://www.adobe.com/devnet/flex/videotraining/content/exercise26.html

Original issue reported on code.google.com by huypha...@gmail.com on 26 Oct 2009 at 4:56

[GoogleCodeExporter]

Flash doesn't has the support for resource bundle to use for Internalization 
support.
This code is ported from it. It will be good to use the flex way.

Original comment by chesswhi...@gtempaccount.com on 26 Oct 2009 at 6:00

[GoogleCodeExporter]

Yes, I know. The way we did in Flash was a quick solution to get the 
localization done!

For this project, we can do the localization in phases:

Phase 1: Embed the localized (language) strings .properties file inside the 
main .swf file.  The size and the 
initial loading time is bigger but the response time would be better. Also, it 
is more simple and less work.

Phase 2:Convert each localized (language) strings .properties file into a .swf 
module and load them 
dynamically based on the user's selection.

Original comment by huypha...@gmail.com on 26 Oct 2009 at 12:16

[GoogleCodeExporter]

Completed Phase 1.

SVN Revisions:
http://code.google.com/p/chesswhiz/source/detail?r=15
http://code.google.com/p/chesswhiz/source/detail?r=16

Note: The 'LocalMgr.as' has been removed and replaced by the built-in Flex ' s 
ResourceManager singleton 
and the pre-defined member variable 'resourceManager' available in every 
UIComponent.
Close this Issue for now because Phase 1 is good enough for the 1.0 Release.

Original comment by huypha...@gmail.com on 29 Oct 2009 at 2:43

• Changed state: Fixed