From W3C Wiki
< Headlights2013(Difference between revisions)
|
|
| Line 1: |
Line 1: |
| - | ===Name of idea===
| + | Moved to Team wiki |
| - | | + | |
| - | Standardizing Gestures
| + | |
| - | | + | |
| - | ===Submitter name===
| + | |
| - | | + | |
| - | Doug Schepers
| + | |
| - | | + | |
| - | ===Classification===
| + | |
| - | This idea is:
| + | |
| - | * A specific technology area that requires new standardization (e.g. structured vocabularies, privacy, REST)
| + | |
| - | | + | |
| - | ===One Hundred Word Description of the Idea===
| + | |
| - | Gestures are still a missing event type, and are frequently asked for, because of ease of programming.
| + | |
| - | | + | |
| - | ====Longer Description====
| + | |
| - | There are several groups that are working on advanced User Interface events, including the WebApps WG, the Web Events WG, the IndieUI WG, and the new Pointer Events WG. However, all of these events are '''low-level''' (near-hardware layer, like mouse or touch surface) or '''high-level''' (user intentions, like ''undo'', ''redo'', ''next page'', ''zoom'', etc.). '''Gestures''' reside in the '''middle layer''' (e.g., a specific set of low-level mouse or touch events might be combined via gesture to evoke a high-level action like ''undo'').
| + | |
| - | | + | |
| - | Gestures are potentially different for each platform, each browser, each device, and even each webapp. So, a good approach may be not to define a set of gestures, but a way to map combinations of low-level events to high-level events.
| + | |
| - | | + | |
| - | Note, however, that gestures may be a patent minefield.
| + | |
| - | | + | |
| - | ===Benefit(s) to W3C===
| + | |
| - | * improves the capabilities of the Open Web Platform with a much-requested feature
| + | |
| - | | + | |
| - | ===Which of our stakeholders would be the most enthusiastic in supporting===
| + | |
| - | * some browser vendors
| + | |
Latest revision as of 15:57, 5 December 2012
Moved to Team wiki
