If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Why wayland needs CSD? I don't see point of CSD at all
One of the reasons is effects quality I believe. With CSD you have one buffer which holds your entire window's contents, including window decorations. The compositor (Wayland) can then transform/warp/etc your window however it wants (for all those pretty Compiz-like effects) without doing to much special stuff to get rid of the aliasing between the window contents and decorations.
There may be other, more technical reasons for it, but I'm unaware of them. Also, as someone else mentioned, Wayland can do both.
Because Mir and Wayland are so similar the amount of work to do them both is not as much as you would think.
They can simply support both too you know. There is not going to be a driver war.
If we can somehow convince the vendors to ship agnostic drivers with an agnostic
buffer sharing mechanism that would work, but I'm not sure they want to put in the
effort of distributing yet more packages than they already do.
Why not have a library called libdecoration that is used by GTK+, Qt, Clutter, EFL, FLTK, Tk, etc.
Then all widget toolkits will re-use and share the same code for decorations.
Then all applications will have the same decorations, instead of GTK+ and Qt and others have application windows with different looking decorators.
We need a common unified well-integrated look-and-feel.
People always think about developers as a bunch of manpower that you can to oblige them to do what you want.
With that prerequisite in mind, they think that it is a smart idea put all that manpower on the same project and so you can achieve an impressive development speed.
You can force a developer to work on what you want only if you paid him for it, otherwise he will spend his free time in what he want and if the "big project" going to a direction that he don't like, he will stop to work on it or will fork it.
So thinking about a hundreds of free devs that move all togheter in the same direction just because it will be a nice amount fo manpower is just an accademic wast of time.
The good thing about Mir is that competition is stirring up wayland development and we could say goodbye to Xorg sooner than we think.
This support mentioned in this article is the result of a lot of slow work over a long period. Is a post like this going to appear every-time something get's improved Wayland support simply because of all of the FUD floating around about Wayland being vaporware? They have been developing it for years yes, but they have actually been developing it in that time. This idea that Mir shook them out of some lazy complacency is asinine: at best it just forcing people to make their intentions known about it.
I reallly wish someone would explain to me how mir is competing. How is it different other than its lack of functionality?
Its the same issue the gnome guys addressed. Everyone knew Wayland would happen "Eventually" but they werent really pushing because there was no downside to NOT. they were no competitors or alternatives or anything, so the wayland guys and gnome and kde could just chill and do whatever.
Now Mir's here and its the classic example of "We're gonna try harder and win just to give a 'screw you!' to the other guys." So now Wayland development and Wayland-enablement has kicked up