Talk:OLPC Human Interface Guidelines
Contents
Introduction
General Comments
The page needs copy-editing. "apply this principal" [principle]; "it's" for [its], etc.
Who Should Read This Document
How to Read This Document
Internal hyperlinking
external links to API
The Core Ideas
Activities, Not Applications
Instead of "much more than a semantic difference in the naming convention" say "much more than a difference in the naming convention" since semantics is about meaning, not naming. Nitpicker 21:26, 27 October 2006 (EDT)
Collaboration
Creation
"the best way to learn how to write a program is to write one" or perhaps to teach someone else how to write one. The aphorism that those who cannot do it teach it instead is false and pernicious. Nitpicker 21:26, 27 October 2006 (EDT)
"apply this principal" -> "... principle" Nitpicker 21:26, 27 October 2006 (EDT)
Journaling
Design Fundamentals
Know Your Audience
- Inexperienced
- Young
- International
Key Design Principles
Respell article section title to match this one. Nitpicker 23:22, 27 October 2006 (EDT)
- Performance
- Usability
- Simplicity
- Reliability
- Adaptabilty
- Interoperability
- Mobility
- Exposability
- Accessibility
Add
- Modelessness
- Command gestures do not change meaning (at all). Since modal dialog boxes make all other command gestures fail completely, they should never be allowed. To add insult, such boxes with only one choice available have purely negative utility.
[This is in contrast to applications with multiple text editor functions inside, all different, so you can't spell check a file name, for example.]
- Monotony
- Only one way to do any given task. [No need to stop to decide which way to do it.]
See "The Humane Interface" by Jef Raskin for more detailed and science based discussion of a full range of user interface issues. He also started the Macintosh project at Apple and thus began the Graphical User Interface craze that is still with us. Nitpicker 23:22, 27 October 2006 (EDT)
