Adam, how do you implemented the stack in each sublayout, is common to the whole layout or we got independent ones? On Mon, Apr 6, 2009 at 2:03 AM, Adam Vogt wrote:

I think that this needs a screenshot to explain how useful this could be for replacing all those other modules that combine layouts, once we have a sort of managehook set up for adjusting this thing =)

This is with 2 screens, the lower one is is 1280x800

http://omploader.org/vMWhpbg/sublayout.png

I'm not aware of any serious issues with this incarnation of TabbedModifier, so please try it out :)

* On Sunday, April 05 2009, Adam Vogt wrote:

...

Tue Mar 3 01:57:01 EST 2009 Adam Vogt * Add Apply message to L.WindowNavigation

Thu Mar 19 12:15:31 EDT 2009 Adam Vogt * sort exported modules in cabal file

Mon Apr 6 00:13:01 EDT 2009 Adam Vogt * Document and extend BoringWindows to support multiple sources of boring.

The Replace and Merge messages are added to support layouts sending a list of windows that should be skipped over. The sources are tagged by a string key, so it is possible though unlikely for different sources of boring windows to interfere with eachother.

Mon Apr 6 00:24:17 EDT 2009 Adam Vogt * Add X.L.SubLayouts: A modifier for nesting layouts

This LayoutModifier offers many options for managing the grouping of windows which are then handled by a single sublayout. The illusion of different sublayouts can be had by specifying which alternative layout should be used for each group. Decorated layouts can be used if they can be applied by a function like X.L.Tabbed.addTabs.

_______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad