- xmonad - Haskell.org

darcs patch: Don't print anything in getWMProtocols
by Jason Creighton 25 Jun '07

25 Jun '07

Sun Jun 24 15:10:19 MDT 2007 Jason Creighton <jcreigh(a)gmail.com> * Don't print anything in getWMProtocols Removed print statement from getWMProtocols, which was presumably there for debugging. Thanks to shachaf on #xmonad for pointing this out.

2 1

Issue 31 in xmonad: Documentation for new features in 0.3
by codesite-noreply＠google.com 25 Jun '07

25 Jun '07

Issue 31: Documentation for new features in 0.3 http://code.google.com/p/xmonad/issues/detail?id=31 New issue report by dons00: We require documentation for the new features in the 0.3 branch: * floating layer and how to use it * log hooks * writing new layouts and other extensions * using xinerama New tiling algorithms need screenshots too. In particular, the tabbed mode. -- Don Issue attributes: Status: Accepted Owner: dons00 Labels: Type-Enhancement Priority-Medium 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: remove BackCompat.hs
by Daniel Wagner 25 Jun '07

25 Jun '07

This patch takes the BackCompat module out of XMonadContrib. It's been some two weeks since it stopped being sufficient, and I have since switched to 6.6, so maintenance will stop. ~d

2 1

Issue 17 in xmonad: User-definable X monad state type
by codesite-noreply＠google.com 25 Jun '07

25 Jun '07

Issue 17: User-definable X monad state type http://code.google.com/p/xmonad/issues/detail?id=17 Comment #5 by dons00: In fact, I'll go so far as to say a solution for module-local state should be done prior to 0.3. it's a basic extensibility issue. Issue attribute updates: Labels: -Priority-Low Priority-Medium 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

Issue 17 in xmonad: User-definable X monad state type
by codesite-noreply＠google.com 25 Jun '07

25 Jun '07

Issue 17: User-definable X monad state type http://code.google.com/p/xmonad/issues/detail?id=17 Comment #4 by dons00: Two requests recently wanted simple module-local state. One in particular, remembering the last focused workspace, and binding a key to switch to it, could be considered a basic use case for this module-local state feature. One solution, btw, would be a module type class with private state (ooh, an associated type..). And given some time thinking about this, I think a light weight way to declare simple state types, that are module-private would be best. Lambdabot does this, perhaps we can do it with a type class in a similar way. The 'remeber last workspace' would be a nice thing to support for 0.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

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

25 Jun '07

Issue 12: Support _NET_WM_STRUT property for status bar programs http://code.google.com/p/xmonad/issues/detail?id=12 Comment #4 by dons00: Investigate the _NET_WM_WINDOW_TYPE_DOCK property. Which is set by gkrellm, kicker et al. _NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_DOCK. -- 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 12 in xmonad: Support _NET_WM_STRUT property for status bar programs
by codesite-noreply＠google.com 25 Jun '07

25 Jun '07

Issue 12: Support _NET_WM_STRUT property for status bar programs http://code.google.com/p/xmonad/issues/detail?id=12 Comment #5 by jcreigh: I'm looking into this. The tricky bit is what to do with dock-type windows, as we want them to be always visible, but we don't want to "unmanage" them, because we need to care about some things, eg, property change events. Issue attribute updates: Owner: jcreigh -- 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 11 in xmonad: ui idea: user-specified filters to 'manage'
by codesite-noreply＠google.com 25 Jun '07

25 Jun '07

Issue 11: ui idea: user-specified filters to 'manage' http://code.google.com/p/xmonad/issues/detail?id=11 Comment #2 by dons00: Frequently requested (filters to set windows on particular workspaces, and in particular layers). should do this for 0.3 -- should be trivial. Jason, want to have a go? Issue attribute updates: Status: Accepted Labels: 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

Issue 18 in xmonad: Support other task bar / dock properties?
by codesite-noreply＠google.com 25 Jun '07

25 Jun '07

Issue 18: Support other task bar / dock properties? http://code.google.com/p/xmonad/issues/detail?id=18 Comment #4 by dons00: I'm merging this into the STRUT PR. Issue attribute updates: Status: Duplicate -- 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 4 in xmonad: Implement float layer
by codesite-noreply＠google.com 25 Jun '07

25 Jun '07

Issue 4: Implement float layer http://code.google.com/p/xmonad/issues/detail?id=4 Comment #5 by dons00: Last remaining task here is the stackset change, to be done soon. -- 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