Forgot your password?
typodupeerror
GUI Open Source News

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

Posted by Unknown Lamer
from the now-with-more-bling dept.
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.
This discussion has been archived. No new comments can be posted.

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

Comments Filter:
  • WHAT (Score:4, Insightful)

    by Anonymous Coward on Saturday March 09, 2013 @03:35PM (#43127317)

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

    FFS TFS needs some TLC.

    • Re:WHAT (Score:5, Informative)

      by dead_user (1989356) on Saturday March 09, 2013 @03:53PM (#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 (Score:5, Informative)

      by PineHall (206441) on Saturday March 09, 2013 @04:00PM (#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."

      • by HiThere (15173)

        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: (Score:2, Insightful)

      by Lumpy (12016)

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

    • by Walzmyn (913748)

      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.

    • by Anonymous Coward

      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 mon

    • by loufoque (1400831)

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

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

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

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

  • "Proof of Concept" (Score:4, Interesting)

    by timeOday (582209) on Saturday March 09, 2013 @05:13PM (#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 (Score:4, Interesting)

    by Eravnrekaree (467752) on Saturday March 09, 2013 @05:17PM (#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.

    • 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

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

    • 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 (Score:4, Insightful)

      by dbIII (701233) on Saturday March 09, 2013 @07:16PM (#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.

      • by 21mhz (443080)

        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.

        • 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.
          • by 21mhz (443080)

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

            No, it's not. Please educate yourself.

            • by dbIII (701233)
              Oh really? Instead of dumb playground games how about some detail that shows that I am incorrect.
              • by 21mhz (443080)

                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

                • by dbIII (701233)
                  So what part of your quote contradicts my bit about a dumb framebuffer? It appears to confirm it instead.
                • by dbIII (701233)
                  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.

    • by arendjr (673589)

      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 ne

  • by Lars Op den Kamp (2827885) on Sunday March 10, 2013 @07:00AM (#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]"

Business is a good game -- lots of competition and minimum of rules. You keep score with money. -- Nolan Bushnell, founder of Atari

Working...