Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
It now only need be a name that does not contain a comma.
|
|
|
|
|
|
This update triggered cascading map ID changes. This system needs
rewriting to handle automatic adjustment of map IDs.
Perhaps the logging format should be changed to log the stable ID?
|
|
This handles funky newlines and trims trailing junk, albeit in a not
particularly elegant way.
|
|
Second range parameter is exclusive
|
|
Rarely, 24 hour blocks will still contain undefined records.
These are infrequent enough to not impede overall analysis (you can use
mv.heap.def.filterAll(); dc.redrawAll() to confirm), but when loading in
multiple datasets, can have a substantial number of records occurring
before them.
This should become a non-issue again when the scrubber keeps track of state
outside of the logs being collated.
|
|
|
|
This also adjusts the method for comparing filters, allowing a chart to
define a "filterCompare" method that will be used to compare filters if
available.
This finally removes the date chart special case for setting filters.
Array instance checking will now use foo instanceof Array instead of
typeof(foo) == "array", which was unreliable (sometimes it's "object").
Trellis chart brush containers will now redraw the brush when set
externally.
renderBrush no longer takes brushG as a parameter. I'm not sure what I
was thinking when I made it so.
The deselected area will not yet fade.
The trellis chart still requires substantial refactoring and consistency
fixes; I'm not sure that the parameter specifications are currently
correct.
|
|
|
|
No broadcasting functionality yet.
|
|
d3.select(this) is wasteful and not always reliable
|
|
Deselecting areas, applying filters, and broadcasting filters are not
implemented yet.
|
|
Before, if you were quick or your connection was slow, you could select the
files before mv.init registers the callback.
This left things stuck, either requiring another set of files to be
selected, or a refresh of the page.
This closes #18.
|
|
|
|
|
|
mv.loader.use takes an array of URLs, which are fetched via d3.xhr.
This also restructures mv.loader to refactor out some shared functionality
between mv.loader.use and the file selector change events.
mv.loader could still use some cleanup.
http://css-tricks.com/examples/ButtonMaker/ makes a pretty neat css button.
Hopefully, it's visually attractive enough so people in a hurry know where
to go. :)
|
|
Upstream merge on exposing xhr.responseType pending.
|
|
|
|
The inner loader closure was redundant. Apparently I really like closures
during late night coding.
main.js should no longer have to deal with raw loading events; only UI
specific callbacks.
|
|
Also remove a stray curly brace
|
|
.zip must be at the end of the file name.
Progress bars are not fully descriptive in this mode yet
This also alters the mv.loader interface.
The onprogress callback now takes current and total.
The each callback is now passed an after parameter, to be called when it's
done.
|
|
|
|
This should all be done by delta updates.
d3 joins, while fun, aren't really the tool for the job here. :)
|
|
|
|
|
|
|
|
Previously, you could still click on the (fully transparent) pieces.
|
|
|
|
This should hopefully make things apply more cleanly for reconnections and
fallbacks.
|
|
This is by no means even close to comprehensive (legacy compatability for
determining browser width is a total mess in and of itself).
However, this is enough for manavis to work on recent versions of Firefox.
It's not quite as fast as chromium, but it is entirely workable.
Older versions aren't really worth testing, as the entire application is very
js intensive.
|
|
|
|
Easier to make things easily parseable now than have to deal with logs later.
|
|
|
|
Active filters will only be applied from users in the same channel.
This closes #14.
|
|
It was previously very hard (impossible?) to select upper values.
|
|
|
|
Also filter KILLXP by default.
This closes #16.
|
|
|
|
|
|
Sort the pie chart the other way.
Still doesn't feel right. Perhaps a bar chart would be better.
|
|
|
|
|