Currently it saves everything in config path (.config/openmw) which is against the XDG standards. Also, it's inconvenient to have the screenshots in the same folder as the config files and logs.
My suggestion is:
Linux:
- config files, logs: .config/openmw
- screenshots: .local/share/openmw
Windows: create subfolders (config, screenshots) in the openmw appdata folder.
Bonus task: A cache folder would be good to have (a place to save temporary data, so that it doesn't have to be rendered / calculated on the next run)
Examples:
- map generation (although a GUI to delete those would be handy, since they'll be outdated when the user installs new mods)
- conversions of binary data in the bsa files (e.g. like the rotated cursors in my latest pull request)
On linux, that would be .cache/openmw, on windows, again creating subfolder in openmw appdata.
[1] XDG base directory spec http://standards.freedesktop.org/basedi ... atest.html
Pathmanager standards compliance / new paths
- psi29a
- Posts: 5361
- Joined: 29 Sep 2011, 10:13
- Location: Belgium
- Gitlab profile: https://gitlab.com/psi29a/
- Contact:
Re: Pathmanager standards compliance / new paths
Isn't it illogical that log files to into a .config dir? Shouldn't only config files go there?
Re: Pathmanager standards compliance / new paths
Not sure. .local/share might be more appropriate. (Along with a subdirectory "logs" and "screenshots")
- psi29a
- Posts: 5361
- Joined: 29 Sep 2011, 10:13
- Location: Belgium
- Gitlab profile: https://gitlab.com/psi29a/
- Contact:
Re: Pathmanager standards compliance / new paths
I'm OK with that.scrawl wrote:Not sure. .local/share might be more appropriate. (Along with a subdirectory "logs" and "screenshots")
Re: Pathmanager standards compliance / new paths
I think better place for temporary files on windows is somewhere in %USERPROFILE%/AppData/Local/Temp/OpenMW, not in AppData/OpenMW (where configs would be). I hope windows gurus will correct me.scrawl wrote:on windows, again creating subfolder in openmw appdata.
Regarding OS X:
configs into ~/Library/Preferences/OpenMW (like now)
temp data into ~/Library/Caches/OpenMW
logs into ~/Library/Logs/OpenMW
Re: Pathmanager standards compliance / new paths
Not this discussion again We had that before and it wasted a lot of time. We ended up with deciding that the current solution is reasonable enough (for now).