Navigate into large Explorer panel

[azlux]

Hi (again),

I have a LOT of object into my ldap.
I see you have implement "first/last" search with (g / G) but when you do it, the selector don't follow.

I think last/first entry if a feature from tview directly. https://pkg.go.dev/github.com/rivo/tview#hdr-Navigation-Table
Can you make the selector follow the navigation ?
Or maybe just an option to inverse the sort into the Explorer panel (really useful when you debug something, we create new tests object in the bottom of the tree).

Best regards,
Azlux

[Macmod]

Thanks for the suggestion @azlux :)

Currently we don't "follow" the original keybindings from tview - godap may override some in specific cases (which wasn't the best decision now that I think of it - to fix that we would have to plan a new major release). For instance, according to tview docs about the navigation around TreeNodes:

Nodes can be selected by calling SetCurrentNode(). The user can navigate the selection or the tree by using the following keys:

    j, down arrow, right arrow: Move (the selection) down by one node.
    k, up arrow, left arrow: Move (the selection) up by one node.
    g, home: Move (the selection) to the top.
    G, end: Move (the selection) to the bottom.
    J: Move (the selection) up one level (if that node is selectable).
    K: Move (the selection) to the last node one level down (if any).
    Ctrl-F, page down: Move (the selection) down by one page.
    Ctrl-B, page up: Move (the selection) up by one page.

In godap we currently override Ctrl-F and Ctrl-B. j / k / K / J seem to work fine, but for some reason g / G don't. I'll have to investigate this issue a bit further to understand why it's behaving like that and what we can do to improve it.

[Macmod]

In the official tview example for the TreeView g / G do behave weirdly - g doesn't do anything, and G moves the scroll but not the selection (?)...

I think that's it - it's really by design. g only scrolls to the top, G only scrolls to the bottom. The proper shortcuts for navigating through "large" trees would be CtrlB and CtrlF. For now, if you need this sort of navigation, comment out the switch event.Key() block from tui/explorer.go:623 or change the keybindings from CtrlB and CtrlF to something else. The same "issue" happens in tui/search.go:599.

Apart from the keybinding conflict, I also feel that there should be a way to navigate just "inside the current level" - like when traversing a large OU/container with hundreds of objects, there should be keybindings to move one page down, one page up, to the first sibling node or to the last sibling node. If we are to do anything with regards to changing the keybindings we might as well think about this improvement.

[azlux]

there should be keybindings to move one page down, one page up
This part is already working with the key PageUp and PageDown.

For g/G, I don't have any problem if you don't implement a way.
I personally don't really like key-bindings, lot of shortcut to memories for every app.
I was more wondering if it's was a bug or not.

For my case, it's was because I was searching a Group into a big list of Person (my organization is messy), and I knew my groups was at the end, that all.