You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{
"name": "ITD",
"description": "Interface To Device",
"gradient_type": "C", // did I get this right?"cs": "??", // no clue"associated_root": true, // ideally we get an associated root too!"degrees": [
null,
"single- or few-button on-device interface for X (e.g., power+volume controls on a smartphone, reset button on a device)",
"single- or few-button wired controller for X (e.g., [wired] computer mouse, plunger for triggering explosives)",
"single- or few-button short-distance wireless controller for X (e.g., garage door opener)",
"single- or few-button long-distance remote controller for X",
"hybrid wired/wireless controller for X", // not sure about what to do with this degree"full-function long-distance remote controller for X (e.g., phone app for IoT devices)",
"full-function short-distance wireless controller for X (e.g., TV remote, wiimote)",
"full-function wired controller for X (e.g., [wired] computer keyboard)",
"full-function on-device interface for X (e.g., )"
]
},
Here's a rough sketch of distinctions that could be made by an "INTERFACE TO DEVICE" affix:
degree of control:
degree of separation:
I think a 2x4+1 affix would work best for this (so, ignore the "other and/or unspecified" options)
This would be useful for finding a way to derive "garage door opener" that doesn't require a separate root
The text was updated successfully, but these errors were encountered: