Using Subversion
 

The subversion server is up for public checkout at http://svn.linuxpowered.com/openeq
You can get Subversion at http://subversion.tigris.org/ - to check out our beautiful and possibly broken sources, those of you using a *nix system can use the following command:
Windows users can find win32 binaries of subversion, or there are several clients out including TortoiseSVN which supports SVN as a windows shell extension, TortoiseSVN can be found at http://tortoisesvn.tigris.org/

A small guide for those intending to develop follows, targeted for those using the native svn client.

Checking out the sources
Once you have already checked out sources, you only need to update the source.
from the working directory(openeq/) should do the trick. However, note that if any files were changed, subversion will NOT overwrite them. After updating, you need to revert back(or forwards, as the case may be) to the working copy using svn revert:
Multiple files may be reverted, and to revert the entire tree, change to the working directory and
This will revert the entire tree to whatever version is currently loaded.

Making changes
We're always glad to get any help we can, and to get your code to us, you must submit patches. Simply edit files in place, and whenever you are done, submit a patch. Change directory to the working dir(openeq/) and do the following:
Foobar should probably be replaced with something pertaining to the purpose of your patch :). Then email the patch or post it in the development/bugs/feature request forum(as appropriate) and we'll get down to testing it. To apply a patch you feel like testing, make sure you're reverted back to the current revision, change to the working directory, and do the following:
The < is necessary because patch will not read files directly, it must be fed them through standard in.
If you find yourself with a totally messed up file and can't seem to fix it, you can revert to the working revision at any time using `svn revert`.

Coding guidelines
Certain guidelines must be followed while coding both the C++ and Python portions of OpenEQ to ensure that the project looks as neat and consistent as possible. Please follow these guidelines at all times:
C++ Development: http://home.archshadow.com/~daeken/o...elines_cpp.txt
Python Development: http://home.archshadow.com/~daeken/o...nes_python.txt
Thank you for keeping OpenEQ clean!