On Mon, Mar 14, 2016 at 6:06 AM, john smith wrote:
> As long as people are putting their hands up
There is no vote on this, and there won't be one.
> Is it possible to write a plugin that re-maps core shortcuts
Edit -> Keyboard Shortcuts
> and changes default menu layouts etc?
The can't be suc
As long as people are putting their hands up, I never save in xcf and
would prefer a workflow that was open, edit, save in same format.
However, rather than try to change the core code to appease those with
a similar thought, I would like to know if it is possible to change
this behaviour with a p
Sounds good to me. I'm more than capable of choosing the correct file
extension(s) and settings for myself. I think it's beneficial to have those
settings already intelligently defaulted to when saving. I believe it will
save some clicking in most workflows. Also good that it can be turned on
and o
> Am 01.03.2016 um 15:05 schrieb C R :
>
> If Save intelligently determines the file format that is most likely to be
> used to save, Export should not be necessary. Just "Save" and "Save As"
> would suffice.
>
That's nearly exactly what I did with my patched version on
http://gimp.lisanet.de
I
If Save intelligently determines the file format that is most likely to be
used to save, Export should not be necessary. Just "Save" and "Save As"
would suffice.
We could use the "multi layer" & "layer outside layer boundaries"
convention to suggest that the user save to xcf, as normal to preserve
Am Montag, 29. Februar 2016, 23:57:10 schrieb C R:
> > That would be terrible. Users not understanding the concept would suddenly
> > be
> > facing images where they can just save to JPEG while others can't, but PNG
> > is
> > still enabled (because they somehow added an alpha channel), and even
>
Hello Pavel,
On Mon, 29 Feb 2016 22:21:49 +0100 pa...@pamsoft.cz wrote:
> 2. Do you know some photo/image viewer which can display xcf files? I am not
> aware of any. Maybe there is some, but it is not important at the moment. The
> important message is, that poeple (I appologise to Alex for s
>
>
> That would be terrible. Users not understanding the concept would suddenly
> be
> facing images where they can just save to JPEG while others can't, but PNG
> is
> still enabled (because they somehow added an alpha channel), and even other
> images support XCF only (maybe because the layer is
Am Montag, 29. Februar 2016, 23:07:57 schrieb C R:
> It would probably be okay to use "Save" in a case where there is not much
> data to be lost by doing so. Like if you flatten the layered image first.
> If you've done that without exporting anything, it's pretty safe to assume
> you wouldn't lose
On 03/01/2016 12:07 AM, C R wrote:
> To sum up:
> Multiple layers = Save = .xcf
> Single layer = Save = .jpg/.png/ imported file format
This would overload the Save action again - something we explicitly got
rid of by separating Save and Export.
Save = XCF
Export = Everything else
Simple as
Am Montag, 29. Februar 2016, 22:21:49 schrieb pa...@pamsoft.cz:
> Hello,
Hi.
[...]
> 2. Do you know some photo/image viewer which can display xcf files? I am
> not aware of any. Maybe there is some, but it is not important at the
> moment. The important message is, that poeple (I appologise to A
It would probably be okay to use "Save" in a case where there is not much
data to be lost by doing so. Like if you flatten the layered image first.
If you've done that without exporting anything, it's pretty safe to assume
you wouldn't lose anything you were worried about by saving to the imported
Hello,
OK, once the discussion is here again, I will also add my 2 cents. There
are definitively more than 2 people disapointed by this change. I am the
third one. I've got somehow used the new concept, so I don't complain
and don't want to get back the former UI, but let me explain two
impor
Hello,
On Mon, 29 Feb 2016 19:31:00 + "A. da Mek" wrote:
> > 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
> 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,
On Mon, 2016-02-29 at 18:22 +, A. da Mek wrote:
> >
> But what I am trying to explain is that they do not know that it is
> easily worked around.
A possibility might be to have a link on the save dialogue, "export to
non-GIMP-native formats" that gets rid of the save dialogue and brings
up e
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
On 02/29/2016 12:37 PM, Alexandre Prokoudine wrote:
Well, how many of them do you expect to read release notes?
P.S. On of the ideas we had for future point releases (3.0, 3.2 etc.)
is a dialog that runs the first time the new version is launched and
guides users through major changes.
That so
On Mon, Feb 29, 2016 at 8:29 PM, A. da Mek wrote:
> How many of common users do you suppose to be subscribed to the developer
> list?
Well, how many of them do you expect to read release notes?
P.S. On of the ideas we had for future point releases (3.0, 3.2 etc.)
is a dialog that runs the first
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
Hi all,
On Mon, 29 Feb 2016 13:15:49 +
C R wrote:
> Also, the old way of forcing a user to bypass a warning message every time
> he/she wants to save to the loaded format is (workflow-wise) much worse
> than just learning the "Export" hotkey imho. Also, it's clearly not a
> "flaw"; it's not
* A. da Mek [02-29-16 10:20]:
> >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.
Alexandre Prokoudine writes:
> >Also, if you think that changes of this sort should be officially
> >talked about in any other way than they already have been, I'm
> >listening.
A. da Mek writes:
> A warning on the download page.
> A tip of the day (if possible the first one).
The Save-Export spl
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
On Mon, Feb 29, 2016 at 5:16 PM, wwp wrote:
> A pain in
> the *ss to deal w/ user support sometimes, a bigger pain when users
> come from Windows userland (or other kind of dumb users).
I don't think this kind of generalization is really appropriate.
> The other very important (to my eyes) point
Hello,
On Mon, 29 Feb 2016 13:15:49 + C R wrote:
> Also, the old way of forcing a user to bypass a warning message every time
> he/she wants to save to the loaded format is (workflow-wise) much worse
> than just learning the "Export" hotkey imho. Also, it's clearly not a
> "flaw"; it's not
Also, the old way of forcing a user to bypass a warning message every time
he/she wants to save to the loaded format is (workflow-wise) much worse
than just learning the "Export" hotkey imho. Also, it's clearly not a
"flaw"; it's not broken, it's working as intended.
If there were a vote, I'd vote
On Mon, Feb 29, 2016 at 3:20 PM, A. da Mek wrote:
>>> 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
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
On Mon, Feb 29, 2016 at 12:34 PM, A. da Mek wrote:
>> 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 bother to discuss it somewhere?
One o
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
29 февр. 2016 г. 11:35 пользователь "A. da Mek" написал:
> For an average user, GIMP already has everything what
> we need. 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
From: gimp-developer-list on behalf of
A. da Mek
Sent: 29 February 2016 08:35
To: gimp-developer
Subject: Re: [Gimp-developer] Export instead save directly
...But as I already said, this would be not much important if the
users were properly informed
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
I think the real intention was to prevent the user from accidentally
writing to a file format that throws away any layers which have been
created and other useful image information. It was a little strange at
first for me, but I've gotten quite used to the hotkeys for exporting. It's
a shame to rev
> 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
* Alexandra Sachsenweger [02-28-16 11:27]:
> Hello,
> I have a little problem with the 2.8.16 version of Gimp. I'm not really so
> clear that other file formats can not be saved directly. I save my photos
> like in PNG and it must for this version export to PNG. What is this with
> the export? I f
37 matches
Mail list logo
