181–190 of 204 posts
Earlier quoted context omitted.
True but the leap from GTK2 to GTK3 is a lot bigger than from GTK3 to GTK4. I'm not sure when the "port" to GTK3 started, but if it was from before GTK4 was a thing, it makes sense that they wanted to finish the GTK3 stuff first.
> I'm not sure when the "port" to GTK3 started Probably more than 10 years ago.
Earlier quoted context omitted.
i can remove network access capabilities from a desktop app after it is installed. i can't easily do that with an app running in a browser. likewise monitoring and detecting network access per application is easy. tracking down which browser tab is making which network connection is a lot harder.
You are either confused about something, or you're simply refusing to engage with reality. > Any nefarious thing a browser-based app can do, a local program can do, too, [or worse!]
for a desktop application, at least on linux there are tools available to further constrain its access to the system by monitoring its activity, removing capabilities or placing the app in a container or even a VM. (VM are available on windows and mac too, but i don't know about other features)
to contain a browser app in this way i would have to run a contained copy of the browser as a whole, and i still can't easily limit network access.
further, almost all desktop applications on linux come from a trusted source or a trusted intermediary and have undergone at least some kind of review, whereas browser applications can be reviewed but it is non-trivial to ascertain that i am running the exact same version that was reviewed.
it is possible, and it is my hope for all this to change. i actually believe browser applications are a good idea, but the ability to audit, and constrain browser applications needs to improve a lot for that to happen.
Earlier quoted context omitted.
There were no thumbnails because no one wrote the necessary infrastructure before some one actually did. One person did most of the work and there were no other problems than actually writing code.
Okay, so what were all the other people doing? If it's one person's worth of work (as I suggested), and there was at least one person working on GIMP, why did they not do it? The fact that it was easy to do doesn't explain why it didn't happen. If anything, it makes it more mysterious. Unless you are genuinely telling me that there wasn't a single person working continuously on GTK for 20 years. It seems to me that t…
Earlier quoted context omitted.
There were no thumbnails because no one wrote the necessary infrastructure before some one actually did. One person did most of the work and there were no other problems than actually writing code.
> There were no thumbnails because no one wrote the necessary infrastructure before some one actually did. We are talking about GTK 3, right ? " Why not be honest and resign yourself to the fact that version 0.8 is followed by version 0.8, which is then followed by version 0.8? " jwz
Earlier quoted context omitted.
Many years ago, I lost my work because of this "unique UI" and pledge never to use Gimp again, unless its behavior changed. When you open a non-Gimp file, for instance a PNG, and you want to update the source file, you need to "export" to PNG. And if you close the tab, Gimp warns you that your work isn't saved, because it hasn't been saved in its native xcf format. There is no way to know if the work has been saved t…
This is standard behavior in pretty much any kind of art/content creation app. You have a project file which can be saved and reopened in the app, saving the state of the layers/effects/etc to be edited later, and can “export” a final render to a specific format for your medium. Image/video editing, digital audio workstations, 3D-modeling programs, they all behave like this, for good reason since it usually takes a l…
I started using GIMP around 2003 as a small child, and I remember being hyped for 3.0 and non-destructive editing even back then. I'm in my thirties now. Slow and steady wins the race. Congrats to the GIMP team, can't imagine the catharsis they will experience when 3.0 officially drops.
I remember getting a copy of the Motif-based GIMP for AIX sometime in 1996 or so.
I used GIMP earlier today. So thank you all involved! After so many years I keep going back to it for quick edits.
After so many years I keep going back to it for quick edits.
Earlier quoted context omitted.
I fell for this before. Wasted a few weeks' free time adding thumbnails to the GTK file chooser, only to find out that the library itself has bugs which they refused to fix that make it difficult to do. Now I just have a patched version installed locally. The only way to improve these projects is to change how they're managed, which you can't do with a patch.
There is thumbnails support in the GTK4 file chooser now. That probably required shitloads of fixes in GTK, but now it works. The way to change projects is to write good code and work together with the other devs that made something you wanted to contribute to and then improve it together.
GIMP doesn't use GTK4.
Earlier quoted context omitted.
To clarify, I wasn't talking about the developers' priorities as a whole. I personally get inspiration for "big" projects to work on by scrolling various platforms and seeing what the most frequent complaints are, but that's not how development decisions are made. And I can promise you, non-destructive editing was repeatedly requested by users, not just software developers. I have also seen a large number of users ha…
> compared to the larger number of users asking for more CMYK support, shape tool, built-in Resynthesizer etc This is because people with the complaint about text tend to open the software, see how bad moving text is, then close it and never open it again. They aren't the ones going onto your forums to complain. And when they do the bug stays open for 8 years (and counting) with the best response currently being to t…
more likely they just didn't feel as strongly about it as you do. difficult to move text is an inconvenience. and just to be clear, i have experienced the problem myself and got annoyed by it, but never annoyed enough that i would report an issue or look for alternative software. but lack of CMYK support or non-destructive editing are showstoppers that can't be worked around.
Earlier quoted context omitted.
Okay, so what were all the other people doing? If it's one person's worth of work (as I suggested), and there was at least one person working on GIMP, why did they not do it? The fact that it was easy to do doesn't explain why it didn't happen. If anything, it makes it more mysterious. Unless you are genuinely telling me that there wasn't a single person working continuously on GTK for 20 years. It seems to me that t…
The people who are doing the work, or a paying for the work, on GTK think that other tasks are more important or fun to do than the tasks you wish should be done. You might think that they are wrong and that other features are more important than a modern accessibility stack or whatever else the GTK devs have been doing, but the only way to change that is to actually engage in that project.