Futilities/human/ui standards: Difference between revisions
No edit summary |
No edit summary |
||
| Line 17: | Line 17: | ||
==Notes== | ==Notes== | ||
===Command Links=== | |||
Handy command for making a commandlike link to a php executable: | Handy command for making a commandlike link to a php executable: | ||
ln -r --symbolic ./{{arg|X}}.php {{arg|X}} | ln -r --symbolic ./{{arg|X}}.php {{arg|X}} | ||
...where {{arg|X}} is the name of the executable php file (first line must be {{fmt/code|#!/usr/bin/php}}. and the file must have {{fmt/code|+x}} permission). | ...where {{arg|X}} is the name of the executable php file (first line must be {{fmt/code|#!/usr/bin/php}}. and the file must have {{fmt/code|+x}} permission). | ||
===Advanced Path Syntax=== | |||
Keep in mind the counterintuitive reality that <code>bash</code> does ''helpful'' processing on the <code>~</code> (tilde) character, converting it into the path to your home folder, while it also does ''unhelpful'' processing on the <code>*</code> (asterisk) character, expanding it into a list of matching files which may totally confuse the app, if it is not inside quotes. | |||
You ''can'' in fact get the preferred behavior for both of these by putting the asterisks in quotes but leaving the tilde outside -- like: | |||
~/path/"*.ext" | |||
Unescaped quote characters will protect their contents from preprocessing, but will also be removed before the preprocessed result is passed to the app. For me, the above would then be passed as: | |||
/home/woozle/path/*.ext | |||
Revision as of 00:15, 21 September 2022
|
User Interface standards and conventions as used in The Futilities
|
Guidelines
- Commands will always identify themselves when run (name, version, date of last major revision).
- In general, the app should always guide the user towards constructing a useful command string.
- When a command is run without proper input (including no input), it should at least:
- describe itself (name, version, revision date)
- show the format it expects for input arguments
- list any available options
- link to a documentation page.
- describe what is missing
- Error messages will be human-readable.
- If an operation might take a long time, there will be visual feedback regarding progress.
- This feedback does not have to be quantitative or make any estimates about completion, but if possible it should provide enough information for the user to compare with other runs on similar data and make their own reasonable guess.
- The application should not, by default, take extra time to gather information necessary for estimating percent-completion or time-to-complete. It may offer this service as a user option, however.
If a machine-interface is desired (e.g. communicating with the app via JSON or XML), there will be an --API flag; when that flag is used, these guidelines do not apply. I have not had need to implement this yet, however.
Notes
Command Links
Handy command for making a commandlike link to a php executable:
ln -r --symbolic ./<X>.php <X>
...where <X> is the name of the executable php file (first line must be «#!/usr/bin/php». and the file must have «+x» permission).
Advanced Path Syntax
Keep in mind the counterintuitive reality that bash does helpful processing on the ~ (tilde) character, converting it into the path to your home folder, while it also does unhelpful processing on the * (asterisk) character, expanding it into a list of matching files which may totally confuse the app, if it is not inside quotes.
You can in fact get the preferred behavior for both of these by putting the asterisks in quotes but leaving the tilde outside -- like:
~/path/"*.ext"
Unescaped quote characters will protect their contents from preprocessing, but will also be removed before the preprocessed result is passed to the app. For me, the above would then be passed as:
/home/woozle/path/*.ext