Thanks. This is basically what I was thinking, but in more detail. John On Thu, Apr 12, 2012 at 01:10:49PM +0100, Michael Whapples wrote: > Properties are simply key/value pairs, if these are sufficient then a > properties file is enough. If you need more (eg. in settings if you want > a single config file with multiple sections then properties files will > not be enough for settings). > > Having said the above, simple key/value pairs can be fairly powerful if > used correct. Rather than having a single config file with multiple > sections, you can have multiple sections by having multiple properties > files for settings. Multiple files can make it harder for hand editing > to know where to find a particular setting, but BrailleBlaster is not > that sort of application, I would imagine all configuration should be > done through the UI and the user should not be concerned with how > settings are stored (eg. they would not care if you were using files, > databases, etc), all they would care about is how that particular method > of storing would allow them access (eg. databases or files on a server > may allow users to have settings that follow them about regardless of > computer they use). > > My general thought is, unless there is a reason to go with more > complicated things stick with the simpler. There may be valid reasons > for settings. As for languages I thought classes as far as the > application went were fairly easy to drop in for properties files, so I > probably would say properties files and then switch to classes as and > when the need shows. > > Remember on languages, properties files are much simpler for people to > add, classes require compilation and the compiled version would be > harder to edit if someone needs to. > > Michael Whapples > On 12/04/2012 12:13, John J. Boyer wrote: > >We have properties files for English and Chinese, which were sent to the > >list previously. There will eventually be more such files for other > >languages. I have come to realize that they should be in the directory > >dist/programData/lang . There will also be a dist/programData/settings > >directory, which will contain properties files for system and user > >settings. Will properties files be adequate for locale handling, or > >should we use ResourceBungle classes? Similarly, will they be adequate > >for settings or should we use the classes in java.util.prefs ? > > > >Thanks, > >John > > > -- John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc. http://www.abilitiessoft.com Madison, Wisconsin USA Developing software for people with disabilities