Editing The Humane Interface (section)

=== Non-standard interaction architecture ===

Raskin also advocates a document-centered approach to computer interfaces that entails several radical changes to the current nature of operating systems and software:

* An end to stand-alone applications {{En dash}} every software package should be structured as a set of tools available to users on any document. For example, in the middle of writing a text document, a user should be able to do a mathematical computation by writing out the computation in the document, then hitting some "calculate" function.{{sfn|Raskin|2000|pp=140-142}}
* An end to directories and file names {{En dash}} "the content of a text file is its own best name." Every document should be identifiable by its contents, so there should not be need for directories or names for user-generated documents; Raskin argues that these names tend to be cryptic and make files difficult to find afterwards.{{sfn|Raskin|2000|loc=sec. 5-3|pp=117-123}}
* [[Zooming user interface]] {{En dash}} Raskin advocates an interface he calls [[Archy (software)|ZoomWorld]], in which the user navigates around a two-dimensional plane containing a graphical representation of every document on the computer. The user can zoom out to see all the documents, or zoom in on any specific document in order to read and edit it.{{sfn|Raskin|2000|loc=sec. 6-2}}

Raskin further asserts that interface design should be subject to [[regulation]], analogous to [[building code]]s. This could be done by establishing legal safeguards to protect consumers from harm, and establishing professional guidelines and standards to evaluate good practice and interface quality.{{sfn|Raskin|2000|pp=200-202}}