|
Post by turbov21 on Mar 13, 2008 13:47:01 GMT -5
Would it be possible to have a checkbox on the installation that lets me choose not to install the sample applications? I may the in the minority here -- and if so, please ignore me -- but the first thing I do after installing an updated version of RBP is delete the samples, for two reasons:
1. I find the wiki is the best form of tutorial/example sheet out there, and
2. I already have my own example projects that I'm more familiar with.
For an initial installation, I think the included examples are a must, but for me, someone who's used RBP and is just upgrading, they tend to make installation all the more tedious. I have to be careful not to erase my "public" directory when clearing them out, and before that, I have to make sure I don't confuse myself by copying my projects into the new installation directory before getting rid of the examples.
Again, if I'm the only one who does this, then please ignore me. However, as RBP matures and we get more releases, I can see this being kind of a problem for people with their own large, established libraries. Thank you.
|
|
|
Post by mikeukmid on Mar 13, 2008 14:04:04 GMT -5
There is a 'Projects root' option in preferences which may be of some help. You could you move your projects to another folder ouside of rbp and just delete the sample apps when a new version is installed and edit the new prefs accordingly.
Maybe Carl would introduce a 'Browse for projects' option if you ask nicely. ;D
|
|
|
Post by turbov21 on Mar 13, 2008 22:09:43 GMT -5
There is a 'Projects root' option in preferences which may be of some help. You could you move your projects to another folder ouside of rbp and just delete the sample apps when a new version is installed and edit the new prefs accordingly. My only qualm with that is that if I build up a large library, moving my files to another directory might break a lot of code that depends on specific paths, and installing new versions of the executable in a new directory each time means I've still got to move my "public" directory (or the files within) if I want to get use out of the updated manual. It's not a huge hurdle to overcome -- which I want to keep stressing -- it just strikes me as being an easily removable hurdle if there was a way to install new files without the examples. Old versions would be over-written, but your stuff would be left intact.
|
|
|
Post by StefanPendl on Mar 14, 2008 3:02:00 GMT -5
My only qualm with that is that if I build up a large library, moving my files to another directory might break a lot of code that depends on specific paths, and installing new versions of the executable in a new directory each time means I've still got to move my "public" directory (or the files within) if I want to get use out of the updated manual. I would never use absolute paths, your programs will always run from the installation root, you can check this with the DefaultDir$ variable or the FILES command.
|
|