-
Notifications
You must be signed in to change notification settings - Fork 88
Support GNOME 45 (moved to ESM) #175
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
Comments
same with ubuntu 23.10 gnome 45 |
+1 |
@Sominemo Thank you for your work. Actually I started the upgrade too, but I am a web developer w/o any experience. I did not found enough docs to start the development... If you know any updated description how to start developing and testing an extension, step-by-step, pls share with me too. The bigger problem the tesing. I created a GNOME inside the GNOME as a documentation says, but I do not know how to use it exactly. |
@7system7 I don't have prior experience with GNOME extensions and I used the GJS Guide as a reference: |
@Sominemo big thank you it works like a charm. |
This usually calls for a fork, from there look into publishing to the GNOME extensions page. There isnt anything else for GNOME 45 so it would be appreciated |
Does the extension have to already be installed before performing your commands? I tried to use your PR and still don't have the menu showing for applications that would normally show one (e.g. Brave browser, Chrome, etc). Trying to figure out exactly step by step what I need to do here. Lol |
@p134c0d3 Were you ever able to figure it out? |
Unfortunately I did not. Ended up just moving back to KDE where it's supported natively and made a similar looking setup (macOS looking) on that. Plus with Wayland it's got the natural scroll gestures I enjoy using. Gnome restricting everything (mainly referring to customizations, but other examples are there) made it no longer enjoyable to use for me. |
Information
What is the current behavior?
The extension is not working 'cause the GNOME moved to ESM. 😢 But we are waiting for this extension, because it is sooo awesome.
Steps to reproduce the problem
What is the expected behavior?
To work.
The text was updated successfully, but these errors were encountered: