-
Notifications
You must be signed in to change notification settings - Fork 4
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
Adjust UI code to be properly responsive #530
Conversation
…out the database, relying on remote API entry points for that
It is activated if DASH_TELEMETRY is set in the environment.
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 @karpov-sv -- this is a super interesting PR! As it touches many aspects of the code, I will break into sections. Also when it comes to the layout, I test on several screen sizes using the responsive mode of Firefox:
Name | screen size | resolution | DPR | Comment |
---|---|---|---|---|
Laptop 1 | 13'' | 1920 x 1080 | 1 | e.g. HP elitebook from 2020 (my default) |
Laptop 2 | 14'' | 1280 x 800 | 2 | e.g. macbook pro from 2020 |
Desktop | 24'' | 1920 x 1080 | 1 | e.g. DELL P2417H (my default) |
Smartphone | 6'' | 360 x 800 | 4 | e.g. Galaxy S20 |
Let's start with the main page :-)
Main page (index.py)
search bar & logo
I think would even be more disruptive in the look change of the main page, and keep reducing the logo to 20%
and center the logo+bar (in the case of no table shown) in the page. In the end, that would feel more like popular search engine main page (small logo on top of the search bar, all centered in the page). What do you think?
General layout for table
I like the fact that buttons are on top, and visible by default:
I would add a space between these buttons, and the header and the table though, to avoid crowded zone. What do you think?
However, the basic look for the result table looks to me too 'raw' and too small for large resolution devices, such as laptop 1
and desktop screen
(this is why I've added transparency before, and make it bigger):
Any strong opinion to revert back to the previous look? Or proposal to improve the current look for all platforms?
Skymap
There used to be transparency around the map -- can we keep it?
Preview
The new look is too "raw" from my opinion:
Maybe a dark background on the simple_card object (to contrast more with the underlying page), and a bit of transparency on the card elements?
Also, I see that you change the cutout colormap from Greys_r
to Hot
. What was the motivation?
…hould hide them completely then?..
…proper measurements
… are properly normalized
…lower right part of the card
… last alert content tab
…lightcurve points
…er. Also, invert the difference cutouts of negative detections to make them more visible
…r show where it goes
…. Uses js-based POST as direct GET tends to just open plainly in the browser, until we change its Content-Disposition.
apps/cards.py
Outdated
html.Div(APIURL, id='download_apiurl', className='d-none'), | ||
], position="center" | ||
), | ||
help_popover( |
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 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.
Summary of this work -- @karpov-sv do I miss something? Layout improvement or change
New features
Code improvement
|
There are also newly introduced features for displaying the info on whether the point is negative or low quality in the popup, and for inverting the difference cutout for negative detection. Also, now it displays the alert content for the clicked data point, like the cutout. |
Agree! |
Committed! |
Some links that may be useful here:
https://getbootstrap.com/docs/5.1/layout/breakpoints/
https://getbootstrap.com/docs/5.1/utilities/display/