Jump to content
  • entries
    1212
  • comments
    1738
  • views
    1145009

Cool technology of the day. . .

Sign in to follow this  
johnhattan

120 views

OK, it's nothing new, but the client-server version of CVS is very cool. I'd seen some public CVS projects out on the web, but I'd never really had the chance to work with one up close. After looking at the wxWindows mailing list, it was apparent that there were some interesting bug-fixes and enhancements that were available, but not on the official distributions.

For the uninitiated, CVS is a client-server version control system that works over the Internet. The server is the source code repository, and clients can connect to the repository, download the latest code, and upload the changes. Like most version control systems, it's based on a check-out/check-in mechanism which helps prevent lost updates. It also has the ability to allow anonymous logins for read-only access. This allows me to connect whenever I want to download whatever files have been updated since the last time the author made an update.

Maybe it's just me, but I think that an embedded version of the CVS client would make a cool software distribution mechanism. It could work similarly to the Windows Update Wizard, checking the version numbers of your windows components and updating them as necessary. If the CVS client could be put into a common DLL, companies could put their latest updates on CVS servers, and your app could automatically check to see if it's the latest version, downloading it if necessary.

Of course, it'd be great for these little multi-person game projects that I keep seeing proposed on the Internet. It'd ensure that everyone was getting the latest sources, and it'd prevent lost updates.

CVS is available at Cyclic Software. There is source code available, and there's a pretty good Windows front-end. It runs on a buncha platforms, which would also make it nice for cross-platform projects.




On the STL front, I'm back to using Microsoft's implementation of the STL, as the third-party implementations crashed the compiler in various ways. I had grand dreams of being able to use a single set of container classes on whatever platform I developed the new games for, but MS's compiler ain't stable and robust enough for it. MS's implementation is good enough, however. If I'm not too ambitious about the template stuff, it should be portable to compiler-specific STL's.
Sign in to follow this  


0 Comments


Recommended Comments

There are no comments to display.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!