pivot-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Chambers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PIVOT-940) Localisation Using a Non Class Related File
Date Fri, 04 Apr 2014 21:25:16 GMT

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

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

Hi Roger,

Thanks for the reply:] 

I was more trying to make the point that the JAVA resource bundle way of doing things in this
case does not make any sense.
The bxml files don’t need to be done like this, so why are json files being done this way?
There is no reason in a bxml architecture that you would ever have either localisation in
a different place to the bxml and stylesheets.
More requesting can we just have some way of directly loading the file like the bxml file.
The bxml is to separate the GUI from the Code, so that different people can work on it etc.
By tying the localisation back into the code, it seems to be working the wrong way.
The bxml can be included into the jar as well, but in a place that makes more sense if that’s
where you want to store them...

For example in my currently application suite I am working on:

So you end up with:
Library.jar	(All the  classes Packaged together AAA.BBB.CCC.DDD.EEE)
gui		(Directory of Gui/*.bxml and Gui/*.json stylesheets)
conf		(Application Config Files and database etc...)
application.sh	(Something to run it...)

Now in which group does it make sense to put the localisation? I think it should be in the
gui directory with the bxml... Because language is just presentation...

PS-By the way this is not really big deal, easy to work around, bit messy but just seemed
strange to me...
Regards,
Mark.



> 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
>
> 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)

Mime
View raw message