[IAEP] 2 design proposals: home view, discoverable shortcuts
jameson.quinn at gmail.com
Sun Mar 22 17:09:06 EDT 2009
Proposal 1: home view: "Filtered ring w/ side panels"
Proposal 2: shortcut keys
monopoly key (windows key) would be the frame key. This would also be
available as ctrl-enter as a (hopefully unnecessary) backup.
F1-F4 would be view / zoom level, as currently. Pressing F3 while already in
home view would toggle view all/ring view, while pressing F4 while already
in app view would cycle through open activities. If we ever get different
friend sets or something, we could do something similar for F2. F9-F12 would
be reserved for sugar, too - for instance, journal, context-sensitive help.
F5-F8 would be for activity-specific functions. (IMO this is consistent with
the XO keyboard and a fair way to divvy up this set of keys)
alt-<key> would be reserved for application-specific shortcuts.
alt-<numeral> would switch toolbars to toolbar x. Holding alt would bring up
a translucent letter over the appropriate icon in the toolbar. Python apps
(at least) would get keys assigned for free, though they could do it
manually with an underscore char (or similar) before the given letter. This
behind-the-scenes magic would respect localization - shortcuts would change
by language. Shortcuts would be available even if the given toolbar were not
ctrl-<key> would be reserved for sugar-wide (or nearly) shortcuts. This
would presever z, x, c, v as the 1984 mac standards. ctrl-numeral would be
equivalent to Fx (ie, F1). Other globally-available keys: print screen, view
source, power/volume/brightness controls, shut activity (ctrl-escape),
next/previous activity, possibly in the future
chat-with-people-sharing-with-me-now/ bulletin board, etc. Holding down
control would bring up a static cheat sheet of these shortcuts.
All other keys would have their conventional meaning, except for num lock.
The number pad would always be numbers, and pressing num lock would cause
the machine to make a loud farting noise.
(copy of above at
Did I leave anything out, or not explain anything?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the IAEP