Étoilé Desktop Environment
etoileos.com
etoileos.com
A few details for those who'd like to know: GNUStep is a reimpementation of the OpenStep API, which was an effort by Apple and Sun to bring the insanely great NextStep API to your regular workstation (I think my facts may be a little wrong here ; feel free to correct me). Etoile is built using GNUStep, with the desktop model based around the OS X dekstop (check out my desktop and compare it to Etoile: http://img136.imageshack.us/my.php?image=picture1rn3.png).
The best part about Etoile is not that you get to use a fast, lightweight, (sorta) modern desktop environment for your favorite open source OS, it's the fact that you get a great oject oriented API similar to Apple's Cocoa for writing applications with. I've been looking at Cocoa for the past month or so, and I can assure you it's a great framework to write desktop apps in. Sure, Objective-C can be a little weird at first, but once you get used to it you'll find it's a very well thought out language. And BTW, GNUStep even has replacements for Apple's XCode and Interface Builder. I don't quite remember what the XCode replacement was called, but the IB replacement is called Gorm (which is not a cool name).
Upvoted for awesomeness.
Still, if it's really a nice platform, I hope it would become popular enough that popular applications could be easily coded to work with it.
They'll just look different from the etoile applications.
I could turn your question around: Why did they start their own instead of just supporting, say, XFCE?
Because XFCE doesn't have the same goals as they do. If you listen to the interview with them on FLOSS Weekly at twit.tv, they talk about how they want this thing to grow, and what they want it to be. The best example I guess I could give is that they are creating a desktop environment based on concepts in Smalltalk. The look isn't the important thing (at least right now). The cohesiveness of it all is what's interesting.
It's easy to say that getting rid of X would be a win, but replacing it at this point would be much more work than fixing what's wrong with it.
1) An MIT-licensed reimplementation of Cocoa (Foundation + AppKit + some CoreFoundation plain-C APIs)
2) A cross-compiler GCC toolchain that produces native Win32 binaries and installs into Xcode. (There is also some degree of Linux support.)
The benefit of this combination is that you can basically add a Windows target to an existing Cocoa project in Xcode and have it produce an .exe file... At least if all the methods used by your application happen to be implemented in Cocotron.There's still quite a bit of the Cocoa API missing, but the amount of work already done is impressive -- and one of the really great things about Cocotron is that it feels so easy to contribute to the base frameworks. The Foundation and AppKit projects are clean of cruft, neatly laid out, and they are built as Xcode projects so there's no toolchain learning curve: if your favorite esoteric NSString method is missing, you can simply open Foundation.xcodeproj and implement it.
For me, Cocotron is cross-platform Objective-C that "just works". YMMV.
The thing that's sort most interesting about this is CoreObject, which is modeled off of the ideas of SmallTalk images.