mapbox / mapbox/mapbox-gestures-android
Common repository for pointer data
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 30
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Since there's only one entry point to pass `MotionEvent`s, there's no difference between the data each gesture detector is working with.
We should centralize this incoming stream of events in one "repository" (`AndroidGestureManager` class?) that will server pointers map, distances, spans, and velocities for the gesture detectors. This should significantly decrease the memory and computation footprint of those computations which are effectively repeated by each gesture detector, because of the inheritance.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the single entry point that passes MotionEvents into the gesture detectors and inspect how each detector computes pointer maps, distances, spans, and velocities. Evaluate the proposed AndroidGestureManager as a shared repository; done means the detectors consume centralized event data without repeating those computations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100