Skip to content
This repository has been archived by the owner on Nov 30, 2021. It is now read-only.

Investigate why some visualizations cannot be captured/restored #4

Open
thinkh opened this issue Mar 20, 2018 · 2 comments
Open

Investigate why some visualizations cannot be captured/restored #4

thinkh opened this issue Mar 20, 2018 · 2 comments
Labels
status: question Further information is requested

Comments

@thinkh
Copy link
Member

thinkh commented Mar 20, 2018

It seems that some examples, e.g. Reorderable Matrix, the visualization state cannot be captured and restored.

Hypothesis
Vega supports Group Marks, to support a Multi-Coordinated-View-like setup.

Group marks provide their own coordinate space and can include nested data, signal, scale, axis, legend, title and mark definitions.

The function view.getState() captures only signales and data attributes that are available at root level (and not at group level).

Hence, we need to define how to push the signal/data to the root level so that it can be captured and restored. This part must be described in the paper as well.

@thinkh thinkh added the status: question Further information is requested label Mar 20, 2018
@thinkh thinkh self-assigned this Mar 20, 2018
@mstreit
Copy link
Member

mstreit commented Mar 20, 2018

It makes it more complicated but it's an interesting aspect how we can handle MCV in VEGA.

@thinkh
Copy link
Member Author

thinkh commented Mar 21, 2018

Does not have a priority at the moment, since we decided to use an adapted Gapminder as example in the paper.

@thinkh thinkh removed their assignment Mar 27, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants