VS Code is also accessible from the keyboard. The most important key combination to know is Ctrl + Shift + P, which brings up Command palette . From here, you have access to all the features of VS Code, including keyboard shortcuts for the most common operations.
the Command palette gives access to many commands. You can run editor commands, open files, search for symbols, and see a quick preview of a file, all using the same interactive window. Here are a few tips:
another example of fman
The quickest way to explore fman shortcuts is via the Command palette :
Just press Ctrl + Shift + P (or Cmd + Shift + P for Mac) in fman to open it.
Now that the command palette (see above) has become a normal user interface functionality for advanced users and developers on certain applications (vscode, sublimetext, some pythonides, jupyterlab … etc.), I think in any complex program with many hidden tools / features, a palette of commands would be of great help.
A modern command palette serves 3 separate purposes as far as I can see
- Discovery of commands / features depending on what you want to do (ex: duplicate a file? Export a tree structure? Create a time stamped zip? … etc.)
- Discovery of shortcuts
- Executing commands that do not have an obvious visual interface or that are deeply nested somewhere and would require a few clicks. Or for the lazy who type faster, then move the mouse and click and don't remember the shortcuts.
The way I see human memory works is by associating what is the base object of the dictionary (key, value). And our intention is also directly related to the action we want to take. Generally, in any software, a user must learn to match their intention to the learned behavior of the steps to be performed in the software to achieve their goal. (let me know if I can explain this better). I find that the command palette shortens this approach and allows for a faster learning / practice experience.
Personally, I find it easier to remember the words and actions of what I want to accomplish than the steps I need to do to get there, so often I have to search for the exact recipe on Google and execute it manually. However, a palette of commands greatly helps with this and reduces the effort required to get it right. Google has also been a big push for people to switch from structured information to searchable (?) / Searchable information. I've also always thought that the command line was great for running when you know what you want, and the user interface is great for discovery.
As far far into the future we go from learning behaviors to simply dictating what we want and letting the software figure it out, that's what all this wizarding stuff is for.
So my question is this: is it only useful for people of certain types (i.e. developers) or is it widely applicable to the general population?
MacOS has the help search function, which is similar or its action item is quite good.
If someone wanted to implement such functionality in software, what would be the guidelines for them from a UX perspective?