[Bf-committers] Setting a default system scripts directory

Campbell Barton ideasman42 at gmail.com
Tue Sep 22 05:22:37 CEST 2009

On Mon, Sep 21, 2009 at 12:41 PM, GSR <gsr.b3d at infernal-iceberg.com> wrote:
> Hi,
> r.hoelzemer at googlemail.com (2009-09-21 at 2019.31 +0200):
>> > That is why I wrote the spec & tried to call attention to it a couple
>> > of times, months ago. But now, with tight releases ahead, it feels it
>> > will be rushed and will have to be fixed down the road instead of
>> > having a system that could work years like SDNA did with .blends.
>> If you mean the spec at
>> http://wiki.blender.org/index.php/BlenderDev/Blender2.5/ResourceFilePaths
>> then that's a real shame. I found the spec logical and predictable.
> 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.

GSR, Quickly read over your proposal and generally like it but didn't
think over each issue deeply or compare to the wiki.

You mention an an API to open, close, read and write files.
To me this can the a part of a broader plan but makes your proposal
harder to discuss. Do we need a new api? what will the api look
like?... etc.

Could you review any discrepancies with the winter camp wiki make a
shortlist of changes you can go ahead and make right away.
Should be fairly easy and coexist with my recent changes.

More information about the Bf-committers mailing list