On Tue, Feb 14, 2012 at 3:18 AM, wrote:
> From: Alex Wu
>
> Hi krh
Hi Alex,
> This patch is the implementation of the method 3 of the
> proposal(http://lists.freedesktop.org/archives/wayland-devel/2012-February/002085.html)
> for handling panels when compositor has a top fullscreen regular
2012/2/17 Kristian Høgsberg :
> - The EWMH standard has a lot of properties, window types and
> language for standardizing out-of-process desktop components such as
> pagers, panels and desktop backgrounds. We're not going to try to
> standardize that in 1.0, the focus is going to be on the commu
On Fri, 2012-02-17 at 12:05 -0800, Bill Spitzak wrote:
> Kristian Høgsberg wrote:
>
> >> 1) Are you planning to support on-screen keyboard apps? If so, how this
> >> is going to be implemented, so that a malicious/compromised app couldn't
> >> act as such "on-screen keyboard" and inject keystrokes
Kristian Høgsberg wrote:
1) Are you planning to support on-screen keyboard apps? If so, how this
is going to be implemented, so that a malicious/compromised app couldn't
act as such "on-screen keyboard" and inject keystrokes to other apps?
We can restrict access to functionality on a per-appli
wuzhiwen wrote:
Hi Bill,
Thanks for your reply. I summarized my scheme as following:
1. Make the panels always atop the top regular window.
This means no hiding operation to panels, all things is about stacking
adjustment. Compositor will check the window status and adjust the stacking
every
Juan Zhao wrote:
You opposed ""clicking the window" will raise it"?
YES I OPPOSE IT!!
Please don't act surprised. There are people who actually think this is
THE biggest mistake in GUI design ever and that it has seriously damaged
the ability to work with multiple documents and
On Fri, Feb 17, 2012 at 1:39 PM, Joanna Rutkowska
wrote:
> On 02/17/12 09:43, Tiago Vignatti wrote:
>> Hi,
>>
>> On 02/16/2012 08:36 PM, frqb4td wrote:
>>> In "The Linux Security Circus: On GUI isolation" (link:
>>> http://theinvisiblethings.blogspot.com/2011/04/linux-security-circus-on-gui-isolat
On 02/17/12 09:43, Tiago Vignatti wrote:
> Hi,
>
> On 02/16/2012 08:36 PM, frqb4td wrote:
>> In "The Linux Security Circus: On GUI isolation" (link:
>> http://theinvisiblethings.blogspot.com/2011/04/linux-security-circus-on-gui-isolation.html
>>
>> ) - The Invisible Things Lab's blog, Joanna Rutko
---
src/compositor.c | 10 ++
1 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/src/compositor.c b/src/compositor.c
index b4e9749..86a87f5 100644
--- a/src/compositor.c
+++ b/src/compositor.c
@@ -1459,8 +1459,11 @@ notify_key(struct wl_input_device *device,
struct we
---
src/compositor.c | 20 +-
src/shell.c | 60 -
2 files changed, 42 insertions(+), 38 deletions(-)
diff --git a/src/compositor.c b/src/compositor.c
index ab90ded..b4e9749 100644
--- a/src/compositor.c
+++ b/src/composi
---
src/wayland-server.c | 44
src/wayland-server.h | 22 ++
2 files changed, 66 insertions(+), 0 deletions(-)
diff --git a/src/wayland-server.c b/src/wayland-server.c
index fce6025..fc4fab0 100644
--- a/src/wayland-server.c
+++
In order to separate pointer and keyboard grabs, we need to
introduce a keyboard grab interface but first we must rename
some generic types to denote which device is holding the grab.
Type renames:
wl_grab_interface -> wl_pointer_grab_interface
wl_grab -> wl_pointer_grab
wl_input_device_start_gra
This patch set introduces wl_keyboard_grab_interface which
seperates grabs into device specific contexts. This will allow
a finer grain of control for keybindings. The bulk of the
patches are just renames.
___
wayland-devel mailing list
wayland-devel@lis
Hello,
So with 0.85.0 Wayland and Weston released, it's a good time to figure
out what the plan is going forward. We had a two day workshop in
Brussels leading up to FOSDEM and we went through the Wayland protocol
to figure out what's missing and what to do about various loose ends.
We also worke
I updated the patches with the changes I discussed with Pekka and pushed
them to
git://github.com/anderco/weston dnd-sprite
I can resend them if needed.
On 02/15/2012 05:02 PM, Ander Conselvan de Oliveira wrote:
Here's a second attempt to getting drag and drop icons implemented.
This uses
Hi Pekka,
Thanks for reviewing this. Comments below.
On 02/16/2012 06:05 PM, Pekka Paalanen wrote:
On Thu, 16 Feb 2012 16:42:03 +0200
Ander Conselvan de Oliveira wrote:
I actually had not consider the case where the drag surface is
transformed. We definitely want to move it according to the
t
wl_egl_window/wl_egl_pixmap are implemented in mesa, however these drawables
can also be update in video/camera modules.
One example is that libva also manage buffer object for it, so the attributes
of the drawable should be accessed outside of mesa.
See Benjamin's work to enable libva for waylan
Hi,
On 02/16/2012 08:36 PM, frqb4td wrote:
In "The Linux Security Circus: On GUI isolation" (link:
http://theinvisiblethings.blogspot.com/2011/04/linux-security-circus-on-gui-isolation.html
) - The Invisible Things Lab's blog, Joanna Rutkowska describes attacks
from one X11 app on another and th
18 matches
Mail list logo
