Skip to content

Parcoords: ellipsize long labels; show full text in tooltip #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 404 commits into from

Conversation

kernc
Copy link
Owner

@kernc kernc commented May 18, 2017

Ellipsizes labels that are too long to prevent overlapping. But always show full label text in mouse hover tooltip.

Before

screenshot - 05182017 - 07 49 37 pm

After

screenshot - 05182017 - 07 47 22 pm

etpinard and others added 28 commits June 6, 2017 16:36
- as now gl2d traces now come with cartesian svg layers
  (for select/lasso modes)
- hoveron was added *just* to make scatter/hover.js
  not break, it's functionality was never implemented in scattergl.
- this brings back first render for 1e6 pts in close to 1500ms
- add relayout logic so that updating into dragmode select/lasso
  triggers a recalc.
- ... to make image test pass
- to compare output with better gl2d tick patch
- instead of 'old' mesure that uses glplot.viewBox
- this makes gl2d ticks 'more on-par' with SVG
I don't understand why we need to initInteractions twice,
but it seems necessary to do both before and after finalDraw
standardize on assets/delay and increase the updateCamera delay
if you mouseout of the gl2d plot while hovering on a point,
this ensures that unhover will be triggered.
prior to this the test "scattergl after visibility restyle"
consistently failed for me locally
seems like chrome has a more efficient image encoder now
etpinard and others added 21 commits June 28, 2017 15:38
- use graph-wide <g.zoomlayer> for ternary zoom effects,
  no need to another layer to accomplish this.
- broken since plotly#448
- 🔒 down with test
Fix scatterternary lasso/select drag modes
- so we might be able to reuse them for contourcarpet
- and test getVisibleSegment
minor change to the algorithm probably due to cleaner open/closed criterion
this makes contours.coloring='lines' work with carpet
also fixes some unusual bugs like if the first contour is not shown
that were fixed long ago for contour
same as contour - it's *probably* ok without this but I'm a little
worried about some restyle call changing element order unexpectedly.
also a bugfix to findBestTextLocation - surprised that didn't break
anything before!
@kernc
Copy link
Owner Author

kernc commented Jul 6, 2017

@monfera Could you have a quick look at this? It's only five lines or so.

@monfera
Copy link

monfera commented Jul 6, 2017

@kernc thanks for the PR, I see it's been around for quite some time. I'm on another task now, will check back with you ASAP.

@monfera
Copy link

monfera commented Jul 6, 2017

@kernc your PR didn't register with us b/c it's a PR toward your own repo rather than the upstream (ie. it doesn't show up here: https://github.com/plotly/plotly.js/pulls) - there are some key issues, please issue the PR toward the plotly org as it's a better place for comments

@kernc kernc force-pushed the parcoords-ellipsize branch from 5269c30 to a28e116 Compare July 6, 2017 18:44
@kernc
Copy link
Owner Author

kernc commented Jul 6, 2017

I was just following your PR guidelines which state:

Developers are strongly encouraged to first make a PR to their own plotly.js fork and ask one of the maintainers to review the modifications there. Once the pull request is deemed satisfactory, ...

Will open a PR there, thanks.

@monfera
Copy link

monfera commented Jul 6, 2017

Indeed, you're right! I saw the PR is dated May 18 and saw no conversation.

@kernc
Copy link
Owner Author

kernc commented Jul 6, 2017

Some conversation took place in plotly#1703. 😃

Continued in plotly#1857.

@kernc kernc closed this Jul 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants