[zehawk]

This isn't neccesarily a code related question, but I was wondering if there was a way I could code a project with a team of two over a network, so like, when I change the code, the partners see it and we can code a project at the same time. I'm not sure if there is a FREE IDE or program that has this functionality. How do big industries do it? Surely, it's not like one user codes at a time, the whole team codes a project at the same time, I would think.

I have a few things I need:
-The team must be able to code the project, seeing the changes we made at the time we made them.
-Two or more (Most likely no more than four) people need to be able to work on a project.
-I want to be able to compile using gcc
-I have a library on my drive, if I also have the project on my drive, the project should be able to hook up to the library while my team work on the project over a network.
-My editor of choice is Code::Blocks
-If a program does exist that can help me with this, there should be documentation so I can get set up.

YES I looked it up on google. NO I couldn't find anything I was looking for. Can anyone tell me what program their business uses for this? I'm just a small indie game team that has two people, and recruiting a few more. We already settled we can chat through Skype, while we work on the project. Thanks in advance!

[fromTheSprawl]

You should most definitely use SVN or Git. Your changes would show up on their side and vice versa and you can work concurrently.

[Oler1s]

Quote

but I was wondering if there was a way I could code a project with a team of two over a network, so like, when I change the code, the partners see it and we can code a project at the same time.

Collaborative editor.

Quote

How do big industries do it? Surely, it's not like one user codes at a time, the whole team codes a project at the same time, I would think.

Right, but team members are not working on the exact same bit of code. Everyone is working on a different aspect of the code, and changes are merged through a version control system.

if you don't know what a version control system is, please learn about it now.

Anyway, I think you need to rethink how you're going to collaborate. Why does your team need to see each other changes in realtime? Multiple people are not going to be independently working on a portion of the code.

[CTphpnwb]

I work with another person (mostly via the web) on the same projects, and the way that works best for us is that we both make changes to separate copies of the code and then compare our results. If we match then we have a high degree of confidence that our code is doing what we want it to do. We then decide whose code we "like" better and use that to create the version of the code that we will use as a baseline for new changes.

At first glance this may seem slow or wasteful. If the project were simple it would be, but for complicated projects it cuts debugging time dramatically.

This post has been edited by CTphpnwb: 12 September 2012 - 07:11 PM

[zehawk]

Mostly, we would be working on different parts of the code. For instance, because we are making an indie game, I could work on some AI while a friend works on the environment. However, it needs to be real time because if I make a change to the function void foo()so it is now void foo(int something), we can't just compare code because he may be using the old version of foo and we would have to fix everything. I don't know about version control systems, they sound like they over complicate what I want to do. Surely there is a simple way to network so we can code at the same time? I would think there'd be a simple way by now.

[Oler1s]

Quote

However, it needs to be real time

No, it doesn't. If you require real time feedback on changes, it's a sign your development process is broken.

Quote

because if I make a change to the function void foo()so it is now void foo(int something)

Then you are responsible for the merge. What, you make the change and other people are responsible for fixing it??

Quote

we can't just compare code because he may be using the old version of foo and we would have to fix everything

Well, yes? If you change a signature of one of your functions, someone has to modify all existing code.

Quote

I don't know about version control systems, they sound like they over complicate what I want to do.

Then learn the hard way that you need a version control system.

Quote

Surely there is a simple way to network so we can code at the same time

You don't need to code at the same time.

Think about this. You make a change. Who is responsible for making sure the change doesn't break the program.

Your team members? No. You are responsible for that. What if a bunch of other code has to be fixed. You are responsible for that.

So you periodically sync up code through version control and do the merging work as needed.

[zehawk]

I'm sorry for my misunderstandings, I'm simply a beginner who wants to work with my team in real time so we can get the job done faster. I'm looking into GIT right now, and hope I can learn how to use it. I thought it should be in Real Time because I personally do not want to go through sending each other files over email and doing things like that, as I'm sure it isn't very effecient. That is why I was hoping I could work with my team over real time. Sorry I'm just a beginner.

[Oler1s]

Quote

I thought it should be in Real Time because I personally do not want to go through sending each other files over email and doing things like that

Again, which is why you should be using a version control system to merge changes, or at worst case, send patches over email if needed.

Look, I pointed you at the term collaborative editor. You're welcome to try it out. You'll just find out really fast that it's not how work gets done. And then you'll be back here, asking what to do, which is exactly what we've explained.

[Skydiver]

If you work best with a partner, look at Pair Programming which is one of aspects of Xtreme Programming:
http://www.extremepr...rules/pair.html
http://en.wikipedia....air_programming

I've done it a couple of times and found it highly effective. Yes, to an employer, it sounds like a waste of money to pay two people to be outputting only code at the rate of one person, but the benefits are on the backend: automatic peer review happens, automatic crosstraining, and if somebody is out sick or unavailable, you have coverage with somebody familiar with the code.

But as noted in the rules of pair programming, only one person is in control of the keyboard at a time. No simultaneous edits are happening.

This post has been edited by Skydiver: 12 September 2012 - 07:43 PM

[Skydiver]

And a good version control system is key. The word "good" is relative. Some developers prize easy to learn, others prize bulletproof, others want being able to go offline, etc.

[zehawk]

Perhaps, but most of the time we are not really close, we are at our own homes. Perhaps I could just use teamviewer then... I'm looking into using git, but all your answers were helpful to a degree. I'm looking up the Version Control System(git is one of them) and I can perhaps get it up soon. Thanks for the replies guys!

[CTphpnwb]

You can use something like Dropbox and manually version control (keep a log file and date your versions) if there are just a few of you. Is it ideal? No, but it can work.

[JackOfAllTrades]

Relevant blog post that just came over the transom

[jjl]

Quote

I don't know about version control systems, they sound like they over complicate what I want to do.

For God's sake, pick a version control system and read about it for an hour and learn the basics.

Pick one:

http://git-scm.com (my favorite)
http://subversion.apache.org (this one sucks)
http://www.nongnu.org/cvs/ (oldschool)
http://mercurial.selenic.com/wiki/ (small learning curve)

This post has been edited by jjl: 15 September 2012 - 05:20 PM

[fromTheSprawl]

SVN sucks? Hm. I really have to read up on Git.