Beta

Slashdot: News for Nerds

×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Proof-of-Concept Port of XBMC to SDL 2.0 and Wayland

Unknown Lamer posted about a year ago | from the now-with-more-bling dept.

GUI 81

hypnosec wrote in with news that XBMC has experimental Wayland support now. Even better, it's implemented by porting XBMC to SDL 2.0, something that will become important as SDL 1.2 development officially ended and SDL 2.0 should be out in the wild in the not-too-distant-future. The code is only a few days old and has a few serious limitations (input is broken and a bug in weston with threaded clients causes rendering hangs) , but it seems like a pretty good start. The port should also bring SDL 2.0 support to the X11 backend.

cancel ×

81 comments

WHAT (4, Insightful)

Anonymous Coward | about a year ago | (#43127317)

What is XBMC?
What is SDL?
What is Wayland?

FFS TFS needs some TLC.

Re:WHAT (5, Informative)

dead_user (1989356) | about a year ago | (#43127417)

XBMC = XBox Media Center - http://xbmc.org/ [xbmc.org] SDL = Simple DirectMedia Layer - http://www.libsdl.org/ [libsdl.org] Wayland = http://wayland.freedesktop.org/ [freedesktop.org]

Re:WHAT (0)

Anonymous Coward | about a year ago | (#43127495)

You mean XBMC Media Center.

Re:WHAT (1)

Stalks (802193) | about a year ago | (#43127505)

No, he meant Xbox Media Center.

I don't care that they ridiculously changed themselves to an abbreviation, it started as Xbox, and as far as I'm concerned, shall remain as.

Re:WHAT (1)

Lars Op den Kamp (2827885) | about a year ago | (#43129945)

We don't even support the Xbox any more. So "XBMC Media Center" is correct

Re:WHAT (1)

saihung (19097) | about a year ago | (#43130873)

Recursive project acronyms are SO 1996.

Re:WHAT (0)

Anonymous Coward | about a year ago | (#43135347)

Xbox Media Center is equally correct for the purposes of informing the uninitiated. It is actually more informative than the current, technically correct, XBMC Media Center.

Re:WHAT (5, Informative)

PineHall (206441) | about a year ago | (#43127451)

What is XBMC? What is SDL? What is Wayland?

FFS TFS needs some TLC.

XBMC [xbmc.org] is a "software media player and entertainment hub for digital media".

SDL [libsdl.org] is Simple DirectMedia Layer and "is a cross-platform multimedia library designed to provide low level access to audio, keyboard, mouse, joystick, 3D hardware via OpenGL, and 2D video framebuffer".

"Wayland [wikipedia.org] is a computer display server protocol and a library for Linux implementing that protocol."

Re:WHAT (1)

HiThere (15173) | about a year ago | (#43128389)

SDL is also System Description Language, and probably several other things. I suspect that XBMC may really be unique, at least within the field of computers, and Wayland also, but a tiny bit of description for each (perhaps with a link) would not have been amiss.

Re:WHAT (0)

Anonymous Coward | about a year ago | (#43127461)

Re:WHAT (-1)

Anonymous Coward | about a year ago | (#43127513)

Wrong. The article should have been written as if it were introducing the concepts to an uninitiated reader.

Re:WHAT (3, Informative)

Anonymous Coward | about a year ago | (#43128073)

wrong, this is slashdot, not the sunday paper

Re:WHAT (1, Insightful)

Lumpy (12016) | about a year ago | (#43127507)

Because the average slashdotter is so new to the internet that they dont know what Google is for? Really?

Re:WHAT (0)

Anonymous Coward | about a year ago | (#43127569)

Seriously? I think you might be trolling, but surely the vast majority of ./ knows what these things are. It's not like the summary is about a physics article with a bunch of specialised terminology.

You _must_ be new here, welcome.

Re:WHAT (1)

jedidiah (1196) | about a year ago | (#43127803)

I suspect the OP was being sarcastic and indirectly pointing out the key missing piece there that everyone seems to have forgotten. It's one of those key things that Wayland people in general tend to forget when they are pushing Wayland and bashing X.

Rendering the UI is really the least of your worries.

Re:WHAT (1)

Walzmyn (913748) | about a year ago | (#43127837)

I'm glad I'm not the only one. Seems like every third article on /. I have to run to Wikipedia just to figure out what piece of software or what abbreviation someone's blabbering about.
It's like trying to read a forum for a game you're not familiar with.

Re:WHAT (1)

Anonymous Coward | about a year ago | (#43127877)

No, FFS you need to GTFO /.

  If you don't know what XBMC is, don't come onto a comment board to ask. If you want to stay at slashdot and learn what XBMC is, click on any of the previous story links or type that term in the search box. Asking is kind of rude because it diverts the discussion to the place it is now.

Slashdot doesn't need to handhold and add citations everywhere for what are actually common terms in submissions. You should mostly know what XBMC is, as it makes the front page every few months when things like the apple TV are jailbroken to run it or android gets a new app, or someone ports it to the raspberry pi.

But the best thing for you to do is to type XBMC into Google or wikipedia. Those are places to learn new things. Just get in the habit of researching things for yourself, it's a useful skill. Learned Helplessness [wikipedia.org] is not a skill.

Come back to slashdot when you can contribute to the discussion or at the very least make a joke about lonliness or hot grits or something.

Re: WHAT (0)

Anonymous Coward | about a year ago | (#43127963)

Really? I'm not a gamer. Not at all. Not judging anyone who is, but it just isn't my thing. So why the fuck should I know what XBMC is to be able to read /.? The Linux references were familiar but not the XBox reference.

Neither link in TFS mentions what any of these things are (XBMC, SDL, Wayland, Weston or X11) so I can understand the OP's frustration. I realize that I will have to RTFA to learn about new things, but if I have to google everything related to a story then the authors of TFA are not doing their jobs.

As for the XBMC requirement to read /., YCKMFAASWISIYM.

Re: WHAT (2)

BLKMGK (34057) | about a year ago | (#43129097)

So what you got out of this is that XBMC has something to do with games?! You might better hit the search engine again

Re: WHAT (0)

Anonymous Coward | about a year ago | (#43134057)

Fine. Come to slashdot whenever you wish, but only contribute to a discussion if you know what the subject is. Not an ultimatum or a decree in any way, but common sense and good manners. I don't have much of a background in physics, so I'm not going to the Higgs-Boson thread saying "HEY GUYS EXPLAIN ALL PHYSICS TO ME". And then promptly disappearing.

This whole thing was a troll, by the way,

Re:WHAT (1)

loufoque (1400831) | about a year ago | (#43128017)

Who are you, and how can you be this new?

Re:WHAT (0)

Anonymous Coward | about a year ago | (#43128221)

s/new/old/

Those of us old enough to have sub-6-digit UIDs can't be arsed to keep up with the newfangled acronyms that you young whippersnapper 7- and 8-digiters use.

Write out the acronyms and explain how they're important, or get off my lawn.

Re:WHAT (1)

snakeplissken (559127) | about a year ago | (#43128961)

what is ffs?
what is tfs?
what is tlc?

Re:WHAT (0)

Anonymous Coward | about a year ago | (#43129479)

FFS: Ferrite Field Semiconductor, or Facial feminization surgery, or Fertility and Family Survey, or anything else For Fuck Sakes.
TFS: Terrabyte File System, Telecommunication Field Study, or Team Foundation Server
TLC: Telemetry Logistic Control, or The Learning Channel or Time Long Count ...The thing about abbreviations is that is always perfectly ok to make shit up on the fly, and no one can dispute your version because, abbreviated, its all ok, because whatever B.S. you dream up can be abbreviated.

Re:WHAT (0)

Anonymous Coward | about a year ago | (#43129689)

Define hoe-down. Define dancing.

And what is SDL? (0)

Anonymous Coward | about a year ago | (#43127379)

Is that good?

Re:And what is SDL? (1)

PineHall (206441) | about a year ago | (#43127399)

SDL [libsdl.org] stands for "Simple DirectMedia Layer" and "is a cross-platform multimedia library designed to provide low level access to audio, keyboard, mouse, joystick, 3D hardware via OpenGL, and 2D video framebuffer."

Re:And what is SDL? (-1)

Anonymous Coward | about a year ago | (#43127531)

No, like every open source project, it never works the way you want.

Re:And what is SDL? (1)

godrik (1287354) | about a year ago | (#43127773)

Wow, there are really people on slashdot that do not know what SDL is?

Re: And what is SDL? (1)

madprof (4723) | about a year ago | (#43127825)

Why should everyone know what SDL is? You assume it is relevant to everyone.

Re: And what is SDL? (1)

godrik (1287354) | about a year ago | (#43128001)

It is frequently mentionned on slashdot. Many emblematic games when they are ported to new architectures are ported by porting SDL on the new architecture.

Wise use of time and effort? (-1, Troll)

fnj (64210) | about a year ago | (#43127445)

We just had a story Monday that Wayland is deader than a doornail. Kinda makes this a waste of time and effort.

Re:Wise use of time and effort? (2)

EmperorArthur (1113223) | about a year ago | (#43127537)

Really? I thought the story was "Ubuntu team declares interoperability and standards are for losers."

Re:Wise use of time and effort? (0)

Anonymous Coward | about a year ago | (#43127605)

I thought the story was "Ubuntu ventures to contribute more code to the free software world, while walking their own path, which is the freedom they have in the free software world" Free, Free, Freeeeeeeeeeee

Re:Wise use of time and effort? (4, Insightful)

serviscope_minor (664417) | about a year ago | (#43128257)

Wayland is not an interoperable standard.

You've got ubuntu wanting Mir.

You've got Fedora wanting Wayland.

And everyone else uses X, the ancient legacy (and therefore old bad crufty and slow---even though it can run happily on a Sun 3/60) display server that inexplicably has cool features that the others lack. But that's OK because we keep being told how no one uses those features anyway.

X is the interoperable standard, and frankly much better.

Re:Wise use of time and effort? (0)

Anonymous Coward | about a year ago | (#43128459)

Untrue. Wayland is developed by the X.org developers, the main guy used to work for Red Hat, but now works for Intel.

Re:Wise use of time and effort? (0)

rahvin112 (446269) | about a year ago | (#43128641)

You can run X on top of wayland. The misinformation and misunderstanding of what wayland is and what it's trying to accomplish is astounding given the information is a click away. I suggest you visit LWN and consult Corbet's two articles on the subject and educate yourself about what wayland is and what it's trying to accomplish. Wayland is likely to replace X as the default desktop in every distribution and in fact almost every distribution has already announced plans to migrate when it's ready. Remember, you can still run X on top of Wayland.

Re:Wise use of time and effort? (0)

Anonymous Coward | about a year ago | (#43129317)

The problem is that it will soon not work by default anymore. Unfortunately, this is the direction Linux is headed. Dumb everything down and remove all powerfull features. These idiots break decades of backward compatibility for no good reason. And yes, one will be able to install X on top of Wayland. One can install X on top of windows too. It sucks.

Re:Wise use of time and effort? (0)

Anonymous Coward | about a year ago | (#43129425)

Yes, in the same way you can run X on top of Quarts/OS X and on the Windows display manager. The reason people are complaining is that apps will stop running over X11 when they have been ported to Wayland.

Until there is a clear roadmap for Wayland network transperancy people will keep on complaining. The best from efficiency reasons would be to do this in the widget toolkits, I.e.in GTK and Qt, but since no one is doing this, people will keep on complaining, and idiots who have not understood the problem will keep on bitching about X11 being able to run ontop of Wayland.

Re:Wise use of time and effort? (4, Insightful)

serviscope_minor (664417) | about a year ago | (#43129781)

You can run X on top of wayland. The misinformation and misunderstanding of what wayland is and what it's trying to accomplish is astounding given the information is a click away.

Touche.

You can run X on top of anything. That really means very little: you can run it on top of OSX and Windows too. You can't remote Windows or OSX apps using X11 and X11 apps on OSX and Windows are second class citizens: copy/paste is non functional beyond plain text and DnD does not work. Furthermore, you cannot manage the native windows with an X11 Window Manager.

Make no mistake: X11 on Windows and OSX is a poor user experience and it wil be the same on Wayland for the same reasons.

Remember, you can still run X on top of Wayland.

Stop saying that. It's an idiotic think to keep saying because whit true, it is entirely deceptive.

Re:Wise use of time and effort? (1)

blade8086 (183911) | about a year ago | (#43131701)

All excellent points -

relatedly, noone is developing or releasing X windows applications *targeted* at these other platforms -
which is the same 'position' X will be in in this 'run x on wayland' world - further implying that over time
less and less applications will run on X, further implying that over time network transparency will
decrease more and more (since only the new firefox or libreoffice or whatever major software decides not to support X),
so this is a bad *direction* to be headed in.

I have no problems rearchitecting the X server infrastructure to have a fast low layer, and a simplified api talking
to this layer (that remains X, and therefore network-multiclient compatible), which is what most of the (non developer weenie)
people complaining about so-called 'crufty x' are talking about -

but don't !@#$ ruin out of ignorance and shortsightedness the good things in X because of the bad - fix the bad, and
make it compatible with what is.

ditto systemd, dbus and all of that stuff.

dbus? why not just f!@#$ing use the 127.0.0.1 loopback or require setting up a private multicast network????

nono, we need some crappy daemon writting using the hairball that is GLib-object-C being tied into *everything*
on the system.

derp derp derp.

Re:Wise use of time and effort? (1)

serviscope_minor (664417) | about a year ago | (#43132481)

people complaining about so-called 'crufty x' are talking about -

People also love whinging about the old drawing code. The stuff from 1987 which must take *kilobytes* of code space and reqiure hundreds of hours of absoloutely no maintainance whatsoever.

nono, we need some crappy daemon writting using the hairball that is GLib-object-C being tied into *everything*
on the system.

And now we need systemd as well, so the whole lot is tied together with a poorly documented weird-ass daemon which provices little of use except complexity.

Re:Wise use of time and effort? (0)

Anonymous Coward | about a year ago | (#43129469)

And everyone else uses X, the ancient legacy (and therefore old bad crufty and slow---even though it can run happily on a Sun 3/60) display server that inexplicably has cool features that the others lack.

And when X crashes you lose any applications that were open at the time. Not to mention X rapes the CPU when doing something as simple as dragging a window around the screen. Of course, being servitroll_major, you will deny that X crashes from time to time.

Re:Wise use of time and effort? (0)

Anonymous Coward | about a year ago | (#43129771)

I'm sorry but focusing on "when X crashes" really is being unfair.

More likely, your window manager or desktop environment is crashing, causing the X session to be terminated and re-start.

X crashes are incredible rare for me on a wide variety of systems. There's nothing inherent in the X implementation or fundamentally bad about it that gives me any cause to assume Wayland etc. will be any more reliable.

Re:Wise use of time and effort? (1)

blade8086 (183911) | about a year ago | (#43131651)

Because when the wayland display manager crashes, you don't lose any applications at the time? or explorer.exe? or QuartzCompositor or whatever its called on osx, etc?

what is the point of this post?

are you saying that the single-process managing X displays is less stable than the single process running these others?

umm.. because if you are, you are probably wrong.
and if you're not, you're not making any sense.

Re:Wise use of time and effort? (0)

Anonymous Coward | about a year ago | (#43128313)

So, Ubuntu is cooperating with Wayland... Because that's exactly what Wayland is doing.

I'm more excited by emulator support :-) (2)

BLKMGK (34057) | about a year ago | (#43127479)

http://forum.xbmc.org/showthread.php?tid=146711 [xbmc.org]

NES, SNES, MAME, and others. I'll admit Wayland and SDL are interesting but my hardware already runs XBMC fine using VDPAU and I'm more excited about getting the ability to run games vs a different display technology...

Re:I'm more excited by emulator support :-) (0)

Anonymous Coward | about a year ago | (#43128419)

Excite to play only homebrew games, right?
Otherwise that would be a double-standard in the Slashdot community, where software is sacred.

Re:I'm more excited by emulator support :-) (1)

BLKMGK (34057) | about a year ago | (#43129111)

Or perhaps where people who's hardware console has died or who no longer have room for arcade machines but still wish to enjoy the software could enjoy them yes. I'm okay with double standards too occasionally, especially for things that are no longer supported or produced. Emulate say a PS3 and yeah, I think I'd have some issues with that.

Good to see XBMC is adopting more widely used libs (0)

Anonymous Coward | about a year ago | (#43127541)

At first it made sense not using X.org since it's such a terrible mess. But the XBMC developers were being silly trying to keep the dependencies down by doing it all in house. Either SDL or Wayland or both should have been used much earlier...
Hopefully now we'll get the sluggishness out of the GUI's rendering on 1080p in small embedded machines.

Re:Good to see XBMC is adopting more widely used l (1)

Unknown Lamer (78415) | about a year ago | (#43128245)

Have you tried setting the dirty regions option [xbmc.org] ? For whatever reason the default re-renders the entire screen 60 times per second... but you can flip it to only updating when regions are damaged. Once I flipped that on I was able to use xbmc alright on my ancient athlon.

Re:Good to see XBMC is adopting more widely used l (1)

BrokenHalo (565198) | about a year ago | (#43129361)

At first it made sense not using X.org since it's such a terrible mess.

What people usually mean when they say xorg is a mess (without any qualification or substantiation) is that they're bored with it. In reality, xorg is pretty damn powerful: it has a hell of a lot to do, and on the whole it does it remarkably well.

Re:Good to see XBMC is adopting more widely used l (1)

Eunuchswear (210685) | about a year ago | (#43129949)

In reality, xorg is pretty damn powerful: it has a hell of a lot to do, and on the whole it does it remarkably well.

FFS it works on my phone. I don't see what problem people have with poor old X.

Translation (1)

Sir or Madman (2818071) | about a year ago | (#43127557)

Somebody ported some code and it's buggy and it's just another day on da net!

"Proof of Concept" (3, Interesting)

timeOday (582209) | about a year ago | (#43127831)

This is a "proof of concept" in the same way that turning over a shovelful of dirt is a proof of concept for digging a basement. The "concept" isn't at issue; it's all the gruntwork and polish that would be required to make it good enough to displace what's already out there and working. With software, the first few function points appear to solve the crux of the problem, but unfortunately the vast majority of function points still remain and each is just as time-consuming, yet less rewarding, than the first few.

A good idea (3, Interesting)

Eravnrekaree (467752) | about a year ago | (#43127845)

It is always a good idea to use a platform independant library to make porting between different platforms easier. Now that it is working on Wayland, one hopes that Ubuntus plans to fracture the Linux ecosystem can be averted. One thing that people need to remember about the situation situation with Canonicals arrogant plan to attempt a coup d'etat of the Linux graphics stack, is that unlike the window manager where choice is a good thing, having a lot of competing window systems is NOT a good thing. Lets imagine that Canonical announced that it would start using its own kernel, and that this Kernel would not support POSIX, but its own proprietary API. Now Linux applications would not be able to easily run on Ubuntu, and applications for Ubuntu would not be able to easily run on Linux. Having a bunch of incompatible window systems is as bad as that. The Window System is basically the kernel for GUI applications. Basically Canonicals Mir announcement is pretty much does the same, applications must talk to the Window system, so the Window system is as important as the kernel for application cross compatibility between OSs. Canonical is fracturing the Linux ecosystem and trying to greedily and arrogantly grab control of the Linux graphics stack and basically one of the most critical parts of the Linux ecosystem. Canonical's behaviour is outrageous and the Linux community should not tolerate this.

I think now is the time for other Linux Distros to commit to Wayland, leaving Canonical isolated.

We also need to start a petition to get Canonical to commit to wayland and stop trying to develop its own window system.

I also think that Wayland should be made a part of the Linux Standards Base. Perhaps the rights to use of the Linux trademark for companies such as Canonical who blatantly ignore Linux standards should be revoked.

Re:A good idea (0)

Anonymous Coward | about a year ago | (#43127937)

You may not like Canonicals choice... but to say it breaks inter-operabilty... who cares. That's what forking is all about. If you don' like it, stick with a different distribution. It's open source, things like this come with the territory. Move on.

Re:A good idea (3, Informative)

lister king of smeg (2481612) | about a year ago | (#43128085)

Or just install x.org or wayland from the repository while your at it throw another DE like cinnimon kde or xfce and while you are at
wipe out unity problem solved

Re:A good idea (3, Insightful)

Eravnrekaree (467752) | about a year ago | (#43128185)

Thats fine if its a word processor. The problem is that all applications rely on the Window System. You can choose your own word processor, and it affects little else. But, a bunch of incompatable window systems would be a disaster, it would actually take away your choices because now some software runs on window System A, but not window system B, so you end up not being able to use one block of software or another block of software. The good thing about X is that it has been used on all distributions, meaning you could run all Linux software on any Linux distribution, or on any other Unix OS, such as FreeBSD.

It is important to have standards. The same thing applies to web pages. If every person who made a web page decided to make their own incompatable HTML and use their browser to look at it, it means if you used another browser you could not get to their web page.

Re:A good idea (1)

BrokenHalo (565198) | about a year ago | (#43130325)

The problem is that all applications rely on the Window System.

And therein lies Ubuntu's future relevance, or lack of it. A few individuals have complained about certain flaws in X11 without offering anything useful or complete as an alternative, and I rather doubt if Canonical has the resources to do any better, given the vast amount of work involved. If Canonical insists on pursuing this path, I wouldn't be surprised if Ubuntu slips from being the most commonly-used(*) distribution to the least.

* This is from the perspective of an ancient Slackware user who doesn't give a fuck one way or another. ;)

Re: A good idea (0)

Anonymous Coward | about a year ago | (#43127995)

Derailing Linux compatibility is a bad idea in practice, but being free to do your own thing in the "free as in both" software world is a good thing in general. Change for the sake of change isn't really a good approach, unless the same old crap needs to be changed at gun point because its entrenchment will never allow the whole system to improve.

BTW, if Ubuntu went with a different kernel it wouldn't be Linux anymore. ;-)

Re:A good idea (1)

lister king of smeg (2481612) | about a year ago | (#43128101)

Adding Wayland to the Linux standard base would be a bad idea as many if not most Gnu Linux installs are headless and don't need a graphics stack or if they do would need the networking advantages of xorg

Re:A good idea (1)

Eravnrekaree (467752) | about a year ago | (#43129253)

It would be a good idea. it would not require text only distributions to carry Wayland. If you have a Linux distro that is text only, then the GUI standards would not apply. If the distro does have a GUI, then wayland would be required by the standard.

Re:A good idea (0)

Anonymous Coward | about a year ago | (#43130257)

So, you want to take away freedom of choice? Like Windows, where you can either run Win32, or the text-only version of Windows Server, you want those of us who don't like the idea of Wayland to be forced to text only...

Re:A good idea (1)

lister king of smeg (2481612) | about a year ago | (#43140927)

no i am not say that you should take away freedom but that incorporation wayland into the Linux Sandard Base is not a good idea because there is a much more mature and full featured OS independent standard graphics server in place already, X.org. Sure through it in the repo but don't make it part of the LSB, putting it in there would be folly because it is not yet stable is poorly documented and has a long way to go before it is capable of replacing X. As it is now if people would simply put their effort into fixing X's problems and updating the code to take advantage new hardware advances we would be much better off.

Re:A good idea (0)

Anonymous Coward | about a year ago | (#43128131)

I admire your tenacity. You saw a story which had nothing to do with Canonical in any way, but you spat in its face and screamed, "No! I WILL post an anti-Canonical rant today! Even if it means polluting the comments of an unrelated story, I will make sure the world knows my opinion about Canonical!"

Your sheer determination is admirable.

Re:A good idea (1)

serviscope_minor (664417) | about a year ago | (#43128269)

I think now is the time for other Linux Distros to commit to Wayland, leaving Canonical isolated.

Or, how about everyone else stays committed to Xorg and keeps all the neat features that apparently I don't need, or so the Wayland supporters keep telling me.

Re:A good idea (3, Insightful)

dbIII (701233) | about a year ago | (#43128307)

I think now is the time for other Linux Distros to commit to Wayland

How about waiting until it has proved it works and has advantages first. While a dumb framebuffer can theoretically perform better than something with a few layers of abstraction it hasn't done so yet, especially since some of those layers of abstraction in X are quite lean.

Re:A good idea (1)

21mhz (443080) | about a year ago | (#43130027)

How about waiting until it has proved it works and has advantages first. While a dumb framebuffer can theoretically perform better than something with a few layers of abstraction it hasn't done so yet, especially since some of those layers of abstraction in X are quite lean.

If you think Wayland is "a dumb framebuffer", you should educate yourself.

Amusing comprehension failure (1)

dbIII (701233) | about a year ago | (#43130097)

Wayland is of course a way to dump images on a dumb framebuffer as distinct from the extra abstraction within X to place the images in a variety of places, resolutions, color depths etc, so your "educate yourself" line is somewhat comical in this context. Please at least bother to read entire sentences before accusing people of ignorance.

Re:Amusing comprehension failure (1)

21mhz (443080) | about a year ago | (#43141667)

Wayland is of course a way to dump images on a dumb framebuffer

No, it's not. Please educate yourself.

Re:Amusing comprehension failure (1)

dbIII (701233) | about a year ago | (#43144819)

Oh really? Instead of dumb playground games how about some detail that shows that I am incorrect.

Re:Amusing comprehension failure (1)

21mhz (443080) | about a year ago | (#43147227)

OK, it was incredibly hard to dig it out from an obscure document confusingly called the FAQ [freedesktop.org] :

Q: What is the drawing API?

A: "Whatever you want it to be, honey". Wayland doesn't render on behalf of the clients, it expects the clients to use whatever means they prefer to render into a shareable buffer. When the client is, it informs the Wayland server of the new contents. The current test clients use either cairo software rendering, cairo on OpenGL or hardware accelerated OpenGL directly. As long as you have a userspace driver library that will let you render into a sharable buffer, you're good to go.

Re:Amusing comprehension failure (1)

dbIII (701233) | about a year ago | (#43165443)

So what part of your quote contradicts my bit about a dumb framebuffer? It appears to confirm it instead.

Re:Amusing comprehension failure (1)

dbIII (701233) | about a year ago | (#43165515)

Looking more at that FAQ, it's full of useless stuff like the following:

The problem with X is that... it's X

How do you expect me to take such a useless and pointless pile of words that goes around in circles seriously? Nothing about bottlenecks or anything tangible, just braindead self-referential bullshit instead of some sort of half-decent demo apps to prove a benefit over X or even SVGAlib.

Re:A good idea (0)

Anonymous Coward | about a year ago | (#43128397)

As Wayland did not succeed to deliver a new desktop graphic stack, it is understandable that other are trying something different. Canonical was one of the first distributions to go for Wayland. They wanted to use it. However, they were unable to use it, as it is not finished yet. For the smartphone/tablet ports of Ubuntu, Canonical used another display stack. Obviously, they were able to accomplish a operational device in short time. They couldn't use Wayland for that. Now, Wayland is still not able to deliver a running display stack and compositor. This can have different causes, but from a distributions stand point, they it looks like they are stuck.

Reading their traffic on the Wayland mailing list, it looks pretty much like that. Furthermore, there is no documentation on the API or anything else from the architecture available. You cannot pull of such a big project with a small tool method used in many projects. As an outsider, the project looks like a closed shop under documented piece of junk, like Mozilla was after Netscape. Don't mistake that as Wayland bashing. I pretty much like to see one successor to X and I really want to see such thing sooner than later. I had high hopes the Wayland could be that. But I can also understand the critique about the project's governance and development process.

In the end we better agree on one working display thing for Linux and who ever reaches that goal with working software can have my support. Honestly, I would like to see specs. and discussion about the protocol design from both project. How should anyone discuss or even participate in such endeavors without proper communication and documentation.

Re:A good idea (1)

Eravnrekaree (467752) | about a year ago | (#43129277)

You are right that for a long while, the API documentation sucked. They finally posted some, however. It looks good.

Wayland has been open compared to Canonicals process. They have had discussions on public mailing lists about it. There is a working code now as well. Yes it did take a while. I am not sure why, maybe they are perfectionists and were working out the details. They could have pushed out an early version and perfected things in later versions. But when you are dealing with an API, the API may need to be improved upon. When many applications have been targeted for an older version of the API, the you would need to have an extension mechanism and keep around support for the older API in a compatability layer glue code. So maybe they were trying to get the API right at the first go.

Re:A good idea (1)

arendjr (673589) | about a year ago | (#43129723)

It seems to me you're making an issue out of nothing. You say "applications must talk to the Window system, so the Window system is as important as the kernel", but in practice this is not true. Applications talk to a toolkit/library like Qt or GTK, or (as what this article is about, and which you agree is a good idea) SDL. These libraries do the hard work because noone wants to talk to Xlib directly since it's a mess. Now, as long as these libraries all support X, Wayland, Mir or whatever will be around next week there simply won't be a problem.

You said it yourself. "It is always a good idea to use a platform independant library", and I agree. Yet you continue with the rest of your rant as if nobody actually does that.

PS.: I disagree Wayland should be in the LSB. As others already mentioned, let it first prove its worth. And not to forget X's network transparency is very valuable to some. Forcing Wayland into the LSB would be like throwing out the baby with the bath water, at the very least.

We're dropping SDL from XBMC (3, Informative)

Lars Op den Kamp (2827885) | about a year ago | (#43129959)

SDL will soon be dropped from XBMC. I'll quote Cory here to explain things:
"This is an interesting POC, however it’s not really in fitting with how we had planned to handle wayland. I recently rewrote our egl handling so that we can dynamically support various windowsystems on the fly, so that we can have a single binary capable of running X11/wayland/framebuffer. It was explicitly written with wayland in mind. See https://github.com/xbmc/xbmc/commit/2b49c791eb236ae4fe2be90ac7e7b8ccf0aad72f [github.com] for the pull, and https://github.com/xbmc/xbmc/blob/master/xbmc/windowing/egl/EGLNativeType.h [github.com] for the interface.

It’s very pluggable, and I suspect it’d be far less work than what you’ve done here. I was hoping to get to it ages ago, it just hasn’t been a priority yet.

We’ll be dropping SDL soon, since we prefer our own abstractions. See here: https://github.com/xbmc/xbmc/pull/1175 [github.com] "

Cool (0)

Anonymous Coward | about a year ago | (#43148065)

Now do Mir.

Check for New Comments
Slashdot Account

Need an Account?

Forgot your password?

Don't worry, we never post anything without your permission.

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>
Create a Slashdot Account

Loading...