2011/6/30 peter sikking :
> no, nothing changed in the Overwrite workflows.
>
> today's changes can be summarised as:
>
> - in the cases where before Export to was insensitive, it is
> now sensitive and mapped to invoke Export... (the dialog)
>
> - in the cases where Overwrite blocks Export to out
Martin wrote:
> 2011/6/30 peter sikking :
>>> I will update the spec now to formalise this.
>> done, and it was not a one-liner.
>>
>> Martin (prime suspect for implementing the change): please do
>> a careful diff in the wiki to see the changes.
>
> It looks straightforward and I expect to be a
2011/6/30 peter sikking :
> I wrote:
>
>> I will update the spec now to formalise this.
>
>
> done, and it was not a one-liner.
>
> Martin (prime suspect for implementing the change): please do
> a careful diff in the wiki to see the changes.
It looks straightforward and I expect to be able to upd
I wrote:
> I will update the spec now to formalise this.
done, and it was not a one-liner.
Martin (prime suspect for implementing the change): please do
a careful diff in the wiki to see the changes.
thanks,
--ps
founder + principal interaction architect
man + machine
Alexia Death wrote:
> I would really hate it if Ctrl-E would overwrite after import even
> with confirmation.
right. we are never going to mix the 'backward' move of overwriting
the original, imported file (destructive move) with the 'forward'
move of starting/doing an export.
> What I personall
Jeremy: You have some good points, but also Alexia and the rest have.
All this stuff was studied and the consensus was to go ahead with the
current implementation.
Of course it's hard to please everyone and this can look bad for some
people while looks excellent for others.
You already can have a s
On Thu, Jun 30, 2011 at 4:21 PM, Jeremy Morton wrote:
> OK, well that's a terminology thing. I meant export. Why would you keep
> exporting it to a JPEG? I was saying what you're saying; if you're
> opening/importing a JPEG with the intention of editing it and exporting it,
> it only makes sens
OK, well that's a terminology thing. I meant export. Why would you
keep exporting it to a JPEG? I was saying what you're saying; if you're
opening/importing a JPEG with the intention of editing it and exporting
it, it only makes sense to save a lossless (probably XCF) before you get
started.
On Thu, Jun 30, 2011 at 3:40 PM, Jeremy Morton wrote:
> Also I would imagine any sensible user would always save a lossless version
> of a lossy-format image before editing it and saving.
Why would I save it lossless somewhere BEFORE editing a file Ive
imported from a JPG? The loss has already hap
On 30/06/2011 13:30, SorinN wrote:
>>> No, Im telling you that for photographic workflows, desire to
>>> overwrite is rather rare
>
> this is true,
>
> can be an unrecoverable mistake, even for one unique picture
>
> but sometime overwriting is convenient and desired
Also I would imagine any sen
>>No, Im telling you that for photographic workflows, desire to
>>overwrite is rather rare
this is true,
can be an unrecoverable mistake, even for one unique picture
but sometime overwriting is convenient and desired
Probably the best way is to have this choice in Preferences
Also from an Us
On 30/06/2011 12:17, Alexia Death wrote:
> On Thu, Jun 30, 2011 at 2:08 PM, Jeremy Morton wrote:
>> So you're assuming that the user is going to 'accidentally' press ctrl-E,
>> then 'accidentally' click on overwrite even though it's not the default
>> selected button?
>
> No, Im telling you that f
On Thu, Jun 30, 2011 at 2:08 PM, Jeremy Morton wrote:
> So you're assuming that the user is going to 'accidentally' press ctrl-E,
> then 'accidentally' click on overwrite even though it's not the default
> selected button?
No, Im telling you that for photographic workflows, desire to
overwrite is
So you're assuming that the user is going to 'accidentally' press
ctrl-E, then 'accidentally' click on overwrite even though it's not the
default selected button?
--
Best regards,
Jeremy Morton (Jez)
On 30/06/2011 12:01, Alexia Death wrote:
> On Thu, Jun 30, 2011 at 1:56 PM, Jeremy Morton wro
On Thu, Jun 30, 2011 at 1:56 PM, Jeremy Morton wrote:
> But it's more intuative to assume the imported file's location and format.
> If you've imported a file and edited it, it's quite likely you will want to
> write the changes back out to that file. If you want to write them
> somewhere else,
But it's more intuative to assume the imported file's location and
format. If you've imported a file and edited it, it's quite likely you
will want to write the changes back out to that file. If you want to
write them somewhere else, it's easy to bring up the advanced export dialog.
--
Best
On Thu, Jun 30, 2011 at 1:34 PM, Jeremy Morton wrote:
> My suggestion is that this only happen the *first* time the over presses
> ctrl-E after importing and editing a file, though. Subsequent presses
> once the user has confirmed would overwrite without confirmation. It's
> just to avoid overwr
My suggestion is that this only happen the *first* time the over presses
ctrl-E after importing and editing a file, though. Subsequent presses
once the user has confirmed would overwrite without confirmation. It's
just to avoid overwriting by accident.
--
Best regards,
Jeremy Morton (Jez)
O
2011/6/30 Jeremy Morton :
> My suggestion is an export (to the
> original file name and file type), but with a 'are you sure you want to
> overwrite?' dialog before the export happens, with the focus
> automatically on the cancel so 'enter' will cancel the export.
The popup is good when the user d
On 28/06/2011 13:33, peter sikking wrote:
>
> On Jun 28, 2011, at 11:35, SorinN wrote:
>
>> But there was already Ctrl + Shift + E which bring up the dialog for export
>> Ctrl + E was for overwrite without confirm.
>>
>> Probably the logical order was inverse - many peoples expecting Ctrl +
>> E to
> this is why I am insisting that it is not going to change, in the future.
don't get me wrong - as is right now - is very convenient for me and
probably for many others, but seems to disturb a part of designers who
comes with various backgrounds.
to be clear ..when I see for first time that Ctrl
On Jun 28, 2011, at 11:35, SorinN wrote:
> But there was already Ctrl + Shift + E which bring up the dialog for export
> Ctrl + E was for overwrite without confirm.
>
> Probably the logical order was inverse - many peoples expecting Ctrl +
> E to bring up the export dialog,
first of all, ctrl-s
But there was already Ctrl + Shift + E which bring up the dialog for export
Ctrl + E was for overwrite without confirm.
Probably the logical order was inverse - many peoples expecting Ctrl +
E to bring up the export dialog,
2011/6/28 Martin Nordholts :
> 2011/6/26 Jeremy Morton :
>> When I open
2011/6/26 Jeremy Morton :
> When I open a non-GIMP format file, like a PNG, by drag-dropping it into
> GIMP, and then I edit it, I go to export it, by pressing ctrl+E... and
> nothing happens. This is because what I actually have to do is select
> "File | Overwrite (filename.png)".
>
> Wouldn't it
On Sun, Jun 26, 2011 at 7:14 PM, Jeremy Morton wrote:
> I can't configure the same shortcut for 2 things (file-overwrite and
> file-export),
Oh, I finally see what you mean :) Sorry :)
Alexandre Prokoudine
http://libregraphicsworld.org
___
Gimp-develope
I can't configure the same shortcut for 2 things (file-overwrite and
file-export), and anyway I'm making the point that I don't see a
meaningful difference between the two. Once you've executed
file-overwrite once, file-export does exactly what I'd want anyway. Why
not make file-export just d
On Sun, Jun 26, 2011 at 6:42 PM, Jeremy Morton wrote:
> And I've already gotten used to that; it is logical. My issue is when
> you open a non-GIMP format file and then you want to export it back to
> its original format; I think it makes more sense to just be able to
> press ctrl+E (with a popup
On 26/06/2011 15:31, Jason Simanek wrote:
> On 06/26/2011 09:22 AM, Jeremy Morton wrote:
>> The thing is, if I go about it a different way and export another file
>> to overwrite that file, I'm using the export function. Each time I then
>> press ctrl+E, I'm overwriting that file again and again,
On 06/26/2011 09:22 AM, Jeremy Morton wrote:
> The thing is, if I go about it a different way and export another file
> to overwrite that file, I'm using the export function. Each time I then
> press ctrl+E, I'm overwriting that file again and again, without even a
> prompt. I don't see a meaning
He's right here =>>
"I'm using the export function. Each time I then
press ctrl+E, I'm overwriting that file again and again, without even a
prompt. I don't see a meaningful difference between this workflow, and
that of importing/editing/exporting."
He doesn't know that Ctrl + Shift + E bring
The way I think of the workflow, I'm importing a file, editing it, and
exporting it. Overwriting the file on disk is a mere side-effect of
that workflow, and GIMP will prompt me in any case just in case I don't
want to overwrite the file.
The thing is, if I go about it a different way and expo
On Sun, Jun 26, 2011 at 6:00 PM, Jeremy Morton wrote:
> As far as I can tell the usage pattern has already changed heavily from
> 2.6. In 2.6 there was only one save option; now there's a save and
> export. You've already changed that significantly.
Yes, and there should be a better reason for g
As far as I can tell the usage pattern has already changed heavily from
2.6. In 2.6 there was only one save option; now there's a save and
export. You've already changed that significantly.
--
Best regards,
Jeremy Morton (Jez)
On 26/06/2011 14:57, Alexandre Prokoudine wrote:
> On Sun, Jun 26
On Sun, Jun 26, 2011 at 5:49 PM, Jeremy Morton wrote:
> It should be possible.
You are in fact suggesting to heavily break use pattern.
I don't think developers and UI team will fall for that.
Alexandre Prokoudine
http://libregraphicsworld.org
___
Gimp-
It should be possible.
--
Best regards,
Jeremy Morton (Jez)
On 26/06/2011 14:48, Alexandre Prokoudine wrote:
> On Sun, Jun 26, 2011 at 5:43 PM, Jeremy Morton wrote:
>> Let's put it another way: I'm the user and I want GIMP to do that. How
>> can I get it to?
>
> You can't
>
> Alexandre Prokoudi
On Sun, Jun 26, 2011 at 5:43 PM, Jeremy Morton wrote:
> Let's put it another way: I'm the user and I want GIMP to do that. How
> can I get it to?
You can't
Alexandre Prokoudine
http://libregraphicsworld.org
___
Gimp-developer mailing list
Gimp-develope
Let's put it another way: I'm the user and I want GIMP to do that. How
can I get it to?
--
Best regards,
Jeremy Morton (Jez)
On 26/06/2011 14:18, Alexandre Prokoudine wrote:
> On Sun, Jun 26, 2011 at 4:08 PM, Jeremy Morton wrote:
>> When I open a non-GIMP format file, like a PNG, by drag-dropp
On Sun, Jun 26, 2011 at 4:08 PM, Jeremy Morton wrote:
> When I open a non-GIMP format file, like a PNG, by drag-dropping it into
> GIMP, and then I edit it, I go to export it, by pressing ctrl+E... and
> nothing happens. This is because what I actually have to do is select
> "File | Overwrite (fil
38 matches
Mail list logo
