Re: [dwm] No Border Behaviour
Hi, 2008/12/22 Matthias-Christian Ott o...@mirix.org: Yesterday I updated my dwm tree to tip and noticed that the borders were removed (1376). This applies only to clients in tiled layout, is there a reason why this behaviour is not present in monocle? It is present in monocle as well, if there is only 1 client. This makes the new behavior also an indicator for the monocle layout if there are more clients. If no border indicates that there's just one client in the tag it makes some sense, but I rather like borderless if there's only one client visible. This seems more intuitive to me, because borders indicate a separation which is only necessary when there is more than one client visible. Yes, that's how it is supposed to be. Kind regards, --Anselm
Re: [dwm] No Border Behaviour
Anselm R Garbe wrote: Hi, Hi, 2008/12/22 Matthias-Christian Ott o...@mirix.org: Yesterday I updated my dwm tree to tip and noticed that the borders were removed (1376). This applies only to clients in tiled layout, is there a reason why this behaviour is not present in monocle? It is present in monocle as well, if there is only 1 client. This makes the new behavior also an indicator for the monocle layout if there are more clients. If no border indicates that there's just one client in the tag it makes some sense, but I rather like borderless if there's only one client visible. This seems more intuitive to me, because borders indicate a separation which is only necessary when there is more than one client visible. Yes, that's how it is supposed to be. I think, this doesn't make much sense. My proposed conception of borderless clients seems more reasonable and intuitive to me. If you take borders not as decoration (as some window manager do), but instead as separating entities, that are used to distinguish windows, it makes sense to omit the borders if only one particular window is visible, because they aren't serving any purpose. In others words: borders are superfluous in that case. What do others think about this? Maybe I have just a different conception of it than everyone else. If so, I'll simply implement this for myself, otherwise I think dwm's behaviour should be altered. Kind regards, --Anselm Regards, Matthias-Christian
Re: [dwm] No Border Behaviour
I agree with Matthias. The purpose of a border is to separate one client from another. If there is only one client visible at a given time (i.e. monocle) then borders in my opinion are a waste of space. So borders should be set to 0 whenever the layout is monocle, regardless of the number of clients tagged under the selected tag(s). -voltaic On Thu, Jan 8, 2009 at 10:15 AM, Anselm R Garbe garb...@gmail.com wrote: 2009/1/8 Matthias-Christian Ott o...@mirix.org: I think, this doesn't make much sense. My proposed conception of borderless clients seems more reasonable and intuitive to me. If you take borders not as decoration (as some window manager do), but instead as separating entities, that are used to distinguish windows, it makes sense to omit the borders if only one particular window is visible, because they aren't serving any purpose. In others words: borders are superfluous in that case. I think that is exactly how the current dwm implementation is supposed to be -- I never said anything different to that (at least not that I intended it). Kind regards, --Anselm
Re: [dwm] No Border Behaviour
I think, this doesn't make much sense. My proposed conception of borderless clients seems more reasonable and intuitive to me. If you take borders not as decoration (as some window manager do), but instead as separating entities, that are used to distinguish windows, it makes sense to omit the borders if only one particular window is visible, because they aren't serving any purpose. In others words: borders are superfluous in that case. I think that is exactly how the current dwm implementation is supposed to be -- I never said anything different to that (at least not that I intended it). Kind regards, --Anselm I agree with Matthias. The purpose of a border is to separate one client from another. If there is only one client visible at a given time (i.e. monocle) then borders in my opinion are a waste of space. So borders should be set to 0 whenever the layout is monocle, regardless of the number of clients tagged under the selected tag(s). -voltaic It is possible for multiple clients to be visible at the same time in monocle if one or more of them is floating. - David
Re: [dwm] No Border Behaviour
[2009-01-08 18:05] voltaic volt...@gmail.com I agree with Matthias. The purpose of a border is to separate one client from another. My view is: the (highlighted) border is to indicate the active client. (Normal borders are only placeholders for the highlighted border.) meillo signature.asc Description: Digital signature
Re: [dwm] No Border Behaviour
On 1/9/09, voltaic volt...@gmail.com wrote: I agree with Matthias. The purpose of a border is to separate one client from another. If there is only one client visible at a given time (i.e. monocle) then borders in my opinion are a waste of space. what's the problem? that's how tip works read carefully: On Thu, Jan 8, 2009 at 10:15 AM, Anselm R Garbe garb...@gmail.com wrote: 2009/1/8 Matthias-Christian Ott o...@mirix.org: borders if only one particular window is visible, because they aren't serving any purpose. In others words: borders are superfluous in that case. I think that is exactly how the current dwm implementation is supposed to be -- I never said anything different to that (at least not that I intended it). the only debatable question is the monocle+multiple window case, but the current solution seems perfectly reasonable you can write your own layout in config.h if different behaviour is needed
