Standalone JS pkg

[manzt]

The custom DataTable Mosaic client should be published to npm and usable without the Python-based db.

[timelyportfolio]

@manzt Absolutely loving quak and would really like to see it available as a standalone JS package. If you pursue this option, would it be possible to add an option filterBy similar to mosaic/vgplot so that we can tie together DataTable with mosaic inputs? Here is a really, really ugly example (please excuse my foolish ignorance of Typescript and lots of other things) https://stackblitz.com/~/github.com/timelyportfolio/quak.

[domoritz]

In other words, make quak a mosaic component that satisfies the component interface?

[timelyportfolio]

@domoritz yes, would be a really nice addition to the components.

[timelyportfolio]

And while I originally was only thinking the DataTable it would also be even nicer if each of the filters in the column headings would be available as input components. Not sure how much of a lift this would be. I am happy to help, but you can probably already see some of my limitations by the example.

[manzt]

Yes! This is my intention. I think DataTable fits the definition of a "Mosaic component" (it extends from MosaicClient). Right now you could access the filterBy with:

import { coordinator } from "@uwdata/mosaic-core";
import { datatable } from "./lib/clients/DataTable.ts";

// setup df table in database...

const dt = await datatable("df", { coordinator: coordinator() });
const filterBy = dt.filterBy; // use with other clients

Originally I'd had this lifted up one level, where you could create and pass in the crossfilter selection (filterBy) yourself, but I don't see much of a difference between the APIs (and also potential to pass in a Selection that wasn't a crossfilter felt like a poor API design). Open to reverting to:

import { coordinator, Selection } from "@uwdata/mosaic-core";
import { datatable } from "./lib/clients/DataTable.ts";

// setup df table in database...
const filterBy = Selection.crossfilter();
const dt = await datatable("df", { coordinator: coordinator(), filterBy: filterBy });

if there are things I'm missing!

Just want to setup a minimal, public API to make the JS release in a way that interfaces very well with the rest of the mosaic ecosystem.

[manzt]

Here is a really, really ugly example (please excuse my foolish ignorance of Typescript and lots of other things) stackblitz.com/~/github.com/timelyportfolio/quak.

wow, totally love that we can share (low-friction) ideas with stackblitz this way. new to me, thanks for sharing, @timelyportfolio :)