Topic: Good new docu on configuration
Good new docu on configuration
Hi guys,
I really think that the updates you've made to the documentation are really good! One thing I was especially needing was the chapters about manual editing the configuration file (conf.xml) and using it as a way to share your configuration between machines.
I see also a file that has some significance, userpreferences.dat. Seems that some of the configuration is stored in this file? Can you explain why I need both files...
I really think that the updates you've made to the documentation are really good! One thing I was especially needing was the chapters about manual editing the configuration file (conf.xml) and using it as a way to share your configuration between machines.
I see also a file that has some significance, userpreferences.dat. Seems that some of the configuration is stored in this file? Can you explain why I need both files...
Hi Franklin,
Thanks for the positive feedback. The relationship between the two files is as follows: From the application perspective, the conf.xml file is treated like a read-only master configuration. The userpreferences.dat file then works as a "modifications to the master configuration" layer. In other words: If you change something in the UI of datacleaner, then you change userpreferences.dat. But if you register something in conf.xml, then that will become unmodifyable from within the UI. So that is why eg. the "orderdb" datastore cannot be changed or deleted in the UI, but you can remove it from conf.xml if you want to.
Why go to all this length and not just have a single configuration file? That's because it is nice that the hand-editable configuration file is clean and manageable, while the configuration file (userpreferences.dat) that the UI works with is likely to be filled with all sorts of state information that the user will likely not be interested in (eg. the size of windows, visual preferences and more like that).
Thanks for the positive feedback. The relationship between the two files is as follows: From the application perspective, the conf.xml file is treated like a read-only master configuration. The userpreferences.dat file then works as a "modifications to the master configuration" layer. In other words: If you change something in the UI of datacleaner, then you change userpreferences.dat. But if you register something in conf.xml, then that will become unmodifyable from within the UI. So that is why eg. the "orderdb" datastore cannot be changed or deleted in the UI, but you can remove it from conf.xml if you want to.
Why go to all this length and not just have a single configuration file? That's because it is nice that the hand-editable configuration file is clean and manageable, while the configuration file (userpreferences.dat) that the UI works with is likely to be filled with all sorts of state information that the user will likely not be interested in (eg. the size of windows, visual preferences and more like that).
Log in by clicking the login link at the top of the screen
Go back to forum.
