-
Notifications
You must be signed in to change notification settings - Fork 323
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
Implement loading spinner for visualisations. #6512
Conversation
|
There is a separate task for it: #5214
This is the same spinner as for the documentation panel. Should that also be updated? @wdanilo |
@MichaelMauderer do you have an estimate of how long would it take? |
I'd say one or two points. |
Question – why do we estimate that to 1-2 points? I already created such a "spinner" for text in EnsoGL. When you are truncating text, the three dots after it are animating (we can re-use it). I implemented that in approx 30 minutes back then – I remember that I was on a call with Sylwia, she asked me about it and I implemented that before the call ended, couple months ago. I'm talking about the shape and its animation. If you are already placing the spinner in a correct position, then placement should not be a problem. Assuming that creation of shape is let's say 30-90 mins (let's assume 3x what it took me back then), why we have 1-2 days estimate here? Anyway, the text spinner might be refactored and re-used. It's here: |
It's always easier to estimate after the fact :) I've added a new EnsoGL based spinner, but it is not fixing #5214. That will require some more work, as there is an issue with the layer ordering. It will need some additional work as right now, the docs panel is in HTML and overlays all EnsoGL objects, so the spinner is never visible. |
@@ -174,18 +176,39 @@ impl View { | |||
let display_object = display::object::Instance::new(); | |||
let background = background::View::new(); | |||
let overlay = overlay::View::new(); | |||
display_object.add_child(&background); | |||
// display_object.add_child(&background); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, btw I also touched this line one time. I was like "why the heck do we need it?". And I still don't understand why.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is some cruft in here. We once had an EnsoGL background, but that did not work well with HTML/.JS visualizations, as the layering was problematic. So, we added an HTML background, too. But that was problematic with EnsoGL visualizations (of which we have none currently, I think). We should sort this out at some point.
QA: 🟢 |
* develop: Implement loading spinner for visualisations. (#6512) Fix blank input port (#6614) Add `Date_Range` (#6621) All Vector operations shall be applicable on java.util.ArrayList (#6642) Fix redirect paths and enable authentication and new dashboard by default (#6605) Fix #6287: wrong nested breadcrumb ordering (#6617) Whitelist AWS Cognito domains (#6643) Revert "Add COOP+COEP+CORP headers (#6597)" (#6647) Fix shortcuts table formatting (#6644) Automatic type based dropdown does not include singleton in a union type (#6629) Make Meta.get_annotation work for constructor (#6633)
Pull Request Description
Fixes #5088. Adds a ensoGL spinner for visualizations waiting on data.
Peek.2023-05-08.09-58.mp4
Important Notes
This spinner will not show up for the duration where visualizations are processing data on the frontend. If this is a concern, visualization need to implement heir own loading spinner, or we need to provide a unified API for them to keep the spinner visible.
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
Unit tests have been written where possible../run ide build
.