From: Dima K. <no...@di...> - 2014-06-25 20:54:23
|
Arnout Engelen <no...@bz...> writes: > I'd appreciate your thoughts on this approach. Details at > http://notion.sourceforge.net/notionkeys3.html . Some thoughts in no particular order: - This layout does not use the arrow keys at all. Those are a pretty natural target for WM navigation, and I think they should be utilized. The arrow keys could do the same things as some of your other bindings to give the user a choice. As an example, I have - meta-left/right cycles tabs - meta-up/down cycles workspaces - meta-shift-left/right cycles screens - With your proposed bindings, how does one move objects between containers? Specifically one should be able to move - windows between frames and - workspaces between screens One way to do that is to tag/attach. In your proposed list I don't see a way to move workspaces between screens; am I just not seeing it? - In your reference page does "attract" mean "attach"? - In your proposed bindings is meta-z same as meta-k k in the current defaults? There needs to be some way to bring up the focuslist. Finally, it would be great to maintain some compatibility with other similar WMs. As far as I can tell, awesome is the current king of the hill, so how about we simply co-opt their defaults for our defaults? Their default bindings are here: http://awesome.naquadah.org/wiki/Awesome_3.x Not all of our functions have analogues in their world, and vice versa, but for functions that do have analogues, I think we should match them. dima |