Open Ou7law007 opened 1 month ago
Can someone tell me why things break on Ubuntu after updates, unlike Windows?
I made a change that should fix this.
How do you guys do GNOME extension development?
Coming from native Win32 API development on Visual Studio, where even kernel drivers can be (somewhat easily) debugged with a proper debugger and with code symbols, it was a nightmare to just setup the development environment with GNOME Builder and you cannot even set break points to learn the APIs!!
And you have the problem with Xorg vs Wayland which makes it even more difficult to just run the code.
I had to restart xorg every time and check the errors with journalctl -f -o cat /usr/bin/gnome-shell
With Wayland, apparently you have to restart/logout. (It took me a while to even understand that you can login with different windowing systems that each have pros and cons)
I used gjs.guide, specifically:
GNOME extension development could be way more fun, if one could attach a debugger and debug the code properly without restarts, especially since the same APIs are supported in multiple languages including JS, python, C etc.
I made a change that should fix this.
75
This is good. Thanks @Ou7law007 On Debian sid with GNOME 47 it enables and starts and most of it works. A few things that don't:
There was 100% functionality with version 12.7 on GNOME 46.4.
Any ideas anyone?
Just in case anyone stumbles on this thread, the additional fixes for GNOME 47 were committed here: https://github.com/zhrexl/DrawOnYourScreen2/pull/72/commits/f921ca6b3c7741e682fb1b2e512b2bd6d9e7a308
Includes a modification to the export const StaticColor
declaration.
https://github.com/zhrexl/DrawOnYourScreen2/pull/72
Thanks, @cryptbrn