Re: [Gimp-developer] Quick-edit workflow

2013-11-13 Thread peter sikking
Jehan wrote: > Should I change the action's names to follow their label? In > particular "Export" would correspond to "file-export" and "Export > As..." corresponds to "file-export-as" (otherwise we would end up in > the strange situation where "Export" <=> "file-export-to" and "Export > As..." <=

Re: [Gimp-developer] Quick-edit workflow

2013-11-13 Thread Jehan Pagès
Hi, On Wed, Nov 13, 2013 at 11:49 PM, peter sikking wrote: > Jehan wrote: > >> Just checking master, currently when "overwrite" is shown, export-to >> is not grayed out but it is invisible. >> That means that it is active and can be run if you know the shortcut, >> but you can't export from the m

Re: [Gimp-developer] Quick-edit workflow

2013-11-13 Thread peter sikking
Jehan wrote: > Just checking master, currently when "overwrite" is shown, export-to > is not grayed out but it is invisible. > That means that it is active and can be run if you know the shortcut, > but you can't export from the menu (for people who don't know > shortcuts, new or casual users, etc

Re: [Gimp-developer] Quick-edit workflow

2013-11-12 Thread Akkana Peck
Jehan Pagès writes: > Just checking master, currently when "overwrite" is shown, export-to > is not grayed out but it is invisible. > That means that it is active and can be run if you know the shortcut, > but you can't export from the menu (for people who don't know > shortcuts, new or casual user

Re: [Gimp-developer] Quick-edit workflow

2013-11-12 Thread Jehan Pagès
Hi, On Wed, Nov 13, 2013 at 1:45 PM, Jehan Pagès wrote: > Hi, > > On Sun, Nov 10, 2013 at 2:25 PM, peter sikking wrote: >> guys + girls, >> >> it is a tricky thing, this overwrite vs. export. >> >> there is a difference, overwrite is for working ‘backward’ >> as I called it: doing some work on a

Re: [Gimp-developer] Quick-edit workflow

2013-11-12 Thread Jehan Pagès
Hi, On Sun, Nov 10, 2013 at 2:25 PM, peter sikking wrote: > guys + girls, > > it is a tricky thing, this overwrite vs. export. > > there is a difference, overwrite is for working ‘backward’ > as I called it: doing some work on a non-gimp file and > feeding this directly back to it. it is labelled

Re: [Gimp-developer] Quick-edit workflow

2013-11-12 Thread peter sikking
Richard Gitschlag wrote: > PS: Can we get some accelerator keys put on those menu labels sometime? apart from Overwrite (by design), where are you missing one? --ps founder + principal interaction architect man + machine interface works http://blog.mmiworks.net

Re: [Gimp-developer] Quick-edit workflow

2013-11-12 Thread Richard Gitschlag
> From: pe...@mmiworks.net > Date: Sun, 10 Nov 2013 02:25:47 +0100 > To: gimp-developer-list@gnome.org > Subject: Re: [Gimp-developer] Quick-edit workflow > > I think I can see what Akkana means: when there is no export > target, the menu items are “Export to” and “Export...

Re: [Gimp-developer] Quick-edit workflow

2013-11-09 Thread peter sikking
guys + girls, it is a tricky thing, this overwrite vs. export. there is a difference, overwrite is for working ‘backward’ as I called it: doing some work on a non-gimp file and feeding this directly back to it. it is labelled brutally and frankly, with intent. export is for working ‘forward’, tow

Re: [Gimp-developer] Quick-edit workflow

2013-11-09 Thread Simon Budig
Richard Gitschlag (strata_ran...@hotmail.com) wrote: > And similar to you, one thing *I* don't get is why "Export" and > "Overwrite" need to be separate commands. Because without this distinction you'd accidentially overwrite your precious orignal file after accidentially doing an "Export" instead

Re: [Gimp-developer] Quick-edit workflow

2013-11-09 Thread Richard Gitschlag
> Date: Fri, 8 Nov 2013 20:15:23 -0800 > From: akk...@shallowsky.com > To: gimp-developer-list@gnome.org > Subject: Re: [Gimp-developer] Quick-edit workflow > > I've found that the new model makes me stop and think every time > I save or export anything. For one thing

Re: [Gimp-developer] Quick-edit workflow

2013-11-08 Thread Akkana Peck
peter sikking writes: > what we were missing was a quick succession of ctrl shortcuts > (cmd on mac) that close unsaved images. > > I worked on it with mitch and it is now in git. > > so now everyone can press ctrl-W to close a document, keep > the finger on the ctrl and press ctrl-D in the dialo

Re: [Gimp-developer] Quick-edit workflow

2013-11-08 Thread peter sikking
Ramkumar, > However, > the process for overwriting the PNG image is too complicated; export > (Ctrl+E), overwrite file: , then close (Ctrl+W), and close > without saving: . What can we do to make this process simpler? this part got me thinking-checking-planning. what we were missing was a quick

Re: [Gimp-developer] Quick-edit workflow

2013-10-31 Thread Joao S. O. Bueno
On 31 October 2013 05:36, Karl-Heinz Zimmer wrote: > Yes, you can add such a shortcut, please go to: > >Edit / Keyboard shortcuts ... Just a somewhat unrelated notice - as I consider this one of GIMP's most important features: in GIMP you don't have to go to "Edit->Preferences->Interface->Ed

Re: [Gimp-developer] Quick-edit workflow

2013-10-31 Thread Karl-Heinz Zimmer
Yes, you can add such a shortcut, please go to: Edit / Keyboard shortcuts ... There you see the entry File ... Overwrite: Disabled Just change that to a shortcut you like. Cheers Karl-Heinz On Thu, 31 Oct 2013 10:28:00 +0530 Ramkumar Ramachandra wrote: > Sorry, I didn't notice the "F

Re: [Gimp-developer] Quick-edit workflow

2013-10-31 Thread Ramkumar Ramachandra
Sorry, I didn't notice the "File > Overwrite " menu option. Perhaps a keyboard shortcut for the same would be nice. ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listin

[Gimp-developer] Quick-edit workflow

2013-10-30 Thread Ramkumar Ramachandra
Hi, I often use GIMP to make minor edits to PNG images quickly. However, the process for overwriting the PNG image is too complicated; export (Ctrl+E), overwrite file: , then close (Ctrl+W), and close without saving: . What can we do to make this process simpler? We need to indicate to the user th