On Wednesday 17 August 2011 05:20:21 you wrote: > Re Windows, > the QDesktopServices::StandardLocation enum handles the system paths. > Config *is* data
OK then on Windows ConfigLocation will return the same as DataLocation. On Unix, though, XDG_DATA_DIRS/XDG_DATA_HOME is very different from XDG_CONFIG_DIRS/XDG_CONFIG_HOME. > and goes into the correct place according to application/user > data HomeLocation/(yourdir or .yourdir)- user config / data (dot is a unix > convention) DataLocation - application system wide config Not sure what you mean exactly here (seems to address both Windows and Unix?) > Also, the registry is a storage location. Speaking of which QSettings might > be a valid mechanism for your software as well, since that is the Windows > Way. Personally, I'd put any config in the registry that other programs > would need to use, and use a config file for the rest. QSettings supports > that too. QSettings has its own issues (not compliant to the freedesktop.org desktop- entry standard, stateful API, not sure if it's maintained, etc). More generally I think the question of "in which path is configuration stored" (when configuration files are used, i.e. not when using the windows registry), should be separate from the code that implements a particular configuration system (QSettings, KConfig, etc.) -- David Faure, [email protected], http://www.davidfaure.fr Sponsored by Nokia to work on KDE, incl. Konqueror (http://www.konqueror.org). _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
