On Mon, Mar 25, 2013 at 3:08 PM, Thiago Macieira
> On segunda-feira, 25 de março de 2013 14.45.21, Scott Moreau wrote:
>> Northfield stands on the shoulders of giants, years worth of work and
>> history to get to the point where we are today. It has been some 8
>> years since compiz has exposed these many restrictions found in X
>> protocol. We want certain effects to be readily possible and are not
>> inherently restricted by certain caveats of the display server
>> protocol. I expect that wayland core protocol will be added to support
>> the basic functionalities expected as part of todays Linux Desktop. I
>> believe that there wont be any problems with this particular effect
>> and others. However, I want to make absolutely sure of that.
> What we're asking is that you avoid forking Wayland at all. Don't change
> library, don't change the default extensions (including wl_shell), don't
> new default extensions. You said you want to avoid incompatible changes:
> avoiding the fork also avoids the temptation.
> Try to do your changes in a different extension. Copy the current
> a new one and modify it to your heart's desire. If, at the end of your
> experiment, you conclude that the current wl_shell is flawed by design,
> Wayland should deprecate it and adopt yours. On the other hand, if we
> that your improvements can be added incrementally, we can simply do
This sounds great but this is not the solution I have come up with.
> I'll ping you on IRC to discuss this. Several people have asked you to do
> and you have either missed the point or failed to explain to us why the
> is necessary.
> PS: compiz is also a bad example. It might have been a great experiment
> resulted in improvements in most existing WMs, but it was a horrible WM.
> had bugs with its core WM functionality that went unfixed for years.
I think compiz is in fact the very model example of what a compositing
manager for the Linux Desktop should be. Yes, it has had many bugs
over the years but many of these are because the X protocol is
extremely difficult to work with and inherently problematic. We can do
the same things now, but this time, uninhibited, thanks to the driver
situation. I am sorry that you feel this is unnecessary but I
> Thiago Macieira - thiago.macieira (AT) intel.com
> Software Architect - Intel Open Source Technology Center
> wayland-devel mailing list
> [email protected]