Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

What if I want to use GNOME's nice touch functionality and rich set of apps, but not the style? (Which in my subjective view is wayyy too gray).

Why do those things have to be tightly coupled all of a sudden? We've made it through decades without breaking theming, what changed?



> We've made it through decades without breaking theming, what changed?

According to the GNOME team, application developers were getting bug reports filed against their application about broken interface elements, and GNOME was having bug reports filed for the same. The devs stated it was the fault of the theme being used, and as such it would eliminate a lot of headaches for both if themes were forbidden.

"Independent developers" set out to explain this in more detail. [1] While it is targeted at vendors who created their own themes for branding, it echos the overall sentiment toward theming from GNOME itself.

A blog post from a dev as well. [2]

[1] https://stopthemingmy.app/ [2] https://blogs.gnome.org/tbernard/2018/10/15/restyling-apps-a...


That sounds like it'd be solved by a filter rule in their bug tracker, removing theming altogether seems like a strong overreaction imo.


That's called GtkGesture. Just use it. The libadwaita components literally bind the gesture to the ui design pattern widget.

If you just don't want the ui design pattern just use the gesture, it's already there waiting for you to make something with it.


I'm not talking about a library, I'm more concerned with DEs implementing the library.

Things like swipe with three fingers to switch desktops, swipe up with three fingers to show open windows etc. Why is all that stuff tied to a UI theme?


It's not, you're just confused.

Swipe to switch desktops is implemented in GNOME Shell and Mutter. GNOME Shell's default CSS style is also called Adwaita, but it in no way affects the availability of gestures.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: