We are not the only ones having to deal with the “Documents” folder on a Linux system. Freedesktop has created a solution for the problem. @Punkduck and @Wolgade: could you check if there is a
~/.config/user-dirs.dirs file on your system and check its contend?
wolgade wrote:Aranuvir wrote:BTW, the current concept of the code obliges to either hard code the location of the home folder, or to pass the information to the program on every startup via an environment variable or a command line option, which I consider an advanced use case.
If the current code can read the path from an environment variable or a command line argument, it shouldn't be too hard to get the path from a config file. This would fit anyone's needs. Just edit a single line and save your stuff wherever you want.
The option already exists (it was introduced for the PortableApps (Windows Tm) experiment) and is a command line option for the current Python2. But it was too intrusive in the core code, making Jonas worrying about his headless branch. So it is now an environment variable in the current Python3 branch and if you want to move the makehuman folder forever, you can reconfigure bash.rc to set a “MH_HOME_LOCATION” environment variable
. Honestly, I don’t think these are solutions for common users, and I do not want to give support for this advanced options.
Separating configuration files from the rest of the user’s content (for example a .makehuman.rc file or ./config/makehuman folder) would be the most flexible solution, allowing the user to store his content at any place of choice. Though, this will probably lead to greater code refactoring and to discussions, where to locate the config files on other platforms. IMHO, storing everything in one folder is the simplest solution for a multi platform application.
Currently there is already a working solution to move the makehuman folder to a “Documents” equivalent based on parsing user-dirs.dirs, with a fall back solution, if the “Documents” folder can’t be located.
I agree with punkduck, that moving the content of the user’s folder to a new location should be done by an external script, and we probably will need some cleanup actions, anyway, IIRC the Python3 code will crash on Python2 npz-files.
Robs intention was, to find out if anyone feels the need to move the makehuman folder to another location. Personally, I’m indifferent about this question, but if we agree to move the folder, I’d suggest the solution described above, that might not work for everyone.
BTW, would you mind giving the current development branch a try? I’d like to know if you experiance any OpenGl issues on your systems (the master branch currently will not move the location of the makehuman folder).
Some new features: plugins in the users folder and loading at run time, saving targets, weight estimation based on bsa, scripting console can make use of Jupyter/qtconsole (if existent on the system), sorted tags, fixed numpy exporting issue…
Most annoying known issues: OpenGl failures. Not working FBX exporter.