[Bf-committers] Setting a default system scripts directory

Ralf Hölzemer r.hoelzemer at googlemail.com
Mon Sep 21 23:03:06 CEST 2009


2009/9/21 GSR <gsr.b3d at infernal-iceberg.com>:
> No, that is a version-less one, just moving the files to new locations
> and names. The one I wrote is:
> http://www.infernal-iceberg.com/blender/config-layout-and-file-handling-250.mbox.txt
>
> It was posted to some developer in private at start of 2009, then
> pointed to it in this list, in April when talking about disallowing
> load of 2.50 data by 2.49 binary (nobody surprised by .Bfs yet?) and
> in May, about migrating to new names. Bretch posted it in this same
> thread some days ago.

Somehow I did miss that post, sorry.
Looks even more thought out than the wiki version and makes sense. I
like the idea of not overwriting datafiles until they landed safely on
disk.
I was bitten by that behavior a few timed due to crappy network
connections in our studio. :)

Regarding accessibility of hidden config directories - how about
providing an extra button in the preference panel that opens the
current config dir in the default file browser?
That would solve the problem that some people have with hidden folders
without breaking "unix style" configuration directories.
It would also be good for lazy people who don't want to go all the way
to C:\Documents and Settings\USERNAME\Application Data\Blender.
Fundation\Blender\Configuration\VERSION\

In linux, xdg-open [path] could be used for this. There surely must be
some way to do the same thing in win/osx?


More information about the Bf-committers mailing list