- xmonad - Haskell.org

Issue 118 in xmonad: Install default configuration template
by codesite-noreply＠google.com 04 Jan '08

04 Jan '08

Issue 118: Install default configuration template http://code.google.com/p/xmonad/issues/detail?id=118 New issue report by dons00: We can make it even easier to get into configuring xmonad by installing a default xmonad config file. Two approaches: * xmonad-example.hs that is, install an example in the right location, with a name that hints on how to use it. * xmonad.hs Install a real xmonad.hs, and only compile it if ghc is available. We'd also need a way to create the config file in the first place. Is it copied as part of the install process? Issue attributes: Status: Accepted Owner: dons00 Labels: Type-Enhancement Priority-Medium Usability -- 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 82 in xmonad: Gaps moved to contrib
by codesite-noreply＠google.com 04 Jan '08

04 Jan '08

Issue 82: Gaps moved to contrib http://code.google.com/p/xmonad/issues/detail?id=82 Comment #3 by dons00: Any objections to moving the basic gap handling into a layout? The case for hardcoded gaps in the core seems less compelling now there's EWHM support in other contribs. Issue attribute updates: Summary: Gaps moved to contrib Labels: -Type-Defect Type-Enhancement -- 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 19 in xmonad: Investigate a way to allow contrib extensions to use compositing.
by codesite-noreply＠google.com 03 Jan '08

03 Jan '08

Issue 19: Investigate a way to allow contrib extensions to use compositing. http://code.google.com/p/xmonad/issues/detail?id=19 Comment #7 by thayerw: > tiling, compositing wm would probably take a big chunk of the tiling wm market. I just want to second this. I think there is huge potential in having a composite tiled environment, in terms of both special fx *and* usability. It has been mentioned elsewhere, but some of the possibilities include: * zoom in/out inactive windows instead of resizing the viewport * zoom in to maximize or partially maximize a client over the top of other clients * Flip 3D style rotation of clients * quickly view all workspaces with an expo-style overlay IMHO drop shadows are superficial when compared to the real enhancements in usability this could provide. -- 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 19 in xmonad: Investigate a way to allow contrib extensions to use compositing.
by codesite-noreply＠google.com 03 Jan '08

03 Jan '08

Issue 19: Investigate a way to allow contrib extensions to use compositing. http://code.google.com/p/xmonad/issues/detail?id=19 Comment #6 by thayerw: > tiling, compositing wm would probably take a big chunk of the tiling wm market. I just want to second this. I think there is huge potential in having a composite tiled environment, in terms of both specials *and* usability. It has been mentioned elsewhere, but some of the possibilities include: * zoom in/out inactive windows instead of resizing the viewport * zoom in to maximize or partially maximize a client over the top of other clients * Flip 3D style rotation of clients * quickly view all workspaces with an expo-style overlay IMHO drop shadows are superficial when compared to the real enhancements in usability this could provide. -- 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

Ubuntu packages available
by lithis 03 Jan '08

03 Jan '08

I created Ubuntu Gutsy packages from nomeata’s Debian packages, for both i386 and amd64. You can get them from nomeata’s site, http://people.debian.org/~nomeata/xmonad/gutsy/ . (Until the amd64 packages are there, you can download them at http://hethrael.com/xmonad/ .) I don’t know what will happen if you install them and have a self-compiled version installed too; I uninstalled X11, xmonad, and xmonad-contrib before installing them.

3 2

Issue 117 in xmonad: composite support?
by codesite-noreply＠google.com 03 Jan '08

03 Jan '08

Issue 117: composite support? http://code.google.com/p/xmonad/issues/detail?id=117 Comment #1 by dons00: Duplicate of #19, http://code.google.com/p/xmonad/issues/detail?id=19&can=1&q=compositing which i've reopened. To make progress on this, we need someone to identify the basic compositing api, so we can do a haskell binding to it, and work out if a compositing hook is needed for xmonad. Once the api is identified, everything else should be easy. We just need that initial groundwork done. 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 19 in xmonad: Investigate a way to allow contrib extensions to use compositing.
by codesite-noreply＠google.com 03 Jan '08

03 Jan '08

Issue 19: Investigate a way to allow contrib extensions to use compositing. http://code.google.com/p/xmonad/issues/detail?id=19 Comment #5 by dons00: > roberth.sjonoy, xmonad should get optional composite support through use of libxcomposite. It should be able to make unfocused windows transparent etc, real transparency for consoles and shadows. Issue attribute updates: Status: Accepted Labels: Component-Contrib -- 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 03 Jan '08

03 Jan '08

Issue 12: Support _NET_WM_STRUT property for status bar programs http://code.google.com/p/xmonad/issues/detail?id=12 Comment #17 by loupgaroublond: * avoidstruts are toggled per workspace, rather than per screen (whether this is good or bad is debatable) It makes more sense to me, the way it is, and I have my config set up even to do ToggleStruts on a per Layout*Workspace basis. -- 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 117 in xmonad: composite support?
by codesite-noreply＠google.com 03 Jan '08

03 Jan '08

Issue 117: composite support? http://code.google.com/p/xmonad/issues/detail?id=117 New issue report by roberth.sjonoy: xmonad should get optional composite support through use of libxcomposite. It should be able to make unfocused windows transparent etc, real transparency for consoles and shadows. Issue attributes: Status: New Owner: ---- Labels: Type-Defect Priority-Medium -- 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 03 Jan '08

03 Jan '08

Issue 12: Support _NET_WM_STRUT property for status bar programs http://code.google.com/p/xmonad/issues/detail?id=12 Comment #16 by SpencerJanssen: AvoidStruts still has a few issues: * it scans all top level windows on every refresh -- a performance bug waiting to happen * we don't correctly subscribe to property events on dock windows, so the detected gap isn't always accurate * avoidstruts are toggled per workspace, rather than per screen (whether this is good or bad is debatable) * with core gaps, each edge can be toggled independently, not so with avoidstruts We can consider removing gaps when these issues are resolved. -- 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