3 ms·
One principle is that text/command interface and graphical user interface aren't separated. As in: what if.. you could use a GUI and type commands? Some softw
by romwell 7y ago
One principle is that text/command interface and graphical user interface aren't separated.
As in: what if.. you could use a GUI and type commands?
Some software, like CAD programs (AutoCAD, 3DS MAX) and games (HalfLife, Quake, etc) have been doing it forever, but all these solutions are ad-hoc.
We could have had this as a default.
- j88439h84 7y agoThe text editors all have that, afaik.
- pvg 7y agoThat's more of an implementation detail than a principle to me. Some graphics programs have CLIs. Lots of GUIs have CLIs with various levels of integration. And as you say, we've had that forever so it's not something that's, say, in a Smalltalk system that doesn't exist now.
- TeMPOraL 7y agoClose, but this is still but a shadow. The kind of UIs I think about have text commands and GUI commands being essentially the same; your clicking issues commands, but you can also start typing and then use mouse to select GUI elements as arguments - because things drawn on screen are first-class objects, not just their rendering. Think e.g. of typing "ls" (or pressing a button) to be shown directory listing, on which now you can click, drag&drop, etc. You start typing "rm", and now all entries can be clicked to add as arguments. Or, you start typing "find -mtime" and now you can click on any of the visible timestamps, etc.