12 ms·
If you take a look at the GTK+ ecosystem...it's kinda broken, too. Simple use case: Make a sidebar fade in and fade out, while changing the dimensions of the r
by cookiengineer 6y ago
If you take a look at the GTK+ ecosystem...it's kinda broken, too.
Simple use case: Make a sidebar fade in and fade out, while changing the dimensions of the right box. Pretty close to impossible to implement in a clean manner, even within glade.
And then, try to support a mobile device in a responsive way with libhandy.
Now you throw the towel and just get on with 20 lines of CSS and literally two HTML elements.
CSS should not be underrated when it comes to layouting. It is super flexible, and UI frameworks always will lack behind due to their architectural patterns.
- jmnicolas 6y agoI never coded GTK apps, but isn't the theming done with CSS since GTK 3?
- cookiengineer 6y agoYes, with global css, which is literally one file for every single application, extension, gnome shell, terminal and ui windows on your whole system. That is why so many apps don't work bug free with other themes. There's no way to predict how your app will behave on another system with another theme. So personally I think the mess of overused dummy css classes in the GTK ecosystem is really a bad design. They could've gone with custom, namespaced, ui elements instead of that box.something.something shit. They reinvented divitis. Quite literally.