Slashdot Mirror


Sun Drops Sawfish for Metacity

Cardhore writes: "According to this article, Sun's and Wipro's developers are now working on Metacity, instead of Sawfish. Metacity and Sawfish are two window managers for the GNOME desktop, and Sun has decided to use Metacity over Sawfish for GNOME 2. This decision has been based on issues such as accessibility, maintainability of the code [1], documentation, multi-head support and a general eagerness from the community to commit to Metacity in the future." Here's a brief description of Garret LeSage's experience with Metacity, which is described here as a "boring window manager for the adult in you." Anyone with Metacity screenshots, please post below :)

23 of 447 comments (clear)

  1. Thanks for defining the terms by John+Jorsett · · Score: 4, Insightful

    Metacity and Sawfish are two window managers for the GNOME desktop

    Thanks for explaining, and I hope this is the start of a new policy on /., where potentially-unfamiliar terms are defined. Time after time I've encountered some unexplained reference in an article and wondered, "Am I the only person who doesn't know what this is?"

  2. Where to find it ... by charlie · · Score: 5, Informative
    You can find Metacity here.

    (It doesn't seem to have a web page yet.)

  3. Multihead support? by Jeffrey+Baker · · Score: 4, Interesting
    Funny, I thought the multihead support was relatively bad. I've got metacity installed on Debian unstable. It seems to map windows more or less at random, frequently split between my two monitors.

    I do like the way metacity places dialog boxes though. They are placed horizontally centered and just below the top of their parent window, somewhat like a MacOS X dialog.

    1. Re:Multihead support? by SanLouBlues · · Score: 4, Informative

      Were you running xinerama? wm's need it for decent window placement w/ multiheads. See http://www.tldp.org/HOWTO/Xinerama-HOWTO.html , Specifically http://www.tldp.org/HOWTO/Xinerama-HOWTO-7.html . If you are, sorry for the condescension.

  4. Reason for the switch. by Hornsby · · Score: 5, Interesting

    I just grokked this off of the gnome mailing list here.

    > Btw: Why there has not been any updates for sawfish lately?

    Rumor has it that John was employed by Apple and that as part of the employment contract he's no longer allowed to develop sawfish.


    So there you have it! Before you start flaming back and forth about what's better, think about the logistics behind using a WM that's no longer being maintained.

    --
    A musician without the RIAA, is like a fish without a bicycle.
    1. Re:Reason for the switch. by g4dget · · Score: 5, Insightful
      So there you have it! Before you start flaming back and forth about what's better, think about the logistics behind using a WM that's no longer being maintained.

      Everybody has the source, and it is apparently quite usable since many people sue it. If someone like Sun additional features or bug fixes, they can make them and publish them. The fact that a single person has moved on to doing something else makes little difference for open source software.

      Choosing Metacity may be the right thing for Sun to do anyway, but the departure of even the main developer of Sawfish would not be sufficient reason.

    2. Re:Reason for the switch. by luge · · Score: 5, Informative

      This is particularly a problem for sawfish; not only is it a complex, niche codebase involving fairly obscure stuff (X) that not as many people have experience with, it is also in Lisp, which narrows down the number of potential hackers even more. Nothing wrong with Lisp, mind you, just not as many proficient lisp hackers in the community as there are C hackers. And that does make a difference to community supported projects.

      --

      IAAL,BIANLY

  5. Metacity and GNOME2 by Snorp · · Score: 4, Informative

    http://www.cs.indiana.edu/~jwillcox/desktop.png

  6. I use it... by JanneM · · Score: 5, Interesting

    I started using metacity two weeks ago or so, and I'm fairly pleased. I really liked sawfish, but felt it was time to try something new.

    Pro: easy to set up (not a whole lot of options to choose from, really), fast (much speedier than sawfish), and largely with sensible defaults for everything.

    Con: I miss a few settings, like the ability to remember window size and position. Also, lazy focus only changes focus and does not raise the newly focused window.

    On the whole, a good, solid windowmanager that really feels lean and efficient.

    /Janne

    --
    Trust the Computer. The Computer is your friend.
  7. Couple of screenshots by dizco · · Score: 5, Informative

    There's a couple screenshots here: http://www.lucidus.uklinux.net/metacity/

    Found at http://www.sunshineinabag.co.uk/

    --sean

  8. I want my twm! by Limburgher · · Score: 5, Funny

    I want to be able to do almost nothing, but FAST!

    --

    You are not the customer.

  9. Metacity-Setup might be of some interest by plastercast · · Score: 5, Informative

    On the topic, and with the complaints of no GUI tool to configure Metacity, I just though I would point everyone to a piece of software that I wrote called Metacity-Setup. Im currently working on getting it a little more friendly (its flawed to be sure) but it does basic stuff nicely.

    http://www.gnome.org/softwaremap/projects/metaci ty -setup/

  10. Re:not so bad? by MadFarmAnimalz · · Score: 5, Funny

    Metacity saved our business. Maybe it will save slashdot, too

    Let's get one thing clear; metacity is not Jesus, allright?

    And if it took a new window manager to save your company, then I need its name. I'm worried I might be a stockholder.

    :-)

    --
    Blearf. Blearf, I say.
  11. Re:Thank the submitter by ergo98 · · Score: 5, Interesting

    A while back Slashdot started linking any potentially unfamilar terms to everything2, however this raised the ire of several who felt that this was an abuse of the Everything2 service (which didn't make an awful lot of sense as that's specifically what the service is for)

  12. Couldn't hack the Lisp? by Kaz+Kylheku · · Score: 4, Insightful

    Could programming language ignorance or bigotry be at least partially at the root of this? Probably not, but one wonders anyway.

  13. Re:Just more wasted effort and time by foobar104 · · Score: 4, Insightful

    The world needs one full-assed solution, not 400 half-assed solutions. That's the eternal problem with free software / open source development. Quit bickering about which one is better and which one to use; pick one, stick with it, and get it done.

    I absolutely agree with you. I get so discouraged when I run into things like the 90 items listed under "Window Managers" on Freshmeat, and not a one of 'em especially useful.

    That's the problem with the current state of open source development. Rather than putting 10,000 brains on one project, you put one brain each on 10,000 projects. Net result: almost zero result for a vast amount of work.

    Maybe the only way to get programmers organized is to get a bunch of them in one place and wrap a company around them.

  14. Code Maintainability? by big.ears · · Score: 4, Insightful

    When they say "unmaintainability", this is code-word for "Programmed in Lisp", rather than "Programmed in a sloppy messy spaghetti-like fashion", or "The primary developer is no longer working on it". Most likely, the Wipro programmers don't have much experience with lisp/scheme/rep, and a decision was made to dump it for Metacity, which happens to be written in a language they speak (c, that is).

    If you read the metacity source code, at least on earlier releases, Havoc had written things like "I won't implement idea X, because it is crackrock. Tough luck." Things like making metacity play nicely with XMMS. Of course, this was when it was his pet project and not being considered by Sun/Wipro. One wonders if there will be a Sun fork of the project, or if Havoc will turn over development or make compromises that Sun will inevitably require.

    While I think metacity is a pretty cool project, Sun's decision is probably one of these management mistakes that have been talked about in all the sociology of software development books. Think of all the little bugs that have been sorted out over the years in Sawfish that will have to be solved again. Things like maintaining focus of window when changing desktops using keybindings; or dual-head setups that have different monitor resolutions while using multiple workspaces and desktops. These things will all have to be sorted out again.

    1. Re:Code Maintainability? by The+Pim · · Score: 4, Informative
      When they say "unmaintainability", this is code-word for "Programmed in Lisp", rather than "Programmed in a sloppy messy spaghetti-like fashion"

      Well, I'll just say it: Sawfish is, in my reasonably informed opinion, a well-designed, maintainable program. I read the documentation and looked at the code in order to make some changes of my own (which I never finished...), and I was generally impressed.

      So, while I haven't seen enough evidence to be sure, I strongly suspect someone at Sun is afraid of Lisp.

      --

      The evaluation of an action as 'practical' . . . depends on what it is that one wishes to practice.
  15. Re:Enlightenment by DrXym · · Score: 5, Insightful
    I dumped Enlightenment in favour of Sawmill (as it was known then), simply because E was a big bloated monster that wanted to own the desktop whereas Sawfish knew its place - to be a window manager and nothing more. It was not hard to see why Red Hat dropped it - they needed a WM, not an entire desktop and the kitchen sink.


    Frankly me and probably 99% of other GNOME users don't give a crap what WM they're running as long as it doesn't get in the way of GNOME. It should be as unobtrusive as possible and limit its features to window-manager-y things.


    I suppose E would be a good fit if you didn't want to run GNOME, or could put up with the bloat, or wanted to run kewl gigeresque desktops with metal knobs and shit, but for the rest of who just want to run some GNOME apps, then Sawmill is a perfectly usable and functional WM.


    Ultimately I'd like to NOT KNOW what WM I'm running. I don't really care that much as long as it moves windows around and is reasonably skinnable. If Metacity is a move in that direction then that fine by me. The sooner I don't need to know what WM is running the better.

  16. There's a point to this by hatless · · Score: 5, Insightful

    I think there's some missing the point going on here. From Sun's perspective (indeed, from a sysadmin's perspective), the lack of its own setup tools, relying on a command interface to change settings is a plus.

    Metacity gives GNOME a chance to address one of its manageability flaws, the confilct between a desktop environment and the window manager. Which controls wallpaper? Screensavers? Why are there separate themes and theme settings interfaces for window chrome and the window contents?

    It's because some power users high up in GNOME and window manager development--who usually aren't responsible for any machines beyond their own personal ones--like the flexibility of mixing and matching, and like pushing the bounds of what each component of their system can do. So overlapping--and conflicting--features get built.

    This isn't the end of the world, but it does make a GNOME system more unwieldy than it has to be. KDE can run with several window managers, but it comes with one of its own that leaves configuration matters to KDE. GNOME hasn't had this yet. Enlightenment, sawmill and sawfish have been progressively better fits, but Sun and others who are moving to Metacity probably see it as a simpler route to getting a decent (GTK+ 2, anti-aliasing, multihead, accessibility-enabled) window manager seamlessly tied into GNOME than revamping Sawfish--and subsuming all of its configuration into GNOME--would be.

    GNOME with Sawfish is a much tougher sell to a simplicity-minded CDE administrator than GNOME with Metacity will be, I suspect.

  17. Re:translucent windows and other nonsense by pthisis · · Score: 5, Insightful
    The window management in Windows is better than anything I've seen in Linux.

    I'll agree that translucence and themability are fluff. I might be able to envision an actual use for translucence if I thought about it long enough, but it'd be a real corner case.

    But...

    Things that suck in Windows window management:

    • Click to focus + focus autoraise. The latter is the biggest problem. I can't tell you how often I want to be typing into the window _behind_ another window, so I can see the contents of another window while I type. And click to focus is just annoying, why put another step in the way of my work? There are some hacks to get focus-follows-mouse, but a lot of apps don't work well with it.
    • The task bar. This thing just blows, it's the first thing I turn off in Gnome/KDE. At most I want a couple of launch buttons and a clock, but I _don't_ need the entire bottom half of the screen real estate taken up by icons of every running app, and the thing is only usable if I have at most 8-10 windows open. Usually I have 4-5 times that. Give me alt-tab, windowshade, window groups (and raise/iconify/etc working on entire groups), virtual desktops, and restricted alt-tabs (meta-tab limited to xterm, control-tab limited to mozilla, etc) over that any day. In other words, real tools for managing the windows (which is what I want out of a window manager). Sawfish lets me do that. The groups, especially, are a godsend. Launch an editor, debugger, and GUI designer all in one group, then operate on that group as a whole when I need to. Which leads to...
    • ...MDI or whatever it's called when the IDE/Word/whatever opens a bunch of subwindows inside its own window instead of just opening them as real windows. God this sucks. I already have a window manager, I don't want every application to _also_ have a window manager. Of course, if your IDE takes the approach of putting everything into one window rather than seperate windows which can be grouped together then you need something like this. Ugh.
    • Clippy. Yeah, he's not related to window management but even now that he's dead he deserves to be kicked around.

    Sumner

    --
    rage, rage against the dying of the light
  18. Re:translucent windows and other nonsense by quantum+bit · · Score: 4, Insightful

    For goodness sake, what problem do translucent windows solve? The need to see what's behind your xterm while simultaneously rendering it unreadable?

    Can't argue with that. I like plain light-grey-on-black xterms. Easy to read.

    I'm sorry, but it's true. I don't care if you can make windows "roll up" into the title bar and you think it looks cool - what problem does that solve that wouldn't be handled better by minimising the window and showing it in the taskbar? Really, I'd be interested if someone could tell me the advantage.

    Ummm, ok. Not everybody likes the whole "taskbar" idea. When I'm on a Windows box, I frequently have so many windows open that the taskbar is utterly unusable (takes me 30 seconds just to hover over icons and find which one I'm after). On my X desktop, I have no taskbar or anything like it -- I use sawfish with no desktop envorinment. Just gkrellm in the corner of my left-hand monitor, a tiny pager in the bottom left (4 virtual desktops X 3 monitors == lots of room :), and the windows themselves. If I have too much open and the windows are overlapping, just click on the desktop and I get a nice, easy to read menu with everything grouped by application or class. It really saves me a lot of time. Right-click gives me a list of commonly used programs to start. To answer your question, when I'm not using a window and want to get it out of the way, I shade it. It's a lot easier to find it again since it hasn't changed position.

    Trust me, after getting used to that, it's a pain to work in Windows because it just takes so long to get anything done.

    One feature I absolutely love about sawfish that Windows doesn't have anything close to is the customizible bindings to do almost anything you want. On an MS box, if the title bar of a window is obscured, there is no way to move it without either moving something else first, or using the task bar to raise the window (disrupting your Z order). In sawfish, I just hold down the windows key, grab the window anywhere, and drag it where I want it (without changing the Z order). Incredibly convenient. And Windows+X for an xterm? ;)

    And don't even get me started on focus-follows-mouse. Just imagine having a bunch terminals or whatever, simply pointing at the corner of xmms with the mouse, pressing 'B' for next track, then going back to what you were doing. Windows has a hack with tweak UI that tries to do this, but some apps (*ahem*, MS OFFICE *ahem*) insist on raising themselves to the top whenever they get focus, which is incredibly annoying...

  19. Re:Enlightenment by Mandelbrute · · Score: 4, Insightful
    So therefore it's not hard to guess the cause of Red Hat / Raster split - Red Hat wanted a functioning, lightweight WM to put behind GNOME so it could sell it to businesses and normal users
    RedHat (or a person who was there at the time and is unlikely to still have a job) wanted a window manager that looked like win* with a bit of fvwm thrown in so that win* users could use their distribution easily from day one - not a bad goal really. E with the right theme gave them that almost from the first day Raster worked there. Raster then proceeded to put stuff into E that would not be used in that cut down theme. One of Rasters superiors (who is probably no longer at RedHat) who was not particularly skilled in the use of email flamed Raster and his "posse" (simply being an unprofessional way of refering to the unpaid developers) for putting stuff in in their spare time which wasn't in the business plan. Raster was not supposed to get the email, but technical illitracy will out - and eventually raster went off to work somewhere else with different management. Google will tell you more. The other window manager was used simple becuase it was the window manager for gnome.

    Enlightenment was briefly part of gnome, but the dependencies and politics killed that. At that point E ran on a variety of platforms, and the gnome people of the time didn't have any short term plans to move off x86 hardware and linux. Raster et al more or less had a choice between personally porting the rapidly moving target of the gimp tool kit (gtk) to Solaris etc, or just keeping the window manager seperate. Gnome at the time was sadly dominated by politics over functionality, but thankfully moved on to where it is now. There were actually arguments at the time over whether it should ever be ported to any kind of commercial OS for idealogical reasons. In hindsight, the Enlightenment project was better off without that, and other themed window managers were developed to work with gnome and kde. E v0.16 of course works with both.

    E was always about "kewl fx" as well as funtionality anyway - the alternatives were fvwm (not fvwm2) which looked pretty horrible and was time consuming to configure, and windowmaker, which had a few cool features like the dock.

    I wouldn't have called Enlightenment a desktop shell (E16) at the time that GNOME was being released
    That, I believe, is the long range plan. E at the time was simply a window manager with icons, menus, and a pager. The filemanager etc comes seperately, as whatever one you pick from kde, gnome or myriads of unconnected projects.