mathoudebine / mathoudebine/turing-smart-screen-python
Additional/Custom date/time Options
Nobody has claimed this yet.
- Dominant language
- Rich Text Format
- Stars
- 2.3k
- Forks
- 412
- Avg merge
- 21h 10m
- Merged PRs (30d)
- 7
Description
Is your feature request related to a problem? If so, please describe the problem.
Only two predefined date/time stats are available: DAY and HOUR.
Describe the feature / solution to your problem you'd like
The ability to define additional date/time stats entries.
Describe alternatives you've considered / and or tested
Could be implemented via custom stats, however native support would be appreciated.
Screenshots / photos & mockups of the Turing screen
In the simulator screenshot below, DAY is displaying "day month year" at the top left, HOUR is at the top right. This has been achieved by following the Babel date formatting according to this comment: https://github.com/mathoudebine/turing-smart-screen-python/issues/99#issuecomment-1825394507
Below DAY is shown the "current" weekday as static text: "Wednesday" (would be FORMAT: "EEEE").
(Note: I don't know Python, but was able to modify the simulator to use the current date. Everything else are the STATIC values.)
Environment:
- Revision of this project: Release 3.3.4
- OS with version: Kubuntu 22.04
- Python version: 3.10.12
- Hardware: Simulator (AMD FX-8350)
Additional context
This would open a lot of theme formatting flexibility.
Based on the errors I've seen playing with the Babel date formatting, each custom DATE entry would probably need to declare whether it instantiates a datetime.time or datetime.date object internally, i.e
OBJECT: date # date (day/week/month/year, etc) / time (hour/minute/second, etc)
Thus, the DATE entry I faked in the screenshot above could be achieved via:
DATE:
WKDAY:locale
TEXT:
OBJECT: date
FORMAT: "EEEE"
SHOW: True
X: 40
Y: 75
FONT: simply-mono/SimplyMono-Bold.ttf
FONT_SIZE: 32
FONT_COLOR: 204, 0, 0
BACKGROUND_IMAGE: background_grid_color.png
Contributor 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.
Research direction
The issue names no files or tests. Start by tracing the existing DAY and HOUR date/time stats and the custom-stats path described in the request, then verify that an added date entry can format weekday and other date/time values without breaking existing themes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100