GUI Application

Jun 25, 2007 at 5:01 AM
Is there a GUI application to do the functionality of this program? If not can that be added as a feature request?
Coordinator
Jun 25, 2007 at 6:31 AM
Right now, it's a command line client with selected GUI bits.

You should open a new feature request on the issue tracker. Also, what kind of GUI client are we talking about? Something like WinCVS (stand-alone? Windows only or cross-platform?)? TortoiseSVN (shell-integration)? AnkSVN (Visual Studio integration)?
Jun 26, 2007 at 9:58 AM
My vote would be for something like TortoiseSVN (Shell-integration). That way we can check in files that we aren't necessarily editing in Visual Studio.

BradWilson wrote:
Right now, it's a command line client with selected GUI bits.

You should open a new feature request on the issue tracker. Also, what kind of GUI client are we talking about? Something like WinCVS (stand-alone? Windows only or cross-platform?)? TortoiseSVN (shell-integration)? AnkSVN (Visual Studio integration)?

Jul 25, 2007 at 7:04 PM
Probably most GUI's would not be compatible with the model for checkout which is "edit-merge-commit". Visual SourceSafe for example is "checkout-edit-checkin". Thats' why I would also suggest TortoiseSVN. We use it as a corporate wide source control client and it works great.

But you need to think this through. This isn't just a client side issue. It's the other end that would have to be programmed and TortoiseSVN talks to Subversion which you need to install. What is the present server side software, and could it be combined with Subversion in a coordinated checkout for existing users? Sounds like an involved task, that is more easily handled by just converting to SubVersion. But then, what is the chance that enough momentum could develop so that this whole site and all the projects would do that simultaneously? Don't hold your breath..., it's a darn big project, with a lot of people required to agree with it, and there are security issues.

What is more possible is 3 tier approach, the first two which you control. Install Subversion on a server and have jobs that use the Subversion command line interface and the Codeplex client both running as you - Google "encrypted dos batch files"). They could send what you enter into a TAG branch back to the CodePlex site. Your TRUNK could be your daily changes, and your TAG your commit changes. (If you are a TortoiseSVN/Subversion user you would know what this meant).

There are probably similar schemes that would work just as well, including using a "checkout-edit-checkin" client to a middle tier. Most of them have command line interfaces for retrieving the updates from the middle tier.

Coordinator
Jul 30, 2007 at 11:47 PM
Edited Jul 30, 2007 at 11:48 PM
If you want to use TortoiseSVN with CodePlex then take a look at SvnBridge. It's still in Alpha but it works against any CodePlex project.