Frontmatter
| id | 505 |
| title | Touch events concept |
| state | Closed |
| labels | enhancementhelp wanteddiscussionstale |
| assignees | [] |
| createdAt | Apr 24, 2020, 5:34 PM |
| updatedAt | Sep 28, 2024, 4:31 AM |
| githubUrl | https://github.com/neomjs/neo/issues/505 |
| author | tobiu |
| commentsCount | 2 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | Sep 28, 2024, 4:31 AM |
To be fair, I did not look at native touch-related browser events for many (5?) years.
Was thinking that at this point there will be events like swipe or rotate out of the box.
This assumption was naive, I did not even find proposals.
Took a quick look at:
https://github.com/hammerjs/hammer.js
And created a ticket, since (again) invalid import statements.
https://github.com/hammerjs/hammer.js/issues/1249
From the concept we do need something similar for neo. I would prefer to use global (doc.body) events and delegate them through the cmp-tree.
we can just pass the basic touch events from main to the app worker and add a manager class there which can map the touch based input into events which do make sense.
thoughts?