I added text first and then I drag second text into the canvas. Should it be offset from the first one to aid selection?

Drag a new text mark and you cannot edit its text property automatically!

Unfortunately, this is a limitation in Vega (axes don't register events). Perhaps we can ping @jheer to add this to Vega. Or, in the worst case, come up with a workaround in the iVis.

I’m not sure if this is a bug or my misunderstanding.

With rundown dataset, I facet data by title.
Then I add a text mark and drag title to its text value.
Somehow it only shows “undefined”.

If I drag title to the text, it works just fine.

Similar to #27 but for pipeline properties

Comments from group meeting indicated that the resize boxes weren't enough of a visual cue to see which mark was currently selected.

The spacing makes me thought that 1-20 of 60 and the arrow are a part of the extend panel.

Users will be unsure about what to put in the text boxes.

After I remove “medal_type” from fill color, the color becomes black on the panel but the marks become transparent.

Afterward, I change fill color to other and marks are correctly colored.

Medals dataset. Group by country. Sort by median count. The sort by gets added before the group by which breaks everything.

Once we have the ability to reimport Lyra states, it should be fairly trivial to save an array of states and then "replay" them. It's a story!

I don't think we need to spend any time on the UI for building out these stories, but there are definitely UI considerations for playing the stories back.

We should be able to drag data fields onto the visualization to add a "group by" data transformation. Perhaps dropzones around the current selected layer for vertical/horizontal/layered layouts?

We already have an export() method which dumps out the current state of Lyra as JSON. We should be able to import this state back in.

E.g. width sliders should display text output for the particular value of the slider currently set.

Put this off as long as possible. But adding features for #17 introduced a number of show-stopping regressions. This is not good.

To make clearer what group injection is doing, have it add a group mark under the current layer, rather than doing everything through callbacks. We'll likely want to make this group mark more constrained (e.g. not being able to change the pipeline, or apply a visual transformation?).

To hide things, sometimes you set width to 0, sometimes you check a box, sometimes you set colours to white. Standardize this.

Unlike Mac’s finder, clicking on text bubble in vde doesn’t select it.

Also, with openhand cursor, people will expect to drag it.

Uncaught TypeError: Cannot read property 'type' of undefined vega-1.3.3.js:5432
axis_def vega-1.3.3.js:5432
axis.def vega-1.3.3.js:5404
(anonymous function) vega-1.3.3.js:5212
encodeGroup vega-1.3.3.js:5211
encode vega-1.3.3.js:5177
encodeGroup vega-1.3.3.js:5221
encode vega-1.3.3.js:5177
encodeGroup vega-1.3.3.js:5221
encode vega-1.3.3.js:5177
main vega-1.3.3.js:5155
vg.Model.prototype.encode vega-1.3.3.js:6429
vg.View.prototype.update vega-1.3.3.js:6647
(anonymous function) Vis.js:104
(anonymous function) vega-1.3.3.js:4643

I was changing many item on the screen and I made a mistake and click undo. Then all my work disappears and Uncaught TypeError is shown in the console.

If I encounter this again, I will provide more steps about what I did.

Drag-and-drop to rearrange pipeline items, like marks/layers.

It’s faster than clicking group and move mouse back to field name and drag those back.

As pointed out in meeting, we typically want most precision/steps at low widths, and less so at high widths.

If you switch to a horizontal/vertical layout, there's literally no way to go back to an overlap.

• Use SASS/LESS
• Tighten property inspectors
• Fix "accordion" of marks. Perhaps animation? Or split tree listing + properties inspector?

User might not know that there are multiple lines.

Can't scroll group by tabs.

Put some padding inside this rounded text box.

Right now, you can only delete items in the pipeline. You should be able to toggle them to temporarily disable them.

Not being able to drag them is fine. But we should be able to aggregate, or, in the worst case, hide the onhover dropdown.

TypeError: Cannot call method 'indexOf' of undefined
    at https://courses.cs.washington.edu/courses/cse512/14wi/vde/src/js/vis/marks/Rect.js:134:27
    at Object.Scope.$eval (https://courses.cs.washington.edu/courses/cse512/14wi/vde/src/js/lib/angular-1.1.5.js:8926:28)
    at Object.Scope.$apply (https://courses.cs.washington.edu/courses/cse512/14wi/vde/src/js/lib/angular-1.1.5.js:9006:23)
    at Object.mousemove (https://courses.cs.washington.edu/courses/cse512/14wi/vde/src/js/vis/marks/Rect.js:133:26)
    at HTMLCanvasElement.<anonymous> (https://courses.cs.washington.edu/courses/cse512/14wi/vde/src/js/vis/iVis.js:110:64)
    at HTMLCanvasElement.__onmousemove (https://courses.cs.washington.edu/courses/cse512/14wi/vde/src/js/lib/d3.v3.min.js:1:4531) angular-1.1.5.js:6349

I drag rectangle, hoping to move it then I see these in my console.

Medals dataset. Group by Country_Code. Filter by "key == 'USA'" and you have a hang.

Another one: filter by "mean(Count) > 35" and hang. Incidentally, "mean(Count) > 25" and others work fine... So perhaps it when we filter out all groups/data?

In this screenshot, we can click on “Key”, “Medal Type”, or “Count" to show properties panel for each axis but there is no way to minimize the panel yet. This can be annoying for small screens.

Maybe there should be a minimize button or we just make the axes title act as show/hide toggle button.

I think if we have undo full functional, we don’t need this alert for removing item anymore.

Perhaps we want to rewrite the data table using our own library since we're really pushing dataTables beyond what it was meant to be doing.

If I understand correctly, the only way to do this right now is to delete the transform and recreate group-by with the column we want.

(It’s bouncing a bit)

Adding a formula transform that uses aggregation produces an "output" field. This is not ideal.

I think clicking the arrow should collapse the panel.

This might help the authoring flow a bit. (So user don’t have to drag mark to the canvas once and then drag variable for one more time.

@arvind what do you think?

There are two possible solutions I think of right now

a) tooltips
b) allow users to resize column

Once a value has been added to the range in the scale popup panel, there is no way to remove it.