Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 28

Thread: Wayland Demonstration At XDS 2010

  1. #11
    Join Date
    Aug 2009
    Posts
    2,264

    Default

    Quote Originally Posted by sylware View Post
    What are the differences between wayland and GTK/Clutter ported to use directly libdrm/gallium3d/libxkb?
    Well... Clutter is a graphic library on top of which the Mutter WM is made.
    GTK is a widget toolkit that uses Xlib, which Wayland doesn't have, so that's why it must be ported to Wayland.
    Wayland is a tiny display server. It's using EGL? If so (don't realy remember with all that info flying around) then GTK+ will probably render to a texture/pixmap which Wayland will use (compositing) for drawing windows.

    If they want to use it for meego, it shall be C++/Qt (erk!), wouldn't it?
    Ah, yes; MeeGo, my fault I think the 'Gnome/GTK+'-'camp' will use C, but since Nokia has Qt, Nokia will probably use C++, but Wayland is pretty low level with KMS and the State Trackers and such so the implementation might just be C. I don't know that much about Wayland yet

    (I'm sad to see the C dependency swapped for a C++ dependency in meego)
    Politics

  2. #12
    Join Date
    Aug 2008
    Location
    Finland
    Posts
    1,633

    Default

    Quote Originally Posted by V!NCENT View Post
    Ah, yes; MeeGo, my fault I think the 'Gnome/GTK+'-'camp' will use C, but since Nokia has Qt, Nokia will probably use C++, but Wayland is pretty low level with KMS and the State Trackers and such so the implementation might just be C. I don't know that much about Wayland yet
    I wouldn't rely on that kind of assumptions. Mesa has C++ code too. Better just go check what Wayland consists of.

  3. #13
    Join Date
    Aug 2009
    Posts
    2,264

    Default

    Quote Originally Posted by nanonyme View Post
    I wouldn't rely on that kind of assumptions. Mesa has C++ code too. Better just go check what Wayland consists of.
    And neither do I. I just treid to answer his questions to the best of my extremely limited knowledge. So If I came over as "It will be like this" then what I mean is "I dunno, maybe it's like that?"

  4. #14
    Join Date
    Dec 2008
    Posts
    166

    Default GTK+ stack

    Well... I meant what will be the differences between GTK+ stack on top of wayland and the GTK+ stack on top of libdrm/gallium3D/libxkb?

    (Since I love C++, I allowed myself to phase it out from the thread)

  5. #15
    Join Date
    Oct 2008
    Posts
    3,152

    Default

    Supporting Qt doesn't mean that Wayland is necessarily c++. The changes required are done inside the Qt code, so that instead of drawing onto an pixmap or opengl texture, it instead draws on whatever Wayland uses. Wayland itself doesn't need to be touched at all.

    Of course, I'm not sure what Wayland is written in, it may have already been c++ from the start or it could still be plain C.

  6. #16
    Join Date
    Dec 2008
    Posts
    166

    Default GTK or Clutter backend

    [QUOTE=smitty3268;148724]Supporting Qt doesn't mean that Wayland is necessarily c++. The changes required are done inside the Qt code, so that instead of drawing onto an pixmap or opengl texture, it instead draws on whatever Wayland uses. Wayland itself doesn't need to be touched at all.

    Of course, I'm not sure what Wayland is written in, it may have already been c++ from the start or it could still be plain C.[/QUOT]

    It is not what I meant. What added value would have a wayland backend instead of a libdrm gallium 3d libxkb backend for gtk or clutter?

  7. #17
    Join Date
    Sep 2010
    Posts
    147

    Default It's written in C

    Quote Originally Posted by smitty3268 View Post
    Of course, I'm not sure what Wayland is written in, it may have already been c++ from the start or it could still be plain C.
    Wayland is written in C.

  8. #18
    Join Date
    Sep 2010
    Posts
    12

    Default

    Thanks for explanation. So, it is safe to say that Wayland is what will become X12

  9. #19
    Join Date
    Nov 2009
    Posts
    91

    Default

    Quote Originally Posted by gnufreex View Post
    Thanks for explanation. So, it is safe to say that Wayland is what will become X12
    No that would be wrong. X12 would be an evolution of X11. Wayland is a completely different project that can replace X but is much less featured. If you want network support for example you'd still have to run X on top of Wayland.

  10. #20
    Join Date
    Dec 2008
    Posts
    166

    Default C++ is kludge, we all know it

    Quote Originally Posted by Plombo View Post
    Ok good.

    Now, what benefit a wayland backend will have compared to a libdrm/gallium3D/libxkb backend for GTK+/Clutter?

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •