Slashdot Mirror


First Xouvert Milestone Released

An anonymous reader writes " The first milestone of xouvert, the X-server replacement has been released. Xouvert includes MAS giving the X server its very own sound server. Nice. :) Also, just noticed that enlightenment quietly released an update to the 0.16 series. " (Here's a link to the Xouvert download page.)

34 of 404 comments (clear)

  1. The things people complain about X... by ObviousGuy · · Score: 3, Insightful

    People complain about X a lot, but when it's all boiled down there really isn't much to complain about. X is a great windowing system.

    --
    I have been pwned because my /. password was too easy to guess.
    1. Re:The things people complain about X... by Goth+Biker+Babe · · Score: 2, Insightful

      Typically most people think X == XFree86 and so show their ignorance. If X is so bad how come SGI/IRIX still uses it for their visualisation systems. A client server architecture does not slow down a windowing system. Badly written software slows down a windowing system. Crippling the existing XFree implementation by coming up with a system that doesn't support any of the useful facilities of X is not an improvement. Hell even XP uses a client/server architecture. And then even inefficient XFree86 performs well enough to display full screen video on one of my monitors whilst I use the other one and that's on my 750Mhz Duron machine.

      I'm afraid that Xouvert shows the worst side of Open Source. And that is that anyone can write OpenSource. Where's all the profiling data showing where XFree86 is slow. Why if you're trying to improve on XFree86 are they using a code fork and not starting from scratch? It seems to me this whole project is based on a gut feeling that removing all that socket code will speed it up rather than doing the proper research.

    2. Re:The things people complain about X... by fucksl4shd0t · · Score: 4, Insightful

      I'm afraid that Xouvert shows the worst side of Open Source. And that is that anyone can write OpenSource. Where's all the profiling data showing where XFree86 is slow. Why if you're trying to improve on XFree86 are they using a code fork and not starting from scratch? It seems to me this whole project is based on a gut feeling that removing all that socket code will speed it up rather than doing the proper research.

      Another poster already showed you their FAQ where they say they cannot remove network transparency.

      I think the Xouvert actually shows one of the best sides of open source. They are being non-critical of the fact that the XFree86 organization is slow, bloated, and more or less unable to keep XFree86 in a constant, modern state. Instead, they are providing a 'branch' of XFree86 that will focus on being bleeding-edge and providing fast turnaround for development and testing, so that they can interface with the slow, bloated XFree86 organization to improve XFree86. I think that says a lot of good things about OpenSource, taking care of our own, getting the job done, etc.

      --
      Like what I said? You might like my music
    3. Re:The things people complain about X... by jilles · · Score: 2, Insightful

      X is just a protocol. The whole problem is that most implementations of X are not particularly good implementations of a 2D windowing system. When you make remarks about those problems to an X proponent, you get the (correct) reply that it is not a problem with the protocol. He will then kindly request that you whine about your problems somewhere else.

      The problem with XFree86 is that it is developed by people who are not particularly interested in improving it (at least I have no other/better explanation for the current configuration interface. There are so many obvious potential improvements that you just have to wonder what the fuck these guys are doing). This is basically the reason for the fork.

      --

      Jilles
    4. Re:The things people complain about X... by herulach · · Score: 2, Insightful

      My point entirly. Its not that you cant do it, it just doesnt work out of the box, which was my point. Joe Average isnt going to want to muck around installing the new KDE or something so he can change screen resolutions, hes just gonna say:
      'Sod this, Windows does that straight away'

  2. just what we need... by gamlidek · · Score: 1, Insightful

    yet another X server/manager to try. *sigh* It'd be nice if we could get everyone to focus all their energy on making the current X managers to play nice rather than go off and make more. freedesktop.org is a nice start towards fixing the linux desktop, methinks.

    -jp

    --
    "In theory, theory and practice are the same; in practice, they are not."
    1. Re:just what we need... by SQLz · · Score: 2, Insightful

      I always see people post stuff like..

      It'd be nice if we could get everyone to focus all their energy on making...insert software name/type here.

      This is how open source happens my friend. In a way, they are ALL working on the same thing. Since this is open source, the code, the ideas, the research, the development can all be shared between them meanwhile the competitiveness keeps them going.

      Its much better than say, having a bunch of people who don't like each other work on the same thing or having talented developers not work at all.

      Also, its not a window manager.

  3. Funny.... by IamTheRealMike · · Score: 4, Insightful
    People were talking about XFree forking for so long and nothing ever happened. Now within the space of a few months, we have two!

    It seems at least to me that the freedesktop.org x server (kdrive) is where the interesting stuff is happening, but we'll see how the Xouvert guys get on.

  4. sounds nice by axxackall · · Score: 5, Insightful
    Xouvert includes MAS giving the X server its very own sound server. Nice. :)

    Just nice? It's excelent! This is the biggest X Windowing achievement since first actual implementation of X Windows.

    It is in human nature to assotiate visual and audio information in the process of percepting it. Therefore video without audio mean seriously broken usability. That's why I think all these years X Windows has been developed in essentially wrong direction. The made in recent XFree86 versions transparency, which is really just a candy, while so important prime functionality was missed all the time.

    I am really happy that MAS in Xouvert now. I am going to switch to Xouvert as soon as possible. Good-bye, XFree86 - thank you for keeping me in the void silence all these years.

    --

    Less is more !
    1. Re:sounds nice by evilviper · · Score: 2, Insightful
      We haven't needed esd and arts from the first place if sound would be handled by X since the beginning.

      I see, you're simply anti-unix. You think there should be one monolitic application that has everything integrated to it. Is too damn much work for you to type "esd &".

      Because that's what X is supposed to do - to isolate window managers, desktop managers and just applications from any knowledge about hardware.

      Sound apps like esd know nothing about the hardware (well, almost nothing). All they do is mux audio streams together, and send them to /dev/dsp. Not exactly low-level knowledge.

      In case you haven't noticed, XFree86 does not, nor has it ever, come with sound-drivers, or sound apps, so I have no idea why you think it's the responsibility of X to handle sound as well. It's not like sound is an exclusively GUI-based feature... If X is handling sound, how do I play sounds when X isn't running? That's right, you'd have to have the sound-system manager as a seperate daemon, like esd.

      I hope that at some point Gnome and KDE developers will drop their "proprietary" sound servers
      THEN perhaps Gnome and KDE will have more available human resources to *focus* on improving the usability and configurability of their applications.

      -1 Complete Moron
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    2. Re:sounds nice by axxackall · · Score: 3, Insightful
      I see, you're simply anti-unix. You think there should be one monolitic application that has everything integrated to it.

      RTFA - they integrated X and MAS, not merged the code. Unix *is* integration of protocol layers, listeners and daemons, and applications. The integration of MAS with Xouvert is done in completely Unix way.

      When GNOME is everything - that *is* monolitic.

      In case you haven't noticed, XFree86 does not, nor has it ever, come with sound-drivers, or sound apps, so I have no idea why you think it's the responsibility of X to handle sound as well.

      RTFA, Xfree doesn't, MAS does. it's responsibility of MAS to handle sound and it's great that X and MAS are integrated now to handle both graphics and sound in a same network-transparent way.

      If X is handling sound, how do I play sounds when X isn't running?

      What *graphics* do you see when X isn't running? That's right. TTY is for system management tasks, not for entertainment. When you want to entertain - you run your desktop. When you are not local - you run it remotely. And now it will have sound.

      --

      Less is more !
    3. Re:sounds nice by GreyWolf3000 · · Score: 3, Insightful
      When GNOME is everything - that *is* monolitic.

      Not really; you don't type "gnome" and have a full blown web browser, media player, kitchen sink all-in-one app. Gnome is, essentially, a set of foundation libraries and application framework for building consistent applications that play nice together. The vanilla Gnome distribution contains many applications (a web browser, applets, gnome-panel, etc.), but Gnome is about as monolithic as a Linux distribution. Fedora or Debian may have a thousand programs on it, but that doesn't mean that they are monolithic.

      What *graphics* do you see when X isn't running? That's right. TTY is for system management tasks, not for entertainment. When you want to entertain - you run your desktop. When you are not local - you run it remotely. And now it will have sound.

      A lot of folks out there use X-less desktops. mplayer for example can output sound AND video to the command line (with framebuffer support), and I think the parent was afraid that if MAS were widely adopted, and integrated into X, then audio support for the command line would fade. The parent (albeit rather rudely) meant that by bundling a sound server with X, people who choose not to run X will not have sound (assuming MAS becomes popular).

      What the parent failed to realize is that you can run MAS without running X (or if you can't, there's bound to be an X-less MAS server around).

      Personally, I fail to see the importance of tying a sound server to the X server (even if it is merely association), but if it means the acceptance of a standard, network transparent protocol, I'm all for it. I'm sick of sound being nonstandard in Linux.

      --
      Slashdot: Where people pretend to be twice as smart as they really are by behaving like children.
    4. Re:sounds nice by Greg+W. · · Score: 2, Insightful

      Personally, I fail to see the importance of tying a sound server to the X server (even if it is merely association),

      An example may help clarify. Suppose you're running X on a diskless workstation with sound capability. You could run xmms locally, having it read the Ogg and MP3 files from an NFS server, and that would work fine. But what if you wanted to run xmms on a remote system, and have it display and play music on your local desktop? You could set the $DISPLAY variable to get the video onto your screen, but the sound would still come out on the remote system, because $DISPLAY has nothing to do with audio.

      I haven't looked at Xouvert except to read the main page and the FAQ just now, so I'm not sure exactly how MAS works or how it's integrated with X. But if they have made "ssh -X me@remotebox xmms" work, then they've really achieved something.

    5. Re:sounds nice by axxackall · · Score: 2, Insightful
      Personally, I fail to see the importance of tying a sound server to the X server (even if it is merely association),

      Two examples:

      I want my sound being network-transparent and automatically follow my $DISPLAY variable. Remember, X11 is network transparent.

      I want to make sure that video and audio are in sync. Today they are not. Recent improvement in Linux is a help. But it's not a general soultion (it doesn't cover even all cases on Linux itself). Remember, X11 is not just for Linux. Need more examples?

      --

      Less is more !
  5. Re:Humble Dev's Request by Anonymous Coward · · Score: 2, Insightful

    No you're not. Check his post history, he's just an idiot ;).

  6. How's this going to work with KDE/gnome etc? by carnivore302 · · Score: 5, Insightful

    Xouvert has its own sound engine, MAS. If Xouvert catches on, does this mean that the sound engines of KDE and gnome will become obsolete, or will they collide with MAS?

    If they collide, it basically means that KDE and gnome will have to support both X11 and Xouvert. I'm not sure if that is achievable. On the other hand, if they don't collide what's the use of MAS? I'm pretty happy with the way it works now. So I'll then continue working without MAS.

    --
    Please login to access my lawn
    1. Re:How's this going to work with KDE/gnome etc? by Amiga+Lover · · Score: 5, Insightful

      If Xouvert catches on, does this mean that the sound engines of KDE and gnome will become obsolete, or will they collide with MAS?

      There's a few places Linux has failed miserably for me as a desktop, and consistent audio has been one. If I get KDE audio working, six other non KDE apps suddenly go silent, If I get those working, KDE audio apps error on me. Same story sadly. Now, perhaps it's just me not knowing what to futz around with, but to repeat a cliche, "I shouldn't have to do that".

      Perhaps kernel level device sharing would work, but I don't know if adding another sound engine would help much

    2. Re:How's this going to work with KDE/gnome etc? by TheRaven64 · · Score: 4, Insightful
      Perhaps you should look at FreeBSD? It contains kernel-level sound mixing, and exposes several virtual /dev/dsp devices (/dev/dsp.0, /dev/dsp.1) which are mixed together to produce the final output. I have the KDE sound daemon pointing at one, the Gnome one pointing at another and leave `legacy' apps and games (which can't tolerate the latency imposed by one of these daemons) to use /dev/dsp (which is a symlink to /dev/dsp.0). In the 5.x series, this is handled automatically, and each request to open /dev/dsp returns a new mixer channel, rather than the device.

      Having said that, MAS is not a replacement for /dev/dsp. For one thing, it is network transparent (so I can run a MAS enabled MP3 player, for example, in a remote X session, but still hear the sound.) MAS is cross platform, so I can (in theory) post the sound between any combination of machines that run an X server, as I can with X11. MAS uses a stream/filter graph-based model, and so is very flxible. I regularly use a remote X session, and audio is one of the things I have been missing. MAS should provide that, and this is the first real implementation I have seen. Hopefully it should make it into the main XFree86 trunk soon...

      --
      I am TheRaven on Soylent News
  7. X is not bloated! by lokedhs · · Score: 4, Insightful
    X isn't and never was bloated. People think it's large just because the framebuffer memory is included in the "ps" listing.

    Read the explanation on the freedesktop site. There they mention the fact that people developed X on really old VAX machines. I even ran X myself on an old VAXStation II which had several times less memory than your average palmtop computer, hardware which happens to run X as well.

    1. Re:X is not bloated! by kinnell · · Score: 3, Insightful

      The X server itself may not be bloated, but the XFree86 source distribution certainly is. Everything from client libs to Xeyes are included in the build system, and working out how to configure it to only build the parts you need is not an easy task. Not to mention the amount of cruft you have to download. This is a shame, because there is no reason why it has to be like this, but clearly the XFree86 people aren't interested in the problem. If Xouvert can modularise it well like they plan, this will be a massive improvement in itself.

      --
      If I seem short sighted, it is because I stand on the shoulders of midgets
  8. Re:MAS, networked sound ?!?!? by CRCulver · · Score: 2, Insightful

    why not use alsalib or libaudiofile?



    Well, ALSA is the Advanced Linux Sound Architecture, and any X11 replacement would have to serve FreeBSD and the Hurd as well.
    As far as libaudiofile goes, I'm not sure it is strong enough to serve as the basis for an entire array of audio uses.

  9. Re:MAS, networked sound ?!?!? by Anonymous Coward · · Score: 1, Insightful

    > can anyone tell me what network-transparent sound is going to offer me besides bloat?
    Maybe ip-phone on X-terminals.

  10. Why Linux needs a standard GUI toolkit by October_30th · · Score: 2, Insightful
    Yes, it means "stagnation"

    Ok. I see now. I just didn't realize before that standards organizations like IEEE are just stagnating the development. What a revelation! How far our technology would have developed already if we just didn't hang on to standards. Who the hell needs consistency anyway?

    a lousy GUI that will remain lousy forever

    Linux desktop will remain lousy as long as the distro manufacturers refuse to create a common set of rules for a standard Linux application toolkit.

    Having such a standard would not stop a pro like you from reconfiguring your desktop to your liking, but it would make the initial desktop look the same on every distro and thus easily adapted by a newbie.

    On a more personal note, the mishmash of different toolkits (run xawtv and some kde applications side by side and you'll see what I mean) just makes the GUI look so goddamn ugly and cumbersome to use ("now did I move the scrollbar in this application with the mouse middle button or with the left?" etc.).

    --
    The owls are not what they seem
  11. Re:Gombine and Gonquer, with XouverG by t_hunger · · Score: 3, Insightful

    A consistent GUI allows for the things you learned in your word processor to be reused in your browser, e-mail client, etc. Thanks to the thousand of toolkits, desktop environments, support libraries, sound backends, printer support solutions, etc. that's plain impossible in X. So a user has to spend lots of time relearning how to do simple tasks for each application he uses (and mixing them up after learning them). That ruins productivity!

    Wether someone runs one or onehundred word processors is absolutly irelevant to the GUI consistency discussion.

    --
    Regards, Tobias
  12. Re: warning to ACs, post AC means Ashcroft at door by Anonymous Coward · · Score: 2, Insightful

    It's not a bad thing, unless you are doing something wrong...

    Or unless somebody thinks what you're doing is wrong. Better to just say, "On the internet you're going to get logged and there's not a whole lot you can do about it."

  13. Who really wants all that garbage? by Nichademus · · Score: 3, Insightful

    After checking out the following screenshot: http://freedesktop.org/~keithp/screenshots/sharp_s hadow.png and then reading the contents of the X-Chat window, specifically, "I'm hoping to do things that won't be fast enough with 2D/3D hardware as it exists today.", I have to ask: Who really wants all this shadowing, and translucent windows, and animated desktop graphics? I mean seriously, what's the point? Does it help you get you work done? Does it increase your productivity? I see it being more of a nuisance and distraction.

    It certainly shows that Mr. Packard works for HP, what with him writing software that would require users to purchase new hardware just to have the next generation desktop. Hell, the desktop might as well be free, if we have to shell out the dough to purchase a new video card.

    1. Re:Who really wants all that garbage? by Just+Some+Guy · · Score: 4, Insightful
      Who really wants all this shadowing, and translucent windows, and animated desktop graphics?

      I do. I really don't know how they'll benefit me, but I guarantee that someone will make a newly-possible feature that, once you see it, you'll wonder how you lived without.

      OK, here's a tiny example. What if your window manager used translucency to indicate window selection: the window with focus is opaque. The one you just left is slightly less so. The one before that is starting to become transparent. I think that'd be a much stronger (and faster) visual indicator than "window with focus is dark blue, windows without focus are lighter blue".

      Is that a trivial example? Sure. But the point is that we don't know what will turn out to be the productivity enhancing killer feature that we've been waiting for until we try it. These new features may very well be useless and unused, but they could also change the way we use our systems. New functionality is good.

      --
      Dewey, what part of this looks like authorities should be involved?
    2. Re:Who really wants all that garbage? by pebs · · Score: 2, Insightful

      Who really wants all this shadowing, and translucent windows, and animated desktop graphics? I mean seriously, what's the point? Does it help you get you work done? Does it increase your productivity?

      Yes, we want it. Yes, it makes us more productive. Yes, it helps get work done. Its quite simple: visual cues. For example, you minimize a window, and you see it animate its way to the taskbar. That animation cues you as to where it will be when you want to select it in the taskbar.

      Shadow effects are helpful because they give you a clear distinction between windows (or widgets such as menus), and you can quickly tell where a window ends.

      Translucency, I don't know how useful that will be. Probably because I've never used an app with translucency. Maybe it'll be helpful, maybe it won't. I'll give it a try, though. Maybe it'll be good for things you want to keep open, but don't want to have to compromise desktop real estate for.

      I don't think this is about trying to sell hardware, its more about giving users what they want. Personally, I like my GUI looking nice. I like the fact that Gnome looks great (IMO, better than Windows and KDE). I'd like to see shadowing and maybe some other effects. I'd like my desktop to be as smooth looking as OS X (but not bloated and ugly like WinXP).

      --
      #!/
  14. Linux is going to decimate the desktop world by Moderation+abuser · · Score: 2, Insightful

    Because it's cheaper and good enough. That combination wins every time. It does not have to be better.

    --
    Government of the people, by corporate executives, for corporate profits.
  15. Enlightenment release by sirReal.83. · · Score: 3, Insightful

    "Also, just noticed that enlightenment quietly released an update to the 0.16 series."

    uh... that was over a month ago, on November 5th. It was a good little bugfix release, though.

  16. Enlightenment is a good example of.... by bnavarro · · Score: 4, Insightful

    Why keeping a project in an alpha/beta state is a bad idea. I used to use E a long time ago, but they never went 1.0, and all the distros just started ignoring it, so now I use Sawfish.

    This is a real pet peeve of mine. There are many OSS projects that do this. OpenSSL, anyone? The question is, why?? There must be a stable enough "beta" version of E that could be considered production quality, and should have been bumped up to 1.0 release status. I know that this is the case for OpenSSL, and a lot of other OSS projects out there. The fact is companies and non-hackers don't like adopting software that's advertised as "beta" quality. If you wan't your project recognized in the Real World, step up to the plate.

    I know this sounds like a whining rant, but I belive that the plethora of OSS projects forever stuck in a "beta testing" phase is one reason for hesitation for mainstream adoption of Linux.

    1. Re:Enlightenment is a good example of.... by who+what+why · · Score: 3, Insightful
      There are plenty of 1.0, stable window managers out there. E16 has never gone gold because the developers (i.e. Rasterman) want to turn it into an entire desktop environment, not just a window manager. They launched on a massive rewrite (and then another, and another).

      E has become a place for experimental ideas that just wouldn't be accepted into a more stable project. Check out Rasterman's research into software vs OpenGL hardware rendering for Evas.

      We already have enough stable window managers (especially for use with GNOME and KDE)... The Enlightenment team are working on something new and different, the lack of which is something often lamented around here always complain about in these X discussions. Let them work it out at their own pace, and maybe you'll be blown away by the next release.

  17. Re:Gombine and Gonquer, with XouverG by adrianbaugh · · Score: 3, Insightful

    Asking for consistency between desktop environments is unreasonable. For one thing, it imposes a burden on developers who are ultimately trying to scratch their own itch. For another thing, nobody asks for consistency between MacOS and Windows environments, yet KDE and gnome have no reason to be any more similar than those two. The fact that they both use the same server application (X) is irrelevant - the projects themselves are as different as chalk and cheese (one written in C, one in C++; one using bonobo for IPC, one using something else, one focussed towards strict HIG, one using different UI guidelines etc.) and it is quite remarkable that they coexist as well as they do. If you stick to one or the other then you get consistency, just as you want. If you mix and match, that's your lookout.
    Besides which, have you ever really considered the "consistency" of Windows apps? Internet Explorer has a different feel to Office apps, which in turn are different to apps made by third parties (nobody will convince me that Windows Explorer's CD-burning capability shares anything in terms of look or feel with Roxio CD Creator, or that Excel is consistent with Quattro Pro).

    --
    "'I pass the test,' she said. 'I will diminish, and go into the West, and remain Galadriel.'"
    - JRR Tolkien.
  18. I do. by Z-MaxX · · Score: 2, Insightful

    And, I would guess, many OS X users were seduced by the oh - so - beautiful user OS X user interface. I don't use OS X, but I wish I did, at least, if it was open source. (I need to be able to hack my OS.)

    OS X uses translucency, antialiasing, smooth shadows around windows, window warping, and 'fancy' things like the launcher bar thing (sorry, Mac users, I don't know the name of it!) at the bottom of the screen. Have you ever actually used OS X? Try it. Go to CompUSA or something and play around with a G5.

    Apple's interface makes you forget you're looking at simply a matrix of pixels, which is displaying rectangular regions called 'windows'. The smoothness of everything *far* surpasses anything I have seen in X. I've used KDE, Gnome, Fluxbox, IceWM, and others. I've tried hundreds of themes. I've made my own themes. But I still have no good visual cue where the bounds of the focused window are. The drop shadow is, IMO, a great feature. Your peripheral vision picks up the area of the focused window automatically.

    I could go on and on, but the point is, some people *do* care about having a beautiful desktop. It is also a usability feature and can make a person more productive.

    I spend 70% of my life looking at it, and I want it to be beautiful, dammit.

    --
    Dr Superlove 300ml. I use my powers for awesome