[ 
https://issues.apache.org/jira/browse/PIVOT-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13970411#comment-13970411
 ] 

Mark Chambers commented on PIVOT-940:
-------------------------------------

>From the Java Files is where I am having trouble. for example:
mPumpCardPane[i] = (CardPane) 
bxmlSerializer.readObject(mPumpCardPane[i].getClass(), 
vFoundConfig.mGUITemplate,true);
Now where do i put the json file? is it CardPane.json... does that mean I have 
to expand the Pivot Jar... or just put this anywhere in the class path?

I may be missing something simple here that is already implemented?

> Localisation Using a Non Class Related File
> -------------------------------------------
>
>                 Key: PIVOT-940
>                 URL: https://issues.apache.org/jira/browse/PIVOT-940
>             Project: Pivot
>          Issue Type: Improvement
>          Components: core-json, core-serialization, wtk
>    Affects Versions: 2.0.3
>         Environment: ALL
>            Reporter: Mark Chambers
>            Assignee: Sandro Martini
>            Priority: Minor
>              Labels: Localization
>             Fix For: 2.1
>
>
> Currently it seems that the resources in Pivot are done that same way as the 
> JDK, so .json files are associated with the classes. 
> Since anybody working in an International software industries has to deal 
> with the problem of continualy having to translate applications languages, it 
> seems strange to have to wrap up the languages with the Class Files.
> Ideally an external file, should be able to be specified, like the bxml 
> file... That is sitting somewhere with the other resource files, 
> configuration files etc...
> No reason to link it too the class, since 95% of class are not even GUI 
> components, and the way Apache Pivot does it is has a single GUI class, so 
> why bother linking it to the Class...And it is relevant to the bxml files not 
> the classes...
> Also means that when you wrap it up in a Jar for deployment the language 
> files can be sitting outside, so distributors and resellers, or open source 
> community members etc. can make the application support their language 
> themselves, just by copying,renaming and modifying the Language file...means 
> we can obfuscate jars easier etc...



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to