Announcement
Collapse
No announcement yet.
Wayland Demonstration At XDS 2010
Collapse
X
-
It's written in C
Originally posted by smitty3268 View PostOf 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.
Leave a comment:
-
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?
Leave a comment:
-
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.
Leave a comment:
-
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)
Leave a comment:
-
Originally posted by nanonyme View PostI wouldn't rely on that kind of assumptions. Mesa has C++ code too. Better just go check what Wayland consists of.
Leave a comment:
-
Originally posted by V!NCENT View PostAh, 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
Leave a comment:
-
Originally posted by sylware View PostWhat are the differences between wayland and GTK/Clutter ported to use directly libdrm/gallium3d/libxkb?
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?
(I'm sad to see the C dependency swapped for a C++ dependency in meego)
Leave a comment:
-
Originally posted by V!NCENT View PostWayland is X, stripped of all the old stuff, geared at the future, acting more or less as R&D in practise. It's not network oriented. To achieve network computing and 'legacy' compatibility it can use Xserver. It's much more abstract. Porting GTK/Qt has been discussed and porting GTK is in the works (or so I believe; news is scarce).
It started as a hobby project by a Red Hat employe. It's not realy that much of a hobby project anymore in the sense that Intel and Nokia are planning to use Wayland for Meamo; it's great for embedded systems.
There is the possibility that, over time, X.org will grow, but not fully, towards Wayland, due to Waylands 'new tech', where proven.
If they want to use it for meego, it shall be C++/Qt (erk!), wouldn't it?
(I'm sad to see the C dependency swapped for a C++ dependency in meego)
Leave a comment:
-
Originally posted by sylware View PostWayland would be the bare minimal network protocol for a modern GPU stack?
I really have to look further into it.
It started as a hobby project by a Red Hat employe. It's not realy that much of a hobby project anymore in the sense that Intel and Nokia are planning to use Wayland for Meamo; it's great for embedded systems.
There is the possibility that, over time, X.org will grow, but not fully, towards Wayland, due to Waylands 'new tech', where proven.
Leave a comment:
Leave a comment: