4 ms·

I'm confused how that's related, the issue you're talking about is in the file manager, not GTK. I don't believe any of the primary nautilus maintainers are als

I'm confused how that's related, the issue you're talking about is in the file manager, not GTK. I don't believe any of the primary nautilus maintainers are also primary GTK maintainers, at least not anyone in that issue. (Please correct me if I'm wrong about that) But, since I've said this before, I'll say it again: If the other people who use the toolkit want to have input, they need to contribute more. AFAIK there are zero non-GNOME devs working full time on GTK. I hope that changes, i.e. I hope the other desktops can find funding to send more designers and developers to collaborate with the GNOME people so everyone can have their say. That is the real issue here, I think it's incorrect to suggest that anything was "taken." It's open source, there isn't anyone who's going to take the code away from you unless you blatantly violate the license.

traverseda 6y ago
Maybe your distro patches it, but last I checked typeahead wasn't available in GTK-file-picker. It uses recursive search instead. https://gitlab.gnome.org/GNOME/gtk/-/issues/839 https://gitlab.gnome.org/GNOME/gtk/-/issues/839 Also: https://bugzilla.gnome.org/show_bug.cgi?id=748672 https://bugzilla.gnome.org/show_bug.cgi?id=748672 The GTK devs were saying that they wanted a flag shared between nautilus and the file picker that would enable/disable typeahead. Unfortunately nautilus refuses to implement that flag, which I think means we're all still relying on forks for that feature. So you're not really allowed to solve one without solving the other, last I checked. So yeah, the issues is very much in both, and you can't solve the issue with GTK without solving it in Gnome.
- cycloptic 6y ago
  >So you're not really allowed to solve one without solving the other The final comments from the developer directly contradicts this claim: >I'd be happy to review a merge request that added the ability to disable recursive search in the file chooser using a GSettings option ... I was thinking more along the lines of having a key in the file chooser settings schema that would be observed by Nautilus. The idea there is that the key should be in a standard location read by nautilus (or some other GTK file manager) if it also decides to implement that feature. Edit: I also should note that it appears there was not even initial consensus about this, the other GTK developer seemed to be skeptical at first.

traverseda 6y ago

Maybe your distro patches it, but last I checked typeahead wasn't available in GTK-file-picker. It uses recursive search instead. https://gitlab.gnome.org/GNOME/gtk/-/issues/839 https://gitlab.gnome.org/GNOME/gtk/-/issues/839 Also: https://bugzilla.gnome.org/show_bug.cgi?id=748672 https://bugzilla.gnome.org/show_bug.cgi?id=748672 The GTK devs were saying that they wanted a flag shared between nautilus and the file picker that would enable/disable typeahead. Unfortunately nautilus refuses to implement that flag, which I think means we're all still relying on forks for that feature. So you're not really allowed to solve one without solving the other, last I checked. So yeah, the issues is very much in both, and you can't solve the issue with GTK without solving it in Gnome.

cycloptic 6y ago
>So you're not really allowed to solve one without solving the other The final comments from the developer directly contradicts this claim: >I'd be happy to review a merge request that added the ability to disable recursive search in the file chooser using a GSettings option ... I was thinking more along the lines of having a key in the file chooser settings schema that would be observed by Nautilus. The idea there is that the key should be in a standard location read by nautilus (or some other GTK file manager) if it also decides to implement that feature. Edit: I also should note that it appears there was not even initial consensus about this, the other GTK developer seemed to be skeptical at first.