Hi Paul, It's true that a property file is more flexible - because it is text that doesn't need to be compiled. But I wonder if there is a performance difference between a text and a compiled property file, especially for are a large number of entries. I don't have any evidence from a code profiler to prove this, but I suspect that a compiled file will load faster than a text/property file. If you only have a small number of entries, it won't make any difference, but for large amounts of info, it might.
Just a thought... -----Original Message----- From: Paul Kavanagh [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 8:01 PM To: [EMAIL PROTECTED] Subject: Resource bundles best practices Hi everyone, a colleague of mine wishes to use ListResourceBundles to store resources such as button labels etc. I think it'd be better to use property files in order to isolate locale-specific data so that it can be translated/modified without changing the code and forcing a recompile. He thinks the likelihood of us translating the data is slim however, and wishes to use ListResourceBundles to store objects such as keystrokes, eg Ctrl-C, for which we would otherwise need to map from a String -> javax.swing.KeyStroke. My question is, even if the likelihood of translating is slim, is it not worthwhile having the gui data isolated in any case ? Also, what is the best practice for storing keystrokes in property files ? Thanks in advance, -Paul _______________________________________________ Advanced-swing mailing list [EMAIL PROTECTED] http://eos.dk/mailman/listinfo/advanced-swing _______________________________________________ Advanced-swing mailing list [EMAIL PROTECTED] http://eos.dk/mailman/listinfo/advanced-swing
