OpenCut-app / OpenCut-app/OpenCut
[FEATURE] reconsideration about timeline implementation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 89.8k
- Forks
- 8.9k
- PR merge metrics
- No merged PRs in 30d
Description
Problem
Just saw your work, checked your web beta version, I've had already experienced building a timeline, I wanted to suggest an important reconsideration before it's too late, about your current timeline implementation using React DOM (html/css...) which will affect the performance by a lot and instead use canvas like opencut (and most powerful online video editors) does
Solution
use canvas implementation
Alternative
Anything else?
No response
Contributor guide
No contributing guide indexed for this repository
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
The issue names no file, test, or entry point; begin by locating the existing React DOM timeline implementation in the TypeScript project. Review the proposed canvas approach and define what timeline behavior and performance evidence would count as done, since the payload provides no validation target.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend, performance, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100