+- Hot Door CORE Forum (http://hotdoorcore.com/forum)
+-- Forum: All forums (http://hotdoorcore.com/forum/forumdisplay.php?fid=1)
+--- Forum: Getting started (http://hotdoorcore.com/forum/forumdisplay.php?fid=6)
+--- Thread: getting started (really, from square one) (/showthread.php?tid=35)
getting started (really, from square one) - Rick Johnson - 10-14-2014
At the risk of being ejected from this forum for being such a noob (again), I have to ask to get a grasp on this. Much has changed since I once churned out plugins for AI CS3, and I'm only an illustrator, not a professional programmer as most others here are, so little of this is intuitively obvious to me.
I would presume that the contents of the Headers, Binaries, and Resources folders would remain untouched by me, and could therefore be shared by different projects, so in the "Getting Started" page of the CORE site, is "2. Create a Libraries folder (anywhere is fine) and copy hdi_core into it" a one-time step, or to be repeated with each project?
Thanks in advance -- Rick
RE: getting started (really, from square one) - garrett - 10-14-2014
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.