Embed video?
- Dominant language
- Java
- Stars
- 39
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Embedding video in questions would be a significant accomplishment. Kahoot allows video to be added to questions by providing a YouTube link. However, a primary goal of Toohak is the ability for quizzes to be played without the influence of latency or an internet connection at all.
However, videos are big and complex. Similar to the audio issue in #1, the implementation could take several forms. The same questions are raised (see the audio issue), but also the following new ones:
1) Where would the video be played? Does the server window size need to increase or just be adaptive?
2) What about video looping?
3) What if users don't have a local copy of the video they want to embed?
A potential solution is to simply add an additional tab to the server's tabbed view and provide playback controls, but this greatly increases complexity and takes processing time away from actually hosting the quiz. Additionally, it would require that the users be close to the server machine and that the server screen be visible. This goes against the goal of allowing users to play without physical proximity to the server.
Transmitting video data to the clients is an unlikely solution. The data would have to be compressed as much as possible and serialized, which could incur serious latency and overheads. A potential solution for the latency is to send all multimedia data to clients before the quiz begins, but the complexity issue remains.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the related audio issue (#1) and reviewing how the server and clients currently handle quiz media. The issue raises unresolved choices about playback location, looping, local availability, transmission, and offline use; define those requirements and an acceptance path before implementation. Done should include a documented video approach that preserves the project's offline and low-latency goals.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100