On Tue, May 14, 2013 at 9:46 PM, Bill Spitzak spit...@gmail.com wrote:
John Kåre Alsaker wrote:
I expect a compositor to render deviations of the desired scaling
factor without scaling windows. The range when this is allowed is
reported to clients so they can try to render at
John Kåre Alsaker wrote:
For example a compositor may want to use a 1-1.2 range with
1.1 as
the desired scaling factor. A clients which are only able to
draw at
integer scaling factor would round that up to 2 and let the
On Tue, 14 May 2013 13:43:12 -0700
Bill Spitzak spit...@gmail.com wrote:
You may also want to allow different horizontal and vertical scales,
mostly because all plausable implementations can do this with no loss of
speed, and the scaler api allows this. You will need to define if this
is
On tis, 2013-05-14 at 13:43 -0700, Bill Spitzak wrote:
al...@redhat.com wrote:
+ /description
+ arg name=scale type=fixed/
+/request
/interface
Fixed is not a good idea for scaling factors. You cannot accurately
represent values like 2/3 or 1/fixed. For an actual
On Tue, 14 May 2013 12:26:48 +0200
al...@redhat.com wrote:
From: Alexander Larsson al...@redhat.com
This adds wl_surface_set_buffer_scale() to set the buffer scale of a
surface.
It is similar to set_buffer_transform that the buffer is stored in a
way that has been transformed (in this
---
src/cms-colord.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/cms-colord.c b/src/cms-colord.c
index 33f23b2..af6b5fa 100644
--- a/src/cms-colord.c
+++ b/src/cms-colord.c
@@ -478,7 +478,7 @@ colord_cms_output_destroy(gpointer data)
WL_EXPORT int
This also fixes a compile warning when building the tarball.
---
src/cms-colord.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/src/cms-colord.c b/src/cms-colord.c
index af6b5fa..6056407 100644
--- a/src/cms-colord.c
+++ b/src/cms-colord.c
@@ -127,6 +127,7 @@
Hello happy coders,
Here are a few patches for weston, with some explanations.
They all should be updated from the previous reviews.
http://git.sardemff7.net/wayland/weston/log/?id=master..wip/patchesshowmsg=1
These patches are all independant changes to weston:
— weston.pc and layers patches
Hello,
I thought a bit about it and like to present my ideas.
I mainly thought about it from the shell/compositor site when I like to
minimize, maximize surfaces from keybindings, like in some window managers.
For example the client can still request minimize, maximize, fullsrceen and
toplevel
On Wed, 15 May 2013 14:20:21 +0200
Alexander Preisinger alexander.preisin...@gmail.com wrote:
Hello,
I thought a bit about it and like to present my ideas.
I mainly thought about it from the shell/compositor site when I like to
minimize, maximize surfaces from keybindings, like in some
On ons, 2013-05-15 at 11:13 +0300, Pekka Paalanen wrote:
On Tue, 14 May 2013 12:26:48 +0200
al...@redhat.com wrote:
Lots of good stuff snipped. I'll try to fix things up based on that.
Some responses below.
+ /description
+ arg name=scale type=fixed/
Are you sure you really
On Wed, May 15, 2013 at 9:11 AM, Alexander Larsson al...@redhat.com wrote:
On ons, 2013-05-15 at 11:13 +0300, Pekka Paalanen wrote:
On Tue, 14 May 2013 12:26:48 +0200
al...@redhat.com wrote:
Lots of good stuff snipped. I'll try to fix things up based on that.
Some responses below.
+
This allows the shell to inform the surface that it has changed
state, current supported states are default, minimized, maximized
and fullscreen. The shell implementation is free to interpret the
meaning for the state, i.e. the minimized might not always mean
that the surface is fully hidden for
On Wed, May 15, 2013 at 09:17:37AM +0100, Richard Hughes wrote:
---
src/cms-colord.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Thanks, this and 2/2 applied.
Kristian
diff --git a/src/cms-colord.c b/src/cms-colord.c
index 33f23b2..af6b5fa 100644
--- a/src/cms-colord.c
+++
On Mon, May 13, 2013 at 11:51:11PM -0700, Dima Ryazanov wrote:
Looks like that theme uses different names. Also, add the correspoding
horizontal and vertical resize cursors, just for consistency.
---
clients/window.c | 24
1 file changed, 16 insertions(+), 8
On Mon, May 13, 2013 at 06:14:46PM -0300, Rafael Antognolli wrote:
Hi Jason,
On Wed, May 8, 2013 at 9:26 PM, Jason Ekstrand ja...@jlekstrand.net wrote:
Hi Rafael,
On Wed, May 8, 2013 at 6:04 PM, Rafael Antognolli antogno...@gmail.com
wrote:
Hello,
I've been looking the Weston
On Wed, May 15, 2013 at 12:12:43PM -0500, Jason Ekstrand wrote:
On Wed, May 15, 2013 at 9:39 AM, Mikko Levonmaa mikko.levon...@gmail.com
wrote:
This allows the shell to inform the surface that it has changed
state, current supported states are default, minimized, maximized
and
Alexander Larsson wrote:
In fact, working on this in weston a bit it seems that in general, scale
is seldom used by itself but rather its used to calculate the buffer and
screen size which are then used, and we want both of these to be
integers. So, it seems to me that we should specify scaling
On Wed, May 15, 2013 at 1:37 PM, Mikko Levonmaa mikko.levon...@gmail.comwrote:
On Wed, May 15, 2013 at 12:12:43PM -0500, Jason Ekstrand wrote:
On Wed, May 15, 2013 at 9:39 AM, Mikko Levonmaa
mikko.levon...@gmail.com
wrote:
This allows the shell to inform the surface that it has
Alexander Preisinger wrote:
+ entry name=toplevel value=1 summary=surface is neither
maximized, minizized or fullscreen/
Maybe normal? toplevel sounds like it is in the same layer as popup
notifiers.
+This event is sent in respons to set_maximized, set_minimized or
+
Pekka Paalanen wrote:
Minimize is a little special, since the client does not need to react
specially for it to look right.
The client does have to react if there is a floating panel that also has
to disappear.
For example the floating shared toolbox with 2 main windows. It should
only
Alexander Preisinger wrote:
+enum name=state
+ entry name=default value=0/
+ entry name=minimized value=1/
+ entry name=maximized value=2/
+ entry name=fullscreen value=4/
Are these supposed to be flags? Like that it can send multiple states in
one
Mikko Levonmaa wrote:
+event name=state_changed
+ description summary=The surface state was changed
+The compositor or the user has taken action that has resulted in
+this surface to change state.
+ /description
+ arg name=state type=uint/
+/event
/interface
On Wed, May 15, 2013 at 01:57:10PM -0500, Jason Ekstrand wrote:
On Wed, May 15, 2013 at 1:37 PM, Mikko Levonmaa mikko.levon...@gmail.com
wrote:
On Wed, May 15, 2013 at 12:12:43PM -0500, Jason Ekstrand wrote:
On Wed, May 15, 2013 at 9:39 AM, Mikko Levonmaa
mikko.levon...@gmail.com
I agree that the thread is a little daunting and gets
political/personal towards the end. But between Pekka, Jason and Bill
I see concensus and I'll try to summarize here:
- The server needs to be able to initiate state changes, but the
client is in control. The server requests a
On May 15, 2013 9:37 PM, Mikko Levonmaa mikko.levon...@gmail.com wrote:
I agree that the thread is a little daunting and gets
political/personal towards the end. But between Pekka, Jason and Bill
I see concensus and I'll try to summarize here:
- The server needs to be able to initiate
Mikko Levonmaa wrote:
i.e. when going from maximized/fullscreen to the default state the
compositor could remember the last size and propose that to the client.
The client has to know the default size:
1. It may have initially shown maximized. The compositor therefore has
not seen it in
On Sun, May 12, 2013 at 04:20:59PM +0200, David Herrmann wrote:
[bcc to gnome-shell-list and kwin, to keep discussion on wayland-devel]
Without a generic graphics-server like xserver, compositors need to
handle input devices themselves if run as wayland compositors. To
avoid having several
28 matches
Mail list logo
