Antoine Beyeler

I gave it a look. It's very easy watch, e.g., all Python files that are located in the same directory as the sketch file. The actual reloading is trickier. You...

Alternatively, we could add some optional API to the sketch class, like a list of additional files to watch/reload, or a flag to opt-in to watch/reload all python files in...

Yes. In terms of Jeremy's new proposal, to me it make sense to see the tombstone in the "raw" data (e.g. where each row corresponds to a log event), because...

> I'd like a repro for this ```rust use eframe::egui; fn main() -> eframe::Result { env_logger::init(); // Log to stderr (if you run with `RUST_LOG=debug`). let options = eframe::NativeOptions {...

> There are three alternatives: > * Round widgets to physical pixels > * Round widgets to logical ui points > * Only round when `pixels_per_point` is an integer >...

A possible avenue might be to split the tile download/cache part from the rendering part, and make the former optionally swappable by a custom implementation.

What you're seeing is basically the axis label slightly overlapping the tensor. That label disappears on hover, thus the dynamic behaviour. The root cause is that this label is cropped...

@tfoldi First, thanks again for your contribution, and for putting up with our slow responses so far. With 0.19 out and the huge push on the dataframe and video fronts,...

I just discussed the data model aspect of this PR with @jleibs and we reached the following decision. We introduce a new `GeoPoints` archetype as per this outline: ``` table...

> > For the scope of this PR, the recommended/optional components should be included only so long as they are actually supported by the view. If they are not, then...