Design Team/Proposals/Keyboard Action - Revision history

FGrose at 23:28, 14 February 2011

2011-02-14T23:28:43Z

← Older revision		Revision as of 19:28, 14 February 2011
Line 20:		Line 20:
	Existing proposals block below: --></noinclude>		Existing proposals block below: --></noinclude>

	=== discoverable, consistent, lazy-programmer keyboard shortcuts ===		=== [[#discoverable, consistent, lazy-programmer keyboard shortcuts\|discoverable, consistent, lazy-programmer keyboard shortcuts]]===
			<noinclude>
	http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg03938.html		http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg03938.html

Line 50:		Line 50:


	~~<noinclude>~~
	==Subpages==		==Subpages==
	{{Special:PrefixIndex/{{PAGENAMEE}}/}}		{{Special:PrefixIndex/{{PAGENAMEE}}/}}
	</noinclude>		</noinclude>

FGrose at 00:20, 13 February 2011

2011-02-13T00:20:45Z

← Older revision		Revision as of 20:20, 12 February 2011
Line 17:		Line 17:
	:'''Reviewer Comments:'''		:'''Reviewer Comments:'''
	:: comments here (signed with: --~~~~)		:: comments here (signed with: --~~~~)
	END OF BLOCK line~~</noinclude>~~		END OF BLOCK line
	~~Pre-existing~~ proposals block below: -->		Existing proposals block below: --></noinclude>

	=== discoverable, consistent, lazy-programmer keyboard shortcuts ===		=== discoverable, consistent, lazy-programmer keyboard shortcuts ===

FGrose at 00:10, 13 February 2011

2011-02-13T00:10:16Z

← Older revision		Revision as of 20:10, 12 February 2011
Line 1:		Line 1:
	<noinclude>~~{{TOCright}}~~<!-- START OF BLOCK -- 1. COPY & PASTE this BLOCK to below the END OF BLOCK line.		<noinclude>__TOC__<!-- START OF BLOCK -- 1. COPY & PASTE this BLOCK to below the END OF BLOCK line.
	2. PASTE it before any pre-existing proposal,		2. PASTE it before any pre-existing proposal,
	3. then OVERWRITE the place holders with your information,		3. then OVERWRITE the place holders with your information,
Line 5:		Line 5:
	5. Click [Show preview] to check formatting, and adjust as necessary.		5. Click [Show preview] to check formatting, and adjust as necessary.
	6. Click [Save page] to complete the edit.		6. Click [Save page] to complete the edit.
	~~-->~~
	===<Your proposal's pithy name here>~~=== <!-- Leave the === prefix and suffix~~ ===		===<Your proposal's pithy name here>===
	~~-->~~
	:'''Rationale:''' ~~<!-- leave this line -->~~		:'''Rationale:'''
	:: <Your rationale here>		:: <Your rationale here>
	:'''Features:''' ~~<!-- leave this line -->~~		:'''Features:'''
	:# <1st feature here>		:# <1st feature here>
	:# <2nd feature here>		:# <2nd feature here>
	:'''Implementation Details:''' ~~<!-- leave this line -->~~		:'''Implementation Details:'''
	:: <Details here>		:: <Details here>
	:'''Reviewer Comments:''' ~~<!-- leave this line -->~~		:'''Reviewer Comments:'''
	:: comments here ~~<!-- reviewers: leave the :: prefix and overwrite up to this signature code~~: --~~~~		:: comments here (signed with: --~~~~)
	END OF BLOCK line ~~-->~~</noinclude>		END OF BLOCK line</noinclude>
	~~<!--~~ Pre-existing ~~Proposal Block~~ -->		Pre-existing proposals block below: -->

	=== discoverable, consistent, lazy-programmer keyboard shortcuts ===		=== discoverable, consistent, lazy-programmer keyboard shortcuts ===

FGrose at 15:57, 11 May 2009

2009-05-11T15:57:04Z

← Older revision		Revision as of 11:57, 11 May 2009
Line 47:		Line 47:

	:: <!-- reviewers: leave the :: prefix and overwrite up to this signature code: --~~~~		:: <!-- reviewers: leave the :: prefix and overwrite up to this signature code: --~~~~
			-->

FGrose at 15:55, 11 May 2009

2009-05-11T15:55:40Z

← Older revision		Revision as of 11:55, 11 May 2009
Line 1:		Line 1:
	{{~~DesignProposal\|subject=Keyboard_Action~~}}~~<!-- Keep this line -->~~		<noinclude>{{TOCright}}<!-- START OF BLOCK -- 1. COPY & PASTE this BLOCK to below the END OF BLOCK line.
	~~<noinclude>~~<!-- START OF BLOCK -- 1. COPY & PASTE this BLOCK to below the END OF BLOCK line.
	2. PASTE it before any pre-existing proposal,		2. PASTE it before any pre-existing proposal,
	3. then OVERWRITE the place holders with your information,		3. then OVERWRITE the place holders with your information,
Line 7:		Line 6:
	6. Click [Save page] to complete the edit.		6. Click [Save page] to complete the edit.
	-->		-->
	==~~[<span class~~=~~"plainlinks">[{{fullurle:index.php\|title={{PAGENAMEE}}&action=edit}} edit]</span>]~~ <Your proposal's pithy name here>== <!-- Leave the == prefix and suffix == -->		===<Your proposal's pithy name here>=== <!-- Leave the === prefix and suffix ===
			-->
	:'''Rationale:''' <!-- leave this line -->		:'''Rationale:''' <!-- leave this line -->
	:: <Your rationale here> ~~<!-- leave the :: prefix, overwrite the rest of this line -->~~		:: <Your rationale here>

	:'''Features:''' <!-- leave this line -->		:'''Features:''' <!-- leave this line -->
	:# <1st feature here~~> <!-- leave the :# prefix, overwrite the rest of this line --~~>		:# <1st feature here>
	:# <2nd feature here> ~~<!-- ditto -->~~		:# <2nd feature here>

	:'''Implementation Details:''' <!-- leave this line -->		:'''Implementation Details:''' <!-- leave this line -->
	:: <Details here> ~~<!-- leave the :: prefix, overwrite the rest of this line -->~~		:: <Details here>

	:'''Reviewer Comments:''' <!-- leave this line -->		:'''Reviewer Comments:''' <!-- leave this line -->
	:: comments here <!-- reviewers: leave the :: prefix and overwrite up to this signature code: --~~~~		:: comments here <!-- reviewers: leave the :: prefix and overwrite up to this signature code: --~~~~
	END OF BLOCK line --> </noinclude>		END OF BLOCK line --></noinclude>
	<!-- Pre-existing Proposal Block -->		<!-- Pre-existing Proposal Block -->

	== discoverable, consistent, lazy-programmer keyboard shortcuts ==		=== discoverable, consistent, lazy-programmer keyboard shortcuts ===

	http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg03938.html		http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg03938.html
Line 47:		Line 44:
	:'''Reviewer Comments:''' <!-- leave this line -->		:'''Reviewer Comments:''' <!-- leave this line -->
	::http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg03332.html		::http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg03332.html
	::~~[<span class="plainlinks">[{{fullurle:index.php\|title=Talk:Design_Team/Vision/Proposals/Keyboard_Action&action=edit&section=1}} edit]</span>]~~ [[Talk:Design_Team/Vision/Proposals/Keyboard_Action#discoverable,_consistent,_lazy-programmer_keyboard_shortcuts \| comments on talk page]]		::[[Talk:Design_Team/Vision/Proposals/Keyboard_Action#discoverable,_consistent,_lazy-programmer_keyboard_shortcuts \| comments on talk page]]

	:: <!-- reviewers: leave the :: prefix and overwrite up to this signature code: --~~~~		:: <!-- reviewers: leave the :: prefix and overwrite up to this signature code: --~~~~



			<noinclude>
			==Subpages==
			{{Special:PrefixIndex/{{PAGENAMEE}}/}}
			</noinclude>

FGrose: Design Team/Vision/Proposals/Keyboard Action moved to Design Team/Proposals/Keyboard Action: trim path

2009-05-09T20:22:34Z

Design Team/Vision/Proposals/Keyboard Action moved to Design Team/Proposals/Keyboard Action: trim path

← Older revision	Revision as of 16:22, 9 May 2009
(No difference)

FGrose at 02:54, 1 May 2009

2009-05-01T02:54:18Z

← Older revision		Revision as of 22:54, 30 April 2009
Line 24:		Line 24:

	== discoverable, consistent, lazy-programmer keyboard shortcuts ==		== discoverable, consistent, lazy-programmer keyboard shortcuts ==

			http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg03938.html

	(revised 4/23/09)		(revised 4/23/09)

Homunq at 17:02, 24 April 2009

2009-04-24T17:02:40Z

← Older revision		Revision as of 13:02, 24 April 2009
Line 34:		Line 34:
	alt-<key> would be reserved for sugar-wide (or nearly) shortcuts. <s>This would preseve z, x, c, v as the 1984 mac standards.</s> Globally-available keys: print screen, view source, power/volume/brightness controls, shut activity (alt-escape), next/previous activity (alt-tab), possibly in the future chat-with-people-sharing-with-me-now/ bulletin board, etc. Holding down alt would bring up a static cheat sheet of these shortcuts after a short delay.		alt-<key> would be reserved for sugar-wide (or nearly) shortcuts. <s>This would preseve z, x, c, v as the 1984 mac standards.</s> Globally-available keys: print screen, view source, power/volume/brightness controls, shut activity (alt-escape), next/previous activity (alt-tab), possibly in the future chat-with-people-sharing-with-me-now/ bulletin board, etc. Holding down alt would bring up a static cheat sheet of these shortcuts after a short delay.

	ctrl-<key> would be reserved for application-specific shortcuts, including z, x, c, v. ctrl-<numeral> would switch toolbars to toolbar x. Holding ctrl would immediately bring up a translucent letter over the appropriate icon in the toolbar. Translucent letters would also flash briefly when clicking on a toolbar button, to aid discovery. Python apps (at least) would get keys assigned for free, though they could do it manually with an underscore char before the given letter ("_Print" would be p, "P_rint" would be r, "Print__o" would be o). This behind-the-scenes magic would respect localization - shortcuts would change by language. Shortcuts would be available even if the given toolbar were not open. <s>Alt shortcuts would not duplicate ctrl shortcuts, so copy, paste, undo, and exit would not have alt shortcuts.</s> ctrl-shift would be the reverse action, and ctrl-alt would be modified action (such as paste and pop from clipboard instead of just paste).		ctrl-<key> would be reserved for application-specific shortcuts, including z, x, c, v. ctrl-<numeral> would switch toolbars to toolbar x. Holding ctrl would immediately bring up a translucent letter over the appropriate icon in the toolbar. Translucent letters would also flash briefly when clicking on a toolbar button, to aid discovery. Python apps (at least) would get keys assigned for free, though they could do it manually with an underscore char before the given letter ("_Print" would be p, "P_rint" would be r, "Print__o" would be o; all would display as simply "Print"). This behind-the-scenes magic would respect localization - shortcuts would change by language. Shortcuts would be available even if the given toolbar were not open. <s>Alt shortcuts would not duplicate ctrl shortcuts, so copy, paste, undo, and exit would not have alt shortcuts.</s> ctrl-shift would be the reverse action, and ctrl-alt would be modified action (such as paste and pop from clipboard instead of just paste).

	Both ctrl and alt would be sticky toggles which reverted to off after a user-settable amount of time, defaulting to 1 second. If a global key (such as Insert or F1) was pressed while ctrl was toggled on, it would be sent to the current activity, not caught by Sugar. This would allow legacy applications which needed these keys to function.		Both ctrl and alt would be sticky toggles which reverted to off after a user-settable amount of time, defaulting to 1 second. If a global key (such as Insert or F1) was pressed while ctrl was toggled on, it would be sent to the current activity, not caught by Sugar. This would allow legacy applications which needed these keys to function.

Homunq at 17:01, 24 April 2009

2009-04-24T17:01:32Z

← Older revision		Revision as of 13:01, 24 April 2009
Line 24:		Line 24:

	== discoverable, consistent, lazy-programmer keyboard shortcuts ==		== discoverable, consistent, lazy-programmer keyboard shortcuts ==
			(revised 4/23/09)

	monopoly key (windows key) would be the frame key. This would also be available as ~~ctrl~~-~~enter~~ as a (hopefully unnecessary) backup.		monopoly key (windows key) would be the grab key.

			Insert would be the frame key (mnemonic: "INSet"). This would also be available as alt-F3 or alt-monopoly 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)		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)

	~~ctrl~~-<key> would be reserved for sugar-wide (or nearly) shortcuts. This would preseve 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 after a short delay.		alt-<key> would be reserved for sugar-wide (or nearly) shortcuts. <s>This would preseve z, x, c, v as the 1984 mac standards.</s> Globally-available keys: print screen, view source, power/volume/brightness controls, shut activity (alt-escape), next/previous activity (alt-tab), possibly in the future chat-with-people-sharing-with-me-now/ bulletin board, etc. Holding down alt would bring up a static cheat sheet of these shortcuts after a short delay.

	~~alt~~-<key> would be reserved for application-specific shortcuts. ~~alt~~-<numeral> would switch toolbars to toolbar x. Holding ~~alt~~ would immediately 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 open. Alt shortcuts would not duplicate ctrl shortcuts, so copy, paste, undo, and exit would not have alt shortcuts.		ctrl-<key> would be reserved for application-specific shortcuts, including z, x, c, v. ctrl-<numeral> would switch toolbars to toolbar x. Holding ctrl would immediately bring up a translucent letter over the appropriate icon in the toolbar. Translucent letters would also flash briefly when clicking on a toolbar button, to aid discovery. Python apps (at least) would get keys assigned for free, though they could do it manually with an underscore char before the given letter ("_Print" would be p, "P_rint" would be r, "Print__o" would be o). This behind-the-scenes magic would respect localization - shortcuts would change by language. Shortcuts would be available even if the given toolbar were not open. <s>Alt shortcuts would not duplicate ctrl shortcuts, so copy, paste, undo, and exit would not have alt shortcuts.</s> ctrl-shift would be the reverse action, and ctrl-alt would be modified action (such as paste and pop from clipboard instead of just paste).

	Both ctrl and alt would be sticky toggles which reverted to off after a user-settable amount of time, defaulting to 1 second.		Both ctrl and alt would be sticky toggles which reverted to off after a user-settable amount of time, defaulting to 1 second. If a global key (such as Insert or F1) was pressed while ctrl was toggled on, it would be sent to the current activity, not caught by Sugar. This would allow legacy applications which needed these keys to function.

	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.		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.

FGrose at 03:43, 23 March 2009

2009-03-23T03:43:47Z

← Older revision		Revision as of 23:43, 22 March 2009
Line 7:		Line 7:
	6. Click [Save page] to complete the edit.		6. Click [Save page] to complete the edit.
	-->		-->
	==[<span class="plainlinks">[{{fullurle:index.php\|title={{PAGENAMEE}}&action=edit}} edit]</span>] <Your pithy ~~proposal~~ name here>== <!-- Leave the == prefix and suffix == -->		==[<span class="plainlinks">[{{fullurle:index.php\|title={{PAGENAMEE}}&action=edit}} edit]</span>] <Your proposal's pithy name here>== <!-- Leave the == prefix and suffix == -->
	:'''Rationale:''' <!-- leave this line -->		:'''Rationale:''' <!-- leave this line -->
	:: <Your rationale here> <!-- leave the :: prefix, overwrite the rest of this line -->		:: <Your rationale here> <!-- leave the :: prefix, overwrite the rest of this line -->