Zarel commented

Well, the maps folder is in there (users would need to put maps there), and so is the saved games folder (users would need to copy savegames from there to upload), and the documentation mentions messing with the config files more than once...

You know, Windows has a Saved Games folder for precisely this purpose (not that anyone uses it, but that's another matter entirely).

Per commented

I'd rather have the files somewhere more visible than somewhere even more hidden. As Zarel indicated, copying savegames and maps (and mods) around is part of ordinary use cases.

DevUrandom set resolution to wontfix

DevUrandom changed status from new to closed

DevUrandom commented

This has already been mentioned 2 years ago: http://gna.org/bugs/?9811
And was first reported by Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435681

It was rejected after discussion, because jumping after some specs cropping up every other day, trying to hide whatever from the user's eyes, was deemed not enough reason to change our filesystem layout.

EvilGuru commented

I disagree. The standard has been around for several years, and a reasonable number of applications follow it.

If we want to do maps and mods properly then we should use file associations (be it to install or just run). Then the user should never need to come into contact with the configuration dir.

Zarel changed status from closed to reopened

Zarel changed resolution from wontfix to ``

Zarel commented

Fine by me. Who wants to write a cross-platform GUI that installs mods when they're double-clicked?

And what about savegames? We really need a dedicated Saved Games folder.

Per commented

Linux really is missing a directory structure for user-modifiable game data like maps and savegames. We could approach the freedesktop games mailing list with a question about this so that we don't invent our own wheel.

cybersphinx commented

Hm, .config is far from standard (I have programs using ~/.progrc, ~/.prog/xxx, ~/kde/too/deep/to/find/anything, ~/.gconf/don't/do/this/by/hand, and now comes another ~/.config and ~/.local with subdirs), so personally I'd close this as "maybe later".

The problem is, we need a somewhat visible directory for savegames, screenshots, mods... and .warzone works well for that imo. Why use another directory for config files?

Paul Wise <pabs3@...> commented

~/.config/ is only far from a standard because relatively few upstreams care about it.

Also, ~/.config/.warzone2100-2.1 is the wrong directory, I'd recommend ~/.config/warzone2100/2.1 instead.

There is $XDG_DATA_HOME, which defaults to ~/.local/share for data like savegames etc:

http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html

There is a library to help make implementation of this easier:

http://packages.debian.org/sid/libxdg-basedir-dev

Zarel commented

I'm not sure ~/.local/share is a good place for savegames... it has a dot in it... savegames should not be hidden.

cybersphinx commented

Oh, it would be ~/.local/share/warzone2100-2.3/savegames then. IMO that's completely silly. And to me this looks like the kind of thing distributions have to enforce by making all their programs use this one standard, then maybe upstream will follow.

cybersphinx changed type from patch to to-do

Emdek commented

Nothing is more annoying that applications creating directories in ~/ directory without asking first (and I've never found Linux native one that does such nasty things, only some crap run using Wine do that).

Approach described by Paul Wise is simply best one, there was already one change in master that made savegames unavailable (renaming theirs folder, removing s).

The only alternative option is to add configuration option to select directory for them.

Emdek commented

Also if Qt is already used then you can use built in methods of QDesktopServices class to get standard path.

cybersphinx commented

http://xkcd.com/927/

Emdek commented

;-)

But here we have one standard and one de facto standard. :-)

cybersphinx commented

http://developer.wz2100.net/ticket/659#comment:7 - as long as there's not one clearly winning standard (and there isn't) I don't see the point of confusing people by changing our current way.

Emdek commented

Sure, but there was already location change for savegames (removed s from directory name, under Linux, at least), but I'm not sure if this is different from that of 2.3.x or only reverted change in master.

Per changed status from reopened to closed

Per changed resolution from `` to later

Per commented

The 's' was changed because the savegame format was changed, and I didn't want people accidentially loading savegames that would no longer work.

As regards my comment above (comment:6), the there has been some discussions of the issue on the freedesktop lists. I found the discussions non-conclusive, with little interest from freedesktop people of addressing the issues raised by the game makers.

In any case, this is a policy issue and this is not a discussion forum. I suggest this discussion is moved to the forum or the mailing list, so that more people can participate. Closing ticket for now.