classtranscribe / classtranscribe/liveplayer
PLAN: Componentize Live Player
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Here are three possible plans:
## 1. Pure JS library
### Pro:
- Light-weight
- More flexible to external developer (can use any framework like React, Vue, jQuery, etc.)
### Con:
- State management?
- HLS.js has already support most of functionalities
- Require more workload, need to redesign
## 2. React Component without Internal State
### Pro:
- Light-weight (relatively), No redundant state management tool (redux, etc.) is needed
- Relatively easy to work on
### Con:
- Need redesign (from dva/redux model to internal state management)
## 3. React Component with Internal State
### Pro:
- Easy to achieve at this state
### Con:
- Heavy component, performance issue
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Inspect the existing live player structure and compare it with the three proposed approaches; done would require a settled componentization direction and an implementation scope rather than another list of options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100