First Xouvert Milestone Released 404
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.)
The things people complain about X... (Score:3, Insightful)
Re:The things people complain about X... (Score:5, Interesting)
Re:The things people complain about X... (Score:3, Insightful)
Re:The things people complain about X... (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.
Re:The things people complain about X... (Score:5, 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.
Re:The things people complain about X... (Score:3, Informative)
That's what's bad about OpenSource. Everyone wants to do the 'kewl' stuff an no one wants to do the grind that many of these projects need. I'm sorry but a hell of a lot of Open Source software just isn't carried out professionally. Yes you can leap in and add all sorts of cool and froody stuff but the boring bits like quality control, documentation etc gets left behind. Where are the code reviews, test suites and the like? It still has the feeling of bedroom hacker development. If I ran my development tea
Re:The things people complain about X... (Score:3, Insightful)
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 f
Re:The things people complain about X... (Score:3, Informative)
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.
Re:The things people complain about X... (Score:4, Informative)
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.
Re:The things people complain about X... (Score:2, Informative)
my experiance lately has been that X id's cards and monitors better the firstime than windows does. [Cntrl]+[alt]+[+} or [cntrl]+[alt]+[-] changes screen resolution on the fly just find on any X you happen to run; in fact when windoser see me do this in Linux, they get envious
Re:The things people complain about X... (Score:2, Funny)
I'd have thought that would be a good thing
Re:The things people complain about X... (Score:5, Informative)
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...
Re:The things people complain about X... (Score:4, Informative)
Re:The things people complain about X... (Score:5, Interesting)
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.
Re:The things people complain about X... (Score:3, Informative)
The ctrl+/- changes the video resolution (the monitor gets a different number of pixels). It does not change the virtual screen (the area that programs think is visible).
Making a way to change the virtual screen, not the video resolution, is what is wanted, and is currently missing.
I am rather annoyed that RandR is so complex. Why couldn't they just send a ConfigureNotify event to the root window? I would think most window managers could be easily rewritten to
Re:Please enlighten me (Score:3, Informative)
offscreen drawing (Score:3, Informative)
Actually, this is isn't correct -- having spent too many years programming video games in the 80s-90s, I'll have a shot at explaining...
You fix the problem of onscreen redraw glitches simply by using double (or triple) buffering - all updates ar
Xouvert is... (Score:5, Informative)
Re:Xouvert is... (Score:4, Funny)
As you see, Xouvert is the Goddess of Open Windows (amongst other things)
Re:Xouvert is... (Score:2)
Re:Xouvert is... (Score:3, Funny)
Just what blog do you think this is?
Funny.... (Score:5, Insightful)
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.
Re:Funny.... (Score:5, Informative)
<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
X is not bloated! (Score:5, Insightful)
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 [handhelds.org].
Re:X is not bloated! (Score:4, Insightful)
Re:X is not bloated! (Score:4, Interesting)
Re:X is not bloated! (Score:3, Informative)
What he's saying is that the source code distribution for XFree86 is way too big. Rather than separate the libraries, X server, applications, and everything else into separate tarballs, they release the entire source tree at once.
Freedesktop is working on splitting the X server out as its own separate release.
Re:X is not bloated! (Score:3, Funny)
One of the most important things here (Score:5, Interesting)
Re:One of the most important things here (Score:5, Funny)
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!
Re:One of the most important things here (Score:2)
Haha! Now I know why javascript is such a bad idea. The only thing I can't figure out, I have my popup blocker in Mozilla disabled, how the hell did they get around it?
Re:One of the most important things here (Score:3, Funny)
Choice is good, here's another alternative. [microsoft.com]
Re:One of the most important things here (Score:3, Funny)
On the same token, some people hate how bloody long it takes to add new features and drivers to X.
And if Xouvert's development model was anything like the Linux Kernel's dev model, then we'd see fairly rapid development, with a very stable tree which has a good release frequency (not too slow, not too fast), and then a dev tree if someone wants to do a daily CVS build. That'd be pretty good.
sounds nice (Score:5, Insightful)
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.
Re:sounds nice (Score:5, Funny)
Re:sounds nice (Score:5, Funny)
Now they just have to rename the project to XMas and everyone will be happy
Re:sounds nice (Score:2)
Thank you, that was about the funniest thing I've read in awhile. :)
Re:sounds nice (Score:5, Interesting)
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.
Re:sounds nice (Score:2, Insightful)
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 &".
Sound apps like esd know nothing about the hardware (well, almost nothing). All they do
Re:sounds nice (Score:4, Insightful)
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.
Re:sounds nice (Score:2)
Why in the world should I start up X just to listen to play an mp3? Hell, I can already use esd to pipe an mp3 from one computer (without X) to another (without X). Thanks, but one more sound server is something we don't need.
Dinivin
Re:sounds nice (Score:5, Interesting)
Re:sounds nice (Score:4, Insightful)
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.
Re:sounds nice (Score:3, Insightful)
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
Re:sounds nice (Score:3, Insightful)
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
Re:sounds nice (Score:2)
Really? How about the command "play"? It is not a gui app, it is a sound app for CLI and it is available whether you are running a GUI desktop or not. You do not need X to use play.
You thus declare that anyone using play from the CLI/non-X interface is invalid use of the system and they MUST use a gui desktop and X to play sounds? There are also other CLI apps for sound that are not in any way tied to X or any desktop. They are not invalid apps if not used in a GUI desktop.
Re:sounds nice (Score:3, Interesting)
Sound apps not needing to know the hardware is no different than X applications not needing to know the hardware when they make xlib calls.
Right now, every system that wants to provide network transparent sound has to reinvent the wheel since no one can agree on the "right" way to do it. Having one chosen as the "blessed" one by Xouert may
Re:sounds nice (Score:4, Interesting)
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).
Re:sounds nice (Score:2)
across network?
Re:sounds nice (Score:2)
If you don't have apps that output sound, then why should MAS waste bandwidth? It's not used! If your app does generate sound and you need to use it remotely then MAS streaming that over the network is surely not a waste of bandwidth, is it?
Comment removed (Score:4, Interesting)
Re:What the Linux and BSD world really needs... (Score:4, Informative)
At least GTK is planning to switch to it, I guess QT as well.
Re:What the Linux and BSD world really needs... (Score:5, Informative)
Linux is going to decimate the desktop world (Score:3, Insightful)
How's this going to work with KDE/gnome etc? (Score:5, Insightful)
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.
Re:How's this going to work with KDE/gnome etc? (Score:5, Insightful)
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
Re:How's this going to work with KDE/gnome etc? (Score:5, Insightful)
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...
Re:How's this going to work with KDE/gnome etc? (Score:2)
I also noticed that it's happy handling mp3 streams. I hope someone with the skills can be pursuaded to do the same for ogg, as streaming my oggs in wav format would impose an unacceptably high network load, and decompressing ogg to wav and re-encoding to mp3 on the fly for streaming would be as obscene a waste of system resources as it would be of sound quality.
Re:How's this going to work with KDE/gnome etc? (Score:2)
So you are happy when you ssh-connect cross a network and run xmms in abosulte silence? I am not happy with that. That's why I applaud arival of sound to networked X windows.
I think esd and arts will collapse to sound event dispatchers for legacy applications (those, which do not speak MAS API).
Re:How's this going to work with KDE/gnome etc? (Score:2)
Much like esd and arts already do. Great, they've just reinvented the wheel.
Dinivin
MAS or NAS (Score:3, Interesting)
is MAS anything like NAS? is it compatable?
Sound server? Why not use ALSA's own native Dmix ? (Score:5, Interesting)
Read this [alsa-project.org] or this [opensrc.org] for more info.
Death to ESD/ARTS today!! (and maybe even JACK, if we can low enough latency).
Sunny Dubey
Re:Sound server? Why not use ALSA's own native Dmi (Score:2)
However, Jack is useful if you need syncing several sources : jack is not a mixer (but can host one), it's a high end synchronisation framework.
The ouput of jack is often alsa, but could be ardour for example. How can you do that with dmix ?
Re:Sound server? Why not use ALSA's own native Dmi (Score:2)
JACK can be a 'pipe' for audio applications - so you can have an mp3 player and an effects processor and you can pipe the audio from one to the other. It allows them to access the sound HW also, but that's not the main feature.
Dmix seems to be focused on accessing the sound device, although with nice additions, e.g. sample rate conversion, which is handy if you use the digital I/O of your card and want to play something other than 44.1/48 kHz files.
Dmix/Jack (Score:4, 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...
MAS and ALSA / OSS (Score:2)
Re:MAS and ALSA / OSS (Score:2, Informative)
Im not certain, can someone verify?
Who really wants all that garbage? (Score:3, Insightful)
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.
Re:Who really wants all that garbage? (Score:5, Insightful)
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.
X Sound server (Score:2)
So what I am wondering is whether or not this new sound extension will work across the network?
Can I log into my machine from another and have the sound come with it?
This could be a serious step forward for projects like LTSP that rely on kludges to get network-transparency for sound..
Improve X? Yes , but only its colour system. (Score:2)
my venerable Xlib programming reference when I'm writing an app that requires liberal use of sophisticated colour. Read only , read write colourmaps etc, all these different types of
visuals , Oh My God , who the hell designed this colour system?? Why the hell do I need a visual? Just give me colour X or the nearest equivalent , I don't give a damn HOW many colours
Enlightenment release (Score:3, Insightful)
uh... that was over a month ago [enlightenment.org], on November 5th. It was a good little bugfix release, though.
Arch (Score:3, Informative)
Does anyone know if you have to create individual UNIX user accounts for Arch users as you do with CVS? I've always hated that about CVS.
Re:Arch (Score:3, Interesting)
There's a project called "tla-pqm" that makes an attempt at solving this. The developers can email a merge request to a tla-pqm server somewhere, and the server will grab the requested changesets and apply them to its archive. It's like
Enlightenment is a good example of.... (Score:5, Insightful)
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.
Re:Enlightenment is a good example of.... (Score:3, Insightful)
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 [slashdot.org] for Evas.
We already have enough stable window managers (es
X-MAS (Score:3, Funny)
Just in time for X-MAS. How convenient.
Re:just what we need... (Score:2, Informative)
Re:just what we need... (Score:5, Informative)
Re:just what we need... (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
Re:Humble Dev's Request (Score:2, Insightful)
Re:Humble Dev's Request (Score:2)
if your project does not adhere to the old protocols exactly it's of no use to me, or a large number of other people/businesses.
Can I connect from a X server to a Xovert server and run remotely?
Re:Humble Dev's Request (Score:2)
Re:Humble Dev's Request (Score:2, Informative)
Please mod parent DOWN. (Score:5, Informative)
Have a read through some of his previous posts on other topics. [slashdot.org]
Thanks.
Re:Humble Dev's Request (Score:2)
Never trust anyone with a slashdot ID = 150,000
What about slashdot ID == 150,001?
What about slashdot ID == 149,999?
Aaaaaa, fuck slashdot.
(cheesiest post I ever made)
Re: (Score:2, Insightful)
Re:MAS, networked sound ?!?!? (Score:3, Interesting)
As for playing sound "fast", all you really want is minimal lag between sound being queued on the server and being put out on the speaker. The main problem there is network lag during congestion; I guess that could partially be offset by (a) a good, switched network and/or (b) QoS providing audio with a higher priority.
Re:MAS, networked sound ?!?!? (Score:5, Informative)
Check their website (Score:4, Informative)
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".
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.
Re:MAS, networked sound ?!?!? (Score:2)
Re:Gombine and Gonquer, with XouverG (Score:2)
Yes, it means "stagnation". Windows is a good example: a lousy GUI that will remain lousy forever because it has to be "consistant". No experimentation means no progress.
Given that most people use only one word processor, one browser, one email client etc. the consistancy argument is no more rational than insisting that your TV should have the same controls as your car.
TWW
Why Linux needs a standard GUI toolkit (Score:2, Insightful)
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 stand
Re:Gombine and Gonquer, with XouverG (Score:4, Insightful)
Wether someone runs one or onehundred word processors is absolutly irelevant to the GUI consistency discussion.
Re:Gombine and Gonquer, with XouverG (Score:4, Insightful)
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).
Re:Gombine and Gonquer, with XouverG (Score:2)
Windows seem somewhat consistent because the widget sets people try to look relatively close to the "official" look, but that make differences in behaviour even more annoying - should I use Alt+F4 or Ctrl+W to close an application window, for instance? Th
QT is available under the gpl (Score:2, Informative)
http://www.trolltech.com/products/qt/freelicens
Re:QT is available under the gpl (Score:2, Informative)
Re: warning to ACs, post AC means Ashcroft at door (Score:2, Informative)
It's all well known about, and well documented. The idea of the AC account is that nobody knows who you are, but admin can always find out things anyway (stuff
Re: warning to ACs, post AC means Ashcroft at door (Score:2, Insightful)
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."