IDE team tool

[Shingetsu Kurai]

Hey all. Right now I got to a point where I start doing things in team XD, lotsa work. (in fact made a group in which the team is etc...) so my question is, is there an IDE that allows people to work on a project simultaneously? Something like Google Docs in documents. My thoughts were something with the cloud, or some special IDE.
Anyone got any ideas?

(btw "Make it yourself won't help, because that would take a load of time and work, and since I don't have an IDE to coordinate work with the team it might take forever XD)

Last note, it's preferred the IDE to be generic: C, C++, C#, Java etc. But if it's only C++, C# or Java I'll understand XD (those are the 3 languages I adore XD)

[laserlight]

I do not know of any such IDE, but a general approach is:

• Have a team plan: divide the work among developers or sub-teams.
• The developers/sub-teams work concurrently on their area of responsibility.
• Integrate (merge and resolve any conflicts).

A version control tool can help.

[manasij7479]

Hey all. Right now I got to a point where I start doing things in team XD, lotsa work. (in fact made a group in which the team is etc...) so my question is, is there an IDE that allows people to work on a project simultaneously? Something like Google Docs in documents. My thoughts were something with the cloud, or some special IDE.
Anyone got any ideas?

(btw "Make it yourself won't help, because that would take a load of time and work, and since I don't have an IDE to coordinate work with the team it might take forever XD)

Last note, it's preferred the IDE to be generic: C, C++, C#, Java etc. But if it's only C++, C# or Java I'll understand XD (those are the 3 languages I adore XD)

Eclipse has a separate interface ..for that.. called Team Sync ...or something similar....(not sure of the name).
I think that is almost exactly what you need.

[MK27]

Eclipse has a separate interface ..for that.. called Team Sync ...or something similar....(not sure of the name).
I think that is almost exactly what you need.

That's kind of awful tho, then you have to dictate to everyone what IDE to use.

I'd much rather just use a version control system, like laserlight recommended. You have to dictate which one that is going to be too, but probably most people would rather learn to use a new VCS (esp. if you can provide a few simple instructions WRT the project at hand) than a whole new programming environment.

A VCS will probably also give you a lot more flexibility WRT to branching, etc. This way, you could have people trying different ideas simultaneously, possibly in sub-teams, compare and contrast the results, and decide which branch to merge into the project's main "trunk". I think that is a pretty standard, widely used development model.

[manasij7479]

That's kind of awful tho, then you have to dictate to everyone what IDE to use.

That isn't necessarily true..
It just provides a good gui interface for the version control system of your choice and some more control over diff-patching .
So.. you can use it without breaking compatibillity with the rest of the team... whatever they may use.

[laserlight]

It just provides a good gui interface for the version control system of your choice and some more control over diff-patching .
So.. you can use it without breaking compatibillity with the rest of the team... whatever they may use.

If that is so, then this feature of Eclipse does not have anything to do with "something like Google Docs in documents" for code. Rather, it is no different from many other IDEs.

[manasij7479]

If that is so, then this feature of Eclipse does not have anything to do with "something like Google Docs in documents" for code. Rather, it is no different from many other IDEs.

Well.. you have a central repo ....(or clones ) and this perspective allows you to track others' changes, make todo lists, comments, documentations ....etc (remaining within the area of compatibility with other environments)...
I think that comes close to what Google Docs has.

Outside that ... where MK27's 'force to use' agrument becomes valid; Eclipse specific API's come into play ..(They actually advertise that feature.... but I am still not able to comprehend what this 'API' is useful for :S )

[laserlight]

Well.. you have a central repo ....(or clones ) and this perspective allows you to track others' changes, make todo lists, comments, documentations ....etc (remaining within the area of compatibility with other environments)...
I think that comes close to what Google Docs has.

Ah. Maybe you are unaware of this, but a primary feature of Google Docs is the concurrent editing of documents such that changes appear in real time. Is this real time aspect of code changing in your editor as another developer is editing the same file what you are talking about? Otherwise, what you have mentioned is really just normal version control using merge rather than file locking, in which case Eclipse is not special at all.

If you are talking about such real time concurrent editing, then it follows that the IDE to use must be dictated, otherwise the benefit of this feature will be lost, even if there is no break in compatibility with other environments.

[bernt]

There is a collaborative editing plugin for eclipse here. There wouldn't be any compatibility with other environments but the OP did ask for an IDE so I'll throw it out there.

[manasij7479]

Ah. Maybe you are unaware of this, but a primary feature of Google Docs is the concurrent editing of documents such that changes appear in real time. Is this real time aspect of code changing in your editor as another developer is editing the same file what you are talking about? Otherwise, what you have mentioned is really just normal version control using merge rather than file locking, in which case Eclipse is not special at all.

Wouldn't that kind of "real time" get messy for code(as oppossed to docs) ?
I mean, one would write half a function, and it gets saved ... and considering it compiles; it will be a disaster, if another grabs a snapshot of the repo in the meantime.
There is a reason write->compile->test->(resolve if something goes wrong )->commit is preferred in Version Control systems.

[laserlight]

Wouldn't that kind of "real time" get messy for code(as oppossed to docs) ?

Yes, I think it would, hence my suggestions in post #2. In fact, I find that it gets messy for docs too.

[Shingetsu Kurai]

Thanks all. For docs it actually isn't messy, but I see your point on that. I'll probably use the Eclipse team sync and get organized XD.