<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:tahoma,new york,times,serif;font-size:12pt">+ 1<br><br>but in addition, the location of the .blender Folder (for custom icon sets, etc.) should also be in the same location.<br><br>cheers<br><span style="font-family: garamond,new york,times,serif;"></span><div><br></div><div style="font-family: tahoma,new york,times,serif; font-size: 12pt;"><br><div style="font-family: verdana,helvetica,sans-serif; font-size: 10pt;"><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Matt Ebb <matt@mke3.net><br><b><span style="font-weight: bold;">To:</span></b> Bf-taskforce25@blender.org<br><b><span style="font-weight: bold;">Sent:</span></b> Tuesday, May 5, 2009 9:19:47 PM<br><b><span style="font-weight: bold;">Subject:</span></b> [Bf-taskforce25] Proposal: .B.blend -> startup.blend<br></font><br>
Hi,<br><br>I noticed the new .b25.blend addition, which got me thinking a bit.<br><br>At winter camp, we agreed that we should move to better folder<br>locations for resource files, especially on OSX. For example, moving<br>the contents of the .blender folder that's hidden inside the<br>application bundle to /Users/UserName/Application Data/blender/ where<br>it's easily accessible, and as the platform standards dictate.<br><br>We should apply the same logic to the .B.blend file. For such an<br>important file, it's terribly inaccessible and difficult to edit. It's<br>necessary to be able to access this file for various reasons<br>including:<br>* For testing/debugging, being able to rename your existing config and<br>test by making a clean file, and renaming back after testing<br>* As an artist, packing up your config to take to a new workstation<br>* Switching between configs for different users on the same workstation<br><br>This is currently very
difficult:<br>* On Mac OS X, files beginning with . are hidden by the finder, so<br>even if they were to by chance look in the non-standard location where<br>it's kept, most users wouldn't even know it exists.<br>* On Windows, dot files are visible in Explorer, but difficult to<br>manage. It's impossible to rename a file to .something.ext, it<br>requires characters before the first dot.<br>* Even on many linux systems, dot files are hidden by default in the<br>file browser.<br><br>A good first step would be to just rename the .B.blend file to startup.blend.<br><br>Not only would it be vastly easier to work with and manipulate on the<br>various systems that Blender supports, but it also gives users a much<br>better indication about the file's purpose. Then, when (as we also<br>talked about at winter camp [1]) we separate this file out to one<br>containing startup UI settings, and one containing preferences, we can<br>give them logical names like
startup.blend and preferences.blend<br><br>So.. comments? :)<br><br>cheers,<br><br>Matt<br><br><br><span>[1] <a target="_blank" href="http://wiki.blender.org/index.php/BlenderDev/Blender2.5/WinterCamp/EditorReviews">http://wiki.blender.org/index.php/BlenderDev/Blender2.5/WinterCamp/EditorReviews</a></span><br>_______________________________________________<br>Bf-taskforce25 mailing list<br><a ymailto="mailto:Bf-taskforce25@blender.org" href="mailto:Bf-taskforce25@blender.org">Bf-taskforce25@blender.org</a><br><span><a target="_blank" href="http://lists.blender.org/mailman/listinfo/bf-taskforce25">http://lists.blender.org/mailman/listinfo/bf-taskforce25</a></span><br></div></div></div><br>
</body></html>