[DESIGNDISCUSSION] Working folder
Posted: Fri Mar 02, 2007 5:33 am
In alignment with my new, more open policy, I have a design change I am planning but would like input on. This will happen alot, though I may move it to the mailing list later so it will be open to a broader audience.
Basically, instead of the RF style, where you have one RF installation per game, you would install RF2 into a separate folder, then games would be like "project folders". To run a game, you would just make a shortcut to RF2 with the working directory the game folder. When ready to distribute your game, you would simply unzip a "RF2 minimal distribution" zip file into your game folder, which would put RF2.exe and the appropriate necessary files to run it into your game folder, thus making it self-contained and ready for distribution to those who do not have RF2 installed.
My take on it:
Advantages:
No need to have multiple RF2 installations.
No need to update many installations when an update comes out.
If developing RF2 itself, you can compile and not have to worry about copying the EXE into multiple folders.
More strict compliance with Linux's GNU Autotools, which like to install programs into the OS's bin folder.
Disadvantages:
Have to make a shortcut to run your game.
Have to take an extra step to distribute your game (though with the other method you would still need to strip development files, tools, etc. from the folder or get a program to do it for you).
Ideas, comments?
Basically, instead of the RF style, where you have one RF installation per game, you would install RF2 into a separate folder, then games would be like "project folders". To run a game, you would just make a shortcut to RF2 with the working directory the game folder. When ready to distribute your game, you would simply unzip a "RF2 minimal distribution" zip file into your game folder, which would put RF2.exe and the appropriate necessary files to run it into your game folder, thus making it self-contained and ready for distribution to those who do not have RF2 installed.
My take on it:
Advantages:
No need to have multiple RF2 installations.
No need to update many installations when an update comes out.
If developing RF2 itself, you can compile and not have to worry about copying the EXE into multiple folders.
More strict compliance with Linux's GNU Autotools, which like to install programs into the OS's bin folder.
Disadvantages:
Have to make a shortcut to run your game.
Have to take an extra step to distribute your game (though with the other method you would still need to strip development files, tools, etc. from the folder or get a program to do it for you).
Ideas, comments?