Open will-moore opened 6 years ago
@will-moore we probably need a longer discussion on when and how to use the crossfilter. It's a great tool but has few limits. E.g. looking at dimensions: https://github.com/square/crossfilter/wiki/API-Reference#dimension: Creating more than 8 dimensions, and more than 16 dimensions, introduces additional overhead. More than 32 dimensions at once is not currently supported, but dimensions may be disposed of using dimension.dispose to make room for new dimensions...
. Do we actually need more than 32 dimensions? Probably not, but that's a thing to take into consideration.
For dc.js we would have to build a user interface to actually do the plotting. We could in principle remove existing plot and add a dc.js plot instead. I have not tried, and do not know if possible, to connect dc.js to existing crossfilter yet. The benefit of doing it would be of course the fact that the plot selection would also filter the data on the grid and in the table. Happy to discuss further.
Been working with crossfilter on a prototype at https://github.com/will-moore/parade-crossfilter and it's looking good in many ways. Still a few questions to work out. Would be good to give a demo and discuss sometime.
Demo video of the "parade-crossfilter" app is at https://youtu.be/FyjGhZxx6es Feedback appreciated!
Having had a look at the crossfilter docs, some thoughts on what adoption of crossfilter might give us:
Current issues:
eval()
for filter functionsCrossfilter provides lots of nice features, but how would it fit into parade?
eval()
functionality, and we simply use 'dataprovider' to load a table (all, or selected columns), which is what crossfilter expects.dimensions
to filter by. Less-than, greater-than, equal or range for numerical columns, equal/contains for string columns.cc @chris-allan @emilroz