Switch LineUp dependency from next to version number

[thinkh]

Closes #603

Summary

• Switch lineupjs dependency from next to version number or github branch (see explanation in issue Switch LineUp dependency from next to version number #603)

• With PR Switch from node-sass to Dart Sass (sass) phovea/generator-phovea#439 we switched from node-sass to sass (Dart Sass) and we can now import LineUp Sass files again and also modify the Sass variables.
  

• Includes many new LineUp features:

  • Add option for html labels and summaries lineupjs/lineupjs#542: Breaking change: if you use any HTML in your column headers, you will need to use this new option instead
  • support categorical dynamic ordering lineupjs/lineupjs#533: Allows ordering of categories in categorical column.
  • improve dropzones lineupjs/lineupjs#534:
  • possible fix for npm install lineupjs/lineupjs#541: Allows npm install of github dep
  • selection indicator lineupjs/lineupjs#535: Selection indicator for overflowing rankings
  • Violin Chart lineupjs/lineupjs#520: New violin chart visualization
  • add tick vis, adjust lightness of bars vs ticks/dots lineupjs/lineupjs#514: Adjust tick visualization
  • Improve Selection Column lineupjs/lineupjs#513: Improve selection column
  • possible approach for lazy data domains lineupjs/lineupjs#512: Very important and breaking change: Allows for auto-infering data domains of columns --> for example, you now have to pass null or NaN for min/max in numerical columns, or undefined for categorical columns for this to take effect. This will require some changes @dvdanielamoitzi @dg-datavisyn (i.e. applications where this is done right now --> can be removed), @oltionchampari (i.e. scores, because the hacky infering is removed with this PR --> scores need to remove a proper min/max for example to infer it automatically).
  • optimize visualizations lineupjs/lineupjs#479: Vis improvements

[thinkh]

I still found a bug while testing. With PR lineupjs/lineupjs#480 text sanitation was introduced. The searchbox' formatItem() has changed. The last commit changes our format function accordingly. It also converts the … to the unicode pendant.

Before

After

[puehringer]

@anita-steiner Because lineupjs now supports github installs again (as seen in this build), should we use github installs again or should we use actual version numbers?
I think version numbers are to be preferred (given a fastish lineup release cycle), as a) lineup will not easily break our workspaces, and b) releases are easier as we don't need to change any versions.

[oltionchampari]

Has this been reported already? Resizing the columns does not work in ordino

Error message:

Edit: Created an issue lineupjs/lineupjs#545

[thinkh]

TODO @thinkh Enable ScheduledRenderingTask in LineUp (after evaluation in https://github.com/datavisyn/reprovisyn/issues/186).

[thinkh]

@puehringer I've enabled the scheduled task executor. Please test it in some apps.

[puehringer]

@thinkh In general, the scheduled task executor works fine for me, except that the loading overlay in the columns is rather annoying. I would prefer those to only show initially, but not when "recomputing". An alternative would be a see-through overlay instead of showing only the loading indicator.

[thinkh]

@puehringer Yes, the flickering is a bit disruptive. From the UX point, I would not remove the loading indicator, since something is still going on the old values are invalid. I like the idea of the half transparent loading indicator that overlays the old state. I think that needs to be changed in LineUp itself, right?