Qtile – A hackable tiling window manager written in Python
qtile.org
qtile.org
Or are you talking about Windows 8 apps being "responsive" in some sense?
So if anyone made a Tiling Window Manager that isolates how much an application can control, and gets rid of this config it to make it work mentality, they would have me sold. I love having multiple desktops on Linux, one feature that Windows lacks to this day. Their tiling, although incomplete, it works for me and what I do.
Sorry if I offended anyone, I'm not a tiling guru, though I'd love to be. I just prefer applications that "just work" without too much effort on the end-users part, as opposed to getting in the way of the end-user.
- in FF, launch a new window, showing a fraction of the frame.
- in Chrome, replace the current window, showing a fraction of the frame.
In both cases, if I want to see the uncropped video, I have to manually switch to Full mode. I know there are hooks[0] to change this behavior to automatically launch a floating window (I don't use YouTube enough to bother), but I don't think there's a way to get the behavior GP described. Is there?
[0] http://xmonad.org/xmonad-docs/xmonad-contrib/XMonad-Hooks-Ma...
If you fullscreen Firefox, it will simply hide UI elements, not take up the entire screen. It is not xmonads responsibility to automatically scale applications.
It's been said before but everyone writing a tiling window manager should make it work just like xmonad does for multiple screens, they really got it perfect.
(Wingo is a true hybrid WM. I like to describe it as "Openbox meets Xmonad.")
Mostly it was the plugin community, which is much larger for awesome and the shared philosophy of the community is very unix-y/small tools focused which is great and makes up for the copy/paste script-kiddy side of it.
Damn do I miss proper monitor support though, luckily I did kinda keep a separation between my main monitor and secondary naturally so it's not as painful for me as it would be for some.
> When xmonad starts, workspace 1 is on screen 1, workspace 2 is on screen 2, etc. When switching workspaces to one that is already visible, the current and visible workspaces are swapped.
I actually like how Awesome does things but I can see how it might be nice to have one set of screens. Though I feel like you could probably script the keybindings to achieve more or less that functionality yourself, it's really easy to mess around with that kind of thing in Lua. Personally I feel like usually since my monitors are of vastly different size (laptop vs external monitor) I actually prefer to have specific layouts on specific monitors.
The main use case I miss is this one. I work with two monitors, either a 30" and a sideways 24" or a 30" and my laptop screen.
Gvim, terminal windows, etc on the primary and web browser on the secondary. Works fine in xmonad and awesome.
But then I have something unusual, maybe I have a screen with a mitm proxy and a detached chromium devtools or console and a repl all layed out nicely to debug something. Aha, I think I found it, let me look at the code ... shit, I layed these out on my primary.
With xmonad I can throw that whole screen over to the secondary, might have to adjust a bit because of the resolution difference but that's way easier than having to move each app over individually which just completely breaks flow.
I tried to script it but it just ends up a mess because you do have to move each application individually and they always require a lot of fiddling.
Lua is very easy to mess around with, my first day with awesome I couldn't find a battery monitor that I liked and that worked with my laptop so I just wrote one that's perfect. Took about 2 hours since I had never written Lua before. The docs were quite good.
Xmonad should take note, have some actual documentation. Auto-generated garbage consisting solely of type signatures doesn't count.
The only time I move entire groups is to push it to the other monitor which is the one thing it can't do.
EDIT: to clarify, it functions in essentially the same fundamental way xmonad's does.
I really do'nt understand why people have huilt so Manu different tiling WM's and have not improved/extended existing ones. The fragmentation hurts the a adoption.
If you've used Slate[1], it's like a (much simpler) version of that, for Linux (well, EWMH-compliant X window managers, specifically).
(Carlisle is a fairly simple wrapper on top of Andrew Gallant's amazing xgbutil libraries[2] for Go.)
[0] https://github.com/cespare/carlisle
Also, I find lxappearance an easy and quick way to set GTK themes via GUI rather than having to edit the .gtkrc files for every option.
You are likely to find that a stand-alone WM requires more manual configuration than a DE. Most DEs have more-or-less unified settings managers, but those settings are really for many disparate components of the environment that a WM won't even try to control. It might be possible to recover some convenience by using a third-party settings manager like the previously mentioned lxappearance (I find the Arch Linux wiki a useful resource in this regard even though I don't run Arch).
Alternatively, you can use xmonad with Xfce (or another DE). That's what I did before completely switching to xmonad and it does make settings management easier.