3 ms·
This is cool, and it's great to see you work on this (and thanks for open sourcing!) One more bit of prior art that might be interesting to you: I worked on th
by dangoor 7y ago
This is cool, and it's great to see you work on this (and thanks for open sourcing!)
One more bit of prior art that might be interesting to you: I worked on the Mozilla Bespin project a long time ago with Joe Walker. Joe was also really big on the command line idea for much the same reason and created [GCLI](https://github.com/joewalker/gcli/blob/master/docs/index.md https://github.com/joewalker/gcli/blob/master/docs/index.md).
GCLI ultimately landed in Firefox Developer Tools, but I don't think it's in the current shipping version. Funnily enough, I just found a video on YouTube of me demoing the command line in Firefox Dev Tools: https://www.youtube.com/watch?v=YwOwJ1_JaKE https://www.youtube.com/watch?v=YwOwJ1_JaKE
The state of the art in web UIs has definitely moved forward, and I'm really happy to see more experimentation with graphical command lines.
- uxamanda 7y agoThis is great! Would love to hear more about your experience working on it if you are interested in sharing – did you notice any particular tasks where this type of interaction shined? My dream would be to have something like built into an IDE so I could save edits directly.
- dangoor 7y agoAs features go, this didn't prove to be super successful (it's no longer shipping with Firefox). I do still think it's a valuable interaction style for being able to activate less-frequently-used features all from the keyboard. It's possible that the fact that web browsers also have the JS Console is just too much, because the JS Console has a command line that people are familiar with. The interaction model is very different, though. GCLI made it quick to type commands, whereas the JS console requires valid JS.
- uxamanda 7y agoInteresting, I could see how that could be confusing.