I was quietly working with GIMP when I had the brilliant idea of \u200b\u200bcreating a animated GIF. It's really easy, just go to layer frame and then choose save as GIF specifying a couple of options.
Everything went well and Picture is perfect. Why mention this? Well, because when I was saving the file GIMP gave me the following message (I do not know if error, warning, information or joke):
is a perfect example of how NOT to make a message:
Evita - descriptive titles such as "GIMP Message." Go man, thanks, I had not realized it was a message or working with GIMP.
- If you're describing a bug, make sure you tell where it comes from. I worked with a single image, so it was not hard to find, but if I have more (which would be normal) that the "GIF image" would be more obvious that an identifier.
- If you give a choice, do not say after the jump you because it's stupid. If you know that a delay should be included because otherwise the CPU will be consumed (in the fires of Mordor by the message as he paints it) why the hell let me tell you not to put delay if you're going to go after me?
- is true that users do not want to hear unfamiliar technical vocabulary. The problem is that writing a technical message slang makes it no less technical, but funny for programmers. A "CPU-sucking animation" is as clear as say "no algorithm polynomial time complexity, we, or flowers.
GIMP can be a good product, but usability should have it as developed as Scooby-Doo value.
0 comments:
Post a Comment