Kanit Wongsuphasawat

Yeah we should make boxplot respect `mark.invalid` - If `mark.invalid` is `null` the current behavior is correct. - If `mark.invalid` is `filter` (default), we should filter. (But right now filter...

We have geographic in the roadmap, but it won't be included in 2.0. Tree map is way more complicated and I don't think we will have it soon.

An interesting question to think is "whether visual transforms do or do not complicate interactive selection". (I don't think we should implement complex layout transform like force, treemap, wordcloud now...

Another interesting point that layout are like projection in a few ways: 1. They take some fields as input and implicitly affect some encoding output. 2. They act like multi-dimensional...

Note that while this "layout" concept is not critical for implementing, we need to think this through a bit as we may want to use the keyword "layout" for composition...

Another thought -- for wordcloud and treemap, they could even have their own composite mark. However, I don't know if we should do that given there are other layouts like...

I don't think layout should be combined with `size` encoding as they are two distinct concepts. Moreover, there are also layouts like `force` that aren't directly related to size.

> I wonder whether there is a way to get filled circles of radius 1 for the smallest circles instead of hollow circles. Yes, you can add production rule, instead...

Just test if the size field is too small (need some epsilon constant), then apply different size, fill, stroke instead.

Idea: You can even set the color to be different color for non-positive number, if color/fill/stroke is not set. (This is a bit more controversial so I'm not 100% sure...