HI, On Thu, Feb 2, 2012 at 4:39 AM, Alex V. Koval <[email protected]> wrote: > 1) There are no good explation of stacking mode in the video screencast > and docs.
Section 2.2 mentions the stacking layout: http://i3wm.org/docs/userguide.html#_changing_the_container_layout Perhaps it could be expanded. If you think you can improve it, please let us know, submit patches, etc. > 2) "Resize" section of default config file is too complicated. I've come > with much better solution for me, it is very easy to remember: > > # resize > bindsym Mod4+Mod1+Left resize shrink right 3 px or 3 ppt > bindsym Mod4+Mod1+Right resize grow right 3 px or 3 ppt > bindsym Mod4+Mod1+Control+Right resize shrink left 3 px or 3 ppt > bindsym Mod4+Mod1+Control+Left resize grow left 3 px or 3 ppt > bindsym Mod4+Mod1+Up resize shrink down 3 px or 3 ppt > bindsym Mod4+Mod1+Down resize grow down 3 px or 3 ppt > bindsym Mod4+Mod1+Control+Down resize shrink up 3 px or 3 ppt > bindsym Mod4+Mod1+Control+Up resize grow up 3 px or 3 ppt > > P.S. May be I just don't get the defaule resize mode. I've tried > it a few times and later just disabled it because were unable to learn > it fast. Resizing with the keyboard is complicated. We have some ideas to provide simpler resizing with the keyboard in the bugtracker: http://bugs.i3wm.org/report/ticket/576 We don't use 2-modifier bindings in the default config. I'm guessing here, but I think there are two reasons for that. First, it would probably complicate things. Second, we ask the user what modifier he'd like to use in the config wizard, and thus using 2-modifier bindings wouldn't make much sense. Whether using 2-modifier bindings in the default config would make things easier or not is completely subjective, and I don't see the default bindings for resizing changing unless we introduce different ways to resize. I could argue that the bindings I set up for my laptop are clearly better, but that doesn't mean they should be the default bindings. :-) > 3) [minor issue ]Modkey + jkl - difficult to re-learn after xmonad, > awesome and others which have assigned different meanings for those keys > by default Kind of personal taste too, no? > 4) [minor] I can not find the shortcut for Alt-Tab. Simple, this should be > ability > to cycle windows on current desktop. Most of newcoming users would feel > bad without it. There's no such concept in i3, as focus follows the tree hierarchy. Using any tiled window manager requires learning, unfortunately, and i3 is no different. That said, if you're considering implementing this, please ping Michael first to see if he would accept it. > 5) [minor] Floating mode for the whole desktop. Let me explain. Tiling & > stacking > are very good for hard work, where all space is occupied > by different windows. But there are situations when I don't need > this. Sometimes I want to see my nice background and a few floating > windows over it. It would be good to have such a mode for desktop, > as a fallback for a typical user to normal work. > > The other argument: I use to put very nice background on my desktop, > and would never see it if I always work in tiling. > > It is also _very_ important IMO if we would ever have floating > mode for desktop, it should support 'smart' window placement. I've > explained > what I mean in this video: http://youtu.be/eS-mchtzJsg but generally it > means > the following: place window in biggest onuccupied space on current > screen. That's probably not going to happen, as Michael already stated in the past. i3 is a pure tiling window manager, floating exists mostly for popups and compatibility with the occasional broken application. The snapping behavior has been shot down already in the past: http://infra.in.zekjur.net/pipermail/i3-discuss/2011-September/000286.html Also, using the "beautiful desktop background" argument will get you nowhere. i3 prioritizes functionality over form, and thus a point like this is never going to be taken seriously. If you want to see a beautiful image, use a image viewer or switch to an empty workspace. :-P > 6) *Always* pressing Modkey+H, Modkey+V before every next program open is > overkill. I think more smart would be to cycle this. Why? Because now > every > next window open always have bigger ratio X*Y where it is comfortable to > work > with apps in square. So, what I mean, exactly, I think it would be > helpful > if: > 6.1. Mod+enter - opens terminal on full screen > 6.2. Mod+enter - opens terminal split vertically > 6.3. Mod+enter (without Modkey+v) opens new terminal split horizontally > > etc... Because I always tend to do it this way. I don't see big necessity > to open tall narrow terminals. > > 6.4. Next one should open horizontally. > > Looks like we come up to somehow called 'spiral' layout, but its smarter > because > when you switch to other window, it would continue splitting this way. Just some clarification. You only need to split before opening a client *if* you want to split the current container. You could argue that the spiral layout you're describing forces one to "unsplit" before launching a client, which would be rather "unproductive" too if that is not what you wanted to do, naturally. What you describe is the Awesome spiral layout. i3, on the other hand, works by making you manage the layout by splitting, resizing and moving containers around in a tree structure. It's a different behavior, I don't see that changing. In the future, you might be able to restore from a previously-saved (or manually composed) layout. That might be enough for your needs. > 7) Its very pity that dmenu does not remember previous choice. It would be > great > to improve this part of dmenu. Yeah, as it's already been mentioned, dmenu is a separate project, created and maintained by different people. Please ping them with suggestions about dmenu (it's part of the Suckless project/community). > 8) Until there are serious bugs remain, like dying tray applications ( > http://bugs.i3wm.org/report/ticket/550) it would be diffcult to advertize > i3. I am upset that such great window manager still don't get great > public attention (like I don't see it in Google Trends), but may be its not > a right time. When everything will be very stable, I will try publish an > article about it in habr (21523 readers) for russian speaking ppl. We are very aware of the bugs in i3 (after all, that's why we track them in the bugtracker). If you can reproduce #550 (or any other bug that needs attention), please post relevant information in the bugtracker. It would be nice if you or anyone wrote articles about i3, but I'd suggest that you take your time adapting to how things work with i3 first. Regards,
