-
Notifications
You must be signed in to change notification settings - Fork 18
Finishing up remaining TODOs in panel's demo #1144
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
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1144 +/- ##
==========================================
- Coverage 89.31% 89.28% -0.03%
==========================================
Files 279 279
Lines 21378 21387 +9
==========================================
+ Hits 19093 19095 +2
- Misses 2285 2292 +7 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
Review from a user perspective:
- Resizing works great !
- Demopanels: With no available places, the demo panels show the confusing error message, that the panel is disabled. More context might be useful for a user like:
Panel diables due to 0 places available
- Visualisation problem in dark mode:
- Sidebar: background colour doesn't adjust to theme, hence the text is not readable
- some text in the horizontal Controlbar above the map and Colourbar Menu do not adjust in font colour, therefore the text is not readable either
- The seperation in the horizontal menubar looks nice and organizes the menu bar really well, however, the dropdown menus and buttons on the left side are not leveled with the ones on the right side.
Thanks for the user review. Please find my comments below.
I decided to just convert the print statements to these messages as is. We plan on aligning all these tabs xcube-dev/xcube-viewer#483 so they all have the same UI design which would then also take care of what is missing for each tab to be useful. Regarding the error message, it is of the user's choice, and as mentioned I used the content from the print statements
I am not able to replicate this issue. Please see the screenshot attached.
Unable to replicate this as well. See screenshot above! |
This issue was being caused by using npm link to use local chartlets build for testing and is not an issue created by this PR. |
"paddingTop": 6, | ||
# Since for dynamic resizing we use `container` as width and height for | ||
# this chart during updates, it is necessary that we provide the width | ||
# and the height here. This is for its parent div. |
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.
This is for its parent div.
It is not clear to what "its parent" is referring too: container of the chart or parent of the chart container.
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.
It refers to the container of the chart. Will update the comment.
chart=None, | ||
style={ | ||
"paddingTop": 6, | ||
# Since for dynamic resizing we use `container` as width and height for |
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.
What container
?
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.
This is a Vega-chart concept which allows the user to set top-level width or height properties to "container" to indicate that the width or height of the plot should be the same as its surrounding container
Co-authored-by: Norman Fomferra <[email protected]>
…sh-xxx-demo-todos
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.
Review from a user perspective:
Spectrum View:
-
Plot format:
- I prefer the representation of reflectances in point and line format. The bar chart makes it difficult to compare the spectra with each other
-
Exploration mode:
- The feature works as described in the tooltip, but the name/wording of the features can be misleading.
- Example: The clearing of the plot when switching from
add
-mode toupdate
-mode. This is not what I would expect as a user.
-
Spelling/ Wording:
- for coherence: "legend" -> "Legend"
- Suggestion for descriptive text: "Choose an exploration mode and select points to visualize their spectral reflectance across available wavelengths in the Spectrum View."
Histogram View:
- The info text is centred. For coherence: position should be left-bound.
Thanks for the review Clara. I have updated the text and fixed the wording as requested.
This was discussed with Norman to keep the bar plots as line chart does not provide the real information when the distance between the wavelengths is too high.
This was done to keep the demo simple. |
Good, so far. Here are my remaining requests:
|
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.
See my comments.
Yes, this was already in row mode, but was waiting for the release from chartlets.
Done
Done
Done I assume it was number 3, if you had missed any, let me know. Screenshots below showing the panels: I have also created a PR for xcube-viewer to use the latest Chartlets and pin the versions for Please also review this tiny PR in xcube-viewer: xcube-dev/xcube-viewer#531 |
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.
Thanks @b-yogesh
This PR finishes up the TODOs in both the Hist2D demo panels and Spectrum View.
CircularProgress for Histogram 2D panel: After investigating, it seems infeasible within the current Chartlets architecture. Chartlets executes callbacks sequentially and returns all responses together, preventing timely progress updates. To yield responses as they complete would require changes on the Chartlets.js side. If real-time updates are needed, we may need to rethink the callback execution architecture. As an alternative, skeleton component in Chartlets (currently in development) could be used to indicate progress.
Other TODOs: All other TODOs for Histogram 2D and Spectrum View have been completed. However, dynamic resizing of the chart when the side panel width changes requires an update to the VegaChart component in Chartlets (Add dynamic resizing for Vega charts bcdev/chartlets#121).
Spectrum View TODO: Add new State properties xcube-viewer#512
Added exploration modes
Update
: Clear the chart but the current selection if any.Add
: Current spectrum is added and new point selections will be added as new spectraChartlets PR (bcdev/chartlets#122) required to make radio buttons styled for this demo.
Addresses: Address open issues in viewer demo panel(s) #1134
Checklist:
Add unit tests and/or doctests in docstringsAdd docstrings and API docs for any new/modified user-facing classes and functionsNew/modified features documented indocs/source/*
CHANGES.md