Since we want our installer to work similar to our zip distribution, it means the default location we pick should be user-writable. Normally programs would install to %PROGRAMFILES%\Blender Foundation\Blender, but this is an off-limits area for normal users. It is pretty common that users don”t have administrative rights (and probably for good reason). Our latest installer will run with current user privileges, and as such has some obvious problems: no write access to places where the user has no permissions to write to. blend files and set up the scripts directory as wanted by the user. Ultimately it should be similar to what unzipping the packed archive does, with the addition of adding the links, registering the Blender executable as default program for. This should obviously be fixed, but currently we don”t have a NSIS guru amongst our developers who could properly address all the issues with the installer. Now, we’ve had our installer for a pretty long time, but pretty often we get reports in our bug tracker, that are related to our installer in some way. I”ll readily admit that this is probably a way that should be considered fairly “hardcore”, since Windows users will be wanting their links in the start menu and/or on the Desktop for free.
In my personal opinion the easiest and nicest way is always to unzip any software distribution and run it from that fresh directory.
Making Blender usage easy to start is something I always try to look at.
0 kommentar(er)
