101–110 of 271 posts
Earlier quoted context omitted.
Krita. I think it's way better than GIMP
Krita is a painting app comparable to Corel Painter. You can't compare it with GIMP or Photoshop.
Earlier quoted context omitted.
I haven't really used Blender (but know Maya, Houdini, Nuke very well). I think "pro" software (a wiggly term) tends to require a non-standard UI (however, I do miss when Photoshop used the base OS' UI). Pro tools end up being a bit of their own window management and filesystem that overlaps with the OS. Their decisions are part of the ergonomics of being productive in the app. I remember when macOS started adding sm…
Microsoft also worked on WinFS as a new file system based on relational database principles. https://en.wikipedia.org/wiki/WinFS
Earlier quoted context omitted.
It's funny because GIMP is one of the tools I hate the most. It's really hard to describe how quickly I want to say no to just about everything that it does. I'm quite open[0] but I'd rather write perl script with imagemagik than use gimp. [0] i can love both emacs and vi and even ed, I've used just about any 2d/3d program ever
Gimp has script fu / python / scheme. It is quite capable of automating and generating images. Gimp is the kind of software you may hate at first but then start to love it for how extensible friendly it is.
This takes a few lines of calls to imagemagick/gm or ~10 lines of python + Pillow.
Do you have any resources how to do this in GIMP?
After googling for a good while, I could not for the life of me figure out how to even get started with this.
I don't want to write an extension for GIMP - I want to use GIMP like I would an image manipulation library.
Otherwise I'm generally very frustrated every time I try use it. It wasn't that way in my teens, back then I would happily spend entire evenings noodling around in it making graphics for web pages and demos/games.
Nowadays just throwing text on a layer makes me want to throw my laptop. That custom widget is so useless, maybe I should try a newer version as I'm still on 2.8 here.
For me it's a case of being the worst open source image editor, except for all the others. The scripts always seem broken, the UI was a mess for a while on a Mac. The multi windowed system was great if the windowing manager expected that sort of thing and terrible otherwise. Ufraw integration seems an awful way of getting to edit raw files and I go years at a time without being able to get it working on a Mac. But it…
Yep. It's cantankerous but gosh darn it, the field lacks something better.
GIMP's name comes from Pulp Fiction. > It took us a little while to come up with the name. We knew we wanted an image manipulation program like Photoshop, but the name IMP sounded wrong. We also tossed around XIMP (X Image Manipulation Program) following the rule of when in doubt prefix an X for X11 based programs. At the time, Pulp Fiction was the hot movie and a single word popped into my mind while we were tossing…
My twitter account was suspended until I removed a post with the word gimp in it. It was not an abusive post.
I have never found GIMP very easy to use but I have respect for anyone that can work with the PSD file format. I wonder which spec they are using today. It seems to become really tough after the 1997 spec.
Now they've reduced themselves to "breaking" compatibility every couple of months to try to get people to maintain their software lease.
Despicable trash.
GIMP is such a strange tool. I actually have used it, semi-frequently - since the 90s! The overall experience of using it has only changed a little in that time. And it gets the job done. I guess that makes it successful! What else has been so stable? But of all the software I have ever used, GIMP is the most difficult to learn. I memorized a few tutorials, this must have been around Y2K, to do the a couple things. A…
Adding a second UI to the codebase (with a friendlier, less conflict inducing name) would be a fantastic addition to the project. Something along the lines of a cooperative fork, I suppose, focused on exposing a minimal set of features but keeping the underlying image processing models. Fewer buttons. Distilled UI. Having a single rapid workflow for saving an edited PNG. [...and this is almost exactly what Glimpse is…
You mean instead of two rapid workflows?
1. File -> Overwrite Existing .png.
First time it is used, there is prompting. After that, no prompting. Has no hotkey.
2. Or use Export As, which has a Shift-Ctrl-E hotkey.
The first time you use Export As, there is prompting. But after the first use, the "Overwrite Existing .png" menu item (for workflow 1) disappears from the File menu and is replaced by "Export To .png". This action has no prompting at all, and has Ctrl-E as the hot key.
Workflow 1 has less initial prompting than 2; it goes straight to the Export dialog (for setting parameters) without prompting for a filename or overwrite confirmation; it's good if you're editing many images and saving just once.
Earlier quoted context omitted.
Krita is a painting app comparable to Corel Painter. You can't compare it with GIMP or Photoshop.
Doesn't matter. People have work to do with tools, not list out all the features. If Krita works for the person, there's no reason to use Gimp or Photoshop.