#Mouseless window manager x full#
#Mouseless window manager x free#
#Mouseless window manager x windows#

If it becomes large enough then it gets enough resources to survive, if not then it's time to finish it. Any new creation starts from one user and grows from there. This is strange conclusion: we don't know if something will stick or not unless we'll try. By that logic Linux itself should never have been created, the iPhone should never have been created, nothing new should ever be created because everyone is perfectly happy with what they have. It really depends on the popularity of said things. Posted 17:47 UTC (Thu) by khim (subscriber, #9252)Īnd therefor (according to you) such choices should be eliminated so that NOBODY is able to use them. No mention was made of any expectation of interest or 'pandering' by others. who said anything about providing support? The original comment was simply about developing alternatives to Weston. However, while we're on the subject of strawman arguments. > However, it doesn't mean that everyone around them has to care about it, and/or pander to their needs, requests, and demands of other projects. Sure, it's not literally _denying_ the freedom to work on alternatives-that was a bit of justifiable hyperbole on my part-but the original comment was clearly disparaging the idea of developers working on anything but the '1 good enough' solution, which, if consistently applied, would include anyone working on Linux.

#Mouseless window manager x free#

Anyone who wants to work on an alternative desktop environment is more than free to do so no-one is denying them that right. > Yes, it would be if anyone had said that, but you're arguing against a strawman. I desperately wish this point was more widely appreciated. We don't need 20 window managers, just 1 good enough one. >.> If there is one thing I would like to happen, then that would be that nobody would replace Weston with anything else. Fortunately I was able to work around or find alternate solutions for the broken bits, and kde4 itself has improved dramatically since then, such that at least with semantic-desktop not only turned off but actually compiled out (gentoo, USE=-semantic-desktop), I can honestly say I'm enjoying kde4 as much if not more than I did late kde3, now. It sounds horrible I know, but there's a productive workflow there that I've grown to depend on, and I was VERY unhappy when an earlier version of it broke with my transfer from kde3 to supposedly ready but still in reality VERY early alpha quality kde4.

#Mouseless window manager x windows#

Combined with (sloppy) focus follows mouse, click-to-raise and with semi-transparent inactive, that lets me work with either the two side-by-side windows or with the almost-maxed and a half-maxed window concurrently, or with all three windows, the back half-maxed one viewable when focused (but not raised) thru the semi-transparent inactive almost-maxed window above it.

#Mouseless window manager x full#

Reasonably current kwin is tiling capable, titlebar height (and lots more) is configurable, and as with any self-respecting kde app, all major triggerable functionality is mapped to configurable hotkeys.įWIW, my kde is highly customized as a sort-of hybrid tiling/floating mixture, with floating dominating, but various windows configured to specific sizes and/or locations, including two dominant themes of maxed-Y/half-maxed-X for side-by-side for things like browsers and terminal windows, and maxed-X/almost-maxed-Y, lacking only titlebar height (and sometimes no-border so I get full app height as if it had the titlebar anyway), for things like tri-pane mail, news and feed-reader clients. It's ok but it could be improved.Of course that, or something very close to it, is already possible with kwin. I came up with this using a static image for now. I almost want to try this myself for fun. If the animation is short enough it won't matter because you won't have time to try to click anything while it is shaking.įor more realism you could look into using the DWM (Desktop Window Manager) to project a 'live' view of the desktop but that's probably not worth it especially if you keep the animation very short. Since during the animation the coordinates of everything will be all over the place, you probably don't want to be bothered with trying to translate mouse clicks on the moving desktop to the underlying control. Then you would just apply some epilepsy-inducing animation to a translate layout transform on the root element. (Check out my blog for a handy FullScreenBehavior for WPF Window).

You would want to grab a screen shot of the desktop and apply it to a full screen WPF window. You would have to accept some certain limitations though. Danny is onto something with the transparent window idea.