saul / gamevis Goto Github PK

Currently the build:js Gulp task always watches, regardless of whether it was called from the watch task.

For filtering, only = constraint is implemented. Implement the other constraints.

A timeline visualisation should be added with the following features:

• Support multiple sessions within a single visualisation
• Slider representing time within the game, allowing the user to 'scrub' through game time
• Events should be able to be visualised on the slider (e.g., round_start). The events to be shown on the slider should be user selectable.
• Spatial events should be able to be plotted on the overview (as connected lines)
• Spatial events should be able to be plotted on the overview (as disparate points)

Transactions should be used so errors occurring during import don't leave the database in an inconsistent state.

These configurations should detail:

• Common entity properties used for filtering, perhaps with user-friendly strings

There is a significant performance issue when performing SQL queries with a large number of results.

Although the query itself takes only 500ms, it takes JS 5 seconds.

I believe there are also additional performance issues with adding many thousands of elements to an array of objects. Vue.js is trying to observe them all when it's not necessary.

Currently very user 'unfriendly' to have to remember event variable names/properties.

Consider using selectize for a more intuitive control for filtering entity props/event variables.

This will allow us to not assume the tickrate (which I believe is different between CS:GO and Dota 2)

Connection strings are currently hard-coded, and should be configurable through either a JSON config file or being persisted by the Electron app.

Ctrl-1 through 9 should jump to absolute tab
Ctrl-Shift-[ and Ctrl-Shift-] should shift relative tab

Some entities (such as hegrenade_detonate) have multiple entities associated with them (thrower and grenade). It should be possible to select which entity you wish to plot.

Integration may be difficult due to the WebGL heatmap library requiring a WebGL context (whereas the timeline visualisations use a 2d context).

Blocked by #13