Use Cases

IDEtalk is created for a team of software developers working on one or related projects. That's why it is aimed exclusively at code-related collaboration.

Here are some basic scenarios. If you are a developer and would like IDEtalk to support your scenario, which is not implemented yet, just .

Code and talk

When I am in a deep coding flow I don't like to switch to another application. So if I need to send my colleague a message I'd better do it from my editor.

Moreover, IDEtalk works on your local network and doesn't require internet connection.

Strange exception

I am working on my module of a project. Suddenly it throws an exception. Looks like the bug is not in my code. And I think I know which developer might be responsible for it.

So I send him this exception with a question - "I did this and that and got this exception. Is it yours? Should I send it to the tracker or you'll fix it?"

Send a "code-pointer"

I start to work on a module and see a "smelling" code fragment. The code was written by my colleague, who is not here right now.

I do not want to fix his code, because he still works on it. Of course I could send the code via instant messenger or email, but the most effective way is to send him a "code pointer" — a navigatable piece of code with my comments and suggestions.

Moreover, he can send a reply to my "code pointer", so we could find a better solution together.

Diff made easy

I have to make some quick corrections to the CSS file, but I know that my colleague's been working on it for some time.

I want to make sure that my changes won't conflict with those made by my colleague, so I view the list of her open files, find the one I need and see the differences between the two versions.

Then I can merge her version with my local file and safely fix what I needed. Or, if there is a conflict, I can send her a message and work on the file using "code-pointers".