10-14-2014, 06:07 PM
No ejections! Ask away.
The entirety of the downloaded CORE library should remain untouched, except perhaps for the Samples folder as you might want to experiment with the plugins therein.
Whether you place CORE in a single/standard location on your machine or copy it for each individual plugin you create is really up to you. Keeping it in one place is less overhead and less disk space, but less "future-proof". Let's say that you create project A and build it against CORE version X and release it to the world. Months later, you want to create project B because CORE version Y has come out and has some new feature you want to take advantage of. So you download CORE version Y and build project B against it and release it to the world as well. Now, some nasty bug report has come in for project A and you want to fix it ASAP...
If you had kept CORE in one location on your machine, then project A might not compile anymore because you replaced CORE version X with version Y when you were making project B. This problem could have been avoided and you could have released a fix for project A faster if you maintained a separate copy of CORE version X for project A and a separate copy of CORE version Y for project B. This way, you can be sure that project A will always compile against CORE until you are good and ready for updating to CORE version Y.
The entirety of the downloaded CORE library should remain untouched, except perhaps for the Samples folder as you might want to experiment with the plugins therein.
Whether you place CORE in a single/standard location on your machine or copy it for each individual plugin you create is really up to you. Keeping it in one place is less overhead and less disk space, but less "future-proof". Let's say that you create project A and build it against CORE version X and release it to the world. Months later, you want to create project B because CORE version Y has come out and has some new feature you want to take advantage of. So you download CORE version Y and build project B against it and release it to the world as well. Now, some nasty bug report has come in for project A and you want to fix it ASAP...
If you had kept CORE in one location on your machine, then project A might not compile anymore because you replaced CORE version X with version Y when you were making project B. This problem could have been avoided and you could have released a fix for project A faster if you maintained a separate copy of CORE version X for project A and a separate copy of CORE version Y for project B. This way, you can be sure that project A will always compile against CORE until you are good and ready for updating to CORE version Y.