jwkvam/bowtie

add timer feature for client

Open

#127 opened on Apr 28, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (760 stars) (70 forks)batch import
help wanted

Description

Some features could be better implemented if the timer were on the client. It would save the server from sending a message to the client. An example where this could be useful is in #121.

Contributor guide

Tech stack
pythonjavascript
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Examine the current server side timer implementation in the bowtie codebase, likely in Python. Then look at the client side code (JavaScript/HTML) to understand how to implement a timer that runs on the client. Refer to issue #121 for context. The goal is to move timer logic from server to client, reducing server messages. Identify relevant files and propose a simple JavaScript based timer solution.
add timer feature for client · jwkvam/bowtie#127 | Good First Issue