On Thu, Jun 13, 2013 at 5:42 PM, Bill Spitzak spit...@gmail.com wrote:
sardemff7+wayl...@sardemff7.net wrote:
This is a requirement so that non-trivial clients can be written
that are not forced to blink the transient windows to change their
parenting.
Do you have a use case for this
On 12/06/2013 21:39, Bill Spitzak wrote:
Shell surface types, exclusive: - top-level - transient (umm,
what was this for, again?) - popup (menu?)
Transcient is for dialog (modal?) boxes, isn’t it?
It means this window stays above another one.
Transient cannot be a type, but instead a
On Wed, 12 Jun 2013 18:31:17 -0700
Bill Spitzak spit...@gmail.com wrote:
Rafael Antognolli wrote:
Rafael Antognolli
I've just updated the proposal, considering my last statement. Take
a look at it and see if it fits your suggestion.
This lets us with 2 surface types (toplevel and
sardemff7+wayl...@sardemff7.net wrote:
This is a requirement so that non-trivial clients can be written
that are not forced to blink the transient windows to change their
parenting.
Do you have a use case for this scenario ? There are probably some I
cannot see, but maybe could we solve them
On 12/06/2013 09:57, Pekka Paalanen wrote:
To get the big picture, let me reiterate the surface classification as
a whole, the way I see it.
Surface roles, exclusive:
- cursor
- drag icon
- shell surface
Each role is an interface then? Simple and efficient, I love it.
Shell surface types,
On Wed, 12 Jun 2013 10:23:33 +0200
sardemff7+wayl...@sardemff7.net wrote:
On 12/06/2013 09:57, Pekka Paalanen wrote:
To get the big picture, let me reiterate the surface classification as
a whole, the way I see it.
Surface roles, exclusive:
- cursor
- drag icon
- shell surface
On 12/06/2013 11:18, Pekka Paalanen wrote:
On Wed, 12 Jun 2013 10:23:33 +0200
sardemff7+wayl...@sardemff7.net wrote:
On 12/06/2013 09:57, Pekka Paalanen wrote:
To get the big picture, let me reiterate the surface classification as
a whole, the way I see it.
Surface roles, exclusive:
- cursor
On Wed, Jun 12, 2013 at 5:23 AM, sardemff7+wayl...@sardemff7.net wrote:
On 12/06/2013 09:57, Pekka Paalanen wrote:
To get the big picture, let me reiterate the surface classification as
a whole, the way I see it.
Surface roles, exclusive:
- cursor
- drag icon
- shell surface
Each role
On Wed, Jun 12, 2013 at 6:25 AM, sardemff7+wayl...@sardemff7.net wrote:
On 12/06/2013 11:18, Pekka Paalanen wrote:
On Wed, 12 Jun 2013 10:23:33 +0200
sardemff7+wayl...@sardemff7.net wrote:
On 12/06/2013 09:57, Pekka Paalanen wrote:
To get the big picture, let me reiterate the surface
On Wed, Jun 12, 2013 at 5:23 AM, sardemff7+wayl...@sardemff7.net wrote:
On 12/06/2013 09:57, Pekka Paalanen wrote:
To get the big picture, let me reiterate the surface classification as
a whole, the way I see it.
Surface roles, exclusive:
- cursor
- drag icon
- shell surface
Each role
On Wed, Jun 12, 2013 at 4:39 PM, Bill Spitzak spit...@gmail.com wrote:
Shell surface types, exclusive:
- top-level
- transient (umm, what was this for, again?)
- popup (menu?)
Transcient is for dialog (modal?) boxes, isn’t it?
It means this window stays above another one.
Transient
On Wed, Jun 12, 2013 at 7:39 PM, Rafael Antognolli antogno...@gmail.com wrote:
On Wed, Jun 12, 2013 at 4:39 PM, Bill Spitzak spit...@gmail.com wrote:
Shell surface types, exclusive:
- top-level
- transient (umm, what was this for, again?)
- popup (menu?)
Transcient is for dialog (modal?)
Rafael Antognolli wrote:
Rafael Antognolli
I've just updated the proposal, considering my last statement. Take a
look at it and see if it fits your suggestion.
This lets us with 2 surface types (toplevel and fullscreen), and 5
states (maximized, minimized, sticky, always_on_top and
On Thu, Jun 6, 2013 at 3:50 PM, Kristian Høgsberg k...@bitplanet.net wrote:
On Tue, May 28, 2013 at 1:10 PM, Rafael Antognolli antogno...@gmail.com
wrote:
On Thu, May 16, 2013 at 2:12 PM, Bill Spitzak spit...@gmail.com wrote:
Pekka Paalanen wrote:
For example the floating shared toolbox
On Tue, May 28, 2013 at 1:10 PM, Rafael Antognolli antogno...@gmail.com wrote:
On Thu, May 16, 2013 at 2:12 PM, Bill Spitzak spit...@gmail.com wrote:
Pekka Paalanen wrote:
For example the floating shared toolbox with 2 main windows. It should
only disappear when *both* main windows are
On Thu, May 16, 2013 at 2:12 PM, Bill Spitzak spit...@gmail.com wrote:
Pekka Paalanen wrote:
For example the floating shared toolbox with 2 main windows. It should
only disappear when *both* main windows are minimized.
You very conventiently removed my next sentence, where I already took
On Tue, May 28, 2013 at 3:10 PM, Rafael Antognolli antogno...@gmail.comwrote:
On Thu, May 16, 2013 at 2:12 PM, Bill Spitzak spit...@gmail.com wrote:
Pekka Paalanen wrote:
For example the floating shared toolbox with 2 main windows. It should
only disappear when *both* main windows
On Wed, 15 May 2013 15:26:02 +0200
Alexander Preisinger alexander.preisin...@gmail.com wrote:
2013/5/15 Pekka Paalanen ppaala...@gmail.com
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
On Wed, 15 May 2013 12:27:17 -0700
Bill Spitzak spit...@gmail.com wrote:
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.
Pekka Paalanen wrote:
For example the floating shared toolbox with 2 main windows. It should
only disappear when *both* main windows are minimized.
You very conventiently removed my next sentence, where I already took
this into account.
- pq
Sorry, obviously I did not read very carefully:
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 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
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
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 Mon, 13 May 2013 17:26:28 -0500
Jason Ekstrand ja...@jlekstrand.net wrote:
On Mon, May 13, 2013 at 4:14 PM, Rafael Antognolli
antogno...@gmail.comwrote:
Hi Jason,
On Wed, May 8, 2013 at 9:26 PM, Jason Ekstrand ja...@jlekstrand.net
wrote:
Hi Rafael,
On Wed, May 8, 2013
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 code relative to maximized windows, and
it seems that the respective code for
On Mon, May 13, 2013 at 4:14 PM, Rafael Antognolli antogno...@gmail.comwrote:
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
Hello,
I've been looking the Weston code relative to maximized windows, and
it seems that the respective code for minimized windows wouldn't be
hard to implement.
The questions are: are there any plans to add it? Is there someone
already working on it? If not, would it be OK if I start
Hi Rafael,
On Wed, May 8, 2013 at 6:04 PM, Rafael Antognolli antogno...@gmail.comwrote:
Hello,
I've been looking the Weston code relative to maximized windows, and
it seems that the respective code for minimized windows wouldn't be
hard to implement.
The questions are: are there any plans
33 matches
Mail list logo
