Live data from Hacker News

The end of the nice GTK button

blog.brixit.nl

651–660 of 666 posts

Re: The end of the nice GTK button

#651
post #648

Earlier quoted context omitted.

>It wasn't even acknowledged as a bug in the beginning, even after screenshots with clear signs of regression were posted. Matthias Clasen closed the bug report saying it wasn't a bug but an intended feature. There's really no appropriate words to describe such behaviour Please stop fanning this flame war. You're making it worse and choosing to omit that the bug was reopened after a better argument was made in favor…

> This is trying to paint someone as being stubborn here after they already changed their mind I just pointed it out because as I said, this behaviour is fairly common on the GNOME issue tracker. There are numerous instances but for now, the Inter font issue comes to mind https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2331 > GTK_THEME is mainly a setting for developers, you should probably not be using that Well…

>the Inter font issue comes to mind

I don't see anything objectionable there. Pay particular attention to this response: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2331#not...

Sadly it's not possible to design a GUI that has correct spacing and stays consistent with every font choice. Variable-width fonts don't function like that, widgets sized to a piece of text will have their layout interfered with when the font size changes.

>this is new information because this blog post... Now I'm wondering if this information was intentionally withheld in that blog post.

It wasn't withheld and it's not new information. You're still assuming bad faith and you need to stop this. Notice the part where it says "Compared to GTK 3", if you're familiar with theming GTK3 you should be well aware of the limitations with those themes. Not much has changed there at all. Theming in this way is essentially just hacking the hardcoded colors to be different.

>The contrast between the background and text in dark mode is too high for me

I have the same problem with some apps and I want you to find a solution but I don't understand what this has to do with GTK. That is going to be a general problem with lots of programs or websites that you visit and reskinning each of them is a huge pain and is not guaranteed to work. Doubly so if you use apps that have any other toolkits or use a custom toolkit, the contrast will still be inconsistent. I speak from experience here. Theming is only a band-aid, I suggest at minimum turning the contrast down on your display or permanently enabling night shift mode. That may not make the contrast perfect but it would at least ensure you never see any high contrast text in any app.

Another option may be to pursue something like a gnome extension that dynamically adjusts the screen's gamma and contrast based on the dynamic range calculated from the contents of the windows. That should be a lot more useful and flexible than manually reskinning every app you use. And it works in other situations like for example, if you have two apps side by side and one has a brighter background color than the other, it would notice that's happening and dynamically adjust accordingly so you don't strain your eyes when moving from one app to the other. I think it's misplaced to present this as a theming problem when this sounds like a general usability problem.

If you really do think it's a theming problem then maybe you could campaign for an officially supported low-contrast option, but that would be far away because every toolkit would have to implement it, and old apps will probably not be updated to support it, and it still probably won't work on arbitrary web sites. From a libadwaita perspective the recoloring API may do everything that you need, in my experience it's web sites that are the worst offender when it comes to eye-straining themes.

>I'm fairly certain that this issue won't be entertained

This doesn't make any sense. Both of those issues you linked did get entertained, and the maintainer was still open to patches to fix the font issue.

>that "real" theming API just changes accent colors and wouldn't solve my issue

No, the current draft allows changing all colors: https://gitlab.gnome.org/GNOME/libadwaita/-/merge_requests/3...

>If there are no feasible alternatives to develop GTK4 only apps besides creating your own widgets from scratch

This is the same as it was in GTK3. It hasn't changed at all, the only difference is the library is called libadwaita instead of libhandy. You also don't have to recreate widgets from scratch, that developer appears to be confused. It's certainly possible for an app developer to reskin the libadwaita widgets. But of course, just as in GTK3 they would have to put in the work to write and maintain their own skin, and ship that as part of their app. Or they can just wait for the recoloring API.

Re: The end of the nice GTK button

#652

Earlier quoted context omitted.

Honestly it's what annoys me most about Gnome. I daily drive Gnome 4x but for the love of god stop making design decisions for mobile users. - Why is there a full screen app drawer? - Why does the top bar do nothing and function like my Android top bar? - Why are there no icons in my tray for my background apps (steam, slack, etc)? - Where can I go to see my current running applications? I would love to use a Linux d…

>Why are there no icons in my tray for my background apps (steam, slack, etc)? I understand the other ones but I don't understand this one. The Android tray does exactly this, background icons on the bar are a mobile feature. If you consider the Windows taskbar to be the ideal desktop experience, it doesn't do that, it hides the icons in a menu.

Not sure what you mean here - both MacOS and Windows have icons in the system tray for background applications and it's been that way since before Android was a thing.

Windows does hide excessive icons, which MacOS doesn't do - it's a great way to hide running the pre-installed Skype and Teams at the same time :laugh:

Re: The end of the nice GTK button

#653
post #548

Earlier quoted context omitted.

IntelliJ is really bad about this sometimes. I get that their software does an incredible amount of really tough stuff behind the scenes (which is why I won't be switching any time soon), but God I wish they prioritized input responsiveness over everything else.

Jetbrains really should just update the JDK they use. With a slightly larger max memory setting than default and using at least G1 garbage collector (ZGC for even better results) they would get a buttery smooth editor, but it is configured quite badly by default. Though sometimes they just have threading issues, which won’t be solved by above.

1000% agree. I am disappointed [1] with JetBrains' attitude to this problem. They seem to judge anyone who isn't using the JDK11-based JBR in 2020 as a difficult customer, and do not acknowledge latency/lagging problems on Linux. Mac users then reply to threads like this saying "works on my computer flawlessly, I don't know what you're talking about", until they confess to being Mac users.

I have tried JAOTC up until JDK16 with some IntelliJ products, but I think you are right in saying that the single most effective knob (or two) to twiddle in the default installation is to enable ZGC and increase the heap size.

Yes, I know JBR provide DCEVM builds (which need to be enabled by downloading the JDK and changing the "boot java" setting, ironically)

[1] and by that I mean "fuming"

Re: The end of the nice GTK button

#654
post #647

Earlier quoted context omitted.

Honestly it's what annoys me most about Gnome. I daily drive Gnome 4x but for the love of god stop making design decisions for mobile users. - Why is there a full screen app drawer? - Why does the top bar do nothing and function like my Android top bar? - Why are there no icons in my tray for my background apps (steam, slack, etc)? - Where can I go to see my current running applications? I would love to use a Linux d…

I've said this on Reddit before, but the current Gnome is excellent for someone who loves it and only needs a few changes to make it work for you. Personally, I like how everything works (you could also say that this is some form of Stockholm Syndrome, ha ha). I like not having anything distracting from The answer for most of these is "there's an extension for that" > - Why is there a full screen app drawer? https://…

I should preface that I love Gnome and am excited by the future. My criticisms come from a place where I want to see it be the best experience possible on desktop, and the obvious choice when it comes to choice of DE.

> there's an extension for that

Yeah this is fair, sadly it's not a satisfying solution. Extensions are often not supported on the latest version of Gnome for some time and even then, there's an issue of discoverability for both experienced and new users.

I understand the desire for customizability, but I'd prefer my desktop environment come out of the box tailored to facilitate a desktop experience.

> https://extensions.gnome.org/extension/6/applications-menu/

I am happy there is an alternative however this has the side effect of removing the "Hit the super key then type a search query" workflow. Ironically, an actual application menu is nearly entirely useless for me outside of niche cases. I have been using start menu search and spotlight for years at this point - gnome's activities overlay is just that with extra animations.

> I rarely have to do this (for me it's almost always IDE, Terminal, Browser), but "alt-tab then escape"

This is exactly how I use my desktop too.

In MacOS I used virtual desktops so heavily to organise this and it was an _incredible_ workflow.

Monitor 1, desktop 1 is terminal, desktop 2 is IDE. Monitor 2 desktop 1 is debugging browser, monitor 2 is slack, music and misc. Flicking between the desktops, everything is positioned exactly where I want it to be and there is no guessing what is going to be shown.

I only started using Alt+Tab after coming back to Windows and now again on Gnome. Alt tab is a bit too guess-y for my taste. If you have multiple windows of the same type (e.g. browser and seperate browser debugger) open, what does Alt-Tab open?

In Gnome, rather than using virtual desktops, I hit the super key and pick the application out of the application mosaic because it's deterministic and faster than Alt-Tab

> I am not sure what this means

Swipe down from the top left and you have applications, swipe down from the top right and you have quick settings. Clock is in the center. The elements are responsive. It looks and functions like the top bar for a mobile device.

The top bar doesn't have application shortcuts, it doesn't show you active background applications.

If you look at the effort that all desktop experiences have made to make their top bar/desktop bar useful, you will see distinct differences when compared to mobile operating systems that have to be cognizant of their use of space.

MacOS has a global menu, taskbar tray, taskbar add-ons (for cpu usage, international clocks, etc) and applications are opened via spotlight (Albert) search.

Windows has shortcuts, a start menu with search, and a taskbar tray, along with lots of options to administer the computer when you right click the start bar.

Gnome offers a horizontally space efficient mobile-optimised top bar and a full screen, mobile style application picker. Application search and the open apps mosaic are the saving factors of it

Re: The end of the nice GTK button

#655

Earlier quoted context omitted.

>Why are there no icons in my tray for my background apps (steam, slack, etc)? I understand the other ones but I don't understand this one. The Android tray does exactly this, background icons on the bar are a mobile feature. If you consider the Windows taskbar to be the ideal desktop experience, it doesn't do that, it hides the icons in a menu.

Not sure what you mean here - both MacOS and Windows have icons in the system tray for background applications and it's been that way since before Android was a thing. Windows does hide excessive icons, which MacOS doesn't do - it's a great way to hide running the pre-installed Skype and Teams at the same time :laugh:

Normally I'm a Mac/Linux user, but last time I tried Windows it hid all the icons by default. They used to show them in older versions but they do not anymore, probably because everyone including the OS vendor itself uses it as a dumping ground for product tie-ins and clutter like that.

Re: The end of the nice GTK button

#656
post #358

I'm going to take a risk here and say that I'm a designer who generally likes flat design. I see a lot of hate here against flat design, and it makes sense. A lot of designers abuse it, making their UIs ambiguous. It's probably true that if flat design was never conceived, UIs would be less confusing on average. But it's clearly possible to do flat design well. iOS is mostly flat, but it's quite beautiful and user fr…

What do you think of the iOS podcasts app then? I have no idea of where to press to view details of a podcast, vs to start playing it. On the main page, the black text starts playing a podcast, and the purple text shows details. Further into the app, the purple text will start playing while the black text will view details. While playing, neither the purple nor black text do anything (they act as title/subtitle). Cli…

I never used the podcasts app before but just gave it a try. I can't seem to reproduce what you're describing. On the top-level pages ("Listen Now" and "Browse"), only the purple play button plays the podcast for me, clicking the purple text (the duration of the podcast) does nothing, and everything else opens the detail view for the podcast. Pictures always open detail views. What version of iOS are you on? I'm on 15.3.1.

Re: The end of the nice GTK button

#657
post #4

All of this is pretty much how I feel on the matter, too. GTK3's interface was a really lovely blend of skeuomorphism and more abstract widgets that came together to make a really unique experience. Even if it didn't work in every context, I appreciated how well it worked for less complicated applications and making great-looking, device-agnostic GUIs. Cawbird was a wonderful native Twitter app made possible with GTK…

I'm sorry but most of this comment is a lot of nonsense. You're certainly allowed to disagree, but when you approach people with comments about their own work that are factually wrong, you'll get corrected. You're confusing those two things and taking it personally and that's a terrible mistake. Don't do that, it hurts you and it hurts everyone else around you. Just to clear up any confusion: - People have been worki…

Oh good, I always look forward to condescending GNOME apologists to reply to my comments. Let's disseminate this comment and use it to help understand why me, OP, and hundreds of other people in this thread are frustrated with the state of GTK and GNOME right now:

> People have been working on the font glitch for the last ten months. It's not easy and the solution is not straightforward.

Then why was it working fine in GTK3? Sounds to me like someone made a breaking change, and didn't anticipate the consequences. The solution is to roll things back or wait until this new implimentation is fixed to push the code to actual users. Unfortunately, the GNOME developers are more interested in scorching earth than they are in maintaining a well-made desktop.

Oh, and it's not because it's a "hard issue" to fix, it's because nobody made a PR for several months. Apparently none of the core maintainers considered it much of a problem.

> The choice of whether to allow themes or not belongs to the app developer. This hasn't changed at all from GTK3.

No, it doesn't. There is not a single application written with GTK3 that can stop me from changing it's theme. I'm sorry if you disagree, but that's just an outright lie (I say this as someone who actually writes GTK3 code).

> The stylesheet isn't forced at all, when you develop an app you can configure your styles to always override the platform theme.

...and I can override it again. Any questions?

> Pinning your packages to GTK3 in protest doesn't help you.

Correction, it doesn't help you. It keeps my applications looking just fine.

> It doesn't make a difference to the GTK developers at all.

That seems to be a recurring trend when negotiating with GNOME/GTK developers. I don't care, I'm perfectly satisfied taking matters into my own hands since they'll ignore me anyways.

> If you want to make use of some GTK4 features eventually, it would be best to start working with it and getting your issues sorted out now.

I don't. What features are there, right now? Worse text rendering? Less accessibility features? More extreme, abrasive maintainers and fewer people writing code? A worse native experience, more middleware and less software freedom? Less native packaging? More Flatpak bloat? Worse touchscreen compatibility and an increasingly fractured codebase? More broken custom widgets that don't adhere to the GNOME HIG? An uglier, flatter overall design philosophy? Militant users and developers who hunt people down when they express their feelings about software they used to use on Hacker News?

Worse looking buttons?

You can keep it.

> You can ignore what the other app maintainers are saying, that has no effect on you.

I don't even know what you're trying to say here, but it sounds like doublespeak. This entire comment does, actually, and I'm not sure what your goal was by posting this. Nothing you've said accurately describes the reality of using GTK applications, it's more like an idyllic reflection of what people think the ecosystem should look like, ignoring everyone who doesn't throw away their current workflow to live in GNOME-land. Unless you start acknowledging the pragmatic reality of GTK's end-users, GNOME will continue to hemorrhage maintainers and stir up unnecessary and counterproductive drama for the sake of a few people's ego. And to think that what I said was nonsense, get a grip...

Re: The end of the nice GTK button

#658

I'm going to take a risk here and say that I'm a designer who generally likes flat design. I see a lot of hate here against flat design, and it makes sense. A lot of designers abuse it, making their UIs ambiguous. It's probably true that if flat design was never conceived, UIs would be less confusing on average. But it's clearly possible to do flat design well. iOS is mostly flat, but it's quite beautiful and user fr…

> Why do we need to remove unneeded clues, you ask? To make room for more important things. If Instagram was littered with gradient buttons and blue underlined links, they'd draw attention away from the real content, the pictures. If Figma had too much personality, it'd influence users' designs. This is an oversimplification and not always correct in all situations. Take the original article as an example. How did 3D…

I should have addressed the original article. As a sibling commenter mentioned, I didn't say all flat designs are good, quite the opposite. That to-do list design is very mediocre.

A desktop to-do list app that I think is super well done is Reminders on MacOS. Its basic functionality is immediately intuitive, and it gives love to power users too with its secret ability to parse natural English (e.g. "laundry at 9") for adding notification times.

Re: The end of the nice GTK button

#659

I'm going to take a risk here and say that I'm a designer who generally likes flat design. I see a lot of hate here against flat design, and it makes sense. A lot of designers abuse it, making their UIs ambiguous. It's probably true that if flat design was never conceived, UIs would be less confusing on average. But it's clearly possible to do flat design well. iOS is mostly flat, but it's quite beautiful and user fr…

> If it's not obvious, it's probably not a critical feature, just a nicety for those who discover it. That's a really bad way to go about usability. It's pretty frustrating you're looking for a feature to have to hunt for it like you're playing a point & click game. At that point I wouldn't even call it a feature, it's an Easter egg.

This is an interesting/surprising reply to me, so I've spent some time thinking about it.

The problem is that design is always a compromise between discoverability and post-discovery efficiency. Consider the swipe-left-to-delete pattern. It's not discoverable, but once you've learned it, you wouldn't want it any other way. Designers sometimes compensate for the lack of discoverability by adding a slower but more discoverable way of doing the same thing, like an "Edit" button that reveals a delete button on every item. Thus making swipe-left-to-delete a non-critical feature, and a nicety for those who discover it.

Another example is clickable usernames. We have an unspoken expectation that clicking a username in any app takes you to the user's profile. This expectation is so ubiquitous that apps (like HN) don't provide any additional indication that usernames are clickable. Imagine if every username on every app was a full blown bordered, textured button. Even someone with zero design sense would feel something's off.

It simply isn't possible to maximize both discoverability and efficiency at the same time. Every feature needs to decide who it wants to cater to and who it's comfortable leaving behind.

Re: The end of the nice GTK button

#660

Earlier quoted context omitted.

I'm sorry but most of this comment is a lot of nonsense. You're certainly allowed to disagree, but when you approach people with comments about their own work that are factually wrong, you'll get corrected. You're confusing those two things and taking it personally and that's a terrible mistake. Don't do that, it hurts you and it hurts everyone else around you. Just to clear up any confusion: - People have been worki…

Oh good, I always look forward to condescending GNOME apologists to reply to my comments. Let's disseminate this comment and use it to help understand why me, OP, and hundreds of other people in this thread are frustrated with the state of GTK and GNOME right now: > People have been working on the font glitch for the last ten months. It's not easy and the solution is not straightforward. Then why was it working fine…

>I always look forward to condescending GNOME apologists to reply to my comments.

Stop. This is nonsense and adds nothing to the discussion, it's like if I started off immediately dismissing you as a "GTK3 apologist" or something like that. If you have a history of getting hostile replies, your confrontational attitude is directly the reason why, and it's something only you have the power to change.

>Then why was it working fine in GTK3? Sounds to me like someone made a breaking change, and didn't anticipate the consequences.

Yes, that's what happened. The whole renderer was changed to a hardware accelerated one.

>The solution is to roll things back

That's not possible because the renderer touches the entire project. It's probably the main feature of GTK4.

>Unfortunately, the GNOME developers are more interested in scorching earth than they are in maintaining a well-made desktop.

Please avoid these comments. This is a pretty meaningless generalization and adds nothing to the discussion. Just like any large project, there are some GNOME developers that focus on new features and some that focus on maintenance.

>Oh, and it's not because it's a "hard issue" to fix

No, this is extremely wrong. The issue actually is that hard. If you are a font rendering expert and you believe the issue is easy to fix, then please submit your own PR. I'll be the first in line to try it if you do.

>There is not a single application written with GTK3 that can stop me from changing it's theme. I'm sorry if you disagree, but that's just an outright lie (I say this as someone who actually writes GTK3 code).

No, this is also extremely wrong. Any external configuration method you use, a GTK3 application can override it or disable it. I'm not disagreeing and this isn't a lie, this is an actual fact of the toolkit. Feel free to list any of them and I'll explain how it can be trivially disabled.

>...and I can override it again.

I'm sorry, now it sounds like you're agreeing with me.

>Correction, it doesn't help you.

No, this has nothing to do with me. You sound like you were interested exploring GTK4 at some point, if you're still interested, then you'll eventually have to take steps to address the issues. If you don't want those then I don't see what your issue is, your original comment seems to be making assertions about nothing in that case.

>That seems to be a recurring trend when negotiating with GNOME/GTK developers.

This sentence right here illustrates the main mistake you've made. GTK is an open source project, by choosing to use it you're not entering in any "negotiation" with anybody. It's a take it or leave it proposition, and that's the way it's always been.

>I'm perfectly satisfied taking matters into my own hands since they'll ignore me anyways.

In the long run, that approach isn't sustainable. I find that most open source projects including GTK or Qt or any of those other toolkits won't ignore you if you have something useful to add or can take real steps towards correcting the issues that you're having. But being combative and approaching everything as a "negotiation" is the exact wrong thing to do and is probably the root cause if you find yourself getting ignored. Don't do that. You are making everything worse for yourself.

>What features are there, right now?

As previously mentioned, there is the hardware renderer with improved performance. There is also the multimedia framework and the new, faster list models. Those are the big features that I know of. It's absolutely fine if you don't want any of those, by all means stay on GTK3. But if you do want those eventually, then you'll need a plan to migrate.

>ignoring everyone who doesn't throw away their current workflow to live in GNOME-land

What I was saying is that those people don't have to affect you. You can use GTK3 or GTK4 or whatever without dealing with them.

>Worse text rendering? Less accessibility features? More extreme, abrasive maintainers and fewer people writing code? A worse native experience, more middleware and less software freedom? Less native packaging? More Flatpak bloat? Worse touchscreen compatibility and an increasingly fractured codebase? More broken custom widgets that don't adhere to the GNOME HIG? An uglier, flatter overall design philosophy? Militant users and developers who hunt people down when they express their feelings about software they used to use on Hacker News?

To hit this in order: The old text rendering can be restored with a flag. The accessibility is actually improved because of the removal of Atk which had some major issues. The maintainers are the same people and it's about the same amount of people writing code. There isn't any more middleware than GTK3. The "software freedom" is the same, it has the same license. Nothing has changed with native packaging, Flatpak is completely optional. The touchscreen compatibility has actually gotten better. The situation with custom widgets hasn't changed from GTK3. The design philosophy in GTK itself hasn't changed, that only affects libadwaita. I'm happy for you to express your feelings but this whole paragraph and some of your previous comment are unhinged and unreasonable.

>Unless you start acknowledging the pragmatic reality of GTK's end-users, GNOME will continue to hemorrhage maintainers and stir up unnecessary and counterproductive drama for the sake of a few people's ego.

This kind of sounds like a threat, you should delete your comment or reword this. It's also pretty unhinged and unprofessional. Also you appear to be under the false impression that I'm a GNOME or GTK developer. I'm just another app developer, in the same boat as you.

Post reply on HN