alright I'm going to go the gnome extension route.
alright I'm going to go the gnome extension route.
GYeah probably the best way to go about it
AMaybe this can help: https://discourse.gnome.org/t/creating-an-extension-with-a-simple-toggle-button/8794
GNOME Discourse
I’d like to create a minimal extension that has a simple toggle button without menu. I simply want the icon that appears in the gnome panel to directly be a toggle button. I found plenty of examples involving toggle buttons within submenus, but I can’t figure out how to register a click handler on the icon directly. Any ideas? const { GObject...
GA full on rebasing app could fuck up people's systems too, I've heard stories about people rebasing so many times that all the dotfiles are fucked and shit starts to get wack
Japps messing with people's dotfiles are not our fault
Ayeah rebasing isn't completely safe
Japps are breaking spec, they should be fixed
AI broke my GTK configuration and then gnome looked really weird
Jlike that qgnome thing that breaks everything
GYeah but if we make it super easy then people could very easily break their systems
AAnother time I broke my font config and all flatpaks couldn't render text
JI'm switching between variants of a common image
GVariants of a single image works, but rebasing between desktops, etc gets messy
Jyeah but that's not our problem to solve
GYeah
Jlike, all these gnome fork things stomp on each other, that's on them
GA framework, nvidia, and developer toggle would be awesome though
GThen we would only need one bluefin ISO
Jyeah
Jplus one ISO is what you'd need for usb keys
JI'm glad someone mentioned the gnome extension, I've been sponsoring the guy who did the desktop cube extension for gnome so I'll just send him a mail
AThat was me
it seemed like the best "quick and dirty" way, it will look rather nice also
it seemed like the best "quick and dirty" way, it will look rather nice alsoJyeah plus simon makes tons of these things, hopefully it'll be a quick and dirty.
JI think I'm going to shoot for "1.0" of bluefin for kubecon
Jso 1 Novemberish, after F39 comes out
ASounds like a good timeline
EGitHub
Currently this prohibits Discover from opening on signed images.
See: https://invent.kde.org/plasma/discover/-/issues/24
To be reverted after this is upstream:
https://invent.kde.org/ravier/discove...
See: https://invent.kde.org/plasma/discover/-/issues/24
To be reverted after this is upstream:
https://invent.kde.org/ravier/discove...
Jthis time we'll remember the 24h delay! hahahaha
ELmao
J
Jnever gets old.
JJhttps://github.com/ublue-os/website/pull/306 need a review here to fix some URLs
Jactually let me find a 404 action we can use
ENever does
JJalright need one more!
JI found this lychee action at work, simple to add, found a bunch of busted links which I just fixed
Lit's such a great theme!
Shey if i would build a image, is there any like commit "rules" that would be good to follow: e.g how to name commits, create another branch where to merge (so use a pull request), use feature branches etc.
@j0rge
@j0rge
JConventional Commits
A specification for adding human and machine readable meaning to commit messages
JThis is generally a good guideline on how to name commits/branches. As for the other stuff I don't know
Sthanks :3
Sis the any like github actions that forces you to use them?
Jyeah they come with it when you clone it
JI'm in meetings all day if someone wants to test the fixes for kinoite: https://github.com/ublue-os/main/issues/132
ETesting right now
E@tulili the Ublue wallpapers package is no-op on Kinoite based images
ELooks like it was set back to /usr/share/backgrounds at some point
Jdoes that affect main?
ENo just images using bling
