-
Notifications
You must be signed in to change notification settings - Fork 498
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
use default chrome instead of integrated app menu #149
Comments
@null-von-sushi thanks for the feedback! I added this in #139 because I wasn't happy with how the app looked with the default chrome: I don't have strong feels either way on this, but if others would like it to go back to showing the default frame (and leave it up to users to make Desktop fit better with their theme) then I'm fine with reverting that PR. |
Not currently. I'm a maintainer on GitHub Desktop but this Linux fork is something that I try and keep up to date in my spare time. Please follow along with the upstream discussion about this desktop#1525 |
It'd be nice if this could be a user configurable action, I don't think there's any solution that is perfect for all use cases honestly.
Interesting. Thanks for the link, I'll keep an eye on the upstream issue... EDIT: It might be worth considering mentioning your fork on the main desktop website (if you want that amount of traffic for this project that is). I only found this thanks to the AUR, most people search the web for software though. |
@shiftkey +1 for reverting #139. Ubuntu's default Gnome theme is indeed awful, but the install base mostly consists of people who a. don't care what Gnome looks like, or b. are going to customize Gnome anyway (like me and @null-von-sushi 😂). Here's a comparison with VSCode, which also uses their own menu by default, but has an option to use native menus: If you're interested, here's my setup:
|
Sweet #139 was clean to rebase out. Here's the new (or old) look: I'd love to submit a PR that adds native menu bars back as an option. I had a bit of trouble running the snap packager on 18.04:
Any ideas how to run the packaging steps (preferably containerized)? |
Yeah, I've only been able to get this working inside the Snapcraft docker container.
This was working fine when I shipped the last update a week ago: https://brendanforster.visualstudio.com/desktop-linux/_build/results?buildId=381
This stuff was working fine for me up until a couple of days ago but something in the docker setup is blowing up because of some change with the Docker images, and it's having a problem parsing this version string: |
Yeah that's the same error I was seeing in the snapcraft image. Glad to know it's not just me! Looks like their containers were updated recently. This commit looks related to the version check issue, and the one before that they moved the squashfs-utils into a prior build step. So it could be as easy as copying the original install process into the build container here and giving it a go. |
@null-von-sushi heads up, if you want to build yourself a version of github desktop with the native menubar, you can check out https://github.com/trxcllnt/desktop/tree/revert-139 and run |
I once tried to run a docker thing and couldn't get it to work, so I am not having high expectations. Oh, and I am not even using Debian/Ubuntu. I will probably just wait for this to be fixed properly. For now I just have a kwin override to show the native titlebar. Having 2 titlebars is annoying, but I don't use github THAT often. Thanks though :) |
Any update on the issue?. Is reverting the code still an option? |
Not really. Been unwell this week and I see there's a new release available and so after I've caught up with that I'm going to open a PR for this change.
Totally. I've only heard feedback against this change, and while I did get some ❤️ reactions on the original PR I also appreciate that some on this issue would like it reverted. I have no strong feelings, but I'd like to confirm that more people prefer reverting so I'll leave the PR open for a bit to gather feedback. |
The most important thing is your health. Don't overwork yourself. Stay healthy 😁. |
I've opened #237 to propose this change. If you're interested in seeing the app use the default chrome, please leave a reaction or approval on that PR. |
This shipped as part of |
Please describe the problem you think should be solved
Github desktop uses Windows 10 style window controls on Linux, which looks very out of place. In addition, this also prevents shadows from showing when using KDE.
This is what it normally looks like:
[Possible Solution] Allow people to enable native titlebars
Just using native titlebars (and menu bars too) should be relatively easy to implement I believe, as that's the default.
I force-enabled them just to add some screenshots to demonstrate how much more consistent it would look. Also notice how the window now has shadows properly showing. I cannot disable the built in windows 10-style window controls Github-desktop shows though, hence this issue.
Just as a side note, KDE can set per-window color schemes, so this is what it would look like with a custom color scheme for Github-desktop:
EDIT: Offtopic, but I just realized this is not the official repository. Does that mean microsoft does not actually support Running github desktop Linux?
The text was updated successfully, but these errors were encountered: