-
Notifications
You must be signed in to change notification settings - Fork 131
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
Wilma Responsive redesign #3972
base: main
Are you sure you want to change the base?
Conversation
Added Bootstrap and updated CSS for Wilma theme to make it responsive (vivo-project#3909) * Added bootstrap and updated CSS for Wilma theme to make it responsive * Fixed View All position * Fixed footer * Added responsiveness to Page managment table * Fixed CapabilityMap responsive * modified Photo Cropping page and minor fixes * Removed unused libraries * Fixed horizonal scroll in the site admin pages * Minor fix in Capability map page * fix: Fixed serach bar button moving out of place * fix: Co-author Network graph size on mobile phone * Fixed tenderfoot bootstrap in search page * Updated bootstrap location and refactored propert group tabs * Reimplemented tab state persistence after refresh feature
…roperty control panel buttons (vivo-project#3932)
@milospp took this for a test spin and works great overall. Note for future reviewers, it is necessary to do a hard refresh to clear your cache of the old wilma.css! I was fooled for a few minutes. |
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.
The responsiveness looks good to me. Tested in Chrome, FF and Safari.
However, although I cannot see any reason for this in the code, so it could be something caused by environment, I cannot load any of the temporal graph google charts when I build from the PR code. I get a cross-site scripting failure from the googlecharts API and jquery query error for the chart height. (see attached for example)
I cannot understand why this is only the case in the newer code, but it is consistently reproducible for me. Apologies if this is something I'm doing wrong.
|
||
if ( groupName == "viewAll" ) { | ||
processViewAllTab(); | ||
} | ||
console.log("View all") |
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.
suggest removing console debugging statement
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.
Removed, thanks for the suggestion.
|
||
<fieldset> | ||
<legend>${i18n().search_form}</legend> | ||
<form id="search-homepage" action="${urls.search}" name="search-home" role="search" method="post" > |
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.
although I don't see any problem with this, just noting the switch from GET to post for the form submission. it doesn't seem related to the bootstrap theming
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's been a while since I added this code, I can't remember why I switched to the POST method... Also, I see that every other theme is using GET.
I reverted it to GET.
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.
Given that the chart issue is already fixed in main, and should be handled by the merge, I think this change looks good.
@@ -20,6 +20,8 @@ | |||
</#if> | |||
</#if> | |||
|
|||
<script src="${urls.base}/bootstrap-5.3.2/js/bootstrap.min.js"></script> |
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 seems bootstrap5 and bootstrap3 would be loaded at the same time according to head.ftl and headScripts.ftl of Nemo theme.
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.
Thank you for the suggestion. It looks like I mistakenly added Bootstrap 5. I removed it from the Nemo theme and tested the themes. It's working fine now. If you catch anything strange, please report it.
Tried out the changes and looks good. @milospp, I did notice some odd behavior if the geo focus map was enabled in runtime.properties (homePage.geoFocusMaps=enabled). See screenshot: |
@gneissone, I fixed the map responsiveness. Can you please validate it. |
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.
Looks good after the update, thank you!
Just confirming that I agree this still looks good after the change to use the bootstrap webjar. |
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 set of PRs not only modifies Wilma theme to have responsive design, but also introduces global dependency for shared components on specific version of Bootstrap which can't safely be done retrospectively.
So it breaks backward compatibility for customized themes
https://wiki.lyrasis.org/display/VIVODOC115x/Creating+a+custom+theme
I think we should find a better way to do that.
@milospp we concluded at a committers meeting the following:
Can you please align this PR in accordance with those conclusions? Thanks |
@chenejac is it also reasonable to change the default theme to 'willow' as part of the PR? |
General idea is that willow will be the default VIVO theme. The team will make the final decision when this PR is close to be merged. |
Just a quick note regarding the name: AFAIK, Wilma and Tenderfoot were named after... "Wilma Tenderfoot". In that tradition it could make sense to call it "Pickle", "Bludsten", or "Theodore". But that just as a sidenote, I have no strong feelings here. |
Wilma was named after the first granddaughter of Jon Corson-Rikert, the IT director at Mann Library and original creator of VIVO. |
Ah, that's cute and new to me. Okay, so (Wilma) Tenderfoot has nothing to to with the original Wilma. Thanks for the correction! But I am sure that Tenderfoot was named after Wilma Tenderfoot. |
I had no idea where Tenderfoot came from, but that certainly makes sense if someone reinterpreted Wilma in a new context. |
I am still seeing the issue with the temporal graphs after merging in the main branch, unfortunately. The sparkline graph works fine. @milospp any ideas what could be going wrong? I tried manually setting a width for the div holding the graph but there was no change. FWIW if I change the theme the temporal graphs work fine. |
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.
Temporal graph issue needs resolved.
} | ||
} | ||
|
||
#graphContainer { |
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.
I suspect this is the problem. If this #graphContainer css is removed then the temporal graph works again.
GitHub issue 3910
GitHub PR Vitro 460
What does this pull request do?
Added bootstrap (only grid style) CSS and modified Wilma theme to leverage its responsive design feature and enhance the overall layout.
What's new?
Mobile optimized design
Avoided horizontal scroll
How should this be tested?
Open every page and test by resizing up to around 400px in width (Mobile device toolbar can be used in google chrome to simulate phone display)
Additional Notes:
Here is the video example
https://youtu.be/9B0_cevrEeE