Mark Keller

> I've commented on this in various places but I think this requires some discussion. That being said, this is not part of the core so it's not a huge...

> Maybe it makes sense to allow the config to be some sort of complicated, extremely well-specified thing that is somewhat unreadable because people should be using API's to make...

Another thing to consider is that even if we decide to implement convenience functions at the object-oriented API level (rather than the JSON level) **initially**, it doesn't prevent us from...

The issue arises when a consumer app (i.e. the HuBMAP portal) tries to load HiGlass via Vitessce. The `import('higlass')` statement causes the webpack build to have an additional file `9.min.js`...

I did have success using this branch to dynamically load HiGlass in the HuBMAP data portal by adding a higlass component to a view config at http://localhost:5001/preview/cell-type-annotations ```sh npm install...

Thanks for looking into the issue in Jupyter. A single-chunk build for Jupyter means no dynamic importing there, right? If so, it feels like removing a feature since we currently...

I had a chance to try the unpkg import for Gosling (http://localhost:3000/?dataset=just-higlass on branch [keller-mark/gosling-test](https://github.com/vitessce/vitessce/blob/keller-mark/gosling-test/src/components/higlass/HiGlassLazy.js#L26)), basically by switching out the HiGlass bundle URL for a Gosling one. It works for...

> the limitation with dynamic loading is due to how vitessce is consumed/bundled by jupyter labextension build, but dynamic imports work in other contexts/bundlers That makes sense, but I worry...

Look into https://anndata.readthedocs.io/en/latest/anndata.experimental.AnnCollection.html#anndata.experimental.AnnCollection

Related to #754