circagraph
Sign inSign up

openchronology/timeline-app on GitHub

The OpenChronology repository on GitHub, mirrored by och-import-github: issues and pull requests as durations (ongoing while open), what happened to them as moments, plus releases, milestones, commits and branches. The Branches view shows the most recently active branches each in a track of its own.

Source: https://github.com/openchronology/timeline-app

3,131 moments · 2026-10-05 CE 20:21:49 UTC – 2026-11-16 CE 12:10:45 UTC · by @athan · @athan

Hold ongoing durations in desktop files, ending at the app's clock

  • github
  • github/openchronology/timeline-app
  • commit
  • main
  • github/athanclark

The SQLite store (and och-convert) keeps an ongoing end (#537) as neither a time nor a moment. Files written before this required one; the first ongoing duration saved into one copies its durations table into one that allows it. The interval tree holds an ongoing duration as a point at its start, like the server's, and a starting end is refused, as is an ongoing end on a timeline without the Gregorian display. The desktop app passes its clock as `now` with each query. Lists and pages of durations read the intervals with ongoing ones resolved in SQL, so their filters, order and offsets are exact; a window returns the ongoing durations resolved, and the app merges them with frameWithOngoing. That function now also answers the server's windows, replacing its own merge, so both stores share one: it takes each placeholder out of the summary holding its start and adds the resolved band or summary. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/commit/f760d58c37ef1c5bcaf96a4fa305df6915429362

Related

Open Hold ongoing durations in desktop files, ending at the app's clock in the timeline

Hold ongoing durations in desktop files, ending at the…