- xmonad - Haskell.org

darcs patch: fix usage info for LayoutScreens.
by David Roundy 22 Jun '07

22 Jun '07

Resend of previously-amended patch. It's good that you're fast Don... :) David Fri Jun 22 06:26:18 PDT 2007 David Roundy <droundy(a)darcs.net> * fix usage info for LayoutScreens.

2 1

Xnest and Xmonad
by Simon Peyton-Jones 22 Jun '07

22 Jun '07

Hi Xmonaders I'm planning to use xmonad as the main vehicle for a 3-hr tutorial on Haskell at the Open Software Convention 2007, in 3 weeks time. The goal is to teach Haskell (not xmonad per se), but by doing it in the context of xmonad I hope to motivate and excite the audience. The audience is professional programmers, not undergrads. They are Java, Ruby, Python experts. I plan to go pretty fast. I want to make use of Quickcheck, maybe HPC, too. So my plan is to show them xmonad and then rapidly zoom in on some small purely-functional part to do some Haskell programming. So I need to - show slides - edit code - recompile - and show the resulting window manager in action Advice is that the safest thing to do is to run xmonad inside xnest, so that the slides, editor etc are not disturbed. SO HERE'S THE QUESTION Can someone give me some idiot-level step by step instructions for how to run xmonad inside xnest, alongside other running applications? I have all the pieces; I just need to know how to set up the config files or whatever. I know some of you have done this. Timescale: I'm going to working on this for the next 3 weeks, and then I have to deliver the tutorial. Needless to say I'd also love to have your suggestions for simple Haskell programming stuff that could be described and demo'd in this way. Don is already thinking about this -- thanks Don. thanks (NB: I'm not on the xmonad list, so pls include me in replies!) Simon

3 3

darcs patch: add new LayoutScreens module.
by David Roundy 22 Jun '07

22 Jun '07

This version has only a fixed usage description. Fri Jun 22 06:15:06 PDT 2007 David Roundy <droundy(a)darcs.net> * add new LayoutScreens module.

2 1

darcs patch: add new LayoutScreens module.
by David Roundy 22 Jun '07

22 Jun '07

Hi all, Here's a fix to make LayoutScreens work like Spencer suggested, by simply changing xineScreens itself. Much simpler. And incidentally I've verified with this that Combo+Tabbed+SimpleStacking does in fact seriously misbehave on Xinerama setups. Expect patches to modify the return type of doLayout some day... David Fri Jun 22 06:13:00 PDT 2007 David Roundy <droundy(a)darcs.net> * add new LayoutScreens module.

2 1

darcs patch: change argument order of getWindowProperty to maximize...
by Jason Creighton 22 Jun '07

22 Jun '07

Thu Jun 21 19:06:27 MDT 2007 Jason Creighton <jcreigh(a)gmail.com> * change argument order of getWindowProperty to maximize currying potential

2 1

darcs patches: Circle, Magnifier: raise the focus window
by Peter De Wachter 22 Jun '07

22 Jun '07

[This is a resend, it seems my first mail didn't make it to the list.]

2 1

darcs patch: make Mosaic lay thigs out a bit better.
by David Roundy 22 Jun '07

22 Jun '07

Thu Jun 21 09:26:32 PDT 2007 David Roundy <droundy(a)darcs.net> * make Mosaic lay thigs out a bit better.

2 1

darcs patch: add SimpleStacking module to make Combo and Tabbed wor...
by David Roundy 22 Jun '07

22 Jun '07

This is an amend-recorded version of the SimpleStacking patch, which fixes a (slow) leak and a warning. David Thu Jun 21 08:15:24 PDT 2007 David Roundy <droundy(a)darcs.net> * add SimpleStacking module to make Combo and Tabbed work together. WARNING! This change will break existing Tabbed configurations. The problem is that there is no way within a Layout's "doLayout" to safely modify the layout itself. This makes LayoutHooks fragile, and more to the point, makes SimpleStacking fragile, so we can't safely define a tabbed' = simpleStacking . tabbed A workaround would have been to duplicate the tabbed code, but I'd rather leave the ugliness and get this fixed.

2 1

darcs patch: add SimpleStacking module to make Combo and Tabbed wor...
by David Roundy 21 Jun '07

21 Jun '07

Hi all, This module gets Combo working with Tabbed again, by adding a SimpleStacking layout modifier, which mimics the old stacking behavior, using Spencer's latest patch. However, this is fragile, and I think it's fragile because of a design problem that is easily fixed--but not before work this morning. The trouble is that within doLayout, there's no way for a layout to modify itself, because it can't tell which layout it is... and because it may not be a "root" layout at all. The solution seems simple: redefine data Layout a = Layout { doLayout :: Rectangle -> Stack a -> X ([(a, Rectangle)], Maybe (Layout a)) , modifyLayout :: SomeMessage -> X (Maybe (Layout a)) } so doLayout can modify itself. This makes all the Layout transformers a little harder to write, but a helper module ought to be able to fix that. And it makes me wonder yet again whether we should be defining a class class Layout l a where doLayout :: l -> X Rectangle -> Stack a -> X ([(a, Rectangle)], Maybe (Layout a) modifyLayout :: l -> SomeMessage -> X (Maybe (Layout a)) serializeLayout :: l -> String readLayout :: String -> Maybe (l, String) -- or some other parser-like thing data Layout a = forall l. Layout l a => Layout a This might lend itself to somewhat prettier Layout code that is more "data-structure-based" rather than self-modifying-function-based. I imagine this would lead to friendly interfaces for easy-to-write layout modifiers. David P.S. I'd be curious to see implemented a "popularity-contest" module for xmonad once we've got serialization, which could use the logging mechanism to report on the most frequently used layouts. And yes, this would be in XMonadContrib and only manually enabled. I have no idea how many people are actually using Tabbed, and how likely this is to break folks' Config files. Thu Jun 21 07:55:00 PDT 2007 David Roundy <droundy(a)darcs.net> * add SimpleStacking module to make Combo and Tabbed work together. WARNING! This change will break existing Tabbed configurations. The problem is that there is no way within a Layout's "doLayout" to safely modify the layout itself. This makes LayoutHooks fragile, and more to the point, makes SimpleStacking fragile, so we can't safely define a tabbed' = simpleStacking . tabbed A workaround would have been to duplicate the tabbed code, but I'd rather leave the ugliness and get this fixed.

1 0

is LayoutHooks (and thus Tabbed)
by David Roundy 21 Jun '07

21 Jun '07

It looks to me like LayoutHook is broken when you've got more than one workspace visible. Is anyone using tabbed with multiple screens? If so, is it working fine? It seems like it'd attach the decorations to the wrong layout, which might cause artifacts... When I test it briefly, everything looks fine, but I'm not sure why that is. Maybe because the hooks only have effect on the UnDoLayout. I'm about to write a module that uses them with hooks that matter where they're attached (to handle stacking), so it'll actually matter. Which probably means we'll need some way to identify the layout we wish to attach the hook to, presumably by passing the Stack, which is an awfully big stick to use! :( If only the tag were part of the Stack... :) -- David Roundy http://www.darcs.net

1 0