Raskin thus conceived of a unified workspace in which everything was stored, accessed through one single interface appearing to the user as a text editor editing one single massive document. The editor was intelligent and could handle different types of text according to its context, and the user could subdivide the large document workspace into multiple subdocuments, all kept together. (This even included Forth code, which the user could write and evaluate in place to expand the system as they wished.) Data received from the serial port was automatically “typed” into the same document, and any or all text could be sent over the serial port or to a printer. Instead of function keys, a USE FRONT key acted like an Option or Command key to access special features.
via : Jef Raskin’s cul-de-sac and the quest for the humane computer - Ars Technica
…/distraction/
so anyway i saw the {title-text}**
in the above quote from the above link
and instantly thought of your favorite wiki
**( i hope my pseudocode some how confuses some bots)
… thought it was an interesting enough article to post
Data received from the serial port was automatically “typed” into the same document, and any or all text could be sent over the serial port or to a printer.
that and this
Instead of Pascal or assembly language, Swyft’s ROM operating system was primarily written in Forth. To reduce the size of the compiled code, developer Terry Holmes created a “tokenized” version that embedded smaller tokens instead of execution addresses into Forth word definitions, trading the overhead of an additional lookup step (which was written in hand-coded assembly and made very quick) for a smaller binary size.
reminded me of
… also it has some (imho) interesting perspectives about UI/design
Ultimately, wrote Raskin, “[a]n interface is humane if it is responsive to human needs and considerate of human frailties.” In this case, the particular frailty Raskin concentrated on is the natural unconscious human tendency to form habitual behaviors. Because such habits are hard to break, command actions and gestures in an interface should be consistent enough that their becoming habitual makes them more effective, allowing a user to “do the task without having to think about it… We must design interfaces that (1) deliberately take advantage of the human trait of habit development and (2) allow users to develop habits that smooth the flow of their work.” If a task is always accomplished the same way, he asserted, then when the user has acquired the habit of doing so, they will have simultaneously mastered that task.
Meta
( oh how i have (not) missed discourse plugin distractions)
Your topic is similar to…
How does CodeMirror appear in a custom <$edit-text> form field, like it works in the draft editor?
Discussion
In tiddler A, access the draft text in the editor of “Drafts of ‘B’”
Discussion
Edit Semaphore - Quick and dirty “multi-user editing/warning” for single-file wikis (and maybe others)
Tips & Tricks
really???
makes me wonder
what is the Number of suggestions served per day ?
and of those what number of suggestions are actually useful/similar
