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.)

48 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 Anonymous Coward · · Score: 3, Informative

      Oh dear. It can change resolutions on the fly; it's called the XRandR extension and has been in XFree86 for a while now.

      Secondly, users don't need to know their refresh rates. Almost all major distros include an X setup tool, and even "X -configure" does a decent job.

      Try to get out more, instead of repeating lies on Slashdot. It's not healthy.

    2. Re:The things people complain about X... by 10Ghz · · Score: 5, Interesting

      We don't complain about X, we complain about Xfree.

      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    3. Re:The things people complain about X... by SQLz · · Score: 5, Informative

      Well, you could have read the Xouvert FAQ before posting to educate yourself on what they actually plan on improving. That way, you wound't sound like you have no idea what you are talking about. Anyway, from the FAQ:

      2.5) So why is X so slow on my machine if not for network transparency?

      Yes, XFree86 /can/ be slow, especially on uniprocessor machines, but network transparency is NOT at fault. More common culprits appear to be toolkits, video drivers, and font rendering/render. Render really needs to DMA driven. Right now it pulls bits from the framebuffer using the CPU which with PCI is abysmally slow.

    4. 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
    5. Re:The things people complain about X... by Viol8 · · Score: 4, Informative

      "Changing resolution on the fly springs to mind as one thing it cant do"

      Thats strange , because I've been able to do ctrl-alt-+ and ctrl-alt-minus to change the resolution ever since linux 1.2 days...

    6. Re:The things people complain about X... by mark_lybarger · · Score: 4, Informative

      informative, sure. but... you fail to mention that this feature requires support of the window _managers_ to be able to use this feature. to use this in kde you're gonna need 3.2 which is still in beta. i'm not quite as familiar with other window managers, but last i looked into this, there weren't ANY that let you resize your desktop on the fly similiar to right clicking on the desktop, thenchoosing "resolutions", then selecting something different than the one you're using, and giving you and option to try out the new one.

      IIRC, xrandr has been in xfree since the 4.3 series, which i suppose you could consider "a while now". this version of the server which was released 27 Feb of 2003. are the wm's slow to implement this feature? this is a feature Microsoft has had for 8 years now.

      while XFree86 _is_ nice, it seems very cumbersome to change. there's probably a small list of feature requests from the user community out there, and they're not getting implemented.

      when you tell the truth, be sure to give the whole story.

    7. Re:The things people complain about X... by Tyler+Eaves · · Score: 3, Informative

      That's chaning the sixe of the screen, not the desktop. It's a big differeence.

      --
      TODO: Something witty here...
    8. Re:The things people complain about X... by mark_lybarger · · Score: 5, Interesting

      why, oh why does this ctrl-alt-+ ctrl-alt-minus keep coming up everytime someone mentions they want to change their desktop resolution?

      to a user, this doesn't change the resolution. it seems more like a zoom in, zoom out feature. great if you need to zoom in/out. but if you want to change resolution, you're not going to find it here. a user would want to be in a 1024x768 resolution, have a browser window maximized, and change the resolution to 800x600 and still see that window maximized (and have that entire window displayd on the monitor w/o having to move their mouse around).

      maybe XFree86 could go a step further than implementing a Microsoft change resolution feature. give the ability to have different resolutions on different virtual desktops. that's where it gets close to window manager implementation to me. it would be nice to have one virtual desktop with 800x600 resolution, and one with 1024x768 or what ever the user prefereances are. it would be nice if XFree86 could give each window the ability to be shown it its own resolution.

  2. Xouvert is... by roalt · · Score: 5, Informative

    For the non-french speaking under you: Xouvert means "X open".

    1. Re:Xouvert is... by Anonymous Coward · · Score: 4, Funny

      While you are right in the literal translation, did you think about RTFA ?

      As you see, Xouvert is the Goddess of Open Windows (amongst other things)

    2. Re:Xouvert is... by sharkey · · Score: 3, Funny
      did you think about RTFA ?

      Just what blog do you think this is?

      --

      --
      "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
  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.

    1. Re:Funny.... by POds · · Score: 4, Informative

      Well to quote:
      <quote>
      Eugenia (IP: ---.osnews.com) - Posted on 2003-12-09 01:21:59
      Xouvert: XFree86 fork with some code cleanups and addition of patches that the xfree86 guys were snobbing.

      freedesktop.org's X: Re-write of the core of their server (not a fork), rewrite of some of the extenstions, while reusing some xfree86 code mostly for some other extensions and drivers, but overall a new thing.

      Xouvert would be interesting to serve as the "middle man" towards the migration to fdo's X.
      </quote>

      So yes you'r right. I read on freedesktop.orgs site, or maybe it wasnt, and maybe it was old, but the server only needed less than 800k To run or it was of that size. Their server so far requires a compile for you to configure it as there are no configuration files. That alone i feel would cut out some bloat. The freedesktop.org promises a lot more i believe where as this one we're talking about just imporves on the current X server. But, any improvments are welcome ones.

      Thanx for the text Eugenia

      --


      Giving IE users a taste of their own medicine since 2005 - http://pods.-is-a-geek.net/
  4. Re:just what we need... by noselasd · · Score: 4, Informative

    Uhm, there are actually not that many X servers. It's not like windowmanagers or anything like that. Besides , the goal of Xouvert is to get their changes back to XFree

  5. One of the most important things here by James_Duncan8181 · · Score: 5, Interesting

    Xouvert represents far more then merely tranparent windows etc, it represents a move to a more recognisable OSS model of working. XFree86 is charterised by a fairly closed development process, long patch intergration times, and close control by the steering group. I am greatly looking forward to seeing a true open source methodolgy accelerate development.

    --
    "To any truly impartial person, it would be obvious that I am right."
    1. Re:One of the most important things here by evilviper · · Score: 5, Funny
      long patch intergration times, and close control by the steering group. I am greatly looking forward to seeing a true open source methodolgy accelerate development.

      Yeah, me too. I always hated how mostly stable XFree86 is, and how I don't have to upgrade every week to the lastest version. Thank goodness someone figured out a solution to that problem!
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    2. Re:One of the most important things here by sharkey · · Score: 3, Funny
      I always hated how mostly stable XFree86 is, and how I don't have to upgrade every week to the lastest version. Thank goodness someone figured out a solution to that problem!

      Choice is good, here's another alternative.

      --

      --
      "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
  6. 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 popeyethesailor · · Score: 4, Funny

      I cant believe they dont have a web browser and email client in it yet.

    2. Re:sounds nice by axxackall · · Score: 4, Interesting
      Do we really need ANOTHER soundserver in addition to esd and arts?

      We haven't needed esd and arts from the first place if sound would be handled by X since the beginning.

      Because that's what X is supposed to do - to isolate window managers, desktop managers and just applications from any knowledge about hardware. Gnome or KDE should just fire the sound event, not actually handle it.

      I hope that at some point Gnome and KDE developers will drop their "proprietary" sound servers and just send sound events in a same way as they now do with graphics events. THEN perhaps Gnome and KDE will have more available human resources to *focus* on improving the usability and configurability of their applications.

      --

      Less is more !
    3. Re:sounds nice by boaworm · · Score: 5, Funny

      I am really happy that MAS in Xouvert now

      Now they just have to rename the project to XMas and everyone will be happy :-)

      --
      Probable impossibilities are to be preferred to improbable possibilities.
      Aristotele
    4. 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 !
    5. 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.
    6. Re:sounds nice by t_hunger · · Score: 5, Interesting

      The idea is that you start up MAS instead of whichever Networking sound solution you are using now. MAS is a stand alone server taht can run without X... in fact there are others you could use, but then MAS was developed with professional audio and video conferencing in mind (both needing low latencies) and MAS is has a solid suport from the X consortium behind it. Both are thing I most alternatives can not claim for themselves.

      --
      Regards, Tobias
    7. Re:sounds nice by Nicolai+Haehnle · · Score: 3, Interesting

      The statement about being anti-Unix is very unwise.

      What if the creators of Unix back around 1970 had had terminals with built-in speakers? How high do you think are the odds that they wouldn't have included audio into the concept of a computer terminal?
      I bet you almost anything that we'd have a stdpcm in ISO C today.

      It is absolutely ridiculous that the concept of a terminal only contains the lowest common denominator of text input and output. You should think of the terminal as an interface to the user. It logically follows that all kinds of other devices can become part of an interface, depending on the situation.
      Obviously, sound in/out can be a part of an interface. A USB port or a DVD drive could be part of an interface. After all, the one who physically "sits" at a device should automatically be able to control it (yes, there are exceptions, such as computer pools - the keyword is "exception", though). This would automatically eliminate all those ugly permission hacks that are necessary today, by the way.
      One could even imagine an interface that consists of only sound in/out *without* any form of text or video interface (e.g. interface for the blind).

  7. What the Linux and BSD world really needs... by jcr · · Score: 4, Interesting

    ..is an answer to Apple's Quartz 2D rendering capabilities.

    Linux isn't going to make a dent in the desktop world until it's significantly better than MS windows, not just politically, but in ease of use, quality of rendering, integration, etc, etc.

    Linux already does OpenGL. Take the next step; Apple's already shown you what to do.

    -jcr

    --
    The only title of honor that a tyrant can grant is "Enemy of the State."
    1. Re:What the Linux and BSD world really needs... by jcupitt65 · · Score: 4, Informative
      You're thinking of Cairo. It's a postscript-style graphics model for X/paper/etc., with the X backend based on XRender.

      At least GTK is planning to switch to it, I guess QT as well.

    2. Re:What the Linux and BSD world really needs... by Spy+Hunter · · Score: 5, Informative

      Already in progress at Freedesktop.org, thanks to the awesome Keith Packard. There's Cairo for vector graphics rendering and some unnamed project for double buffered/transparent/warpable windows (and yes there are screenshots, click the link!). Freedesktop.org is rapidly becoming host to many projects that are innovating in the Linux desktop arena. Check out some of the other software hosted there. Of particular interest (to me at least) is D-BUS combined with HAL.

      --
      main(c,r){for(r=32;r;) printf(++c>31?c=!r--,"\n":c<r?" ":~c&r?" `":" #");}
  8. 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
  9. 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
    2. Re:X is not bloated! by swv3752 · · Score: 3, Interesting

      My old Agenda VR3 had a total of 8mb RAM and 16mb Flash- 13mb for the kernel and all programs. It ran XFree86 and FLTK. It was plenty speedy and never had a memory problem.

      --
      Just a Tuna in the Sea of Life
  10. Sound server? Why not use ALSA's own native Dmix ? by phoxix · · Score: 4, Interesting

    The subject pretty much says it all ...

    Read this or this for more info.

    Death to ESD/ARTS today!! (and maybe even JACK, if we can low enough latency).

    Sunny Dubey

  11. Please mod parent DOWN. by reality-bytes · · Score: 5, Informative

    As said before this guy appears *not* to be a Dev on the Xouvert project.

    Have a read through some of his previous posts on other topics.

    Thanks.

    --
    Ripping an new rectum in the fabric of spacetime.
  12. Re:MAS, networked sound ?!?!? by t_hunger · · Score: 4, Informative

    I've seen MAS demoed on a couple of shows already and I did like what I saw. They are aiming for professional quality sound delivery with extremly low latencies which definitly is a good thing. MAS of course is network transparent of course, but the network is just another input-/output device to MAS (like a soundcard), you don't have to use it for local playback. It is a handy feature though: You can pipe your sound to an effects mashine for processing, something that might come in handy in a professional environment.

    --
    Regards, Tobias
  13. Check their website by mendred · · Score: 4, Informative

    I think the following should settle your fears.

    From their site

    "Many of the visually impaired have finely tuned auditory sensibilities, allowing them to react quickly to sound. From its beginning, MAS was designed to handle timing issues exceedingly well. It was optimized to provide tight synchronization of multiple media streams. More importantly, for users dependent on audio cues, it is designed to stop some functions and start others quickly. For example, a user, hearing the opening syllables of a menu option, can either select it or move to another option without waiting for a complete articulation of the option. MAS's original accessibility requirements, developed with leading accessibility authorities, included:

    * Ability to stop utterances quickly
    * Controllable low latency
    * Format independent media handling
    * High audio quality
    * Multiplexing--with priorities
    * Small memory footprint
    * Synchronization of multiple media stream

    "MAS enables low-latency Internet conferencing and telephony. Automatic bandwidth measurements and MAS's dynamically-switchable CODECs insure that the conference quality scales from 56K modems to T1 lines".

    "MAS integrates with a compatible X11 server on your desktop. It processes graphic information locally, alleviating the need for network transmission of uncompressed graphical content. Graphic events are easily synchronized with audio events for professional-quality multimedia and accessibility-enabled applications."

    "MAS handles network-distributed media processing and intricate format configuration tasks. It continually measures system performance and adjusts its actions depending on the available system resources. The longer it runs, the better it knows your system".

    //end direct quote from site.

    Obviously this has been designed for performance/scalability.Of course the real trial is actually running it for yourself but give it a chance before you write it off.

  14. 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
  15. 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?
  16. 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.

  17. 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.

  18. X-MAS by Tin+Foil+Hat · · Score: 3, Funny

    Xouvert includes MAS giving the X server its very own sound server.

    Just in time for X-MAS. How convenient.

    --
    No matter how many of my rights are taken away, somehow I still don't feel safe. -Frigid Monkey
  19. 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.
  20. Dmix/Jack by po8 · · Score: 3, Interesting

    You have correctly identified the competition to MAS: JACK. Some of my colleagues and I have been wondering aloud whether one could build a nice interface to JACK for network audio. It looks like the answer is yes.

    As you correctly note, the real issue is latency. Servers like MAS cannot generally promise reasonable latency on the local side: latency matters there (indeed, it's all that matters).

    Dmix looks cool too, but as folks have pointed out, it's going to be tough to get it to work with the range of systems X runs on. Unless it's optionally layered atop JACK...