Advanced keyboard navigation for widgets (ToC, index, pages, etc.)

Not sure if re-using <ctrl><space> is a good idea - if you have to
toggle through 3 stated it is not as quick anymore.

Maybe a more generic suggestion to toggle between tabs one the focus
is on the side pane ?

Otherwise I would like a specific key, but we use most convenient
combinations already.

Two ideas:

1. Have <Ctrl><Tab> switch the focus between a number of gui elements, including the index tab, the toc tab and the content page, but possibly more. Right now <Ctrl><Tab> cycles focus between some elements, but to be honest, it is not quite clear to me how. Keep <Ctrl><Space> switching only between index and content pane.

2. Have a generic navigation short cut followed by a second specific key. For example <Ctrl><g> ("go to") <i> ("index"), <Ctrl><g> ("go to") <t> ("table of contents"), <Ctrl><g> ("go to") <c> ("content"). This could be expanded for in-page navigation (that's another feature request, I guess). For example: <Ctrl><g> ("go to") <j> ("next heading"), <Ctrl><g> ("go to") <k> ("previous heading") and so on. I realize <Ctrl><g> is already in use, but it illustrates the idea.

To aid the user the "go to" could conceivably even have a small widget, like the "find" widget, that expands where to go to ("go to", pressing "i" expands to "index", etc). Then one could have <Ctrl><g> ("go to") <p> ("page"), start typing the page name with automatic completion in the widget text box. And now I stop this flood of ideas.

Sorry for the late response. Sounds to me like an "advanced navigation" plugin.

Wondering if just the key combo would be enough, or maybe we add a popup showing the choices for visual feedback ?

(Popup maybe without window borders, so not a dialog, but more like a floating menu that disappears as soon as you press the next key)

For simpler key combos (and possibly as a first step) a menu is probably not necessary. For example, for something like <ctrl><g> - <i>, <ctrl><g> - <c> and so on.

As a second step, and certainly for the autocompletion idea floated in my previous comment, a floating / overlay menu would be very useful. I can't think of a good example of such a menu elsewhere right off the top of my head. The Ubuntu Dash comes to mind, but is way more complicated and maybe not a good comparison.

On Mon, Dec 17, 2012 at 8:52 PM, Burkhard Ritter
<email address hidden> wrote:
> For simpler key combos (and possibly as a first step) a menu is probably
> not necessary. For example, for something like <ctrl><g> - <i>,
> <ctrl><g> - <c> and so on.

Well, you expect users to remember those shortcuts - but people tend
to be better at this with visual feedback.

E.g. a popup menu with the "i" in "index" underlined will prompt
people to press "i".

Implementation wise it is also easier - we can't really handle multi
key combo sequences. First key combo will popup the menu, the menu
widget will recieve the next key press and handle it before returning
focus to the main window.

-- Jaap

To clarify, I really like to idea of the floating menu for visual
feedback! I only suggested omitting the menu as a first step, because
I was assuming it might be easier to implement.

On Mon, Dec 17, 2012 at 1:22 PM, Jaap Karssenberg
<email address hidden> wrote:
> On Mon, Dec 17, 2012 at 8:52 PM, Burkhard Ritter
> <email address hidden> wrote:
>> For simpler key combos (and possibly as a first step) a menu is probably
>> not necessary. For example, for something like <ctrl><g> - <i>,
>> <ctrl><g> - <c> and so on.
>
> Well, you expect users to remember those shortcuts - but people tend
> to be better at this with visual feedback.
>
> E.g. a popup menu with the "i" in "index" underlined will prompt
> people to press "i".
>
> Implementation wise it is also easier - we can't really handle multi
> key combo sequences. First key combo will popup the menu, the menu
> widget will recieve the next key press and handle it before returning
> focus to the main window.
>
> -- Jaap
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/988651
>
> Title:
> Advanced keyboard navigation for widgets (ToC, index, pages, etc.)
>
> Status in Zim desktop wiki:
> Confirmed
>
> Bug description:
> With the Table of Contens plugin (ToC) enabled and the plugin
> configuration option "Show ToC as floating widget instead of in side
> pane" disabled, it would be nice to be able to switch (cycle) between
> the main content page, the index and the ToC pane with a hotkey. Maybe
> <Ctrl><Space> could be reused for this; as it is now <Ctrl><Space>
> only switches focus between the main content page and the index (the
> option "Use <Ctrl><Space> to switch to the side pane" has to be
> enabled).
>
> This is zim 0.56 on OS X 10.6.8.
> Gtk version is (2, 24, 10)
> Pygtk version is (2, 22, 0)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/zim/+bug/988651/+subscriptions
>