Re: [Gimp-developer] GIMP needs a new color management person

2015-05-05 Thread A. da Mek
2.5.2015 v 23:21 Elle Stone: I use hacked versions of high bit depth GIMP for image editing - four of them, one for each color space that I use - and I'm very much enjoying finally being able to edit high bit depth images with masks and layers A question from a curious laic: Why four versions a

Re: [Gimp-developer] Export instead save directly

2016-02-28 Thread A. da Mek
> Therefore, I will > probably still to work with the 2.6.11 version on. > For this reason I will Gimp 2.8.16 uninstalled. I suppose that many users returned back to 2.6 for this reason. There should be a clear warning that saving is still possible, only it was renamed to "overwrite". IMO, the i

Re: [Gimp-developer] Export instead save directly

2016-02-29 Thread A. da Mek
01234567890123456789012345678901234567890123456789 >> I suppose that many users returned back to 2.6 for this reason. >> There should be a clear warning that saving is still possible, only it was renamed to "overwrite". >> IMO, the intention of the authors was to educate the users and remind the

Re: [Gimp-developer] Export instead save directly

2016-02-29 Thread A. da Mek
But it does be a shame that many of us were forced by this unfortunate change to revert to 2.6. Many of who? There is no indication whatsoever that the group of people who reverted to 2.6 is any large. How can we know how many of them there is, if they simply downgrade to 2.6 and do not bothe

Re: [Gimp-developer] Export instead save directly

2016-02-29 Thread A. da Mek
How can we know how many of them there is, if they simply downgrade to 2.6 and do not bother to discuss it somewhere? One of the first things I learned when I was in the marketing and PR business is that unhappy customers do complain. A lot. A producer of a commercial product gets the complain

Re: [Gimp-developer] Export instead save directly

2016-02-29 Thread A. da Mek
If there were a vote, I'd vote to keep it the new way (and I process a very very high volume of product photos with GIMP). But those are two different questions: 1) Whether to use the "new" interface or the "old" one. This was already decided long ago. 2) If the users, accustomed to the "old" i

Re: [Gimp-developer] Export instead save directly

2016-02-29 Thread A. da Mek
And that msg has been explained *here* ad nauseam. Please take a moment to view the list archives. How many of common users do you suppose to be subscribed to the developer list? To say nothing of reading archives four years back. Imagine a common user who is not an expert on bitmap editing, a

Re: [Gimp-developer] Export instead save directly

2016-02-29 Thread A. da Mek
As for sticking with 2.6 and refusing to upgrade: really? Well, it's your choice, of course, but there's no way I'd stick with an older version just because of something that's so easily worked around But what I am trying to explain is that they do not know that it is easily worked around. They

Re: [Gimp-developer] Export instead save directly

2016-02-29 Thread A. da Mek
> I still think that there should be a file->import as it's really hard to tell people JPEG and PNG are not native to GIMP when it opens them just fine. Yes, I had the same thought; the current system is asymmetric. If it is insisted that non-xcf files cannot be saved and are exported instead,