This series adds a wl_debug function and associated handler that can be set
by the uesr. The first patch is merely a rename to prepare for the third.
The second adds a useful helper function used by the third.
Jason Ekstrand (3):
Rename wl_debug to debug_server/client
Add a wl_array_printf fu
Signed-off-by: Jason Ekstrand
---
src/wayland-client.c | 10 +-
src/wayland-server.c | 10 +-
2 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/src/wayland-client.c b/src/wayland-client.c
index 363d5dd..799ebab 100644
--- a/src/wayland-client.c
+++ b/src/wayland-cli
In order to keep from overloading the debug handler, we first squash the
entire message into a string and call wl_debug once.
Signed-off-by: Jason Ekstrand
---
src/connection.c | 54 ---
src/wayland-client.c | 6 ++
src/wayland-client.h
Signed-off-by: Jason Ekstrand
---
src/wayland-util.c | 41 +
src/wayland-util.h | 1 +
2 files changed, 42 insertions(+)
diff --git a/src/wayland-util.c b/src/wayland-util.c
index 4fe9c81..c9d6d0e 100644
--- a/src/wayland-util.c
+++ b/src/wayland-util.c
@
FreeRDS is a FreeRDP based RDP server, the server handles incoming connections
and
talks RDP with the peers. FreeRds cooperates with an "out-service": the
out-service creates
the content to display, and FreeRds will take care of encoding the content in
the
appropriate format (bitmapUpdate, remot
From: Ander Conselvan de Oliveira
Record from the output of the surface that has keyboard focus for the
seat used to activate the recorder key binding. If there is no focused
surface, record from the first one.
Also, use the weston_transformed_region() to transform the damage
region of the outpu
From: Ander Conselvan de Oliveira
That way log messages referencing the output are more informative.
---
src/compositor-x11.c |4
1 file changed, 4 insertions(+)
diff --git a/src/compositor-x11.c b/src/compositor-x11.c
index 2ef1b5d..1b178b8 100644
--- a/src/compositor-x11.c
+++ b/src/
Wayland has a lot of components: the code generator, the protocol, the
client/server lib implementation, the design decisions we made to tie it
all together. Yes, we aren't the greatest at documentation and we know that
a lot is missing, but in general we assume experience with traditional
toolkits
Well, the diagrams are very high level, and the docs are about the
API. But if you want to understand how Wayland works internally I
think you must look at the code.
2013/12/18 Artsiom Anikeyenka :
> Hmmm, thanks, but I've seen those. I though maybe there is something more.
> Ok I guess the good q
Hmmm, thanks, but I've seen those. I though maybe there is something more.
Ok I guess the good question will be:
Do most of developers find it detailed and descriptive enough?
I mean I'm still learning so maybe I just don't know enough to understand.
Thanks, and have a very good day :)
On Wed
10 matches
Mail list logo