Game Development Community

T3D Toolbox, New Project Generation, and Subversion

by Jason Parker · in Torque 3D Professional · 03/16/2010 (4:29 pm) · 3 replies

I'm wondering if anyone here is using Subversion with their projects generated by the T3D toolbox, and are also using the toolbox.

I like using the toolbox, I like the convenience of the project generation but I don't really feel the layout of the project folder lends itself to use in source control software.

I'm mainly looking for tips on using the T3D toolbox with Subversion as I am setting up a project with a goal of a basic playable demo to test out some systems by mid-summer. This is not a discussion about whether or not I should use X or Y over Subversion.

#1
03/17/2010 (1:10 pm)
You could just checkout your SVN repository to the T3D project folder.

If you don't like storing your source control there you can use Junction on Windows or symbolic links on OSX to link a folder in the T3D project folder to the external folder where your repository lives.

The only thing needed for your project to show up in the T3D toolbox is the built executable for your game needs to be in the root directory for your project (i.e. C:TorqueTorque 3D 2009 Pro 1.1 Beta 1My ProjectsMyProjectMyProject.exe), or if you junction/link this directory, the junctioned folder needs to have the exe.

Since the install directory of T3D changes when the version changes (i.e. C:TorqueTorque 3D 2009 Pro 1.1 Beta 1) I use batch files in Windows to find this path and setup my junction for me so that I only need to update my batch files and not move my whole repository.

I hope this is what you were asking, I should probably make a resource with my batch files so that it makes a little more sense.

EDIT: I forgot to mention, you need to break the Junction before uninstalling T3D (like when a new version is released) because the T3D uninstaller deletes everything in the "My Projects" folder (which translates into a deleted repository)!
#2
03/18/2010 (6:36 pm)
Yeah, already familiar with junctions. Did that to setup a 'My Documents' like folder on my desktop for accessing the script source to another project of mine. Also familiar with the dangers of deleting when using junctions as it was in the document I read.

What I'm considering doing is three actual projects in Subversion but I'm not sure it's a great idea since they'd be a bit nested. One for the art folder, one for the scripts folder, and one for the game folder they're both in. Not entirely sure that's possible as this'll be my first time with Subversion. A fourth for project-only source files would also be setup, but since I'm the only programmer it'd only be for piece of mind in case I screw up and need to revert, or a hard drive dies.

One thing I'm still trying to learn is how to do user permissions. art and scripts would be available to the whole team, but the tools portion of the game folder would have to be filtered to only T3D license holders on the team. I'm sure I'll get it all going one way or another.

Thanks.
#3
05/27/2010 (4:24 pm)
Figured I'll update this thread before I take it off my watch list.

For any Subversion newbies, the key to using Subversion with your game project folder is the Externals feature. If you want your artists to have access to only update assets in the art folder, set it up as it's own repository. Then setup the game folder, minus art, as it's own repository and set the art folder as a required external with proper path. Same goes with any other section. Also remember to exclude the tools folder if you want non-license owners to be able to check out the game from the repository.