What Happened to 5dwm?

CoolVibe asks: "Remember that project called 5dwm? It was supposed to give us free Unix users a Magic Desktop clone. The project seems to have died. What happened to it? Are there any mirrors? As far as I can remember, this project wasn't open source. Too bad, because if it was, we would have a MD clone. Anyone who remembers working on a SGI machine (I used to use an O2) probably has fond memories of the Magic Desktop for IRIX. If anyone from SGI is listening, how about porting that fantastic piece of work to Linux and the *BSD's?"

Comments

Do we need yet another window manager (YAWM)?

[Bob Bitchen]

I have fond memories of the Irix desktop but it wasn't so good that we need YAWM. There are enough to choose from now. Nostalgia isn't the right reason to choose a window manager IMO. The Open source community really needs to focus on fewer projects and make those projects that are popular robust, make them out-perform the alternatives and give them the features that are taken for granted in the mainstream OSs like MacOS X and Windows. Have a look at sourceforge sometime and you'll agree that things are spread too thin. Lots of projects that have never even released any files. Focus on making what's working now better instead of coming up with another new project will help us all.

Re:Do we need yet another window manager (YAWM)?

[Permission Denied]

OSS does not need managers.

I wrote a window manager because that's what I wanted to do and I was able to do it better than anyone else that's ever written a window manager (because I know what I want in a window manager and everyone else got it wrong when they tried). I don't care if you, or anyone, else finds my work useful - I posted the code because it doesn't cost me anything not to do so. This is my spare time and I'll spend it as I see fit.

If you want me to write whatever god-awful financial database application you may consider useful for your business, you'll have to pay me because that's not fun. That's what I do at work - I write window managers and kernels at home because that's fun, and it's not as much fun dealing with the politics on other window manager projects.

Whoever said that we need some ridiculous system to pander to newbies like OS X or Windows? FreeBSD does everything I want it to do and if there's a problem that bugs me, I'll write a patch. I don't give a damn about its commercial success because I'm not getting a cut. As long as it's still alive with people like me and I can still use it, I'm happy.

If you're really worried about these issues, shut the hell up and write code. Don't come in to some project expecting to manage and direct it, because I don't take kindly to armchair managers.

some may need them , let them do it

[photon_chac]

Well, this project ( developing another WM ) might contribute little to OSS community but , it could bring back a lot of joyful memories to those who had been lived with it. So , IMHO , if there are people willing to spend some time on bringing it to Linux or *BSDs , let them do it and we're glad that they do so , and that's what the author's calling for.

Re:well, for one thing it kinda sucked

[spitzak]

You were correct, up to a point.

Both KDE and Gnome use XDND and you can drag & drop. (Gnome also supports some older protocols but I believe it uses XDND even when you go between two Gnome programs).

The problem is not the protocol, but the data being dragged. About the only things you can drag are text (and recently some url's). But in fact XDND has a type identifier very much like Windows for the type of data. In theory the ability to drag different types of data is identical in both systems. However I can list a few advantages Windows has:

First and foremost is that they list in their header file a simple enumeration of types of data. Yes in many ways the set is stupid and based on 1985 technology (for instance URLs are not specified), but at least the list is there and easy to find. The Linux design suffers greately because the people writing XDND try to be correct and admit that somebody else probably knows how to select the data types better than they do. Unfortunately what happens is nobody does.

Second, for some data types (particularily Bitmap) Windows has a simple method to get it on the screen. So an app that just wants to draw what was dropped on it and not think about it much, it is pretty easy. Compare this to X where it is a total nightmare to draw an image (again caused by engineers who don't want to risk doing it wrong and so only provide low level stuff that describes how the screen works). I would think if you had to do a different call for each letter to draw it you would not drag & drop text either.

I am not sure what the problem is with the Xlib designers. I think a lot of it is paranoia about back compatability, and a lot of it is the inability to see that their interface is not understandable, and that an understandable and simple interface is much more important that the maximum-speed interface.