June 2007 - xmonad - Haskell.org

More on 0.3 release
by dons＠cse.unsw.edu.au 26 Jun '07

26 Jun '07

We've narrowed down the list of tasks left for the 0.3 (floating layer) release. Researchy tasks are bumped to 0.4, to prevent instability coming in: * finish floating layer/fullscreen integration (dons) draft complete, 1/2 day merge, at least a week's testing * (maybe) layout info persist across restart (sjanssen) unknown, easy to test * filters to manage (so you can specify rules for which workspace/layer an app starts in) an hour? ,easy to test * greedy-by-default workspace switching (sjanssen/jcreigh) already implemented Which bumps back to 0.4 the following: * dock STRUT support -- requires sticky windows of some kind * managed gap layer (again, sticky windows somehow) * sticky windows in the droundy style. So, if 0.3 is the floating layer release, looks like 0.4 will be the sticky windows release, assuming we can come up with a nice way to manage us these things. David, get started on thinking about this -- if you're not already :-) -- Don

2 2

darcs patch: MetaModule.hs: add LayoutHelpers. (and 1 more)
by joachim.fasting＠gmail.com 26 Jun '07

26 Jun '07

Tue Jun 26 08:55:22 CEST 2007 joachim.fasting(a)gmail.com * MetaModule.hs: add LayoutHelpers. Also tweaks import ordering slightly. Tue Jun 26 09:14:49 CEST 2007 joachim.fasting(a)gmail.com * Accordion.hs: whitespace. Makes Haddock not complain about not finding documentation for '$'.

2 1

darcs patch: simplify StackSet.delete (and 2 more)
by David Roundy 26 Jun '07

26 Jun '07

Sorry, I forgot to send this earlier. These are the changes needed to support sticky windows. David Sun Jun 24 07:48:54 PDT 2007 David Roundy <droundy(a)darcs.net> * simplify StackSet.delete Sun Jun 24 07:59:31 PDT 2007 David Roundy <droundy(a)darcs.net> * make delete work when window is in multiple workspaces. Sun Jun 24 08:02:08 PDT 2007 David Roundy <droundy(a)darcs.net> * fix apparent memory leak when floating windows are deleted.

4 5

Issue 12 in xmonad: Support _NET_WM_STRUT property for status bar programs
by codesite-noreply＠google.com 26 Jun '07

26 Jun '07

Issue 12: Support _NET_WM_STRUT property for status bar programs http://code.google.com/p/xmonad/issues/detail?id=12 Comment #6 by dons00: Likely needs to be held in a sticky layer, however we plan to support that. See [http://code.google.com/p/xmonad/issues/detail?id=27&can=2&q= #27]. Bumping to 0.4 Issue attribute updates: Labels: -Milestone-Release0.3 Milestone-Release0.4 -- 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

Issue 27 in xmonad: Handle sticky windows
by codesite-noreply＠google.com 26 Jun '07

26 Jun '07

Issue 27: Handle sticky windows http://code.google.com/p/xmonad/issues/detail?id=27 Comment #2 by dons00: Rename this to be the 'sticky windows' issue. Likely to be resolved for 0.4. Issue attribute updates: Summary: Handle sticky windows Labels: -Type-Defect Type-Enhancement Milestone-Release0.4 -- 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: add CopyWindow module, to support sticky/tagged windows.
by David Roundy 26 Jun '07

26 Jun '07

Hi all, Here's support for sticky windows and dwm-style tagging. Requires (I believe) my improved delete. It almost duplicates code in StackSet, since I wanted to make as few modifications as possible. So by default, insertUp will refuse to act on sticky windows, and shift will delete a sticky window from all workspaces but one. We can later decide if we want to change their behavior in core to behave well with sticky windows, or just duplicate it here. My feeling is that this module eventually belongs in core, but that contrib is the right place to develop it. kill1, for instance, I think could probably eventually replace kill (it behaves identically on non-sticky windows), and with changes to the quickcheck tests, insertUp' could replace insertUp. David Sun Jun 24 08:56:48 PDT 2007 David Roundy <droundy(a)darcs.net> * add CopyWindow module, to support sticky/tagged windows. This module allows dwm-style tagging (as I understand dwm). You can have a given window visible in multiple workspaces. If it's visible in two workspaces both of which are visible, a gap will show up in one of them (which is something that needs fixing in xmonad core). Also defines a kill1 which is like kill, but only removes from the current workspace a window if it's in multiple workspaces.

2 1

darcs patch: broadcast unidentified events.
by David Roundy 26 Jun '07

26 Jun '07

This fixes the display bug with Xinerama + my latest doLayout changes for me. David Sat Jun 23 14:41:25 PDT 2007 David Roundy <droundy(a)darcs.net> * broadcast unidentified events. This change is independent of the doLayout change I just sent in, but fixes the problem that change introduces in Decoration, by ensuring that all Layouts get redraw events. I think this is the correct behavior.

2 1

darcs patch: Decoration.hs: added automatic font mana... (and 2 more)
by Andrea Rossato 25 Jun '07

25 Jun '07

As I promised here are the patches: nedDecoration and withGC now take also a font name, this way font management is totally hidden. Let me know. ciao andrea Mon Jun 25 15:57:22 CEST 2007 Andrea Rossato <andrea.rossato(a)unibz.it> * Decoration.hs: added automatic font managment newDecoration now takes also a fontname to set fonts in decorations that use them. If an empty string is send the the default Xorg fonts will be loaded. Mon Jun 25 16:01:12 CEST 2007 Andrea Rossato <andrea.rossato(a)unibz.it> * added configration options and moved font stuff to Decorations.hs Added a new data type to keep configuration options. tabbed now takes the shrinker and the configuration type. Fixed a bug related to vertical alignment of text. Mon Jun 25 16:07:35 CEST 2007 Andrea Rossato <andrea.rossato(a)unibz.it> * Tabbed.hs: updated usage information

2 1

xmobar-0.2 released!
by Andrea Rossato 25 Jun '07

25 Jun '07

Hi! I've just released a new version of XMobar, xmobar-0.2, the status bar for xmonad. This release fixes two memory leaks: one due to an inappropriate use of the FontStruct data structure. The second one due to a probable bug in System.Process.runInteractiveProcess. XMobar now uses runInteractiveCommand, that does not appear to leak memory. You can grab XMobar here: http://gorgias.mine.nu/xmobar/xmobar-0.2.tar.gz if this server is down try here: http://gipc49.jus.unitn.it:8080/xmobar/xmobar-0.2.tar.gz Darcs: http://gorgias.mine.nu/repos/xmobar/ (btw, when I apply new patches to that repository, the new patches show up in _darcs/patches/ as read by the author only... I need to figure that out...;-) Hope you'll enjoy. Andrea

1 0

Issue 27 in xmonad: Unmanaged windows should be able to be assigned to custom layout algorithms
by codesite-noreply＠google.com 25 Jun '07

25 Jun '07

Issue 27: Unmanaged windows should be able to be assigned to custom layout algorithms http://code.google.com/p/xmonad/issues/detail?id=27 Comment #1 by dons00: With line wrapping: In Xmonad, a window becomes unmanaged by having the override redirect flag set. This then means that the windows geometry, defined in .Xdefaults, is used. This is non-optimal when working with multiple resolutions on a regular basis. Laptops that are frequently plugged in to external monitors are screwed. It would be nice if we could have layout algorithms for the non-managed gaps as well as for the managed center. The gaps are rectangles afterall, and you could have a default layout of un-managed so that no functionalty would be changed, just added. More info please, Tim. What is the problem, how do we reproduce it? If its a feature request, clarify what precisely is desired. Issue attribute updates: Summary: Unmanaged windows should be able to be assigned to custom layout algorithms -- 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

2 1