timescale.infoIssue #19 · Time Index semantics
- 2020 editor
- issue
There will be three primary different versions of a time index: - Human Readable - presented as a String in the primary user interface, while editing it, it may be any version of an ADT - a date picker may be used, for instance; yet, while presented on a timeline and hovered with a "mouse over", alternate text may have a form of "March 15th, 2020", etc. - Stored - this is the version that's encoded in the .och files and share link - usually just a Number or Integer (or series of integers for a date) - this aims to take the least amount of memory as possible, while still sustaining an isomorphism between Stored and Human Readable. - Position - this is the value that's annotated in the actual user interface, which will be in SVG. The value itself will be relative to the value of the surrounding viewport, but there is a close relation between Position and Stored - if the Stored value is only a Byte, then the viewport will have a x width of 256, and the Position of some event is that stored value. *Archived by the Wayback Machine on 15 September 2020; the repository has since been deleted from GitHub.*