Export stopwatch times as csv
Maintainers usually reply within 7 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Quiet
- Domain
- mobile-dev
Research direction
Start by locating the stopwatch screen implementation in the FossifyOrg/Clock Android codebase, then find the three-dot menu code and the data structure storing lap and cumulative times (stored internally in milliseconds as noted in the issue). Implement the export function to format these times as CSV matching the provided example, then add a share or save action for the generated file. The feature is complete when the Export button appears in the stopwatch menu and produces a correctly formatted CSV when clicked.
Written by the indexing model from the issue text.
Description
Checklist
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
- This issue contains only one feature request.
- I have read and understood the contribution guidelines.
Feature description
On the stopwatch screen, in the three-dot menu in the top left, I would like an ‘Export’ button that exports the round numbers, lap times and cumulative times as a csv. (Just as it is displayed in the app.)
For example, an export of a 12-second 4-lap session could look like this[^1]:
round,lap_time,cumulative_time
1,2.9,2.9
2,3.2,6.1
3,3.1,9.2
4,2.8,12.0
Why do you want this feature?
The stopwatch is beautiful, but it unfortunately can’t be used for data gathering and analysisas of now.
Additional information
[^1]: Although the app displays the lap times in deciseconds (0.1 s), it’s best to use milliseconds in the export, because that’s how the times are stored internally.
- Dominant language
- Kotlin
- Stars
- 706
- Forks
- 73
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 8
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from FossifyOrg/Clock
-
feature request needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FossifyOrg/Clock#504 · 1 comment ·
Maintainers usually reply within 7 days
-
feature request needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FossifyOrg/Clock#491 ·
Maintainers usually reply within 7 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
FossifyOrg/Clock#448 · 2 comments · 1 reaction ·
Maintainers usually reply within 7 days
-
feature request needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
FossifyOrg/Clock#446 ·
Maintainers usually reply within 7 days
-
bug needs triage
Difficulty 2/5 Under an hour Newbie friendliness 74/100
FossifyOrg/Clock#439 ·
Maintainers usually reply within 7 days
All issues in FossifyOrg/Clock
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Kotlin/kotlin-lsp#288 ·
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
chrisbanes/haze#1536 ·
Maintainers usually reply within 1 day
-
Cassiopeia drops the `präsentiert von` credit printed in the event bodyPossibly taken A pull request linked to this issue is open or already merged. Openafk-ok area:data-quality importer size:S
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
enorm-labs/event-junkie#3166 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
rajpreetcodes/Skills_MCP_Server#25 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
com-lihaoyi/mill#7776 ·
Maintainers usually reply within 1 day