There is a lot of logging going on, perhaps add an option to disable the logging.

A saved story containing scenes with multiple images will only show one image in IE/Edge/Firefox. Haven't tested yet in Safari. The correct behavior occurs in Chrome.

(Alternative to issue #37)

configure # columns in faceted and segmented radial or spiral timelines (currently automatic, not configurable), which in turn affects the number of rows.

Updating the number of facet columns could update the radius of the facets.

Initially: GLOBAL STYLE CONFIGURATION OPTIONS for annotations, captions, images, axes: font, font color, annotation dropline style / visibility; style options must be saved along with a story.

Eventually: LOCAL STYLE CHANGES to individual annotations, captions, images, axis ticks, axis domains, axis labels

Trigger the filter dialog with a filter control in the legend, filter controls next to facet labels, segment labels, chronological axis ticks.

Selecting a new color from the legend color swatch no longer updates the color of events of that category.

This seems to occur more often when filtering

Repro:

• Load AI dataset
• Change to Radial View
• Filter to 1600 (Hide mode)

Given timeline dataset characteristics such as the presence and number of facets, segment granularity, number and distribution of events, number of event categories, recommend combinations of timeline representation, scale, and layout.

A couple of problems with the current implementation:

• If you embed an image from a server that has CORS disabled, then it has issues saving the scene thumbnails.
• If you embed the image using data uris, then a large image can cause the app to become horribly slow.

Interactively add and/or edit an event via a UI dialog by specifying its start/end dates, category, facet, and content text. Conversely, delete individual events. Re-scale if necessary.

Some but not all radial image annotations are letterboxed (cropped vertically) in MS Edge. It could be a image file format issue (PND / JPG?)

Visually indicate scenes in the scene selector that contain annotations: labels, captions, and images.

UI controls for re-ordering the facets (currently facets are ordered alphabetically); this could be done via drag and drop; this ordering would need to be preserved in saved story metadata or in the scene metadata should a story contain more than one facet ordering.

Add (and style) arrows, rectangles, ellipses, lines, freeform pen strokes to timeline scenes

Auto-scroll-to-top happens already if the representation changes across scenes; but if the changes are only annotation / highlighting, no scrolling occurs

There is not enough room to draw curves.

Export read-only interactive slideshow version of saved story for embedding elsewhere on the web: wrap HTML, JS, CSS into iframe or archive

Add a UI element for configuring the size of the radial representation radius; this affects the number of facet and segment columns; this configuration must be saved along with a scene

Segment timeline by different granularities of time (millenia / century / decade / year / month / week / day / hour), within the extent of the dataset, minimum granularity of events, and with some upper bound on the number of segments.

Reclaim space under design space menu options (representations, scales, layouts) by moving hint text into laterally adjacent tooltips.

Within the same timeline scene, annotations (event labels, scene captions, images) may appear in a different z-order from how they were recorded, resulting in undesired occlusion.

Staged animation as it is done currently sometimes results in inconsistent behaviour: events (dis)appearing, scaling, positioning, etc.

Integrate data import and curation pipeline from TimeLineCurator: specify a text document or website, use NLP (e.g., TimeLineCurator uses TERNIP library) to extract events. Allow the author to curate / correct event dates + text and deal with "vague dates" (underspecified temporal references).

the legend should listen to the current filter settings and update to show visible categories only, when using the 'remove' filter mode

• Load some data
• Click on an event to show the annotation
• Record Scene
• Drag the annotation around
• Record Scene
• Go back to the first scene, notice that the original position of the annotation was not restored, but the last position it was in after it was dragged.

Title scenes ("slides") could appear between timeline scenes; currently, these are created by filtering out everything and appropriating captions to the empty canvas

i.e., by showing palette icon (https://thenounproject.com/term/paint-palette/550286/) or similar icon next to legend item

UI controls for configuring timeline orientation.

For linear timelines (currently earlier-to-recent corresponds to left-to-right): top-to-bottom, bottom-to-top, right-to-left (helpful for users whose written language is read right-to-left)

For radial timelines (currently earlier-to-recent proceeds clockwise): counter-clockwise

For spiral timelines (currently earlier-to recent proceeds outwards from center): inwards to center

If you've clicked on a color, the legend pops up. However, if you click on the canvas or anywhere else the legend does not autohide.

Add semi-transparent background rect element to scrolling linear representation upper axis; if possible, draw in front of annotations too

Undo and redo for every interaction / UI state change (currently nonexistent; unrecorded changes to the current state are lost on scene change).

DISTINCTION b/w SCENE-IN-PROGRESS vs. SAVED SCENE: if UNDO / REDO is insufficient, a visual indication of an unsaved in-progress scene vs. previously saved scenes; if editing a previously saved scene, add option to UPDATE or APPEND edits to saved scene; SAVED EDITS TO EXISTING SAVED STORY IN BACKGROUND: verify if this is possible in all browsers

Display minimal yet immediate visual feedback during data or story load / transitions / image import (i.e., pinwheel / wait cursor)

Consecutive events with equal duration are assigned to higher tracks in some facets but not others (vertical tracks for linear representations, concentric tracks for radial representations).

Image annotations should have UI controls for z-order and alpha/opacity, such that images can appear behind the timeline(s); the z-order and alpha values of images must be saved in scene metadata

Currently, images can be 'sent to back' by clicking them while holding the SHIFT modifier key; however, this z-order is not preserved when replaying the scene

Currently, curve is drawn all at once; ideally, events should be control points on the curve and it should be possible for a user to drag them around and edit the curve shape;

inspiration / possible solution: SDCurve.js https://github.com/rpusch/sdcurve.js/

current GIF export does not include animated transitions; implementing a GIF / video export with the animated transitions will require scene + transition timing controls for each scene and transition to be exposed in UI

Assign and re-assign nominal / categorical attributes to the category (color) or facet scales, redraw the timeline(s) upon reassignment.

Hide scene selector by default in playback mode; show scene selector on demand instead; show "scene N of M" label when scene selector is hidden.

(alternative to issue #36)

The radius is currently adjusted automatically given the window/main_svg dimensions, the number of tracks, (and the number of facet or segment columns in the case of faceted / segmented layouts).

The radius could be manipulated directly by clicking and dragging on a control point at the center of a radial timeline. Changing the radius of a single facet should update all facets in sync. This will in turn affect the number of facet rows and columns.

A global minimum and maximum radius would need to be specified based upon the resolution.

• Select Filter, then select the Hide mode
• Click on some category
• CTRL + click on that same category
• Select the "Linear" or "Radial" representation

UI control for re-ordering saved scenes in a story, such as via drag-and-drop within the scene selector.

Via @sqljason, June 19 2017

There is a use case for automatically annotating all non-filtered events.

This would need to take several parameters into consideration: the canvas dimensions, the current representation (linear vs. radial vs. other), the number of events, and the length of every event annotation.

Given all of this, we would try to optimize the placement of all the annotations to prevent any from overlapping with each other, the events, or the axes.

Provide visual indication of animated transitions between representations, scales, and layouts in the scene selector and indicate whether any particular transition is potentially jarring or ill-advised; recommend insertion of interim scenes with helpful transitions to guide the viewer