Hey to all the developers,
I've added a new "feature" to the community for development. It's a Subversion server.
Subversion (SVN) is sorta like the CVS system for version control. It's a lot nicer though. (Read on to know more).
If you don't know how version control systems work, or haven't used SVN before, read chapters 2 and 3 of this
manual located here.
I figured it would be useful for sharing and working on various code together, such as the SDK headers, the Internal Info text files, as well as the OPU version of IBStore, which is running at
http://forum.outpostuniverse.net/test/The system isn't fully working yet, namely, no one is able to commit changes yet. (This I plan on dealing with as soon as I have a system to allow individual access control for different projects in the repository, which should happen within the week.) However, you can checkout the current sources in the repository.
To get started with it, download Subversion from
here. This is the bare minimum you'll need to checkout the latest sources.
You can then checkout the different trees by running the following command, for example to checkout the IBStore source, change directory to where you want to save the source tree, then run the command:
svn checkout svn://outpostuniverse.net/repos/IBStore3.0-OPU
Also, have a look at
http://outpostuniverse.net/~svnopu/listing.php (It should be
http://svn.outpostuniverse.net/ but DNS is failing us, as usual). This is the web interface to SVN, you can examine the repository this way.
You may wish to install a GUI tool to make accessing SVN a lot easier. This is no problem. You can download TortoiseSVN from
here, which is a shell extension to the SVN client. (You still need to download SVN from up above for this to work)
With TortoiseSVN installed, you can right click where you want to save the source tree, go to SVN Checkout, and enter the repository name for the source tree (as above, for IBStore it is svn://outpostuniverse.net/repos/IBStore3.0-OPU )
As this is still somewhat "unfinished" for us, it's not to be 'released' to the public at this time. Later I may implement access controls to prevent the usual public from checking out certain sources.
If you had no clue what all is meant by repositories and such, I urge you to go read Ch2 and 3 of that manual link posted above.
Again, I hope this is a good addition for developers and will enable us to work together on projects more easily.
-- op2hacker