Age | Commit message (Collapse) | Author | Files | Lines |
|
This closes #4.
|
|
|
|
This closes #2.
|
|
|
|
Also set a sane maximum bubble size.
Previously, it operated on a logarithmic scale, which meant some bubbles
weren't being given their due weight.
Thanks to Nard for the suggestion!
|
|
This closes #10.
|
|
This closes #11
|
|
|
|
This should now be implemented efficiently enough for everything else to
still work.
This currently does not allow filtering, but the dimensions are prepared in
a manner that makes this a simple addition.
|
|
|
|
File loading is an asynchronous operation anyway, this is unnecessary.
|
|
They should now only display after files are selected and the loading starts,
where there is something to display.
|
|
There are five modules, as follows:
load.js handles initialisation and management of files
parse.js handles initialisation and management of records
heap.js handles initialisation and management of dimensions
chart.js handles initialisation and management of charts
main.js manages the other modules and status
Status and file loading have been decoupled; file loading no longer directly
updates the status of the progress bars.
This makes the limitations of the current status system more apparent, and
should make the system also easier to maintain, as progress bars are now
updated at more logical times.
The parser remains mostly unchanged. It will need to be altered into a full
stateful parser, but this can happen later.
Dimension management is now simplified, due to the addition of monoGroup.
Most dimension/groups consisted of a single dimension and a group reduced by
count. This convenience function combines these and unifies their access,
beyond mere naming convention.
Charting management is also greatly simplified, adding in chain helpers to
categorise types of charts, by aspects such as being wide, being thin,
being short, as well as helpers to establish common properties for bar and
pie charts. There is now also a helper to take advantage of the unified
monoGroup accessors.
|
|
|
|
This gets rid of a lot of repetition.
|
|
Combat data is stateful. The parser will require rewriting to complete.
|
|
This closes #003.
|
|
|
|
|
|
|
|
This fixes #001.
|
|
|
|
|
|
|
|
|