[Bf-committers] Installation/file paths

[Campbell Barton]

Hey Matt, read through the proposal and most of this seems like common
sense to me, so +1

The choice of using env var's Im not fussed with, it could be solved
with / without IMHO, env vars have their own advantages of course.
But take care to avoid Env var lookups per redraw as we had in the
game engine IIRC.

Another issue is quit.blend's cluttering up the temp dir if they get
unique names.
this already happens with the session blend's so I guess doesn't need
to be solved initially but would be good to think of how it could be
managed.

On Tue, May 11, 2010 at 10:16 AM, Matt Ebb <matt at mke3.net> wrote:
> Hi,
>
> My main task this week is to get the issue of installation and file paths under control, hopefully before the beta release, and definitely before the stable release.
>
> Several differing proposals have been made for this in the past, with no clear consensus and agreement, and there are several messy competing systems in Blender's source right now which need to be cleaned. I've read over the various proposals, and tried to amalgamate something that unifies the ideas and meets all the requirements in each.
>
> The focus here is on a short-term, achievable target of clearing up installation and finding resource file paths. Other things such as UNC paths, unicode/international file access, wrapping FILE pointers etc can be considered separate issues, and looked at after a stable release - this is specifically regarding retrieving system/user data paths.
>
> Anyway, my proposal is here:
>
> http://wiki.blender.org/index.php/Dev:2.5/Source/Installation/Proposal
>
> I hope that this enough to quickly agree on and get moving.
>
> cheers,
>
> Matt
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>



-- 
- Campbell