[dwm] a lone client could be borderless

[Ralph E. Carter]

When only one client is in a workspace (or tagset, or view), 
it could be borderless.

In the default geom, or in bottomstack, the border is unnecessary.
In my favorite monocle, any border would remind that something is 
below.

_
Windows Live Hotmail is giving away Zunes.
http://www.windowslive-hotmail.com/ZuneADay/?locale=en-USocid=TXT_TAGLM_Mobile_Zune_V3

Re: [dwm] a lone client could be borderless

[yy]

2008/3/21, Ralph E. Carter [EMAIL PROTECTED]:

  When only one client is in a workspace (or tagset, or view),
  it could be borderless.

  In the default geom, or in bottomstack, the border is unnecessary.
  In my favorite monocle, any border would remind that something is
  below.


That's a good idea.

-- 


- yiyus || JGL .

Re: [dwm] a lone client could be borderless

[markus schnalke]

Ralph E. Carter [EMAIL PROTECTED] wrote:
 
 When only one client is in a workspace (or tagset, or view), 
 it could be borderless.
 
 In the default geom, or in bottomstack, the border is unnecessary.
 In my favorite monocle, any border would remind that something is 
 below.

No.
The border says: this is the active client.


But anyway, special corner case handling leads to bad code. It
conflicts with generality, which is one of the design principles.


meillo

Re: [dwm] a lone client could be borderless

[Szabolcs Nagy]

On 3/21/08, markus schnalke [EMAIL PROTECTED] wrote:
 But anyway, special corner case handling leads to bad code. It
 conflicts with generality, which is one of the design principles.

if you look into the code then you will realise that the 'one tiled
client' case is handled specially anyway
(there is a 'if (--n==0)' branch)

in my setup if (n == 1) then layout falls back to monocle (which is borderless)

Re: [dwm] a lone client could be borderless

[Ralph E. Carter]

 Date: Fri, 21 Mar 2008 19:49:18 +0100
 From: [EMAIL PROTECTED]
 To: dwm@suckless.org
 Subject: Re: [dwm] a lone client could be borderless
 
 On 3/21/08, markus schnalke  wrote:
 But anyway, special corner case handling leads to bad code. It
 conflicts with generality, which is one of the design principles.

I understand. My principle would be the border only appears when needed.

 if you look into the code then you will realise that the 'one tiled
 client' case is handled specially anyway
 (there is a 'if (--n==0)' branch)
 
 in my setup if (n == 1) then layout falls back to monocle (which is 
 borderless)

Hey!
Thanks to your hint, I did it.

In dwm.c: 
In tileh() and tilev(), call monocle:

if(--n == 0) {
monocle();
return;
}

In monocle(), adjust as discussed above: 

resize(c, mox - c-bw, moy - c-bw, mow, moh, 
RESIZEHINTS);

(It is here that the multi-monitor behavior might be affected. I don't know. 
Have you tried this on multi-monitors?)

Now my dwm-4.9 appears to be perfect.
(Off topic: I apologize for the Windows footer added to these posts. 
I want to leave Hotmail, and do something with Wordpress, or obtain
hosting somewhere, but I am unsure how to proceed.)


_
In a rush?  Get real-time answers with Windows Live Messenger.
http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_realtime_042008

Re: [dwm] a lone client could be borderless

[Don Stewart]

vamosaverlas:
 
  Date: Fri, 21 Mar 2008 19:49:18 +0100
  From: [EMAIL PROTECTED]
  To: dwm@suckless.org
  Subject: Re: [dwm] a lone client could be borderless
  
  On 3/21/08, markus schnalke  wrote:
  But anyway, special corner case handling leads to bad code. It
  conflicts with generality, which is one of the design principles.
 
 I understand. My principle would be the border only appears when needed.

for what its worth, we had to tackle this too in xmonad, which now has
an extension, 'smart borders', that tries to apply this rule. given any
layout, it uses some heuristics to hide the border of windows in that
layout (its a layout modifier, basically)

http://xmonad.org/xmonad-docs/xmonad-contrib/XMonad-Layout-NoBorders.html

so any layout, with a single client, or a fullscreen client, or a
floating window at fullscreen, etc.

for the xinerama case, its a bit tricky: you sometimes need the border
to decide which screen has focus.

-- Don