Let's Make Robots!

Source control

saves versions of files during dev process of code

Source control is an important part of development, whether it be for a website, a major application, or robot instructions/thoughts because you never know what you might have accidently made a chang that cauesed everything to go foobar on you.

Source control essentually allows to organize projects, and save files over and over again while saving the information on what was edited(much more but this is the simplified summary). This way you don't have to keep naming the file robotjumpthroughhoops001 ,002,003,etc . This doesn't happen automaticlaly though, so you will need to make sure that you do updates on a regular basis to your repository(location where file edits are saved to).   Once you get used to this though, you may one day find out why this is such a great and useful tool to have in your robot buiding endevors, ie the foobar comment above.

There are several tools that you'll be able to use with the source control manager, one of the key ones is diff, which allows you to view the (wait for it...)differences in the two file versions plus any notes that you might have added. You did add notes to your updated version, right???

I recommand using subversion(svn for short). It can be run on the major os's(windows/linux/mac/etc) and has a large following, so finding info, help and tools shouldn't be an issue.

I also recommend playing around with the app first to get familiar with it .

 here are some links that may also help in understanding and using version control tools


 (the site above is pretty cool in general, and I recommend exploring it!)


 As a side, this tool may not be for everyone, as it took me a while to get used to it, but since doing so, I've used it for qute a few other projects. This is a real world tool as well used in major industries(technology) and knowing how to use this tool could one day help to get a job somewhere!

 Hope you all find this useful!!

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

I would reccomend a thumbs up to anyone wanting to use SVN, the commands are rather intuitive and fairly easy even from a command line.  If you are the only one using the repository, then it gets even simpler.  Also, if you might use two different computers, SVN helps keep everything up-to-date betwee them, assuming you commit or send your updates.

Personally, I use a PC running linux and a laptop running WinXP.  On Linux box I use the command line SVN and the KDE Addin, kdesvn (currently only KDE3.5) and on the XP box, I use TortoiseSVN, which gives a nice right-click inteface to the working copy.  KDEsvn hooks into Konqueror (the file manager) and can be invoked from it to provide a nice GUI.  

 However, the command line is rather easy as well. 

svn update will get any changes you made from another computer or user.  This will update the hidden working copy.  This will not change your current changes, but will giv you a new base to work from.

svn checkin will add your changes to the repository for anyone else to work from.

If you are interested in learning all you would ever need to, here is a link to an online book:


"See a need; Fill a need!" - Bigweld, Robots