I figured that I wanted a way to batch process images. Since I made the move to Linux, I lost some of my favorite Windows only tools. So I decided to utilize Perl and Gimp as a substitute.
Checking into the Gimp documents I found that Gimp has procedures that can be called from Perl to take advantage of Gimps code. Long story short, I've been banging my head against Gimps poor documentation. At this point, I'm simply frustrated with Gimp and the Perl interface. I spent nearly ten hours just trying to locate and install all the separate Perl modules that I needed to interface with Gimp. To make matters worse, Gimp IRC couldn't point me in the right direction since they've never even heard of the procedures. Code samples and tutorials are just vague enough that moving what I learn to different functions falls flat on their face.
I'm fed up with Gimp. I've decided that Gimps interface documentation simply isn't mature enough to even bother with anymore. So I ask this of you my friendly Monks. Does anyone know how to utilize Gimps Perl interface effectively? Is there a different module to manipulate the images the way I want?
My Current Goal:
I have a collection of images for my website. One of my goals is to assist in changing the colors of the images by replacing pixels of one color with another. The images are stored as needs dictate such as .gif, .jpeg, or .png. I know how to use Perl to filter out the files I don't want altered.
Another, related goal, is rotating an image a set number of degrees and saving each rotation as a different file.
----
Thanks for your patience.
Prove your knowledge @ HLPD
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|