Fritz Lekschas
Fritz Lekschas
As we did in HiPiler, there should be an option to limit the number of previews we're showing. This can either be done by simply not showing more than `x`...
Currently, the main thread is blocked as the items are rendered. This can be troublesome especially when piling.js is used in another library. We should instead move the item rendering...
Currently `pile.js` is relying on a number of pointer events but as soon as we display more than 1.5K instances the performance really drops. On the other hand, the spatial...
The more `PIXI.Graphics` objects we use the worse our performance gets. So let's reduce the number of graphics objects! Some easy ones that can be removed: 1. `image-with-background.js` doesn't need...
To allow visitors to play with the piling library on a lower level, there should be an option to directly adjust the code. Ideally, the code editor is integrated into...
This is related to #46 and #47 Once we can import/export the piling config and we have defined the properties of the piling config we can easily build a UI...
This issue is related to #46 Once we are able to import/export the piling configuration, we should define a JSON schema to describe the piling configurations. We can use this...
The piling configuration is a subset of the entire state. The idea is that one can export and save just the configuration for later reuse with different datasets. Similar to...
The context menu operations are currently implemented in a pretty procedural fashion. I.e., instead of a function called `hideContextMenu()` there are several duplicated calls to query for the menu's dom...
Currently, we only allow the user to choose between SKLearn classifiers and enforce the initialization of a new classifier. (See https://github.com/Novartis/peax/blob/develop/server/classifier.py#L104) It should also be possible to start with an...