The reason I did this is because Wayland and Weston obviously also has a lot of unit test code, so the reason Mir has more LOC than Wayland is very unlikely to stem from that. Again it could just be a ton of comments making Mir larger as Michael stated in the post that he included them (why? iirc CLOC neatly lists code, comments and blank lines separately).
Ubuntu's is right here ready to go.
I am rooting for Wayland but this is the current state of things. Canonical deserves respect here.
1. Canonical took another project developed for Wayland to be able to run Mir with Android drivers.
2. Canonical never contacted Wayland developers about their needs.
It would be good to investigate a little bit. Both things are repeated often, doesn't make it true.
That said, wish them all the best and if they succeed, cool. But that's it.
With Mir and X11 you ask the server to render this content in surface A, then set focus for input at this coordinates and return an event with a server side API, so the server check and process the requirement, in plain english is a police middleman.
Wayland on the other hand is a pure protocol and it does define an API ish way to talk directly to the GPU, wayland doesn't coordinates/handle/interfere with the process in any way, it just generate pointers and minimal references so the compositor can handle surface positioning and input. in fact i can have X application that use my system global libwayland 1.1 and render using Pixman and Y application staticaly compiled with wayland Git that uses EGL and Opengl 3.1 profile to render and Weston[mutter/kwin/etc] won't even know because im talking directly to the GPU and wayland API just return objects with location information and surface information[screen/gpuX/position in internal GPU framebuffer/color depth/colors type/etc] for every specific client, so the compositor later with this minimal information can organize the screen later to present it in any way you like.
see this for an example http://www.youtube.com/watch?v=_FjuPn7MXMs
so to be more precise Mir and X11 are server type Protocols and Wayland is an direct GPU access Protocol, don't believe well start any wayland client app or demo and try to locate the wayland server process i dare you and for god sakes before reply a thread read the freaking code or read the documentation[wayland site even have cool diagrams and big fonts]
for the sake of responding yes any Qt5 + qtwayland QPA or GTK+ 3.8 real application will work in Wayland in both X86 and ARM and with a bit of effort Xwayland can run X11 apps in arm using full accelertation with android drivers and all[libhybris].
no there is no cool premade image with cool images and stuff yet for this, if you want you need real apps meeting the requirements above and a source distro like gentoo to get thing compiled the right way
fix: seems for raspberry there are some premade distros that use Qt5 demos and wayland, check the rasp forum.
as a note: wayland is basically ready and mostly fixing corner cases in the protocol like subsurfaces and age extension, we aren't waiting for wayland anymore but for the clients EFL/Qt5/Gtk-3.10/etc and their respective desktops KDE SC 5/Enlightment/Gnome 3.10 to be ported to wayland, so is very likely that when Mir sees the first beta of unity 8 Gnome will be able to work 100% on wayland with Mutter as compositor and all and for the final Mir release time at least KDE SC 5 will have a beta/rc release.
ofc wayland will get new features over time but the base protocol is frezee since some time now, which is why you see minimal activity in the repos this days[most work is going to mesa and kernel DRM to handle the bufferage extension]
From the main page:
Obviously, I recalled it incorrectly, where it says it can be, I recalled it was, when it's just a possible way to implement it.Wayland is a protocol for a compositor to talk to its clients as well as a C library implementation of that protocol. The compositor can be a standalone display server running on Linux kernel modesetting and evdev input devices, an X application, or a wayland client itself. The clients can be traditional applications, X servers (rootless or fullscreen) or other display servers.
You was (wrote are, but meant was) still wrong with X11 (that's a protocol, and the server normally used is X.org), and from what I read on Mir's spec, about Mir, since it doesn't seem to handle the drawing but the compositing, just as Wayland do.
I'm aware of all the advantages of Wayland, I read the docs (not to the end, yet) because I want to port my pet pr
oject to Wayland.
Anyway, I obviously misunderstood you, I actually thought your post was trying to say Mir was a far better option. I specially misunderstood what you meant with GPU language specification. It sounded like they were redesigning OpenGL or something like that, not just making use of DRI as I'm aware they do.
On another subject, civility is not at all overrated, man, and your HUGE FONTS and BOLDS are pretty impolite.
Last edited by mrugiero; 06-26-2013 at 03:23 PM. Reason: I meant WAS!