https://www.archlinux.org/packages/extra/x86_64/gtk3/ now lists "wayland"
as a dependency, I haven't done any more verifying than that.
- Forwarded message from Arch Linux -
Date: Mon, 18 Mar 2013 22:42:53 +
From: Arch Linux
Subject: FS#33577: [gtk3] Enable Wayland backend
THIS IS
On Fri, Mar 08, 2013 at 10:26:13PM -0600, Jason Ekstrand wrote:
> This commit adds a wl_resource_init function for initializing wl_resource
> structures similar to wl_client_add_object.
>
> From this commit forward, wl_resource structures should not be initialized
> manually, but should use wl_res
On Fri, Mar 08, 2013 at 10:26:12PM -0600, Jason Ekstrand wrote:
>
> Signed-off-by: Jason Ekstrand
> ---
> src/connection.c | 6 --
> src/wayland-client.c | 4 ++--
> src/wayland-private.h| 2 +-
> src/wayland-server.c | 2 +-
> tests/connection-test.c | 13 +++---
On Sat, Mar 09, 2013 at 08:24:10AM -0700, Scott Moreau wrote:
> This fixes the wlshm path which was not updating the buffer correctly.
Yes, thanks. It's a little odd, to see the attach after the damage
posting - conceptually you attach a buffer and then mark the damaged
regions in that buffer. B
On Fri, Mar 08, 2013 at 09:05:06PM +0100, Philipp Brüschweiler wrote:
> Sorry, forgot Reply All.
>
>
> On Fri, Mar 8, 2013 at 9:04 PM, Philipp Brüschweiler wrote:
>
> > On Fri, Mar 8, 2013 at 8:44 PM, Scott Moreau wrote:
> >
> >>
> >>
> >> On Fri, Mar 8, 2013 at 12:35 PM, Philipp Brüschweiler
On Fri, Mar 08, 2013 at 08:35:39PM +0100, Philipp Brüschweiler wrote:
> Fixes https://bugs.freedesktop.org/show_bug.cgi?id=61930
> ---
> src/pixman-renderer.c | 2 ++
> 1 file changed, 2 insertions(+)
Thanks, applied.
Kristian
> diff --git a/src/pixman-renderer.c b/src/pixman-renderer.c
> index
On Fri, Mar 08, 2013 at 02:56:50PM +0200, Pekka Paalanen wrote:
> Implements surface transform inheritance. A 'parent' pointer is added to
> weston_surface::geometry, and is automatically used by
> weston_surface_update_transform(). When updating the transform, the
> parent transform is updated as
On Fri, Mar 08, 2013 at 02:56:49PM +0200, Pekka Paalanen wrote:
> Instead of directly setting the dirty flag on weston_surface geometry,
> use a function for that.
>
> This allows us to hook into geometry dirtying in a following patch.
>
> Also add comments to weston_surface fields, whose modific
On Fri, Mar 08, 2013 at 02:56:48PM +0200, Pekka Paalanen wrote:
> Remove redundant geometry dirtying from surface_commit() to simplify
> further changes.
>
> This code was added in commit 5df8ecac5d31467122a9d8bda6241d5957ae6848
> "compositor: Fix partial repaints"
>
> as the fix to:
> https://bu
On Thu, Mar 07, 2013 at 09:50:00PM +0100, Rune K. Svendsen wrote:
> From: "Rune K. Svendsen"
>
> When an axis (scroll) event results in a key binding function
> being executed, eat the scroll event so the underlying window
> doesn't receive it.
> Thanks to Scott Moreau for helping me solve this.
On Thu, Mar 07, 2013 at 10:15:17AM -0700, Scott Moreau wrote:
> Fix a couple leaks caught by valgrind.
Thanks, applied.
Kristian
> src/gl-renderer.c |2 ++
> src/shell.c |1 +
> 2 files changed, 3 insertions(+)
>
> diff --git a/src/gl-renderer.c b/src/gl-renderer.c
> index a5dc2f
On Mon, Mar 18, 2013 at 03:55:03AM +0100, Sylvain BERTRAND wrote:
> But I'm still kind of uncomfortable to hand over to the
> compositor scaling in the case of fullscreen and buffer transform
> in the case of output tilting (renaming transform to tilting
> would not be a bad idea).
Oops! Of course
On Fri, Mar 01, 2013 at 03:38:23PM +0100, Andre Heider wrote:
> Use --git-dir instead of --work-tree, see
> http://marc.info/?l=git&m=120390208721287&w=2
>
> Signed-off-by: Andre Heider
Yeah, that looks better, thanks.
Kristian
> ---
> src/Makefile.am | 2 +-
> 1 file changed, 1 insertion(+),
On Fri, Mar 01, 2013 at 02:06:03PM +0200, Ander Conselvan de Oliveira wrote:
> On 02/28/2013 03:52 AM, Kristian Høgsberg wrote:
> >diff --git a/src/egl/drivers/dri2/platform_wayland.c
> >b/src/egl/drivers/dri2/platform_wayland.c
> >index b5cd04a..1b42a98 100644
> >--- a/src/egl/drivers/dri2/platfo
On Fri, Mar 01, 2013 at 02:03:20PM +0200, Ander Conselvan de Oliveira wrote:
> On 02/28/2013 03:52 AM, Kristian Høgsberg wrote:
> >---
> > include/GL/internal/dri_interface.h| 14 +++-
> > src/mesa/drivers/dri/intel/intel_regions.c | 33 +++
> > src/mesa/drivers/dri/int
On Mon, Mar 18, 2013 at 4:59 PM, Bill Spitzak wrote:
> For text, I would expect the input method is going to do the key-repeat. I
Not really, there may not be an input method, in which case the client
will get key events directly from the compositor, so the auto
repeating shouldn't depending on i
When the kernel event queue overruns, the evdev.c will:
1. Skip events until and up to the next SYN_REPORT
2. Notify the compositor of the lag, the compositor can specify
a key range of a key buttons to query the state of. The compositor
will also invalidate the button event counters, if any.
Jerome Glisse wrote:
Yes this is the idea i had, the client render in screen space and send
to the server a possible bigger buffer than what its window need.
Client send the screen space buffer size (wdith & height) but also the
untransformed size (width and height) and the transformation matrix
On Mon, Mar 18, 2013 at 4:17 PM, Bill Spitzak wrote:
> Jason Ekstrand wrote:
>
>>> For sub-pixel rendering the solution i have been thinking for a while
>>> but still haven't had time to prototype on weston, is to have weston
>>> send the transformation matrix to the client have the client render
On Mon, Mar 18, 2013 at 3:29 PM, Bill Spitzak wrote:
> Scott Moreau wrote:
>
>> Note to Bill Spitzac: I find your posts to be often frivolous and
>> incoherent. I don't mean to be rude here but I have tried to consider
>> many of your points and you often go on long tangents about some
>> problem
Are there *any* comments on this patch? Tell me if it is wrong, please!
spit...@gmail.com wrote:
From: spitzak
This allows X applications to be run on wayland without having to
delete conf files needed to run the legacy X server on the same machine.
Currently you must use an xwayland.conf fil
Scott Moreau wrote:
Note to Bill Spitzac: I find your posts to be often frivolous and
incoherent. I don't mean to be rude here but I have tried to consider
many of your points and you often go on long tangents about some
problem that doesn't exist in reality or a highly isolated use case.
Many t
On Mon, Mar 18, 2013 at 3:43 PM, Hardening wrote:
> . . .
> I still think it's a good thing for clients to know when the compositor
> is shutting down cleanly. In the present situation, we have the
> following cases:
> * the compositor crashes: from the client point of view the socket
> disconnect
For text, I would expect the input method is going to do the key-repeat.
I can't see any way around that. So for the most common use of key
repeat it is going to be handled outside the client, and users will see
a held-down letter repeatedly insert at the same rate in all clients (or
at least a
Jonas Ådahl wrote:
A logical surface is a special kind of surface that never gets its own
buffer attached, or opaque region set etc. It is obtained by using a
surface handle that can be shared in some way between clients. A handle
is a server wide unique identifier retrieved from the server giv
On 18/03/2013 13:48, Uli Schlachter wrote:
> Hi,
>
> On 18.03.2013 00:30, Hardening wrote:
>> On 17/03/2013 23:59, Sylvain BERTRAND wrote:
>>> On Sun, Mar 17, 2013 at 11:32:21PM +0100, Hardening wrote:
This patch adds a shutdow event so that clients can be notified
when the compositor is
Hi Jason,
First I'd like to thank you for your attention to this matter. I have
been looking for someone to address this series so I can bounce ideas
around and discuss this. There are many interesting possibilities
here. You hit many points dead-on. Comments below.
On Mon, Mar 18, 2013 at 1:10 P
Jason Ekstrand wrote:
For sub-pixel rendering the solution i have been thinking for a while
but still haven't had time to prototype on weston, is to have weston
send the transformation matrix to the client have the client render in
screen coordinate space and when commiting its surface the clien
I think the compositor has to be able to tell the client what transform
it plans to apply to the surface, and the client when setting the buffer
is able to say what transform it used to draw it.
This would also replace the current indications of 90 degree rotations.
The original email does poi
I guess I still question why you are not just calling yy_scan_bytes. If
you look at the output of flex it contains the source code for
yy_scan_bytes, which shows it doing *exactly* the same thing (allocating
a buffer 2 bytes larger, copying the memory block, setting the nulls,
then calling yy_s
Ok, so allow me to try and sum up how I understand the discussion going so far.
It seems as if multiple buffers per surface is probably overkill.
However, we do want some sort of scaling support. Scaling could be
used for things like videos or for a surface that needs to be
displayed at different
Scott,
Allow me to be a bit more specific as to what I am thinking. In
general, I like the requests and events in the protocol, I just think
things should be set out more clearly. The documentation given in the
protocol isn't terribly specific as to how someone is supposed to
implement it. From
On Thu, Mar 14, 2013 at 3:38 AM, Pekka Paalanen wrote:
> On Wed, 13 Mar 2013 19:52:55 +0100
> Sylvain BERTRAND wrote:
>
>> The other option would be to ignore those output properties, and
>> the compositor would manage something with an output agnostic
>> buffer. In that case, we would remove th
On 17 March 2013 22:59, Sylvain BERTRAND wrote:
> Is the socket disconnect not enough information for the clients?
The salient question is: "what would you do differently as a client
given a shutdown message than you would do given a SIGPIPE or an EPIPE
error?"
Whatever it is, it can't involve
On 03/08/2013 09:17 PM, Pekka Vuorela wrote:
> On 19.02.2013 20:26, Jan Arne Petersen wrote:
>> From: Jan Arne Petersen
>>
>> This series finalizes the first version of the text protocol and
>> moves it from Weston to Wayland, so that it can be implemented in
>> toolkits.
>>
>> It adds the missing
Hi,
On 18.03.2013 00:30, Hardening wrote:
> On 17/03/2013 23:59, Sylvain BERTRAND wrote:
>> On Sun, Mar 17, 2013 at 11:32:21PM +0100, Hardening wrote:
>>> This patch adds a shutdow event so that clients can be notified
>>> when the compositor is about to exit (and potentially kill its
>>> child pr
2013/3/18 Yichao Yu
> On Sun, Mar 17, 2013 at 7:30 PM, Hardening wrote:
> > On 17/03/2013 23:59, Sylvain BERTRAND wrote:
>
[...]
> > As most of the time the compositor launched all the wayland clients,
> > they may be killed before they discover the socket has disconnected.
> >
> > It can be se
37 matches
Mail list logo