Quick cropping with GIMP, like in XV
Ignoramus23731
quick crop and resize. XV has nice keyboard shortcuts.
The XV keys are: , and . to resize the picture, and mouse selection
and "c" to crop.
So I can edit a picture in approximately one or two seconds by
pressing, for instance: ",,, <select rectangle with mouse> c Ctrl-S
ENTER ENTER ENTER". That's it.
It is very useful when I have to process a lot of pictures at once,
for example pictures of stuff to be sold on ebay.
I wanted to learn how I can quickly crop and resize an image with
GIMP. I do not want to use menus. I just want to really quickly get to
what I need using keyboard and mouse for area selection.
What I want to avoid is using menus.
So. How do I quickly crop and resize with GIMP using keyboard shortcuts?
--
Due to extreme spam originating from Google Groups, and their inattention
to spammers, I and many others block all articles originating
from Google Groups. If you want your postings to be seen by
more readers you will need to find a different means of
posting on Usenet.
http://improve-usenet.org/
Joost Diepenmaat
> I use XV for image editing, since 90% of time all I need to do is
> quick crop and resize. XV has nice keyboard shortcuts.
[ ... ]
> What I want to avoid is using menus.
>
> So. How do I quickly crop and resize with GIMP using keyboard shortcuts?
My relatively current gimp (2.4.5) does this like: press shift+C (to
select the crop tool) -> select rectangle with the mouse -> press
enter. I believe 2.2 and earlier do not crop on enter.
--
Joost Diepenmaat | blog: http://joost.zeekat.nl/ | work: http://zeekat.nl/
Michael Soibelman
> Ignoramus23731 <ignoram...@NOSPAM.23731.invalid> writes:
>
>> I use XV for image editing, since 90% of time all I need to do is
>> quick crop and resize. XV has nice keyboard shortcuts.
> [ ... ]
>> What I want to avoid is using menus.
>>
>> So. How do I quickly crop and resize with GIMP using keyboard shortcuts?
>
> My relatively current gimp (2.4.5) does this like: press shift+C (to
> select the crop tool) -> select rectangle with the mouse -> press
> enter. I believe 2.2 and earlier do not crop on enter.
>
Also in 2.4.5 (2.4.6 released today!) in the Main menu go
to 'File' -> 'Keyboard Shortcuts' to see all the existing shotcuts or to
modify any you want to use...
Ignoramus23731
> Ignoramus23731 <ignoram...@NOSPAM.23731.invalid> writes:
>
>> I use XV for image editing, since 90% of time all I need to do is
>> quick crop and resize. XV has nice keyboard shortcuts.
> [ ... ]
>> What I want to avoid is using menus.
>>
>> So. How do I quickly crop and resize with GIMP using keyboard shortcuts?
>
> My relatively current gimp (2.4.5) does this like: press shift+C (to
> select the crop tool) -> select rectangle with the mouse -> press
> enter. I believe 2.2 and earlier do not crop on enter.
>
Great!
I have 2.4.5 at home, so I am cool. The crop function also resizes the
image, is that correct?
Ignoramus23731
Very nice. I am keyboard shortcut kind of person. I have 2.4.5 on my
Ubuntu Hardy.
If only GIMP started a little faster. I would then give up on XV
altogether. Right now I am not yet ready.
Too bad that John Bradley slackened off and did not release XV under
GPL.
Michael Soibelman
> On 2008-05-30, Joost Diepenmaat <jo...@zeekat.nl> wrote:
>> Ignoramus23731 <ignoram...@NOSPAM.23731.invalid> writes:
>>
>>> I use XV for image editing, since 90% of time all I need to do is
>>> quick crop and resize. XV has nice keyboard shortcuts.
>> [ ... ]
>>> What I want to avoid is using menus.
>>>
>>> So. How do I quickly crop and resize with GIMP using keyboard shortcuts?
>>
>> My relatively current gimp (2.4.5) does this like: press shift+C (to
>> select the crop tool) -> select rectangle with the mouse -> press
>> enter. I believe 2.2 and earlier do not crop on enter.
>>
>
> Great!
>
> I have 2.4.5 at home, so I am cool. The crop function also resizes the
> image, is that correct?
>
Yes. The image is resized to the size of the selected (cropped) area.
John DuBois
Ignoramus23731 <ignoram...@NOSPAM.23731.invalid> wrote:
>I use XV for image editing, since 90% of time all I need to do is
>quick crop and resize. XV has nice keyboard shortcuts.
>So I can edit a picture in approximately one or two seconds by
>pressing, for instance: ",,, <select rectangle with mouse> c Ctrl-S
>ENTER ENTER ENTER". That's it.
>
>It is very useful when I have to process a lot of pictures at once,
>for example pictures of stuff to be sold on ebay.
Having used xv for 15 years now, I had about the same feeling about simple
image editing in xv vs. the gimp. After I started using the gimp, for some
time I continued to do my cropping in xv and then used the gimp only for those
images that required more sophisticated processing. I've gradually been won
over by the nicer feel of the gimp's crop selection, and the convenience of
doing it all with one tool, particularly after finding its cropping shortcuts.
The last important xv characteristic that I haven't yet found a way to emulate
is the behavior of only opening one command-line-specified file at a time, and
easily (from the keyboard) going on to the next image when I'm done with the
current one. Is there a way of making the gimp behave this way? That is - I
want to specify the files to operate on on the command line, and I do *not*
want them all opened initially; I may be perusing, and selectively editing,
several hundred images in one round (all selected according to some criteria on
the command line). In xv, it's a matter of "hit space to open the next image
in place of the current one"; the closer to that I can get, the better...
John
--
John DuBois spc...@armory.com KC6QKZ/AE http://www.armory.com/~spcecdt/
Floyd L. Davidson
>In article <YJCdnb2xOe0Ft93V...@giganews.com>,
>Ignoramus23731 <ignoram...@NOSPAM.23731.invalid> wrote:
>>I use XV for image editing, since 90% of time all I need to do is
>>quick crop and resize. XV has nice keyboard shortcuts.
...
>Having used xv for 15 years now, I had about the same feeling about simple
>image editing in xv vs. the gimp. After I started using the gimp, for some
>time I continued to do my cropping in xv and then used the gimp only for those
>images that required more sophisticated processing. I've gradually been won
>over by the nicer feel of the gimp's crop selection, and the convenience of
>doing it all with one tool, particularly after finding its cropping shortcuts.
>
>The last important xv characteristic that I haven't yet found a way to emulate
>is the behavior of only opening one command-line-specified file at a time, and
>easily (from the keyboard) going on to the next image when I'm done with the
>current one. Is there a way of making the gimp behave this way? That is - I
>want to specify the files to operate on on the command line, and I do *not*
>want them all opened initially; I may be perusing, and selectively editing,
>several hundred images in one round (all selected according to some criteria on
>the command line). In xv, it's a matter of "hit space to open the next image
>in place of the current one"; the closer to that I can get, the better...
I use XV all the time... as a *viewer*. It's nice
because it will allow a few adjustments here and there,
etc etc., and provides a list as described, without
opening every single image. But there is no way that I
will use it as an editor.
Incidentally, there are some useful patches to XV. One
allows it to view Nikon's NEF files, which I don't find
to be actually useful, but one other patch really is a
gem. If clicking on the right mouse button gets you a
control panel that has a "Delete" button, rather than
"Reject", you have the original XV. It can be a pain
patching it and I don't know if binaries are available
for any given platform, but it is well worth finding a
patched version.
The "Delete" does exactly that, and the file is gone. A
useful, but limited function.
The "Reject" option creates a directory named "rejected"
and puts the selected file into that directory. In the
end, if all was right, "rm -rf rejected" will delete
them all if that is what is desired. But at any point
it is also possible to go back and look at what's in the
rejected directory and revive it. It's just very nice,
and of course one doesn't actually need to delete
"rejected" files! It's possible to do any kind of a
bipolar sort, tossing files into the rejected directory
and then later renaming it to something like "flowers"
or "selected_for_more_editing".
Another useful way to use XV is with a shell function or
alias like this: alias xvv='xv -fixed -geom 1024'
The command xvv will adjust the size of any image to a
maximum of 1024x1024. Essentially it means that even
small images will be shown full screen.
--
Floyd L. Davidson <http://www.apaflo.com/floyd_davidson>
Ukpeagvik (Barrow, Alaska) fl...@apaflo.com
Ignoramus27711
> In article <YJCdnb2xOe0Ft93V...@giganews.com>,
> Ignoramus23731 <ignoram...@NOSPAM.23731.invalid> wrote:
>>I use XV for image editing, since 90% of time all I need to do is
>>quick crop and resize. XV has nice keyboard shortcuts.
>>...
>>So I can edit a picture in approximately one or two seconds by
>>pressing, for instance: ",,, <select rectangle with mouse> c Ctrl-S
>>ENTER ENTER ENTER". That's it.
>>
>>It is very useful when I have to process a lot of pictures at once,
>>for example pictures of stuff to be sold on ebay.
>
> Having used xv for 15 years now, I had about the same feeling about
> simple image editing in xv vs. the gimp. After I started using the
> gimp, for some time I continued to do my cropping in xv and then
> used the gimp only for those images that required more sophisticated
> processing. I've gradually been won over by the nicer feel of the
> gimp's crop selection, and the convenience of doing it all with one
> tool, particularly after finding its cropping shortcuts.
There are a few things in gimp that I find cumbersome, quite probably
due to my lack of knowledge (I plan on asking a few questions
today). However, due to increase in computer speed, gimp is no longer
as slow as it used to be compared to xv.
> The last important xv characteristic that I haven't yet found a way
> to emulate is the behavior of only opening one
> command-line-specified file at a time, and easily (from the
> keyboard) going on to the next image when I'm done with the current
> one. Is there a way of making the gimp behave this way? That is -
> I want to specify the files to operate on on the command line, and I
> do *not* want them all opened initially; I may be perusing, and
> selectively editing, several hundred images in one round (all
> selected according to some criteria on the command line). In xv,
> it's a matter of "hit space to open the next image in place of the
> current one"; the closer to that I can get, the better...
You just need a simple shell script
for i in *.jpg; do
gimp $i
done
the little overhead here is in starting a new instance of gimp every
time.
Michael Soibelman
Sorry if I'm wrong about this but I'm not a very good programmer !! Just
BASIC !1 Seems to me that if you changed this 'gimp $i' to 'gimp-remote
$i' you would save a lot of overhead ?? This leaves just one instance of
Gimp running but opens up each image in its' own window...
Correct me if I'm wrong.
John DuBois
Floyd L. Davidson <fl...@apaflo.com> wrote:
>Incidentally, there are some useful patches to XV. One
>allows it to view Nikon's NEF files, which I don't find
>to be actually useful, but one other patch really is a
>gem. If clicking on the right mouse button gets you a
>control panel that has a "Delete" button, rather than
>"Reject", you have the original XV. It can be a pain
>patching it and I don't know if binaries are available
>for any given platform, but it is well worth finding a
>patched version.
>
>The "Delete" does exactly that, and the file is gone. A
>useful, but limited function.
>
>The "Reject" option creates a directory named "rejected"
>and puts the selected file into that directory. In the
>end, if all was right, "rm -rf rejected" will delete
>them all if that is what is desired. But at any point
>it is also possible to go back and look at what's in the
>rejected directory and revive it. It's just very nice,
>and of course one doesn't actually need to delete
>"rejected" files! It's possible to do any kind of a
>bipolar sort, tossing files into the rejected directory
>and then later renaming it to something like "flowers"
>or "selected_for_more_editing".
That does seem like a useful extension. I'm using the unmodified version, so
if I want to save deleted images, after an xv session I do:
mv $(undelete -l) raw/culled/ && cd raw/culled && undelete .
The OS I'm using implements file versioning in the filesystem namespace, so
this moves the deleted files in the current directory to another directory &
undeletes them. If I don't undelete them, the versions will be purged when
their time is up. A bit of a kludge, but it has worked well :)
John DuBois
Thanks, this is a useful idea. I don't want to start a new instance of gimp
for each image, with the startup overhead, losing the history that allows me to
rerun the last filter, etc. gimp-remote avoids that, and if I use a shell loop
that includes a 'read', going on to the next image become a matter of closing
the image window and then hitting return to tell gimp-remote to push the next
image open.
Ignoramus27711
except gimp-remote does not seem to tell you when gimp is done with
the image.
I edit my pictures from a big perl script, that downloads pix frmo the
camera, calls picture editor (xv or gimp), and then for every picture
left unedited, asks if I want to delete it. Makes for a nice
workflow.
David Hodson
> The last important xv characteristic that I haven't yet found a way to emulate
> is the behavior of only opening one command-line-specified file at a time, and
> easily (from the keyboard) going on to the next image when I'm done with the
> current one.
My FileSequencer plugin might be useful. Not keyboard-driven, but close
to what you want - maybe someone could mod it to your requirements. Go
to http://members.ozemail.com.au/~hodsond/gimp.html and look for "File
Sequencer".
--
David Hodson -- this night wounds time
John DuBois
That's why I'd have the shell loop do a read, and hit return (in the terminal
window exposed by closing the image window) to tell gimp-remote to push the
next image open. That gets it down to ^W to close the current image window,
and return to open the next, which is pretty good, and with a bit more work it
could have the ability to back up to the previous image or generally to go to a
different point in the image list as in xv.