Command Classic - Revision history

Maia: /* Keymap: Why do we want this? */

2024-08-15T06:28:18Z

Keymap: Why do we want this?

← Older revision		Revision as of 06:28, 15 August 2024
Line 15:		Line 15:
	Admiration for the relative simplicity of early Apple keyboards is not limited to me - the Happy Hacking Keyboard is famously inspired by the original Macintosh's symmetrical indented keybank without arrow keys. I think the better place to look is to the first Apple Desktop Bus keyboards, which standardized a layout intended to meet the needs of both Apple II and Mac users in a way roughly analogous to the demands of a modern Unix-like workstation environment.		Admiration for the relative simplicity of early Apple keyboards is not limited to me - the Happy Hacking Keyboard is famously inspired by the original Macintosh's symmetrical indented keybank without arrow keys. I think the better place to look is to the first Apple Desktop Bus keyboards, which standardized a layout intended to meet the needs of both Apple II and Mac users in a way roughly analogous to the demands of a modern Unix-like workstation environment.

	The common take among people who are not HHKB devotees seems to be that the Extended Keyboard, with all of its extra keys and double the price tag, is the more desirable option for Classic Mac fans, but I disagree. None of the additional keys were used in Mac OS outside of DOS compatibility cards and a few idiosyncratic software titles (like Microsoft's), that largely remains true to this day, and even in a *nix/X11 environment, I find ~~that~~ to ~~hold true~~.		The common take among people who are not HHKB devotees seems to be that the Extended Keyboard, with all of its extra keys and double the price tag, is the more desirable option for Classic Mac fans, but I disagree. None of the additional keys were used in Mac OS outside of DOS compatibility cards and a few idiosyncratic software titles (like Microsoft's), that largely remains true to this day, and even in a *nix/X11 environment, I find it to be the case. Keybindings from Readline or the Toolbox are far more important than the IBM-style alternatives and their dedicated keys.

	=== Cursor Keys ===		=== Cursor Keys ===

Maia: /* Keymap: Why do we want this? */

2024-08-15T06:25:51Z

Keymap: Why do we want this?

← Older revision		Revision as of 06:25, 15 August 2024
Line 11:		Line 11:
	== Keymap: Why do we want this?==		== Keymap: Why do we want this?==

	The basic concept is a modern iteration on Apple's in-house keymaps ~~that predated~~ the Extended Keyboard. They evolved through several platforms and models, but all featured a single keybank, with a numeric keypad added on business-oriented machines like the Apple III and Lisa. If navigation keys were present, they lived on the bottom of the main keybank, not in a separate cluster or as an additional mode of other keys.		The basic concept is a modern iteration on Apple's in-house keymaps predating the Extended Keyboard. They evolved through several platforms and models, but all featured a single keybank, with a numeric keypad added on business-oriented machines like the Apple III and Lisa. If navigation keys were present, they lived on the bottom of the main keybank, not in a separate cluster or as an additional mode of other keys.

	Admiration for the relative simplicity of early Apple keyboards is not limited to me - the Happy Hacking Keyboard is famously inspired by the original Macintosh's symmetrical indented keybank without arrow keys. I think the better place to look is to the first Apple Desktop Bus keyboards, which standardized a layout intended to meet the needs of both Apple II and Mac users in a way roughly analogous to the demands of a modern Unix-like workstation environment.		Admiration for the relative simplicity of early Apple keyboards is not limited to me - the Happy Hacking Keyboard is famously inspired by the original Macintosh's symmetrical indented keybank without arrow keys. I think the better place to look is to the first Apple Desktop Bus keyboards, which standardized a layout intended to meet the needs of both Apple II and Mac users in a way roughly analogous to the demands of a modern Unix-like workstation environment.

Maia at 06:25, 15 August 2024

2024-08-15T06:25:26Z

← Older revision		Revision as of 06:25, 15 August 2024
Line 9:		Line 9:
	'''Classic''' is a reference to the original Mac OS, widely referred to as such in the Mac OS X era, and its design principles. It's also a play on old Apple product naming conventions like "Macintosh Classic."		'''Classic''' is a reference to the original Mac OS, widely referred to as such in the Mac OS X era, and its design principles. It's also a play on old Apple product naming conventions like "Macintosh Classic."

	== Keymap ==		== Keymap: Why do we want this?==

	The basic concept is a modern iteration on ~~the~~ Apple ~~Desktop Bus keyboards~~ that ~~were not classified as "~~Extended.~~" Examples from~~ Apple ~~are:~~		The basic concept is a modern iteration on Apple's in-house keymaps that predated the Extended Keyboard. They evolved through several platforms and models, but all featured a single keybank, with a numeric keypad added on business-oriented machines like the Apple III and Lisa. If navigation keys were present, they lived on the bottom of the main keybank, not in a separate cluster or as an additional mode of other keys.
	* [https://deskthority.~~net/wiki/Apple_Desktop_Bus_Keyboard Apple Desktop Bus Keyboard ]~~
	* [https://deskthority.~~net/wiki/Apple_Standard_Keyboard Apple Keyboard]~~
	* [https://deskthority.net/wiki/Apple_Keyboard_II Apple Keyboard II]

	~~Third~~-~~party ADB keyboards often used a similar arrangement~~. ~~It evolved through~~ the Apple ~~III~~, the ~~later~~ Apple II ~~models, the Lisa,~~ and the ~~Macintosh before ultimately being supplanted by an adaptation~~ of ~~the IBM AT layout that began with the Apple Extended Keyboard~~.		Admiration for the relative simplicity of early Apple keyboards is not limited to me - the Happy Hacking Keyboard is famously inspired by the original Macintosh's symmetrical indented keybank without arrow keys. I think the better place to look is to the first Apple Desktop Bus keyboards, which standardized a layout intended to meet the needs of both Apple II and Mac users in a way roughly analogous to the demands of a modern Unix-like workstation environment.

			The common take among people who are not HHKB devotees seems to be that the Extended Keyboard, with all of its extra keys and double the price tag, is the more desirable option for Classic Mac fans, but I disagree. None of the additional keys were used in Mac OS outside of DOS compatibility cards and a few idiosyncratic software titles (like Microsoft's), that largely remains true to this day, and even in a *nix/X11 environment, I find that to hold true.

	=== Cursor Keys ===		=== Cursor Keys ===

Maia at 05:50, 15 August 2024

2024-08-15T05:50:47Z

← Older revision		Revision as of 05:50, 15 August 2024
Line 5:		Line 5:
	== Name ==		== Name ==

	"Command" refers to the primary modifier key ~~in the~~ Macintosh ~~environment~~ and ~~its progeny~~ (NeXT, Be). Its prominent size and ~~placement next to the space bar, like on Apple and NeXT keyboards, are~~ one of these keyboards' most important features.		'''Command''' refers to the primary modifier key on Macintosh computers and their spiritual relatives (NeXT, Be). Its prominent size and location is one of these keyboards' most important features, and a major motivating factor in their creation.

			'''Classic''' is a reference to the original Mac OS, widely referred to as such in the Mac OS X era, and its design principles. It's also a play on old Apple product naming conventions like "Macintosh Classic."

	"~~Classic~~" is a ~~reference to~~ the ~~original Mac OS~~, ~~early Macintosh principles in general~~, and the ~~way~~ Apple ~~affixed the word in some of its own product names (cf. Macintosh Classic)~~.		== Keymap ==

			The basic concept is a modern iteration on the Apple Desktop Bus keyboards that were not classified as "Extended." Examples from Apple are:
			* [https://deskthority.net/wiki/Apple_Desktop_Bus_Keyboard Apple Desktop Bus Keyboard ]
			* [https://deskthority.net/wiki/Apple_Standard_Keyboard Apple Keyboard]
			* [https://deskthority.net/wiki/Apple_Keyboard_II Apple Keyboard II]

			Third-party ADB keyboards often used a similar arrangement. It evolved through the Apple III, the later Apple II models, the Lisa, and the Macintosh before ultimately being supplanted by an adaptation of the IBM AT layout that began with the Apple Extended Keyboard.

	~~== Keymap Design ==~~

	=== Cursor Keys ===		=== Cursor Keys ===

Maia: /* Builds */ Added Build 4 to table

2023-06-21T05:06:07Z

Builds: Added Build 4 to table

← Older revision		Revision as of 05:06, 21 June 2023
Line 99:		Line 99:
	! Keymap		! Keymap
	! Opt Size		! Opt Size
	! Language ~~Key~~		! Language Keys
	! Connection		! Connection
	! Plate		! Plate
Line 112:		Line 112:
	\| JIS		\| JIS
	\| 1.5U		\| 1.5U
	\| 1U ~~Kana~~		\| 1U Hankaku/Zenkaku
	\| USB C		\| USB C
	\| Stainless		\| Stainless
	\| BOX White		\| Kailh BOX White
	\| PBT		\| PBT
	\| Cherry		\| Cherry
Line 125:		Line 125:
	\| JIS		\| JIS
	\| 1.25U		\| 1.25U
	\| 1.25U Eisuu/Kana		\| 1.25U Eisuu+Kana
	\| USB A (cable)		\| USB A (cable)
	\| Aluminum		\| Aluminum
	\| BOX Jade		\| Kailh BOX Jade
	\| PBT		\| PBT
	\| Cherry		\| Cherry
Line 141:		Line 141:
	\| Bluetooth		\| Bluetooth
	\| Stainless		\| Stainless
	\| BOX Silent Brown		\| Kailh BOX Silent Brown
	\| PBT		\| PBT
	\| XDA		\| XDA
	\| Poker		\| Poker
			\|-
			! [[Command Classic/Build 4\|''4J'']]
			\| ''2023.??''
			\| ''Compact''
			\| ''JIS''
			\| ''1.5U''
			\| ''1U Hankaku/Zenkaku<br>Fn layer on split space bar''
			\| ''USB C''
			\| ''Stainless''
			\| ''Kailh BOX White''
			\| ''PBT''
			\| ''Cherry''
			\| ''TOFU60 2.0<br>(Top Mount)''
			\|-
			! [[Command Classic/Build 4\|''4K'']]
			\| ''2023.??''
			\| ''Compact''
			\| ''ANSI(K)''
			\| ''1.5U''
			\| ''1.25U Hanja+Hangul''
			\| ''USB C''
			\| ''Stainless''
			\| ''dangkeebs Cookies n' Cream''
			\| ''PBT''
			\| ''Cherry''
			\| ''TOFU60 2.0<br>(Top Mount)''
	\|}		\|}

Maia: /* Builds */ IME →Language

2023-06-14T10:50:33Z

Builds: IME →Language

← Older revision		Revision as of 10:50, 14 June 2023
Line 99:		Line 99:
	! Keymap		! Keymap
	! Opt Size		! Opt Size
	! ~~IME~~ Key		! Language Key
	! Connection		! Connection
	! Plate		! Plate

Maia: /* Layout Variations */

2023-06-14T10:47:21Z

Layout Variations

← Older revision		Revision as of 10:47, 14 June 2023
Line 61:		Line 61:
	Full-size Command Classic keyboards use a bank layout identical to these, with a only main bank and a numeric keypad to the right, separated by a small gap. Unlike IBM, Sun, and most other keyboards, clusters of navigation keys and dedicated function keys are not used.		Full-size Command Classic keyboards use a bank layout identical to these, with a only main bank and a numeric keypad to the right, separated by a small gap. Unlike IBM, Sun, and most other keyboards, clusters of navigation keys and dedicated function keys are not used.

	== ~~Layout~~ Variations ==		== National Variations ==

	[[Image:Tsundoku_jis.png\|500px\|thumb\|right\|JIS Layout (with both ~~IME~~ keys)]]		[[Image:Tsundoku_jis.png\|500px\|thumb\|right\|JIS Reference Layout (with both language keys)]]

	[[Image:Tsundoku_ansi.png\|500px\|thumb\|right\|ANSI Layout]]		[[Image:Tsundoku_ansi.png\|500px\|thumb\|right\|ANSI Reference Layout]]

	The ~~design~~ concept is layout~~-agnostic~~, but was originally ~~envisioned~~ as a JIS keyboard.		The core concept does not require a specific national layout, but it was originally imagined as a JIS keyboard. Each national variation can be considered to have a "reference layout," which is what I would build in an ideal scenario without regard to parts availability. Actual Command Classic keyboards aim for these, but make adjustments to use keycaps that are actually available.

	=== JIS ===		=== JIS ===
Line 74:		Line 74:
	* 3.5U spacebar		* 3.5U spacebar
	** Not known to be available anywhere currently		** Not known to be available anywhere currently
	** Existing builds make compromises ~~with IME keys~~ to ~~use~~ available ~~spacebars~~		** Existing builds make various compromises to accommodate available keycaps
	*** ~~Model~~ 1 omits the 英数 key to accomodate a 4.5U spacebar		*** [[Command Classic/Build 1\|Build 1]] omits the 英数 key to accomodate a 4.5U spacebar
			*** [[Command Classic/Build 2\|Build 2]] uses 1.25U language keys to the right of the space bar, omitting right Command
	* Two 1U keys for input method mode control		* Two 1U keys for input method mode control
	* Nearly identical the Macway TP-110JIS		* Nearly identical the Macway TP-110JIS
Line 83:		Line 84:
	* 5.5U spacebar		* 5.5U spacebar
	** Uncommon but available		** Uncommon but available
	* Sun "UNIX ~~Keyboard~~" ~~layout~~		** Not a particularly strong preference. Westerners seem to like long space bars, but I think 4.5U is more than enough, and I am not going out of my way to build with a 5.5U space bar.
			** [[Command Classic/Build 3\|Build 3]] adds a 1U Option key to make a 4.5U space bar fit
			* Similar to Sun Type 5/6/7 "UNIX Keyboards"

	== Builds ==		== Builds ==

Maia: /* Modifiers */

2023-06-03T18:23:43Z

Modifiers

← Older revision		Revision as of 18:23, 3 June 2023
Line 39:		Line 39:
	Of course, anybody with a Command Classic who wants to navigate that way in vi(m) can just use hjkl as usual, and even outfit hjkl keycaps with alternate arrow legends, and program their firmware to support them as actual cursor navigation keys on the Fn layer if they choose. I may even start doing that just to be nice, because it doesn't interfere with anything I use. The dedicated arrow keys used in both command line and graphical contexts in the bottom corner, though, adhere Apple conventions because I prefer Apple-style graphical environments.		Of course, anybody with a Command Classic who wants to navigate that way in vi(m) can just use hjkl as usual, and even outfit hjkl keycaps with alternate arrow legends, and program their firmware to support them as actual cursor navigation keys on the Fn layer if they choose. I may even start doing that just to be nice, because it doesn't interfere with anything I use. The dedicated arrow keys used in both command line and graphical contexts in the bottom corner, though, adhere Apple conventions because I prefer Apple-style graphical environments.

	==== Modifiers ====		=== Modifiers ===

	The type and position of modifier keys is the major difference between Apple keyboards and others. Command Classic modifier layouts generally follow Apple conventions.		The type and position of modifier keys is the major difference between Apple keyboards and others. Command Classic modifier layouts generally follow Apple conventions, although Sun keyboards are also an influence.

	===== Command =====		==== Command ====

	Apple keys were another Apple III innovation brought to the Apple II beginning with the IIe. In Apple III and Apple II environments, "Open Apple" and "Closed Apple" were small keys used for only a handful of functions, but they established a precedent of platform-specific modifier keys beyond those included in mainstream teletype and terminal layouts. The Lisa enlarged the Apple key and made it the centerpiece of its graphical menu system's keybindings, which carried over to the Macintosh as the [https://www.folklore.org/StoryView.py?project=Macintosh&story=Swedish_Campground.txt Command key].		Apple keys were another Apple III innovation brought to the Apple II beginning with the IIe. In Apple III and Apple II environments, "Open Apple" and "Closed Apple" were small keys used for only a handful of functions, but they established a precedent of platform-specific modifier keys beyond those included in mainstream teletype and terminal layouts. The Lisa enlarged the Apple key and made it the centerpiece of its graphical menu system's keybindings, which carried over to the Macintosh as the [https://www.folklore.org/StoryView.py?project=Macintosh&story=Swedish_Campground.txt Command key].
Line 49:		Line 49:
	Given its significance, the Command key should be one of the easiest keys on the keyboard to hit. On Lisa and Macintosh keyboards, it is usually 1.5U or 1.75U wide. Command Classic keyboards use a 1.5U Command key placed immediately to the left of the space bar, and sometimes feature a right Command key, depending on the variation.		Given its significance, the Command key should be one of the easiest keys on the keyboard to hit. On Lisa and Macintosh keyboards, it is usually 1.5U or 1.75U wide. Command Classic keyboards use a 1.5U Command key placed immediately to the left of the space bar, and sometimes feature a right Command key, depending on the variation.

	===== Option =====		==== Option ====

	The Option key is another Apple innovation, often equated with the IBM PC Alt key. Unlike the Alt key, though, Option is primarily for chording with Command to access additional GUI keybindings, or combining with mouse actions to modify the result. Apple is less consistent about Option key sizes, but I prefer them to be larger. Command Classic usually uses a 1.5U Option key.		The Option key is another Apple innovation, often equated with the IBM PC Alt key. Unlike the Alt key, though, Option is primarily for chording with Command to access additional GUI keybindings, or combining with mouse actions to modify the result. Apple is less consistent about Option key sizes, but I prefer them to be larger. Command Classic usually uses a 1.5U Option key.

	===== Control =====		==== Control ====

	==== Numeric Keypad ====		==== Numeric Keypad ====

Maia at 18:19, 3 June 2023

2023-06-03T18:19:24Z

← Older revision		Revision as of 18:19, 3 June 2023
Line 5:		Line 5:
	== Name ==		== Name ==

	"Command" refers to the primary modifier key in the Macintosh environment and its ~~spiritual relatives~~ (NeXT, Be). Its prominent size and placement next to the space bar, like on Apple and NeXT keyboards, are one of these keyboards' most important features.		"Command" refers to the primary modifier key in the Macintosh environment and its progeny (NeXT, Be). Its prominent size and placement next to the space bar, like on Apple and NeXT keyboards, are one of these keyboards' most important features.

	"Classic" is a reference to the original Mac OS, early Macintosh principles in general, and the way Apple affixed the word in some of its own product names (cf. Macintosh Classic).		"Classic" is a reference to the original Mac OS, early Macintosh principles in general, and the way Apple affixed the word in some of its own product names (cf. Macintosh Classic).

Maia: Beginning of section reordering to focus on components rather than sources of inspiration.

2023-06-03T18:17:01Z

Beginning of section reordering to focus on components rather than sources of inspiration.

← Older revision		Revision as of 18:17, 3 June 2023
Line 9:		Line 9:
	"Classic" is a reference to the original Mac OS, early Macintosh principles in general, and the way Apple affixed the word in some of its own product names (cf. Macintosh Classic).		"Classic" is a reference to the original Mac OS, early Macintosh principles in general, and the way Apple affixed the word in some of its own product names (cf. Macintosh Classic).

	== ~~Prior Art~~ ==		== Keymap Design ==

	=== ~~Apple~~ ===		=== Cursor Keys ===

	~~Most of the direct inspiration for~~ Command Classic ~~comes from~~ Apple ~~keyboards~~ of the ~~1980s~~.		Cursor key placement on Command Classic is entirely an Apple convention. I am unaware of any off-the-shelf keyboards other than those made by Apple or for Apple platforms that use this placement.

	==== ~~Cursor Keys~~ ====		==== History ====

	Apple first featured a full four-direction set of cursor navigation keys on the Apple III (1980), ~~and all subsequent Apple computer keyboards featured~~ them, ~~except for~~ the ~~Steve Jobs projects (Lisa~~ and ~~the first Macintosh) with their infamous demand that all~~ navigation ~~be accomplished through~~ the ~~mouse~~.		Apple first featured a full four-direction set of cursor navigation keys on the Apple III (1980), which squeezed them into the bottom right corner of the main keybank in a dogleg configuration, with the up arrow above the down arrow, and a pair of horizontal navigation keys to the side.

	~~Prior to Apple Desktop Bus and its standardization of all models on a common keyboard lineup, Apple used two variations of cursor key placement. The first, used by the Apple III and the Macintosh Plus~~ [~~https~~:~~//deskthority~~.~~net/wiki/Apple_M0110A M0110A~~] keyboard, had up and down arrows stacked vertically in the bottom right corner of the main bank, with horizontal left and right arrows next to them on the bottom row (some third-party ADB keyboards use this layout as well).		[[Image:Apple_III_Cursor_Keys.png]]

			Apple's next computer, the IIe, brought many of the Apple III's features to the Apple II line, including an improved keyboard with four cursor navigation keys. While continuing to place the arrows in the bottom right of the main bank, the Apple IIe keyboard moved the up arrow to the bottom, making the cursor keys into a single row.

			[[Image:Apple_IIe_Cursor_Keys.png]]

	~~The second variation appeared for~~ the ~~first time~~ on the ~~Apple IIe~~, ~~remaining on all subsequent Apple II models and making its way to~~ the ~~Macintosh~~ with the ~~introduction~~ of ~~Apple Desktop Bus~~. ~~It places~~ the ~~all~~ cursor ~~keys~~ on the bottom ~~row~~, in left~~/right~~/down/up ~~order~~. ~~It appears~~ on the ~~[https://deskthority~~.~~net/wiki/Apple_Desktop_Bus_Keyboard Apple Desktop Bus Keyboard] (1986)~~, ~~[https://deskthority.net/wiki/Apple_Standard_Keyboard M0116~~ "~~Apple Keyboard~~"] (~~1987~~), and the ~~[https://deskthority.net/wiki/Apple_Keyboard_II Apple Keyboard II] (1990). Command Classic uses this cursor key placement~~. ~~It is more familiar and aesthetically satisfying~~ to me, ~~and~~ it ~~carries an added advantage of compatibility~~ with ~~standard~~-~~size Shift keys~~.		Apple continued to use this configuration on everything featuring cursor keys, outside of the Extended Keyboard line and a one-off reappearance of the dogleg layout on the Macintosh Plus keyboard, until the IBM-derived "Extended" style completely took over in the mid-1990s. This is the placement used for Command Classic keyboards.

			==== Why This Placement? ====

			* Familiarity: This is the placement I know best, that works with my muscle memory, and so it was what I wanted when building a keyboard for myself.
			* Aesthetics: My personal subjective feeling is that this placement looks good, and that shoehorning cursor navigation keys into the upper rows of the main bank looks messy. This includes today's compact mainstream keyboards that place the up arrow to the left of a 1U right Shift in order to implement inverse-T cursor navigation clusters in "60-65%."
			* Compatibility: Single-row placement on the bottom does not interfere with the size or position of the right Shift key, keeping Command Classic slightly closer to common keymaps and making keycap sourcing that much easier. Sourcing parts for these keymaps is challenging enough already that I will take a win where I can.

			==== Why not vi Placement? ====

			vi is my command line editor of choice, and those who know me somewhat well may be curious as to why I didn't go with its traditional hjkl left/down/up/right cursor navigation sequence. The honest truth is that I never developed a habit for it. I first got used to vi on IRIX, which supports cursor navigation with the arrow keys. vim also supports this, and I have only had brief encounters with "real vi" implementations that don't, so hjkl navigation never became muscle memory for me.

			Of course, anybody with a Command Classic who wants to navigate that way in vi(m) can just use hjkl as usual, and even outfit hjkl keycaps with alternate arrow legends, and program their firmware to support them as actual cursor navigation keys on the Fn layer if they choose. I may even start doing that just to be nice, because it doesn't interfere with anything I use. The dedicated arrow keys used in both command line and graphical contexts in the bottom corner, though, adhere Apple conventions because I prefer Apple-style graphical environments.

	==== Modifiers ====		==== Modifiers ====