timescale.info
Sign inSign up

How OpenChronology was built

Every merged pull request of openchronology/timeline-app, its first week of commits and its releases; and before them the 2020 PureScript editor, from snapshots of its deleted repositories in the Wayback Machine. Written to this server through the HTTP API.

327 moments · 2020-03-09T00:15:08Z CE – 2026-11-02T20:11:21Z CE · by @athan · @athan

Issue #37 · Only facilitate LocalStorage at the top-level

  • 2020 editor
  • issue

The only Signal that should be remembered (stored) in a session, is the one that basically backs-up the entire page data (except for navigation; that's encoded in the URL) - this would be the top-level parent signal, which would be an analogue to Timeline.Data (TimeSpaceDecided), but from a user-interface perspective (consideration for zoom level, etc.) The biggest consideration is, what constitutes the difference between user-interface-only data, and document-data? *Archived by the Wayback Machine on 15 September 2020; the repository has since been deleted from GitHub.*

Sources

Open Issue #37 · Only facilitate LocalStorage at the top-level in the timeline