3 ms·
> If it requires to check a documentation then it's probably badly designed in the first place. This notion is perhaps what is wrong with computing today. If
by digi_owl 12y ago
> If it requires to check a documentation then it's probably badly designed in the first place.
This notion is perhaps what is wrong with computing today.
If you come at any interface "tabula rasa" the only way to figure it out short of documentation/instruction is trial and error. "Discoverability" is so a distraction at best, and even then heavily dependent on prior (cultural) experience.
- cm2187 12y agoThe idea of a GUI and Intellisense is to have an embedded short documentation. Next to each checkbox, a GUI should have a plain text, short description of what it does (and a couple of words is often enough). Each item in an intellisense drop down has a short description too. The idea is not to eliminate documentation but to display it in the current context so that: 1. users make the correct choice when they type (i.e. the description will prevent them from making a mistake they would have made otherwise) 2. users know what other choice is available 3. users do not need to look for some offline documentation that may or may not refer to the version of the program they use (or the distribution of linux they use!) or may apply in a different context 4. users do not need to memorize occasionally used commands
- digi_owl 12y agoThey are still referring to documentation then, just now it is in-lined with the knobs they are operating. As such, still failing (in the absolutist sense) the idea of not having to check documentation. And i see much the same working on CLI, via tab completion etc. Using the Linux ip command in the zsh shell can be interesting in that regard.
- justincormack 12y agoThat is less direct though as I assume it is getting the information from the man page, which on Linux may not be maintained with the command (the BSDs are better here), rather than extracted from the source/api of the command itself.
- pdkl95 12y ago> embedded short documentation That would be "--help", which GNU requires[1] in all[2] of their programs. Combined with the tab completion that others have mentioned and the full documentation in man(1)/info(1), it is easy to discover how to use most commands iff you are willing to actually read the documentation that is available. [1] https://www.gnu.org/prep/standards/html_node/Command_002dLine-Interfaces.html#Command_002dLine-Interfaces https://www.gnu.org/prep/standards/html_node/Command_002dLin... [2] modulo a few that emulate very old behavior for comparability reasons
- Tiquor 12y agoSort of. It goes out the window once in an app. GUIs really are good for discoversbility.
- pdkl95 12y ago"The only 'intuitive' interface is the nipple. After that it's all learned." s/intuitive/discoverable/ GOOD GUIs are nice for discoverability, and the same is true for CLIs. There are many GUIs that are absolutely horrid, which rely on non-obvious icons or assume certain usage styles and offer no assistance if you don't have the same background assumptions as the GUI's creator. Having used many different types of programs over the last ~30 years, I have wasted far more time with bad GUIs than I have with bad CLIs. At least with the CLI I can grep the output or documentation for what I want. I cannot grep a menu or GUI form to find some option I've forgotten the name of. What this comes down to is that it is fairly easy to make a good GUI for simple things, and good programmers can make a nice GUI for the moderate and complex tasks. This is where discoverability is primarily useful, as it assists the inexperienced user and the dilettante. For those of us that want to use our computer in a far more serious way, what the UNIX style CLI (shell) provides us is an interface that is still very learnable (IFF you invest in the time it takes to read the documentation!), that enables crafting commands that are simply not practical in any GUI. If you don't believe this, tell me how I can, for example: - recursively walk an arbitrary directory tree of images at ($SRCDIR) - except for any dirfectgory that ends in '.backup' - finding any file that is NOT a PNG, - convert that that file into a PNG - but saving the new files in new directory tree ($DSTDIR), creating any necessary parent directories That would be a mess in any GUI. In bash + imagemagick, it would be: for i in "${SRCDIR}/**/!(*.backup)/!(*.png) ; do dst="${DSTDIR}${i#${SRCDIR}}" mkdir -p "$(dirname "${dst}")" convert "${i}" "${i%.*}.png" done Yes, that's ugly, but at least it is possible.
- raverbashing 12y agoWhile you're right it depends on prior cultural experience/knowledge of the domain, discoverability is very important. That's the "big wall" that got people joking about how to quit vi. Even to get to help, typing :help needs some help to get you there. The critique is not towards vi/emacs, they were like that because of technical limitations. But even then it can be improved Do you need a manual to use an ATM? The GPS system that comes with your car? A new stereo? Today, not being discoverable is a sure way your product won't be used, unless it's very useful in a very strict domain (like Apache, and even then)
- digi_owl 12y agoFirst time i used an ATM, one of my parents were there with me. As such i got instructions in how to do it. I don't have a car with a built in GPS. Operating a stereo comes back to the whole experience thing, as most of the buttons are "old". Most of the button icons to operate a CD player are the same that was used for a casette player back in the day. And likely ones first encounter with either was back when one was a kid trying to get their parent to put on some music or other. The closest i recall to reading about coming at computing "tabula rasa" was about a computer in a wall in India. And there the kids did what kids do, they poked and prodded and broke stuff to see how it worked. This to the point that they developed their own cultural contexts for various icons (one was referred to via some deity name because it looked like a set of drums the deity was depicted using).