/me reads features... Awesome! /me reads Java 7 requirement... Sadness.
You can always share emacs (or vim) under screen, tmux or that other thing Ubuntu uses on a throwaway EC2 instance. I've been doing pair programming sessions on a Google Hangout sharing screens and I'm considering giving this setup another try.
Google Open Sources Collaborative IDE
21–30 of 54 posts
Re: Google Open Sources Collaborative IDE
#22Earlier quoted context omitted.
You can always share emacs (or vim) under screen, tmux or that other thing Ubuntu uses on a throwaway EC2 instance. I've been doing pair programming sessions on a Google Hangout sharing screens and I'm considering giving this setup another try.
Can you explain this in a little more detail, or have a blog post about it? I've been thinking about doing something similar (`screen` for shared coding environment, with some other thing -- skype, say-- for video chat). I'd be very interested to know details about such a set up someone else has used, and any caveats or issues (for instance, screen didn't seem to export the environment faithfully, in my limited exper…
Caveat with using screen: You must suid root the screen binary, which is not very cool.
Put the following in .screenrc:
multiuser on
acladd
Then, start a screen, and the other user can join it using: screen -x /
The slash at the end is important.I like to add some stuff to the screenrc setting up a status bar at the bottom showing all the windows and which users are viewing which window, but I'd have to dig out my old screenrc to remember how.
Skype for audio chat, or some other audio chat (even just a phone call which is what we did a lot back in the day) is essential. Video is less important and hogs a lot of bandwidth.
Good luck, I really hope collaborative remote programming becomes more popular!
Re: Google Open Sources Collaborative IDE
#23Re: Google Open Sources Collaborative IDE
#24After nearly 7 years, Google decided to shut down its Atlanta engineering efforts.
That's a relatively old shop to shut down. Anybody know how big it was?
Re: Google Open Sources Collaborative IDE
#25Bigger news? After nearly 7 years, Google decided to shut down its Atlanta engineering efforts. That's a relatively old shop to shut down. Anybody know how big it was?
Re: Google Open Sources Collaborative IDE
#26Earlier quoted context omitted.
You can always share emacs (or vim) under screen, tmux or that other thing Ubuntu uses on a throwaway EC2 instance. I've been doing pair programming sessions on a Google Hangout sharing screens and I'm considering giving this setup another try.
Can you explain this in a little more detail, or have a blog post about it? I've been thinking about doing something similar (`screen` for shared coding environment, with some other thing -- skype, say-- for video chat). I'd be very interested to know details about such a set up someone else has used, and any caveats or issues (for instance, screen didn't seem to export the environment faithfully, in my limited exper…
Re: Google Open Sources Collaborative IDE
#27It uses Google Wave. Well I guess it's not totally dead.
Apache Wave is alive and well. BTW, I think we can stop calling it Google Wave :-) I run Apache Wave on my laptop just to kick the tires and I had it on a server for a while so I could ask a few people to try it with me. It is an instant install and run from either the svn or mirrored git repo, if you use the default file store. Configuring it with MongoDB as a data store takes some more effort.
Re: Google Open Sources Collaborative IDE
#28Earlier quoted context omitted.
Can you explain this in a little more detail, or have a blog post about it? I've been thinking about doing something similar (`screen` for shared coding environment, with some other thing -- skype, say-- for video chat). I'd be very interested to know details about such a set up someone else has used, and any caveats or issues (for instance, screen didn't seem to export the environment faithfully, in my limited exper…
I have done remote pair programming with screen for a long time. Tmux might be more modern, but I have never tried it. Caveat with using screen: You must suid root the screen binary, which is not very cool. Put the following in .screenrc: multiuser on acladd Then, start a screen, and the other user can join it using: screen -x / The slash at the end is important. I like to add some stuff to the screenrc setting up a…
"I like to add some stuff to the screenrc setting up a status bar at the bottom showing all the windows and which users are viewing which window, but I'd have to dig out my old screenrc to remember how." Or you could use Byobu(https://launchpad.net/byobu) which is an enhancement of GNU Screen and comes with a lot of good features.
Re: Google Open Sources Collaborative IDE
#29Earlier quoted context omitted.
Apache Wave is alive and well. BTW, I think we can stop calling it Google Wave :-) I run Apache Wave on my laptop just to kick the tires and I had it on a server for a while so I could ask a few people to try it with me. It is an instant install and run from either the svn or mirrored git repo, if you use the default file store. Configuring it with MongoDB as a data store takes some more effort.
How good is the UI? Is it the same it had when it was Google wave? Thanks