Trevor Manz

I'm compiling a list of TODOs for the new documentation. The `hg` API should support most of these features, but I think that something like the `FUSE` API should be...

@pkerpedjiev what would it take to tell higlass fronted to use a different `DataFetcher` for certain tracks? (from a viewConfig perspective).

In short, for "local" tilesets, rather than starting a background thread and temporary web-server, we reuse the Jupyter comm for displaying the widget to also send/receive requests for tiles. No...

Ideally we could just extend `DataFetcher` from HiGlass, but its logic is so coupled to `fetch`. Here's the general idea. ```js import hglib from "https://esm.sh/[email protected]?deps=react@17,react-dom@17,pixi.js@6"; window.higlassDataFetchersByType = window.higlassDataFetchersByType || {};...

> There's a function which switches datafetchers based on the type property in the data config. Yup, exactly!

Kind of curious if we should move the `fuse` stuff under something like `experimental`. It would be really great to have this sorted out before a v1, but I anticipate...

Ran into this today... glad to find this issue!

Just agreeing with what's already been stated here. Certainly possible to add to current implementations, but fewer `F`-order arrays "in the wild" haven't made this less of a priority to...

> The Zarr data can be served via an API, with the chunks generated on demand. Xpublish is an example of this. Yes, instead of converting each `tile` to a...

> I now @kylebarron has looked into zarr a bit but seems to have found existing resources (data and/or software) to be lacking or not properly oriented to his application....