TeamWork

So now I'm working on this kind of "over-the-internet" text editor, which will be able to submit real-time code updates so coders can form their own groups and work on their projects with their friends.

TeamWork also offers a variety of other cool stuff like a chat system, a rcon tool and bunch of modifications (plugins that will probably be created by the customers). You will be able to build the project anytime using the MSBuild tool and would be able to see if anything there goes wrong. Languages supported by TW are: C++, C# and VB .NET.

It would be cool if someone helps me on this, I'm fucking with C# right now, but other .NET programmers are welcome in the team.

inb4useless
inb4fuckyou
inb4theresnopointindoingit
inb4douevenlift

WorkTeam

Wonder what I would be doing...
Sending cookies?

You could maybe say something more about what kind of work there's to be done?
-As people will have some idea on what they might be working with

Originally Posted by Jorndel

WorkTeam

Wonder what I would be doing...
Sending cookies?

You could maybe say something more about what kind of work there's to be done?
-As people will have some idea on what they might be working with

No cookies have nothing to do with it. Depending on the help that they can give me, I guess you will have to deal with sockets and HTTP requests. My actual goals are:
- File Transfer service (used to transfer the project files to the users)
- Chat service (a simple one)
- RCON service (full server and client sides are done)
- Subscription service (users must subscribe to a server so they can view the project status, you need the coder key to work with the team of coders)

Again most of them are server-side goals, the client is still under heavy development.

Visual Studio Team Foundation?

SVN commit/update...?

This kind of solutions kinda exist already... Otherwise companies wouldnt be able to work as a team during projects..

For chat, you could probably use IRC. >.<

So.. what're are you asking of us

https://github.com/

Then download your favourite chat client and voila.

The main issue when creating something like this is definitely Version Control. If only one person is working on any particular file at any time then fine, just update the codebase on the server when they're done. However in reality this often won't be the case as people need to work on the same file at the same time and this can lead to really big problems unless proper versioning is implemented and you have merge/discard/etc facilities. This is why Version Control software like GitHub (my favourite) and SVN exist. A lot of really smart people spent a lot of time making these products work as well as they do.

I'm not saying don't bother, but just bear in mind the fact that there are some pretty excellent alternatives already out there.

EDIT: As for integrating a text editor into this, I say that's probably not a great idea. A lot of people like their chosen IDEs the way they are and if your program is explicitly linked through the text editor, it'd be a real pain in the ass to use.

Originally Posted by Jason

https://github.com/ⓘ

Then download your favourite chat client and voila.

The main issue when creating something like this is definitely Version Control. If only one person is working on any particular file at any time then fine, just update the codebase on the server when they're done. However in reality this often won't be the case as people need to work on the same file at the same time and this can lead to really big problems unless proper versioning is implemented and you have merge/discard/etc facilities. This is why Version Control software like GitHub (my favourite) and SVN exist. A lot of really smart people spent a lot of time making these products work as well as they do.

I'm not saying don't bother, but just bear in mind the fact that there are some pretty excellent alternatives already out there.

So true .

Originally Posted by Jason

https://github.com/

Then download your favourite chat client and voila.

The main issue when creating something like this is definitely Version Control. If only one person is working on any particular file at any time then fine, just update the codebase on the server when they're done. However in reality this often won't be the case as people need to work on the same file at the same time and this can lead to really big problems unless proper versioning is implemented and you have merge/discard/etc facilities. This is why Version Control software like GitHub (my favourite) and SVN exist. A lot of really smart people spent a lot of time making these products work as well as they do.

I'm not saying don't bother, but just bear in mind the fact that there are some pretty excellent alternatives already out there.

Yes it's true and I know it, but why not make a software like Team Foundation by us? I mean it would be not just a goal in our (talking more about myself here) early-aged coding carrier but also a great product that why not will attract many people that are interested in those kind of softwares.

TeamWork

Post a Reply

Similar Threads

Tags for this Thread