Increase coloring speed
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.1k
- Forks
- 233
- Avg merge
- 1h 44m
- Merged PRs (30d)
- 1
Description
Possible solution
Saving floating events in localized time (as configured by the user as local_timezone)
This means the floating time table needs to be rebuild when changing local_timezone (or we need to keep one table for each local timezone ever used).
The benefit will be that we can JOIN floating and localized tables when querying for events which will lead to properly sorted events.
Create a table with date-colors.
When not using all configured calendars, a table with the date colours would not be accurate though.
Check how other programs are doing this.
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
Start by measuring the current event-coloring and querying path, then review how floating events, localized times, local_timezone changes, and configured calendars affect the proposed tables. Compare approaches used by other calendar programs. Done means coloring is faster while date colors, sorting, and timezone changes remain accurate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, databases, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100