After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 790440 - Keybindings for the panels
Keybindings for the panels
Status: RESOLVED OBSOLETE
Product: gnome-builder
Classification: Other
Component: keybindings
Flatpak Nightly Channel
Other Linux
: Normal normal
: ---
Assigned To: GNOME Builder Maintainers
GNOME Builder Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-11-16 11:19 UTC by Yotam Nachum
Modified: 2018-01-11 10:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
A screenshot of plotinus in gedit (548.33 KB, image/png)
2017-11-16 11:19 UTC, Yotam Nachum
Details

Description Yotam Nachum 2017-11-16 11:19:02 UTC
Created attachment 363826 [details]
A screenshot of plotinus in gedit

Currently I couldn't find a way to jump between panels, there is more than one way to do it, so I checked several options:

PyCharm and probably the rest of JetBrains IDEs allow users to jump to the panels with cmd + number. The numbeer is shown before the name of the panel, for example 4: Run. They don't have a shortcut for all the panels (probably too much) but you can still jump to those panel with cmd + shift + a (search all the actions in the IDE), the closest thing to that in GTK+ is plotinus[0].

Visual Studio Code is another option that I looked at. You can jump to the panels with keyboard shortcuts that can be seen with mouse hover or be guessed (ctrl + shift + e for explorer, ctrl + shift + d for debugger, ctrl + shift + f for search). When you are inside a panel you can tab a lot of times to move like a web browser but I don't think this is a good UX. They also have search all actions options.

Eclipse have a weird way of doing it, you can move between panels with ctrl + f7 and ctrl + shift + f7. It's better than nothing but like alt + tab it make you click it a lot of times if you need something that is far in the list.

What I conclude from that is a search actions options with some keyboard shortcuts (doesn't matter that much) would be best but I'm not sure what is easier or harder to implement.

[0]: https://github.com/p-e-w/plotinus
Comment 1 Christian Hergert 2017-11-16 11:35:22 UTC
(In reply to Yotam Nachum from comment #0)
> [0]: https://github.com/p-e-w/plotinus

We have something like this built into Builder. It's the command bar¹. You can activate actions (with tab completion) based on the focus widget before activating the command bar. You cannot accurately "scan for any action" in a gtk application because you can have lots of duplicates. Especially so in document based applications.

¹ http://builder.readthedocs.io/en/latest/exploring.html#command-bar
Comment 2 Yotam Nachum 2017-11-16 12:08:47 UTC
(In reply to Christian Hergert from comment #1)

> We have something like this built into Builder. It's the command bar¹. You
> can activate actions (with tab completion) based on the focus widget before
> activating the command bar.

It's similar but not exactly what the options I checked have. It doesn't allow fuzzy search and it doesn't show me the shortcut for next time (like plotinus does in the screenshot or like pycharm does). Also it's based on the focus widget as you said, I can't activate it from a terminal or a documentation page and I couldn't find a way to jump to another panel from there.

>You cannot accurately "scan for any action" in a gtk application because you can have lots of duplicates. Especially so in document based applications.

Sorry, I wasn't clear enough. I only meant to show it as an example for the UI, not to use that code (unless of course you think it would be better that way).
Comment 3 GNOME Infrastructure Team 2018-01-11 10:45:10 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-builder/issues/307.