When cross-compiling Wayland, wayland-scanner should be picked up from the host
system instead of compiling and trying to run e.g. ARM wayland-scanner on X86.
This patch adds --disable-scanner option for disabling the scanner from the
build and using existing wayland-scanner instead (from PATH)
On 6 May 2011 02:10, Kristian Høgsberg k...@bitplanet.net wrote:
I can't remember
when I last had to deal with an unresponsive application
I had this happen to me in Windows XP yesterday. To be fair, I was pushing
the machine by running two VMs, one of which was running Windows update.
Chrome
On 6 May 2011 08:25, Niklas Höglund nhogl...@gmail.com wrote:
so maybe just have some special hotels or similar for this.
Annoying text prediction. Hotkeys, not hotels.
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
On 06/05/11 10:18, Bill Spitzak wrote:
I believe client-side decorations are an absolute must.
The amount of code necessary for an application to use an async protocol
to describe how the window border should appear is greatly larger than
that needed to just draw and handle events in the window
On 06/05/11 10:18, Bill Spitzak wrote:
I believe client-side decorations are an absolute must.
The amount of code necessary for an application to use an async protocol
to describe how the window border should appear is greatly larger than
that needed to just draw and handle events in the window
On Fri, May 6, 2011 at 8:18 AM, Bill Spitzak spit...@gmail.com wrote:
I believe client-side decorations are an absolute must.
The amount of code necessary for an application to use an async protocol to
describe how the window border should appear is greatly larger than that
needed to just
On 6 May 2011 09:42, Sam Spilsbury smspil...@gmail.com wrote:
You cannot assume that there will be a universally adopted method to
styling because we see on every single platform that there will *not*
be one. The best way to enforce styling is to enforce it at the window
manager level, so that
Sam Spilsbury wrote:
Actually, I'm pretty sure in 99% of the cases out there the amount of
code required for individual applications to have a window border
using decorations done on the window manager side is going to be
pretty much nil.
Size? Resize rules? Name? Icon name? Icon? Layer?
I still remember some old windows systems which use client side decoration.
When applications have some problems, you can not use close button to close
them. Any the whole decoration will not be repainted anymore, just leave
users the background color. That is a really bad UX.
I think server side
Window management policy should also be client-side. I may not have been
clear about that. The wayland compositer almost NEVER moves or raises or
resizes a window. Clients do this in response to clicks or whatever. This
would have made it TRIVIAL to implement Gimp the way they intended, as at
10 matches
Mail list logo
