Each set of timers should be associated with a job/task
. This necessitates
the creation of an entire webpage dedicated to managing job/task
. On this
job/task
page, users will be able to add new job/task
, reorganize them,
rename them, and click on them. If a job/task
is selected, the user will be
redirected to the timers
webpage.
Implement the Worker
interface to execute timers in a separate thread,
allowing them to run in the background.
Every recorded time-lapse will be listed in this section.
Calculate the sum of all timers and display it in a totalHours
counter.
To prevent unusual effects while numbers are changing, it is essential to separate each digit into its own element.
The timers
array should include not only the time-lapse but also the
date it was created.
Currently, there is a single setInterval
function that runs continuously until
the tab is closed. It would be beneficial to find a way to stop and
restart the interval function.
Storing timers
in memory will reduce localStorage access and improve
performance.
Currently, all the timers are printed each time we add a timer to the
timers
list.
Identical code fragments exist in all files and could be encapsulated for improved maintainability.