I am trying to localize a component I am making, I put the source
.properities files in my project root as "locale/en_US" etc...

I added the following compile argument to my project "-source-path
locale/{locale}"
Project -> Properties -> Flex Compiler ->Additional Compiler Arguments 

It works but gives me this Warning about how the "Source path entry,
{path_to_my_project}\locale\en_US is a subdirectory of source path
entry, {path_to_my_project}.

So you do you usually do localization withen in a Project of the Flex
Builder.  

Is it possible to make localization of package components?  Flex's SDK
uses the ones in the {SDK_Root}/frameworks/locale/{locale} folder, but
I would hate to have to dump a SWC and localization files in 2
different places to make it feasible for people to use a component.

Renaun

--- In [email protected], "adobeted" <[EMAIL PROTECTED]> wrote:
>
> We have a unique opportunity to define a standard for component
> packaging, delivery, and installation. We need to make sure that end
> users have a reliable, consistant way to get a component installed and
> working. I would like to define this standard here as a group.
> 
> Here are some thoughts:
> 
> 1. KISS - This needs to be simple and consistant. End users should not
> struggle to get a component installed and working. If we all ship
> components in the same structure/pattern, it will minimize confusion.
> 
> 2. Consistant directory structure across components. When a component
> is received it should be easy to find documentation, installation
> instructions, license, and source if included.
> 
> Filesystem or ZIP Archive like so:
> 
> /ComponentName/
> /ComponentName/source/
> /ComponentName/swc/
> /ComponentName/examples/
> /ComponentName/docs/
> /ComponentName/install.html
> /ComponentName/documentation.html
> /ComponentName/license.html
> 
> 3. Consistant instructions in install.html, documentation.html,
> license.html and consistant professional generated documentation.
> 
> 4. Code standards for component source. Define simple guidelines for
> formatting source code. Indentation and comments to improve
> readability of code within source.
> 
> ------------------
> 
> Thoughts, comments, additions?
> 
> Ted :)
>







------------------------ Yahoo! Groups Sponsor --------------------~--> 
Check out the new improvements in Yahoo! Groups email.
http://us.click.yahoo.com/6pRQfA/fOaOAA/yQLSAA/nhFolB/TM
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/flexcomponents/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 


Reply via email to