Some UX suggestions for the GitHub Pages demo

[agriyakhetarpal]

Hi! I had a few suggestions for the demo deployed at https://tiledb-inc.github.io/jupyter-iframe-commands/, and I thought I could list them here.

1. In the "Enter a command" input box, it would be nice if it could display the commands within a dropdown, and attempt to autocomplete the commands as I type them. The reason is that I currently need to click the "List available commands" button to view the available commands, and then copy-paste/type out one of them in the input box. Having a dropdown with the commands would easily save a few keyboard presses and/or clicks here.
2. In the "Enter args (optional)" input box, I'm unsure what to input for each command (i.e., both the input type as to whether it's string/boolean/etc., and what the input should be) – as the available inputs for the commands are not documented. It would be nice if a tooltip with the "?⃝" symbol or similar could explain what a particular command does in a brief sentence, and provide a dropdown for the inputs as well.

I hope these are helpful! Thank you!

[jtpio]

Thanks @agriyakhetarpal for opening the issue and the suggestions!

In the "Enter args (optional)" input box, I'm unsure what to input for each command (i.e., both the input type as to whether it's string/boolean/etc., and what the input should be) – as the available inputs for the commands are not documented. It would be nice if a tooltip with the "?⃝" symbol or similar could explain what a particular command does in a brief sentence, and provide a dropdown for the inputs as well.

Yes sounds like a good idea 👍

In the "Enter a command" input box, it would be nice if it could display the commands within a dropdown, and attempt to autocomplete the commands as I type them. The reason is that I currently need to click the "List available commands" button to view the available commands, and then copy-paste/type out one of them in the input box. Having a dropdown with the commands would easily save a few keyboard presses and/or clicks here.

The main issue is that args are not easily discoverable at the moment. Currently the best way is to look at the JupyterLab source code or check for examples somewhere. But there has been some discussions about it, for example in:

• Formally describe command args and results jupyterlab/lumino#58
• Improve discovery and description of JupyterLab commands jupyterlab/jupyterlab#13962