Skip to content
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

UI changes on upgrade to bslib and Bootstrap 5 #1350

Closed
wants to merge 17 commits into from
Closed

Conversation

vedhav
Copy link
Contributor

@vedhav vedhav commented Sep 24, 2024

Draft PR, will be broken into smaller PRs soon

@vedhav vedhav added the core label Sep 24, 2024
gogonzo

This comment was marked as spam.

@kumamiao
Copy link

kumamiao commented Oct 1, 2024

Thank you so much Vehda for starting the draft PR! I like the general look of the UI, looks more modern that our previous style. A couple of comments from my initial review:

  1. Would it be okay to adjust the filter panel width/proportion? The filter panel seems to be a bit wide, pushing the output panel to be a bit too narrow.
  2. I personally feel it would be great to save a bit more space for each filter, would it be possible to adjust? For example, making the space narrow between filters, removing some boarders Taking the screenshots below as an example, only 4 filters have been selected but it has taken up almost the whole page. When implemented into actual clinical studies, this would make the panel super long.
    Screen Shot 2024-09-30 at 11 54 33 PM
  3. Similar reason as above, I wonder how much value would the buttons for Active filter summary, Filter Data, and Transform Data add, since all of them are collapsable. I know @donyunardi also have thoughts on this. For example, if we have additional features to add in the future, the top will be crumbled.
  4. For the transform, other than looking at the transformed data in the output panel, would it be possible to let the users know whether they have applied or removed the transformer?
    Screen Shot 2024-10-01 at 12 08 25 AM

@vedhav
Copy link
Contributor Author

vedhav commented Oct 1, 2024

Thank you @kumamiao for going through the POC and providing your comments:

  1. Would it be okay to adjust the filter panel width/proportion? The filter panel seems to be a bit wide, pushing the output panel to be a bit too narrow.

Yes, this is possible, there is a CSS variable (--_sidebar-width) that sets the width of the sidebar(the default was 250px and it was changed to 350px). I'll also check if this is something that can be an argument that the app developer can use to customize the space to their need.

  1. I personally feel it would be great to save a bit more space for each filter, would it be possible to adjust? For example, making the space narrow between filters, removing some boarders Taking the screenshots below as an example, only 4 filters have been selected but it has taken up almost the whole page. When implemented into actual clinical studies, this would make the panel super long.

👍🏽 I'll check ways to reduce the space taken by the sidebar elements. In general, the bslib defaults have more padding/margin. We can add custom defaults to our sidebar to overcome these defaults. A good aim would be to stay closer to the space the older version has. Here is a side by side screenshot of current state of the PR and older version just for reference.
sidebar-teal

  1. Similar reason as above, I wonder how much value would the buttons for Active filter summary, Filter Data, and Transform Data add, since all of them are collapsable. I know @donyunardi also have thoughts on this. For example, if we have additional features to add in the future, the top will be crumbled.

It is easy to remove these sidebar buttons because they are a "feature" (unwanted feature 😛). However, removing the icons will still keep this blank space at the top. It will be slightly challenging (not impossible) to move the sidebar hide/collapse icon to another location because it comes straight out of bslib. It has some complex sass rules to make it behave the way it does and we will have to spend some time to investigate. Out of the box the bslib sidebar has that blank space at the top, I just wanted to make use of this blank space by adding these icons.
top-icons

  1. For the transform, other than looking at the transformed data in the output panel, would it be possible to let the users know whether they have applied or removed the transformer?

I don't understand the statement "whether they have applied or removed the transformer". The transformers are always applied.

@kumamiao
Copy link

kumamiao commented Oct 2, 2024

I see, it would be interesting to see how it's like to leave it blank, my intuitive feeling is that it may be cleaner as I personally feel the buttons may not add much. Curious how others feel about this.

It is easy to remove these sidebar buttons because they are a "feature" (unwanted feature 😛). However, removing the icons will still keep this blank space at the top. It will be slightly challenging (not impossible) to move the sidebar hide/collapse icon to another location because it comes straight out of bslib. It has some complex sass rules to make it behave the way it does and we will have to spend some time to investigate.

My apologies I was not clear enough. I meant for the second transformer can we show the status of the transformer? Currently after clicking the button once or multiple times, there is not indication on the status - is the transformer applied, or is it removed? App user can only tell by looking at the data summary or the data itself.

I don't understand the statement "whether they have applied or removed the transformer". The transformers are always applied.
Screen Shot 2024-10-01 at 12 08 25 AM

@vedhav
Copy link
Contributor Author

vedhav commented Oct 25, 2024

Closing the PR. This will be split into different PRs

@vedhav vedhav closed this Oct 25, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Oct 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants