Feat/visuals/first
By sjmarshy

![screen shot 2014-08-25 at 20 47 47](http://ift.tt/1pz0Wti)

August 25, 2014 at 8:49PM
via GitHub http://ift.tt/1nuU3UV

Feat/visuals/first
By sjmarshy

![screen shot 2014-08-25 at 20 47 47](http://ift.tt/YVQGBd)

August 25, 2014 at 8:48PM
via GitHub http://ift.tt/1tCwOgw

Rel/0.3
By sjmarshy

Huge levels of refactoring, involving splitting a lot of the functionality off into their own classes, rewriting how the program handles tags and changing the entire API. The tags were previously parsed in an overly complex and fragile way, whereas now they are simply stored as arrays of strings, simply splitting on colons to break them down into their hierarchies. This turns out to be a hell of a lot easier to deal with, and means a lot of the processing is super simple to write in comparison to what it was like. in short, this brings us far closer to being able to visually display information to the user - in fact, that’s the next step.

August 21, 2014 at 7:49PM
via GitHub http://ift.tt/1nfByUn

Feat/api/tree
By sjmarshy

add api methods to view the tree of your time-tags.

August 18, 2014 at 11:16PM
via GitHub http://ift.tt/1me3xU8

Feat/api/today
By sjmarshy

add api endpoint to enable easy retrieval of time tags associated with midnight of the current day onwards.

August 18, 2014 at 8:24PM
via GitHub http://ift.tt/1p6ZVIA

refactor(everything):
By sjmarshy

index: * formatting: moved Class dependencies into a logical order * formatting: add comments * refactor: remove “most popular” functions, require new Tags Class tags: * create new Class Tags to handle information about all of the tags collected so far api: * change args for init function, swap logfile for Tags instance * remove all previous endpoints, did a large refactor of how tags are handled. removed: * GET /api/tags * GET /api/tags/popularity * GET /api/tags/detail * GET /api/tags/flat * GET /api/tags/flat/raw * add GET /api/tag/:name retrieve the timeseries data for named tag logfile: * moved methods related to tag manipulation to ‘Tags’ due to separate concerns * extend Logfile class from EventEmitter and add two Events: * ‘read’ - emitted on construction once the logfile passed has been read, passes the Object retrieved from the logfile * ‘ping’ - emitted when new information is added to the logfile, passes the time and the plain string tags. record: * remove heavy parsing of tags, instead store them as an array of plain strings * add doesContainTag method, should quickly see if record contains a simple string * removed getTags method, just access #tags man BREAKING CHANGES: quite a lot here - api: none of the API methods are the same, changed them entirely. tags: new class logfile: remove all methods related to tag manipulation, simply reads from and writes to logfile now record: stores tags in entirely new way

August 18, 2014 at 7:31PM
via GitHub http://ift.tt/1BuqGM5

type-lover:

Trip Journal
by Rui Hao

archive older ›
Silly name, serious subject. Design is awesome, and this blog is a celebration of that fact.
Unless otherwise stated, the images on this blog do not belong to me, and every effort will be made to ensure that the source is easily locatable.
Ask
theme by Robin Wragg