[jsword-devel] Idea for optimisation/improvement in iso639 lang props init

[Peter von Kaehne]

Not being a programmer, but the only two times you actually need all this info is 

a) during display of installed modules along languages
b) via the module manager.

My suggestion is that you use this long list only when there are changes :

to a) when you install a new module from a different language
to b) when you refresh the repo content.

On each occasion a much shorter list of actually needed translations could be created and stored and be available for subsequent runs.

Peter

-------- Original-Nachricht --------
> Datum: Wed, 22 Dec 2010 15:07:27 +0000
> Von: Martin Denham <mjdenham at gmail.com>
> An: J-Sword Developers Mailing List <jsword-devel at crosswire.org>
> Betreff: [jsword-devel] Idea for optimisation/improvement in iso639 lang	props init

> I have occasionally tried to improve the slow start-up times of And Bible
> &
> JSword without much success.  However, one area which I have a suspicion
> may
> take time is property file loading.
> 
> I run out of memory part way through when profiling startup but I notice
> iso639.properties which has 7600 lines can take 2 seconds to load up on
> slow
> phones.  I wonder if, instead of storing the language codes in properties
> files we could use methods like Locale.getDisplayLanguage(loc) and other
> Locale methods to completely remove the need for the iso639 properties
> files.
> 
> What do you think?
> 
> Regards
> Martin

-- 
GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt auch mit 
gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl