Fifteen Word Processor Commandments (1984)
wholeearth.info
wholeearth.info
- An interface shall not harm your content, or through inaction, allow your content to come to harm.
- An interface shall not waste your time or require you to do more work than is strictly necessary.
- An interface shall not allow itself to get into a state where it cannot manipulate content.
It also doesn't mention Microsoft Word which had also been released months before with a lot of press attention. A few pages later (after the commandments piece) they discuss the Microsoft Mouse which was essentially released to accompany Microsoft Word. Even though Word for DOS never became popular, it did have the first rudimentary WYSIWYG for the PC but you needed a graphics card which most PCs did not have. Would have been a good mention for this issue though.
If that sounds like a stone-age process ... well, it's the way publishing used to be done: it predates computerization and containerization by some decades, and it was only beginning to change in the 1980s.
To make matters worse, the writing/editing process would be mediated entirely by sending drafts back and forth via the mail, so you can reasonably add a couple of weeks to the process of writing and then approving a draft compared to what it would take today.
Upshot: this issue was probably finalized 3-4 months before the date on the cover. Microsoft Word was quite possibly not available to reviewers in time to make it into the magazine.
(Source: I used to write software reviews for Computer Shopper -- the British version of the title, not the same as the US one -- in the late 80s to early 90s. Smaller country, different tech by then, but it was still a tedious back-and-forth with printed drafts in envelopes with stamps on them (and sometimes floppy disks!).)
One day a few of us cut two classes in a row to finish a layout (so three class periods total including the repro class) and by lunchtime we were all acting really silly and laughing too much. We eventually figured out that we had been leaning over the layout table pasting so long that we had accidentally "huffed" the glue fumes!
this would have been early 80s.
Menus were more like categories, types of operations, and within those sections of the menu grouped like operations.
Each menu had a shortcut for invocation, usually Alt + the first letter of the menu, but sometimes an underlined second letter, or maybe FN key directly.
Within the menu most entries had an underlined key - if the interaction focus was in that menu, that key would invoke the related option / operation.
If there was an action the end user wanted to do frequently, nearly always there was also a direct keyboard combination that could trigger it while in the edit plane.
Many users learned of Ctrl+C / Ctrl+X / Ctrl+V (copy, cut, paste, respectively, for early 'dos' / Windows) or even on Macintosh whatever the respective keys were, from the edit menu. They tended to work in most applications and in the standard OS widgets (think text boxes of just about any sort).
-
These days, that sort of in-situ power user education, to empower new users is much harder to come by. It really doesn't help with so many things are designed mobile phone / web (no OS at all) / console and ported to PC (OMG all the times that inventory or design system in a game irks you).
Then the 2000's came around and Office 2000-something introduced the Ribbon, in an attempt to reduce the amount of UI elements and streamline the process. But the focus was on less UI clutter.
Nowadays there's WYSIWYG editors in web browsers for writing documents like that one from Dropbox or Notion, intentionally limiting how much markup you can do; they're text/word processors again, instead of full design suites.
And a keyboard shortcut is still faster.
The menu shortcut system is really good for those large enterprise systems, where multiple users use it in very different ways. If you're just inputting data, you can slowly learn the shortcuts for that. If you spend your time generating reports, you can learn the shortcuts for that. There doesn't need to be any assumptions about how the software will be used. There doesn't need to be loads of effort put into a flexible UI.
It's sad to see the shitshow that it has become, along with Windows. Talk about lost with no ideas, but desperately flailing to do... something.
Is there a standard way of doing this on modern PCs? Seems like it would be handy given how much text we produce.
end-of-line: C-k, -sentence: M-k
C -> Ctrl key, M -> Alt key
Press Home, then Shift + End or vise versa.
https://superuser.com/questions/947296/is-there-a-keyboard-s...
My OCD is offended.