caelumvox - building on a cloud

I've been searching for a good SVN front end for Linux to replace the command line check in. I want the capability to choose a subset of modified files from which to commit, rather than having to check in the entire directory structure each time by doing a "svn commit .". This feature comes standard with Tortoise, but Tortoise is Windows-only. I first tried out RapidSVN. This is a GTK front end that stores bookmarks on working directories. However, it did not have what I wanted. I also tried eSVN. This is a front end built on qt. Initially, I tried "File -> Open Working Directory..." and this hung. I ran the esvn binary from the directory containing my svn checkout and I was finally able to select a working directory. The GUI also allowed a selectable subset of files! I understand there is a subversion plugin for Eclipse. I will give this a try on my Ubuntu box. All of these attempts were made on a RHEL 5.0 machine.

This is probably going to be a hit. A real-time (yes, an actual real-time) collaborative environment where users can chat and stuff shows up as typing commences. There is so much more, though. Dragging and dropping pics, multiple edits on a single buffer, internal/external extensions, and playback of all activity that occurred in a wave (or wavelet?). I have signed up for the API. Will let you know how it goes!

A great article on what Gene Shadrin calls the OO Design Pyramid: [sys-con.com] The references of this articles might not be enough to infer Shadrin's concept of the OO Design Pyramid, and I'm not sure where he obtained his data for Figure 3 (Design Time vs. Design Flaw), but on the surface I believe this is a fantastic representation of Object Oriented Design in an easy to understand, structured form. Shadrin present a number of plausible ideas here. Using basic concepts without patterns will probably cause an architect to eventually design to patterns, which takes much longer. Designing with patterns but without the basic concepts typically leads to confusion and no "glue" between the patterns. I have read the Gang of Four books, several Fowler books, and others, and have seen them demonstrate the necessity of lower layer concepts with design patterns, but not the other way around. I really feel Shadrin has something here.