-
-
Notifications
You must be signed in to change notification settings - Fork 62
Overhaul UI #280
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
base: master
Are you sure you want to change the base?
Overhaul UI #280
Conversation
Thank you for your contribution, I don't know if it makes sense to review this yet, since this and #278 clash and might create merge conflicts. I also am in favor of publishing the already working UI with #278 to EGO first, before doing this. And then testing it extensively and by multiple users, before releasing it. But overall it really looks good, so I'm going to look at this as soon as the issues and PR's with more priority are resolved. And just from glancing over it, there are a few things to do:
|
101ea17
to
ff610a6
Compare
Hello I'm sorry if this might be rude, but will this PR be merged at some point or is oae MIA? |
Hi, |
What is missing to merge this pull request? How could I help to speed this up? |
So, it’s currently broken? Bummer. No problem with Pano tho, it is great! I understand if they don't want to change the design. |
If you're talking about the artifacts on the screenshot, it's Just because of my screenshot tool which, I think, only works well under wayland,
If your code is hot, I think it's worth a try before launching into a new branch, I would also like to take advantage of the progress of the main branch which has Added highlighting features for code. And also without mentioning all the refactoring necessary to adapt it to the new version of gnome, but frankly if you are determined enough to launch a new branch or even a new extension with these features, it's really worth it.✨👌
😵💫 |
Afaik everything works, that screenshot just has the background set to transparent and the headers enabled. I just haven't updated it since the current branch still works fine. |
Sorry, I thought it was broken because of the artifacts and headers, my bad, how embarrassing 😅 |
😆 , sorry, my bad... I send a better screenshot I think there is still some work to be done, because there are sometimes images that are not displayed.
since there no any activities concerning this PR, it difficult to know 😕 |
@boerdereinar could you please resolve the conflicts so I can merge them? |
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 code looks good from my side. Thanks for this amazing UI overhaul ❤️
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.
General question regarding new icons, is there no adwaita-icon from https://github.com/GNOME/adwaita-icon-theme that is similar and could be used instead?
Since he ticked the box |
…style in compact mode
Can be triggered by: 1. Pressing the action button 2. Ctrl + click on the item 3. Ctrl + enter on the item
This adds support for ZWJ sequences
Note: this causes a windows xp like visual bug in the link item when running Pano in a nested shell
…respected - Item color didn't support this format: rgb(255 0 0)
bee6a39
to
f142b4d
Compare
I rebased the branch on master, there were many merge conflicts, that were not that easy to resolve, so I made a backup of the changes before the rebase on https://github.com/oae/gnome-shell-pano/tree/gnome-theming-v2_before_rebase I think I did it correctly and everything is as expected, but I might have made a mistake. Feel free to modify this or force push ( |
…cal (which is being deprecated)
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 are some default value changes in gschema. If people have already customized it before, these changes will not take effect on their system, right? Maybe we should change the keys or the schema ID. What do you think, @Totto16?
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.
Yes that would be a good idea, as someone, who didn't change most of the settings in didn't notice it.
Changing the schema ID seems to be a good idea, so that incorporates some version or something of that sort 🤔
My first thought would be id="org.gnome.shell.extensions.pano.v2"
or something similar, what do you think?
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.
That would also be great, but I think it is out of the scope of this PR, as accent colors are only introduced as of gnome 47, if I remember correctly. And we need to listen for changes correctly, and interpret colors correctly, since as far as I know, some distros (and maybe also stock gnome) refers to accent colors by name and not by rgb or hex color 🤔
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.
After the schema change, we can merge this.
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.
Please incorporate the schema id change as discussed in #280 (comment)
Great job, would it be possible to switch the color scheme in gnome depending on the light/dark theme? |
That is not that easy, as there are many customizations, that can't just be applied to the dark / light heme. But it's generally a good idea. |
So I am guessing this is almost finished? |
Hi, i would really like to set two things, so for me pano will be totally completed, first is the search entry if is not possible to dynamically display it, is it possible to add option to set is position to bottom and also change the border color, so I can make it presence less visible when I don't need it, seconde is the border radius of the content preview, thanks |
Overhaul UI
Description
This pr fully overhauls the UI as per #185.
New Features
/home/user/*
are shortened to~/*
Misc
yarn run clean:ts
can now fail inbuild:ts
to make building easier while pano is still runningDependencies
color-string
for easy color parsing and conversion to rgbgraphemer
for checking if the copied string contains a single grapheme cluster for the emoji item. This fixes ZWJ sequences not being detected as an emojivalidate-color
hex-color-converter
Screenshots
New UI
Compact Mode
Window Position: Pointer
Incognito Mode
Header Style: Compact
Fixes
Fixes #124
Fixes #150
Fixes #176
Fixes #185
Fixes #272
Fixes #300
Type of change
Checklist