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

use default chrome instead of integrated app menu #149

Closed
null-von-sushi opened this issue May 19, 2019 · 14 comments
Closed

use default chrome instead of integrated app menu #149

null-von-sushi opened this issue May 19, 2019 · 14 comments
Assignees
Labels

Comments

@null-von-sushi
Copy link

null-von-sushi commented May 19, 2019

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:
Screenshot_20190519_010339

[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.
Screenshot_20190519_005908

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:

Screenshot_20190519_005835

EDIT: Offtopic, but I just realized this is not the official repository. Does that mean microsoft does not actually support Running github desktop Linux?

@shiftkey
Copy link
Owner

@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.

@shiftkey
Copy link
Owner

Offtopic, but I just realized this is not the official repository. Does that mean microsoft does not actually support Running github desktop Linux?

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

@shiftkey shiftkey changed the title [UI] Use Native titlebar use default chrome instead of integrated app menu May 19, 2019
@null-von-sushi
Copy link
Author

null-von-sushi commented May 19, 2019

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.

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.

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

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.

@trxcllnt
Copy link

@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:

Screenshot from 2019-06-20 18-47-09

If you're interested, here's my setup:

  • User Themes applies your user theme to gnome-shell controls
  • Activity Configurator lets you clean up the top panel
  • The Gnome GlobalAppMenu and appmenu-gtk3-module to move app menus into the Gnome panel. This project was abandoned by its author but still works great on Ubuntu 18.04.2 w/ a few JSON edits.
  • OS X cursors, High Sierra theme, and fonts:
    (font install instructions)
    wget -O mac-fonts.zip http://drive.noobslab.com/data/Mac/macfonts.zip
    sudo unzip mac-fonts.zip -d /usr/share/fonts; rm mac-fonts.zip
    sudo fc-cache -f -v

@trxcllnt
Copy link

Sweet #139 was clean to rebase out. Here's the new (or old) look:

Screenshot from 2019-06-20 20-41-07

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:

  1. yarn package on my host eventually throws an error trying to exec gtk-update-icon-cache-3.0
  2. yarn package in the azure-pipelines.yml containers fails at the workaroundForSnapPackage() function in scripts/package.ts
    • unsquashfs isn't in the snapcore/snapcraft base
    • after installing squashfs-tools, /src/dist/unsquashfs-root/meta/snap.yaml doesn't exist

Any ideas how to run the packaging steps (preferably containerized)?

@shiftkey
Copy link
Owner

  1. yarn package on my host eventually throws an error trying to exec gtk-update-icon-cache-3.0

Yeah, I've only been able to get this working inside the Snapcraft docker container.

  • unsquashfs isn't in the snapcore/snapcraft base

This was working fine when I shipped the last update a week ago: https://brendanforster.visualstudio.com/desktop-linux/_build/results?buildId=381

Any ideas how to run the packaging steps (preferably containerized)?

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:

@trxcllnt
Copy link

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.

@trxcllnt
Copy link

trxcllnt commented Jul 1, 2019

@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 docker-build-and-package.sh. The only prerequisite is docker, and you shouldn't need to build or install anything in the project itself. Once it's done you can install dist/GitHubDesktop-linux-2.0.4-linux1.deb like normal.

@null-von-sushi
Copy link
Author

@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 docker-build-and-package.sh. The only prerequisite is docker, and you shouldn't need to build or install anything in the project itself. Once it's done you can install dist/GitHubDesktop-linux-2.0.4-linux1.deb like normal.

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 :)

@alitajelsir
Copy link

Any update on the issue?. Is reverting the code still an option?

@shiftkey
Copy link
Owner

Any update on the issue?.

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.

Is reverting the code still an option?

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.

@alitajelsir
Copy link

alitajelsir commented Mar 27, 2020

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.

The most important thing is your health. Don't overwork yourself. Stay healthy 😁.

@shiftkey
Copy link
Owner

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.

@shiftkey shiftkey self-assigned this Mar 28, 2020
@shiftkey shiftkey mentioned this issue Mar 31, 2020
@shiftkey shiftkey pinned this issue Apr 1, 2020
@shiftkey
Copy link
Owner

This shipped as part of 2.4.0 RC1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants