SVN and the Torque Toolbox, I'm totally confused.
by James Brad Barnette · in Torque 3D Professional · 07/02/2009 (4:23 pm) · 4 replies
Granted I do not have a lot of experience with SVN so I may be way off here "I hope I am" so please correct me if I'm wrong in any aspect of this. I'm trying to figure out how to make use if this Torque toolbox widget in a environment where SVN is in use and I cannot for the life of me figure out how I'm supposed to do this. Currently each dev has Torque3D installed locally. Just the standard install nothing was changed. But when new projects are created via the Torque Toolbox. They are put in a sub folder of the install called MyProjects. Now from what I have seen or have been able to figure out rather is there is none of the engine source contained in the project folders. Just the Visual Studio project files and solution files.
So is the torque tool box just not to be used then. Basically I want source control on the whole project and to be able to use the toque toolbox to build my packages and then ignore source art and what not.
Is there someway I can have the torque tool and SVN?
do I not have to have the branches, tags, trunk folder under torque and above Torque 3D 2009 Beta 3?
Someone please tell me I'm just doing it wrong.
So is the torque tool box just not to be used then. Basically I want source control on the whole project and to be able to use the toque toolbox to build my packages and then ignore source art and what not.
Is there someway I can have the torque tool and SVN?
do I not have to have the branches, tags, trunk folder under torque and above Torque 3D 2009 Beta 3?
Someone please tell me I'm just doing it wrong.
About the author
#2
Simply set up VC from within the toplevel folder. If you don't want to check in everything there, then do it selectively or prune the directory hierarchy first (FPS Kit and demos are a reasonable thing to not include here).
In your project folder, you can select what you want and what you don't want in VC, e.g. if you want to exclude source art. Again, I think it's best to check it in along with the rest and have the complete project under VC, especially everything that is a "source" of some sort.
07/02/2009 (11:52 pm)
Simply set up VC from within the toplevel folder. If you don't want to check in everything there, then do it selectively or prune the directory hierarchy first (FPS Kit and demos are a reasonable thing to not include here).
In your project folder, you can select what you want and what you don't want in VC, e.g. if you want to exclude source art. Again, I think it's best to check it in along with the rest and have the complete project under VC, especially everything that is a "source" of some sort.
#3
Personally, I just copied out "Engine", "My Projects" and "Tools" (to make generateProjects.bat work) into my trunk and I'm not using the toolbox until it becomes capable of listing projects outside the T3D install folder.
07/03/2009 (6:55 am)
You can either add the entire T3D folder into a TRUNK, if you want to be able to update the toolbox for everyone (T3D doesn't care about the folder where it is), or just add the "engine" (shared by all projects) and "my projects" folder (or just your project folder) into a TRUNK and have the team checkout that into their T3D folders.Personally, I just copied out "Engine", "My Projects" and "Tools" (to make generateProjects.bat work) into my trunk and I'm not using the toolbox until it becomes capable of listing projects outside the T3D install folder.
#4
07/03/2009 (9:29 pm)
yeah It would be nice to know what its final feature set will be. 
Associate Jaimi McEntire
King of Flapjacks