May 2007 - xmonad - Haskell.org

Issue 4 in project xmonad
by codesite-noreply＠google.com 23 May '07

23 May '07

Issue 4: Implement float layer http://code.google.com/p/xmonad/issues/detail?id=4 Comment #2 by SpencerJanssen: Bumping to 0.3 milestone Issue attribute updates: Labels: -Milestone-Release0.2 Milestone-Release0.3 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

darcs patch: commands-not-bindings (and 2 more)
by glasser＠mit.edu 23 May '07

23 May '07

Here's some things I've been playing around with. I don't actually expect this to be committed; but it might be interesting to people. They depend on XMonadContrib (Dmenu, Dzen, and NamedWindows), including a not-yet-accepted patch "Allow clients of NamedWindows to get at the name"; and copies of dmenu and dzen compiled with Xinerama support (patches by jcreigh and me respectively). The first patch basically gets rid of all the key bindings except one, and makes that key pop up a dmenu which lets the user choose the commands that used to be on key bindings. The second patch is just minor tweaks and not worth paying attention to. The third patch is definitely work-in-progress: it'll dzen the X title of the focused window to each Xinerama screen. I'd like it to eventually list the other windows too. Wed May 23 09:36:14 EDT 2007 glasser(a)mit.edu * commands-not-bindings My initial xmonad tweaks: use dmenu commands instead of key bindings. Wed May 23 11:49:29 EDT 2007 glasser(a)mit.edu * tweak-command-key-and-restart Wed May 23 14:45:53 EDT 2007 glasser(a)mit.edu * Start of a dzen-based per-Xinerama screen window list command.

1 0

patch: Xinerama support for dzen
by David Glasser 23 May '07

23 May '07

Inspired by jcreigh's patch for dmenu (http://www.jcreigh.com/xmonad/xinerama-dmenu.html) here's a patch to add Xinerama support to dzen. By changing stuff in config.mk, you can make it entirely disappear. If it's compiled in, you can add "-xs 1" to your command line to place the message on screen 1, etc. --dave -- David Glasser | glasser(a)mit.edu | http://www.davidglasser.net/

1 0

darcs patch: Extract NamedWindow support from Mosaic into its own m...
by glasser＠mit.edu 23 May '07

23 May '07

Wed May 23 11:58:55 EDT 2007 glasser(a)mit.edu * Extract NamedWindow support from Mosaic into its own module

2 1

darcs patch: remove SwapFocus (which is no longer possible)
by David Roundy 23 May '07

23 May '07

Wed May 23 08:38:41 PDT 2007 David Roundy <droundy(a)darcs.net> * remove SwapFocus (which is no longer possible) This module depended on the focus stack.

2 2

[PATCH: XMonadContrib] Spiral tile layout
by Joe Thornber 23 May '07

23 May '07

Hi, Attached is a darcs patch to XMonadContrib. It is a new tile layout mode that arranges the windows in a spiral. The ratio can be adjusted using mod-h and mod-l as in the other modes. - Joe

4 6

sprial tiling
by dons＠cse.unsw.edu.au 22 May '07

22 May '07

A screenshot of sprial tiling, with X composite stuff, Spencer did, http://cse.unl.edu/~sjanssen/xcomp_spiral.png -- Don

1 1

darcs patch: Make RotView compile.
by Miikka Koskinen 22 May '07

22 May '07

Tue May 22 10:53:38 EEST 2007 Miikka Koskinen <arcatan(a)kapsi.fi> * Make RotView compile. As I'm not a Xinerama user, I'm not sure if rotView should consider only hidden workspaces or also visible but not focused workspaces. I thought hidden workspaces only would be more logical.

3 2

darcs patch: make DwmPromote compile (and 2 more)
by Miikka Koskinen 22 May '07

22 May '07

Mon May 21 15:31:40 EEST 2007 Miikka Koskinen <arcatan(a)kapsi.fi> * make DwmPromote compile Mon May 21 15:32:39 EEST 2007 Miikka Koskinen <arcatan(a)kapsi.fi> * make FindEmptyWorkspace compile Tue May 22 09:21:18 EEST 2007 Miikka Koskinen <arcatan(a)kapsi.fi> * bug fix in DwmPromote. whoops.

2 1

moveLeft, moveRight
by Robert Marlow 22 May '07

22 May '07

Hi I've implemented an alternative to the current "swap" function in StackSet.hs. The alternative uses two functions moveLeft and moveRight (very similar to focusLeft and focusRight) to provide basic window reordering functions. These functions can then be used to build more complicated functions such as DWM-style promoting and the current method of swapping. moveLeft = modify Empty $ \c -> case c of Node _ [] [] -> c Node t (l:ls) rs -> Node t ls (l:rs) Node t [] rs -> Node t (reverse rs) [] moveRight = modify Empty $ \c -> case c of Node _ [] [] -> c Node t ls (r:rs) -> Node t (r:ls) rs Node t ls [] -> Node t [] (reverse ls) Three further functions are also useful: -- -- /O(1)/ Check if focused element is in the master position masterIsFocus :: StackSet i a s -> Bool masterIsFocus = with False (null . left) -- -- /O(1)/ Check if current stack is empty stackIsEmpty :: StackSet i a s -> Bool stackIsEmpty = with True (const False) -- -- /O(l), l is number of windows left of the focused window/. -- -- Get index of focused window in the stack's current ordering focusPosition :: StackSet i a s -> Maybe Int focusPosition = with Nothing (Just . length . left) I find moveLeft and moveRight are useful functions in their own right for binding to keys. But with the above three functions, swap and DWM-style promote can both be built in Config.hs (after importing StackSet qualified as W): untilMaster :: (W.StackSet i a s -> W.StackSet i a s) -> W.StackSet i a s -> W.StackSet i a s untilMaster f s | W.stackIsEmpty s = s | W.masterIsFocus s = s | otherwise = untilMaster f (f s) focusToMaster, masterToFocus :: W.StackSet i a s -> W.StackSet i a s focusToMaster = untilMaster W.moveLeft masterToFocus = untilMaster W.focusLeft promote :: X () promote = windows focusToMaster swap :: X () swap = windows $ \w -> case W.focusPosition w of Nothing -> w Just i -> masterToFocus $ (doTimes (i-1) W.moveRight) $ W.focusRight $ focusToMaster w where doTimes j f x = if j <= 0 then x else doTimes (j-1) f (f x) The advantage is that moveLeft and moveRight are more basic functions for building more complex functionality, especially when combined with masterIsFocus, stackIsEmpty and focusPosition. moveLeft and moveRight also display very similar properties to focusLeft and focusRight meaning they can be checked as thoroughly. The disadvantage is that it's a fair bit more code. The implementation of moveLeft and moveRight are very similar to focusLeft and focusRight. Some clever way to get rid of code duplication would be nice. How does everyone feel about this idea? I can soon have a patch ready with quickcheck properties if it's wanted. -- Robert Marlow <bobstopper(a)bobturf.org>

2 2