Hy, I got two questions: First the more general one: Serveal weeks ago here was a overviewpage with some modules and screenshots. Currently I can only find the haddok text, but there are no screenshots. I think the screenshots were quite usefull for beginners. Sometimes you can't realy imagine what a module/plugin does. The second one: Is there a possibility to add the tabbed-layout not to the whole workspace to maintain the tiled-layout and add the tabs to each of the small windows. More like ion (:/) does it. Does anybody understand what Im thinking about? Thanks a lot! -- Dominik Bruhn mailto: dominik@dbruhn.de
On 12/12/07, Dominik Bruhn
First the more general one: Serveal weeks ago here was a overviewpage with some modules and screenshots. Currently I can only find the haddok text, but there are no screenshots. I think the screenshots were quite usefull for beginners. Sometimes you can't realy imagine what a module/plugin does.
There are at least two "screenshots" references at http://xmonad.org/ page. You might also want to look at http://haskell.org/haskellwiki/Xmonad/Config_archive
The second one: Is there a possibility to add the tabbed-layout not to the whole workspace to maintain the tiled-layout and add the tabs to each of the small windows. More like ion (:/) does it. Does anybody understand what Im thinking about?
I don't. Could you clarify a bit? (With screenshots?:) -- vvv
On 2007-12-12 18:31:35 Valery V. Vorotyntsev wrote:
The second one: Is there a possibility to add the tabbed-layout not to the whole workspace to maintain the tiled-layout and add the tabs to each of the small windows. More like ion (:/) does it. Does anybody understand what Im thinking about?
I don't. Could you clarify a bit? (With screenshots?:)
http://modeemi.fi/~tuomov/ion/screenshots/ion3-1.png Ignore the overlapping in that shot, but notice that there are three panes, each with a bunch of tabs. I think this can kind-of be achieved in XMonad using Combo or LayoutScreens, but these are very inflexible in comparison as they require a recompile to change the number of panes. I agree this would be a nice feature to have, and I believe there's no reason in principle why one couldn't write a general nesting layout combinator. David said a few days ago that the main trouble is XMonad's linear representation of the window stack. Maybe this could be changed for 0.6? :-) /J
Hi Dominik! On Wed, Dec 12, 2007 at 05:05:40PM +0100, Dominik Bruhn wrote:
Hy, I got two questions:
First the more general one: Serveal weeks ago here was a overviewpage with some modules and screenshots. Currently I can only find the haddok text, but there are no screenshots. I think the screenshots were quite usefull for beginners. Sometimes you can't realy imagine what a module/plugin does.
you can see many screenshot with the relative config file here: http://haskell.org/haskellwiki/Xmonad/Config_archive The page you are referring to is gone due to the fact that many many extensions have been added and it was not possible to manually update that file anymore.
The second one: Is there a possibility to add the tabbed-layout not to the whole workspace to maintain the tiled-layout and add the tabs to each of the small windows. More like ion (:/) does it. Does anybody understand what Im thinking about?
If I understand your question correctly the answer is no. The tabbed layout is a full layout with tabs. Instead you want a tiled layout with tabs. We could write such an extension. You could try to do it yourself by starting from the present tabbed layout, though...;) hope this helps, andrea
Hello together, I have 2 questions about dzen and xmonad: 1) I have posted this question in the archlinux forum (http://bbs.archlinux.org/viewtopic.php?pid=307131#p307131) but I think this mailing list is a better place. I want to use dzen under xmonad and let it show the active workspace as well as some extra information (like the output of some script). With xmonad | dzen2 (and some entries in xmonad.hs) I get the workspaces. With gcpubar | dzen2 I get a nice cpu meter. But how can I get both? 2) I have a xinerama dual screen setup. How can I get seperate dzen bars on my both of my screens? Each showing which workspace is active there? Thanks! Nathan
xmonad:
Hello together,
I have 2 questions about dzen and xmonad:
1) I have posted this question in the archlinux forum (http://bbs.archlinux.org/viewtopic.php?pid=307131#p307131) but I think this mailing list is a better place.
I want to use dzen under xmonad and let it show the active workspace as well as some extra information (like the output of some script). With xmonad | dzen2
(and some entries in xmonad.hs) I get the workspaces. With
gcpubar | dzen2
I get a nice cpu meter. But how can I get both?
dzen doesn't multiplex, as far as I know, so the trick is to launch two dzens, with specified width and geometry. xmobar does multiplex, so you could try that instead.
2) I have a xinerama dual screen setup. How can I get seperate dzen bars on my both of my screens? Each showing which workspace is active there?
You should be able to set the screen and geometry for dzen on the command line I think. To show which workspace is active on which screen, you'll need a custom log hook, that prints to two handles, or tags output with which screen it is for, and then your dzens should filter which tagged strings they're interested in. Should be doable in a couple of lines. -- Don
dominik:
Hy, I got two questions:
First the more general one: Serveal weeks ago here was a overviewpage with some modules and screenshots. Currently I can only find the haddok text, but there are no screenshots. I think the screenshots were quite usefull for beginners. Sometimes you can't realy imagine what a module/plugin does.
Yes, it was rather time consuming to keep all the screenshots and docs in sync. We know automatically generate all the extension docs: http://xmonad.org/xmonad-docs/xmonad-contrib/ and i've for now moved all the screenshots here: http://haskell.org/haskellwiki/Xmonad/Screenshots with a little luck we should get inline image support into haddock soon, which will allow inline images in the docs, as we originally had, but also automated generation.
participants (7)
-
Andrea Rossato -
Dominik Bruhn -
Don Stewart -
Jamie Webb -
lobzang＠free.fr -
Nathan Huesken -
Valery V. Vorotyntsev