It depends on the user population and the types of settings you're storing. Do you want to allow (or encourage) your users to muck to around with XML settings outside the application, with no constraints? If it's just colors and fonts and such, where the application just looks ugly but isn't broken, there's no problem. But if you're letting them change comm settings or other things that could break the application, (and that the users may not completely understand), it could easily become a support nightmare. It might be better in this case to let only the application make configuration settings, so you can ensure consistency.
- David Gallardo At 09:03 AM 9/2/2002 +0200, you wrote: >Hi all > >We are developing a desktop application. It is necessary to set up a >system of storing the user's workspace settings. I think there are two >standard options how to do this: > >1. Serialization >2 . Store the settings in an XML file or a set of XML files. > >I wonder which of theses approaches suites better. As of now, I can think >of the following pros and cons : To change your JDJList options, please visit: http://www.sys-con.com/java/list.cfm
