{"id":2315,"date":"2012-06-17T17:47:53","date_gmt":"2012-06-17T17:47:53","guid":{"rendered":"http:\/\/www.bartbusschots.ie\/blog\/?p=2315"},"modified":"2014-08-05T20:20:51","modified_gmt":"2014-08-05T20:20:51","slug":"webifyimages-pm-my-image-editing-scripts-v0-2","status":"publish","type":"post","link":"https:\/\/www.bartbusschots.ie\/s\/2012\/06\/17\/webifyimages-pm-my-image-editing-scripts-v0-2\/","title":{"rendered":"WebifyImages.pm – My Image Editing Scripts (v0.2)"},"content":{"rendered":"

Yesterday I posted my thoughts on watermarking images<\/a> for uploading to the web. This post formed the basis of myself and Allison Sheridan’s discussions in the Chit Chat Across the Pond<\/em> segment on tonight’s Nosillacast Mac Podcast<\/a>. During the discussion we talked a little about how I watermark my images, and I realised that I hadn’t released a version of my image processing scripts since 2008<\/a>! I promised I’d remedy that, so today, after a little tidying up, I’m releasing the current snapshot of my scripts under the FreeBSD license.<\/p>\n

I’m not releasing these scripts as a polished software package that’s ready to use, but rather, as a starting point for anyone who wants to create their own watermarking scripts. If you’re not prepared to get stuck into the command line and a little Perl (VERY little is needed mind), these scripts are of no use to you!<\/p>\n

The scripts rely on the free and open source ImageMagick<\/a> command line image editing tools, so you’ll need to install ImageMagick before you get stuck in. If you’re running OS X, I’d recommend installing ImageMagick via the free and open source MacPorts<\/a> package manager.<\/p>\n

<\/p>\n

\"Download\"<\/a><\/p>\n

All the core functionality provided by the scripts is contained within a single perl package, WebifyImages.pm<\/code>. Any customisations you want to make to the watermarks will need to be made here. The code is well commented, but, unfortunately, it dates back to before my conversion to the Perl Best Practices<\/a> religion, so it barfs out an embarrassing number of warnings when run through perlcritic<\/code><\/a>. I do plan to re-write it some day, and when I do I’ll be making it object orienting, and ensuring that, like all my recently written code, it passes perlcritic<\/code>.<\/p>\n

All command line interactions with the functionality contained within WebifyImages.pm<\/code> is accessed through the perl script webifyFn.pl<\/code>. Once you have the scripts up and running, you should never have to edit this file, it really is just a wrapper. If you add any new functions to WebifyImages.pm<\/code> you’ll need to be sure to add an entry for them into the $WebifyImages::functions<\/code> hashtable or they won’t be accessible via webifyFn.pl<\/code>.<\/p>\n

Installing the Scripts<\/h2>\n

I haven’t written an installer script, so you’ll have to do a little work by hand here. Again, don’t even bother starting with this until you have ImageMagic installed, and know where on your system the binaries for it are located. If you follow my advice and ImageMagick install via MacPorts, the binaries will be located in \/opt\/local\/bin\/<\/code>. If you want to check where they are located, just run:<\/p>\n

\nwhich mogrify\n<\/pre>\n
This should return something like:<\/p>\n
\nbart-imac:~ bart$ which mogrify\n\/opt\/local\/bin\/mogrify\nbart-imac:~ bart$\n<\/pre>\n
This shows that my ImageMagick binaries are indeed in \/opt\/local\/bin\/<\/code>.<\/p>\n
    \n
  1. Unzip the download package, and copy it’s contents to a folder of your choice on your system. I recommend something like ~\/scripts\/webifyImages\/<\/code> (where ~<\/code> is your home directory)<\/li>\n
  2. Open the file WebifyImages.pm<\/code> and make the following edits:\n
      \n
    1. Set the value of $WebifyImages::HOMEDIR<\/code> to the location you extracted the zip to. If you used my suggested installation location, you won’t need to make any changes here.<\/li>\n
    2. Set the value of $WebifyImages::IMAGEMAGICK_BIN<\/code> to the location where your ImageMagick binaries are installed.<\/li>\n<\/ol>\n<\/li>\n
    3. Open the file webifyFn.pl<\/code> and edit the use lib<\/code> directive on line 33 so that it contains the absolute path to the folder where WebifyImages.pm<\/code> is located.<\/li>\n
    4. If your OS’s copy of Perl is not located at \/usr\/bin\/perl<\/code>, you’ll need to edit the first line of both WebifyImages.pm<\/code> and webifyFn.pl<\/code> to reflect the path to your instance of Perl. (this location is the default on OS X and most versions of Linux, so you probably won’t need to change this)<\/li>\n<\/ol>\n
      Customising the Scripts<\/h2>\n
      The first thing you’ll want to do is create your own versions of the image files containing the URL that will be stamped on the images. You’ll need to do two versions of your image file, one on a white background, and one on a black one. I’ve included the Pixelmator<\/a> files I used to generate my image files in the dev<\/code> folder inside the archive, if you’re a Pixelmator user you might find them helpful. Once you’ve created your own image files and saved them somewhere, update the values of the variables $WebifyImages::URL_ICON_ONWHITE<\/code> and $WebifyImages::URL_ICON_ONBLACK<\/code> in WebifyImages.pm<\/code> with the new file paths.<\/p>\n
      Once you’ve done that you’ll also need to update the URLs in the functions insertUrl()<\/code> and insertSemiTransparentUrl()<\/code> on lines 224 and 236 of WebifyImages.pm<\/code>.<\/p>\n
      At this stage you’re ready to start using the scripts, but you may want to do some more customisation.<\/p>\n
      If you want to change the fonts used by the scripts, you can edit the variables $WebifyImages::SCRIPT_FONT<\/code>, $WebifyImages::SANSSERIF_FONT<\/code>, and $WebifyImages::CAPS_FONT<\/code> in WebifyImages.pm<\/code>.<\/p>\n
      If you use a license other than Creative Commons Non-Commercial, Non-Derivative, Attribution<\/a>, then you’ll need to create your own image file to represent that license (or download a different CC icon from the Creative Commons site if you are using a different flavour of CC), and edit the variable $WebifyImages::CC_ICON<\/code> in WebifyImages.pm<\/code> with the path to your image.<\/p>\n
      Using The Scripts<\/h2>\n
      The first thing to make VERY clear is that THESE SCRIPTS ALTER THE IMAGES THEY ARE APPLIED TO<\/strong>. They are designed to be used on images exported from an image management package like Aperture or Lightroom, and are NOT designed to be used on your master images!<\/p>\n
      You apply the functionality contained in WebifyImages.pm<\/code> to images by changing to the directory containing the images in the terminal, and then invoking webifyFn.pl<\/code> on those images. To make things easier you probably want to add the folder you installed the scripts into to your path. The webifyFn.pl script is invoked in the following way:<\/p>\n
      \nwebifyFn.pl [function_name] [function_arguments]\n<\/pre>\n
      To get a list of available functions, and a description of the arguments they expect, run:<\/p>\n
      \nwebifyFn.pl list\n<\/pre>\n
      That really is all there is to it – you can just use my scripts as they are (with your basic customisations obviously), or you can tinker and edit to your heart’s content!<\/p>\n","protected":false},"excerpt":{"rendered":"
      Yesterday I posted my thoughts on watermarking images for uploading to the web. This post formed the basis of myself and Allison Sheridan’s discussions in the Chit Chat Across the Pond segment on tonight’s Nosillacast Mac Podcast. During the discussion we talked a little about how I watermark my images, and I realised that I […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[12,22,16],"tags":[406,374,268,457,458],"series":[],"class_list":["post-2315","post","type-post","status-publish","format-standard","hentry","category-computers-tech","category-photography","category-programming","tag-commandline","tag-image-processing","tag-scripting","tag-software-release","tag-tutorial"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p7t9xK-Bl","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.bartbusschots.ie\/s\/wp-json\/wp\/v2\/posts\/2315","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.bartbusschots.ie\/s\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.bartbusschots.ie\/s\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.bartbusschots.ie\/s\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bartbusschots.ie\/s\/wp-json\/wp\/v2\/comments?post=2315"}],"version-history":[{"count":3,"href":"https:\/\/www.bartbusschots.ie\/s\/wp-json\/wp\/v2\/posts\/2315\/revisions"}],"predecessor-version":[{"id":7804,"href":"https:\/\/www.bartbusschots.ie\/s\/wp-json\/wp\/v2\/posts\/2315\/revisions\/7804"}],"wp:attachment":[{"href":"https:\/\/www.bartbusschots.ie\/s\/wp-json\/wp\/v2\/media?parent=2315"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bartbusschots.ie\/s\/wp-json\/wp\/v2\/categories?post=2315"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.bartbusschots.ie\/s\/wp-json\/wp\/v2\/tags?post=2315"},{"taxonomy":"series","embeddable":true,"href":"https:\/\/www.bartbusschots.ie\/s\/wp-json\/wp\/v2\/series?post=2315"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}