I'm uneasy with all the proposed keyboard changes.
Thus, as for my impression, I would just like to make sure nothing changes and that I can keep
my current layout even when notion as a whole gets update one day. So a solid way to switch
whole layouts would be essential. Something like a query/menuitem to change all layout.
This not only concerns the new, revolutionary change, but even the previous (like switching
Meta to "copyrightedlogo" key to which I find little excuse).
Summarizing: whatever changes introduced, please make sure they're reversible. I believe people have
been using Ion/Notion for years and are quite adapted, so probably the keyboard hasn't been the problem for them/us.
Wojtek
On Wed, Jun 25, 2014 at 01:54:14PM -0700, Dima Kogan wrote:
> 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
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> Notion-general mailing list
> Not...@li...
> https://lists.sourceforge.net/lists/listinfo/notion-general
--
Wojtek Aniszewski
[Eng: voyteck aanishevsky]
[Fr: vôytek anichévsky]
/^..^\ ,-------------------------------------,
( (••) ) ----| My public GPG key ID: AC66485E |
(|)_._(|)~ | please use email encryption! |
`-------------------------------------"
Web: http://www.coria.fr/spip.php?auteur1606
|
