-
Notifications
You must be signed in to change notification settings - Fork 62
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
Select different layouts for multiple and single entry (per-context switcher) #1996
Select different layouts for multiple and single entry (per-context switcher) #1996
Conversation
Hey @doekenorg, I had a chance to review. I encountered a few issues:
Thanks 👍 |
dea25cc
to
5df9a05
Compare
@zackkatz I looked into your issues with the CSS, but I cannot reproduce this in any browser. It all just works properly. The only way I can reproduce is to manually set an Fixed the other two things. |
@doekenorg Hey, can you please update to the new designs? |
630f4e7
to
a011572
Compare
@zackkatz the new designs are in.
I'm not sure how |
…multiple-entries-and-single-entry [ci skip]
…multiple-entries-and-single-entry
Here are my notes from testing this PR. Besides the issues highlighted below and the things not yet tested, everything else works well. 1. Updating existing Views and creating new ViewsUsing the combination of DataTables Table for the MEL and List for the SEL causes a warning message to appear when navigating to the SEL on the front end: "The Single Entry layout has not been configured". Steps to reproduce:
*This also happens when editing an existing View 2. Installing or activating layouts from inside the View switcherTo be clear, this works! I only have a suggestion. When installing or activating layouts, there is a spinner on the cursor while the layout is installed or activated. However, this spinner disappears if you hover over another layout choice. Other layouts are still clickable while this is happening. So, if you move your cursor, it's not clear that anything is actually happening. Maybe we should make it more clear that something is happening, and/or not have the other layouts clickable while this is process is occuring? 3. The Maps layoutPossibly another discussion but I wonder if we want the Maps layout available at all? After all, it is most useful as a widget. Moreover, for the Single Entry Layout, the "Maps (Default)" option is the same as the List layout as far as I can tell, so we could consider removing it as an option there? Things not tested
|
…multiple-entries-and-single-entry
We need to remove this button altogether now that we have a layout switcher.
@doekenorg We're getting close! Just a few more items:
|
- Improve contrast for accessibility against the background colors - Don't have borders hitting up against each other - Make the upgrade button look better (I think) by using a glow instead of white border - Prevent text selection in the menu, which can happen when clicking and dragging and double-clicking
@zackkatz what do you mean with: And on the |
|
Here's what I would propose, as an example: UTM sheet for reference |
@crbdev I changed it to |
…multiple-entries-and-single-entry
Found a bug:
|
@crbdev done If both are the same template, it will just show "Table" or "List" and not "Table / Table". |
Don't know how I got these, but I did!
Adds support for Dashboard Views
Things to test:
Testing different states
Browser test
Check appearance, confirm functionality in:
This PR addresses #1177.
It adds a new dropdown solution with support for icons and descriptions. It also adds a new variable that contains a separate template for the single entry. There is backwards compatibility as the value of the new variable has a fallback to the "old" variable, that is now solely for the multiple entries.
Todo:
In the meantime this can be tested and reviewed for what we have now.
💾 Build file (1861324).