<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Left Justified &#187; photoshop</title>
	<atom:link href="http://leftjustified.net/topic/photoshop/feed/" rel="self" type="application/rss+xml" />
	<link>http://leftjustified.net</link>
	<description>In a few words, explain what this weblog is about.</description>
	<lastBuildDate>Thu, 09 Dec 2010 00:10:44 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Rebuild Woes &#8211; Taping Some Cats Together to Build a Horse</title>
		<link>http://leftjustified.net/journal/2004/09/19/rebuild-woes/</link>
		<comments>http://leftjustified.net/journal/2004/09/19/rebuild-woes/#comments</comments>
		<pubDate>Sun, 19 Sep 2004 05:01:59 +0000</pubDate>
		<dc:creator>Andrew</dc:creator>
				<category><![CDATA[photoshop]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://leftjustified.net/journal/2004/09/19/rebuild-woes/</guid>
		<description><![CDATA[This site has been a bit quite for a while because my computer has pulled a Titanic; it scraped an iceberg about a three weeks ago and has been taking on water ever since. Last weekend I had to jump ship.

The technical issues have been solved and I&#8217;ve taken the opportunity to totally rethink how I store my personal files and perform a clean install of everything. That has left an entirely different problem - a massive loss in familiarity/usability due to a system full of &#8216;default&#8217; settings.]]></description>
			<content:encoded><![CDATA[<p>When you&#8217;re trying to escape a sinking ship, you don&#8217;t have time to go looking for belongings that are scattered over every deck &#8211; the same can be said of trying to capture all the personalised settings and modifications to your favourite programs when escaping a crash-happy computer. The first thing I missed when I got back to work on my fresh system was the ordering and positioning of all the palettes and preferences in Photoshop. This was followed minutes later by a stark and conformingly high contrast UltraEdit interface; complete with 12pt Courier. Wouldn&#8217;t  it have been great if I could have just looked in the root directory of each program and found an intelligently named xml file containing all my preferences?</p>
<p>Proof of Concept<br />
Here&#8217;s a quick example of what I&#8217;m talking about. I&#8217;ve used Photoshop as the example application as it is the closest thing I use to an IDE, it is the program I have been using the longest (as of next birthday I will have been pushing pixels for more than half my life!) and it is far and away my favourite piece of software. Element names have been made purposefully verbose to ease readability .</p>
<p>Below is a snippet detailing how basic preferences could be stored:</p>
<pre class="code"><code>
&lt;preferences&gt;
	&lt;preferencegroup&gt;
		&lt;name&gt;General&lt;/name&gt;
		&lt;pref name=&quot;color picker&quot; value=&quot;Adobe&quot; /&gt;
		&lt;pref name=&quot;interpolation&quot; value=&quot;Bicubic Sharper&quot; /&gt;
		&lt;pref name=&quot;history&quot; value=&quot;30&quot; /&gt;
		&lt;pref name=&quot;export clipboard&quot; value=&quot;true&quot; /&gt;
		&lt;pref name=&quot;zoom resize&quot; value=&quot;true&quot; /&gt;
		&lt;pref name=&quot;auto update&quot; value=&quot;false&quot; /&gt;
		&lt;pref name=&quot;asian text&quot; value=&quot;false&quot; /&gt;
	&lt;/preferencegroup&gt;
	&lt;preferencegroup&gt;
		&lt;name&gt;Display and Cursors&lt;/name&gt;
		&lt;pref name=&quot;color channels&quot; value=&quot;true&quot; /&gt;
		&lt;pref name=&quot;diffusion dither&quot; value=&quot;false&quot; /&gt;
		&lt;pref name=&quot;pixel doubling&quot; value=&quot;false&quot; /&gt;
		&lt;pref name=&quot;painting cursor&quot; value=&quot;brush size&quot; /&gt;
		&lt;pref name=&quot;other cursor&quot; value=&quot;standard&quot; /&gt;
	&lt;/preferencegroup&gt;
&lt;/preferences&gt;
</code></pre>
<p>Simple, yes? Now to use XML to really make a difference. The snippet below is an example of what I really wanted last Monday &#8211; the details of my desktop arrangement within photoshop.</p>
<pre class="code"><code>
&lt;palettegroup&gt;
	&lt;height&gt;710&lt;/height&gt;
	&lt;width&gt;274&lt;/width&gt;
	&lt;x-pos&gt;1292&lt;/x-pos&gt;
	&lt;y-pos&gt;2&lt;/y-pos&gt;
	&lt;palette&gt;Layers&lt;/palette&gt;
	&lt;palette&gt;Channels&lt;/palette&gt;
	&lt;palette&gt;Paths&lt;/palette&gt;
&lt;/palettegroup&gt;
&lt;palettegroup&gt;
	&lt;height&gt;132&lt;/height&gt;
	&lt;width&gt;212&lt;/width&gt;
	&lt;x-pos&gt;1571&lt;/x-pos&gt;
	&lt;y-pos&gt;2&lt;/y-pos&gt;
	&lt;palette&gt;Info&lt;/palette&gt;
	&lt;palette&gt;Histogram&lt;/palette&gt;
	&lt;palette&gt;Swatches&lt;/palette&gt;
&lt;/palettegroup&gt;
&lt;palettegroup&gt;
	&lt;height&gt;382&lt;/height&gt;
	&lt;width&gt;212&lt;/width&gt;
	&lt;x-pos&gt;1571&lt;/x-pos&gt;
	&lt;y-pos&gt;136&lt;/y-pos&gt;
	&lt;palette&gt;History&lt;/palette&gt;
	&lt;palette&gt;Actions&lt;/palette&gt;
&lt;/palettegroup&gt;
&lt;palettegroup&gt;
	&lt;height&gt;218&lt;/height&gt;
	&lt;width&gt;212&lt;/width&gt;
	&lt;x-pos&gt;1571&lt;/x-pos&gt;
	&lt;y-pos&gt;520&lt;/y-pos&gt;
	&lt;palette&gt;Character&lt;/palette&gt;
	&lt;palette&gt;Paragraph&lt;/palette&gt;
&lt;/palettegroup&gt;
</code></pre>
<p>This could easily be extended to include the paths to action files, patterns, brushes and other such goodies. Techniques like the above are the sort of lead the big guys should be taking from the linux/unix crowd. I&#8217;m not saying <em>everything</em> should be controlled via <code>.conf</code> files, but at least give advanced users advanced options.</p>
<p>Oh, in case <a href="http://designbyfire.com/" title="Design by Fire">Andrei</a> stumbles upon this, perhaps you could mention the idea to the guys at <a href="http://adobe.com">work</a>? <img src='http://leftjustified.net/wp-includes/images/smilies/icon_biggrin.gif' alt=':-D' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://leftjustified.net/journal/2004/09/19/rebuild-woes/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>Programming Photoshop</title>
		<link>http://leftjustified.net/journal/2004/08/08/program-ps/</link>
		<comments>http://leftjustified.net/journal/2004/08/08/program-ps/#comments</comments>
		<pubDate>Sun, 08 Aug 2004 11:24:00 +0000</pubDate>
		<dc:creator>Andrew</dc:creator>
				<category><![CDATA[design]]></category>
		<category><![CDATA[photoshop]]></category>

		<guid isPermaLink="false">http://localhost/lj/journal/2004/08/08/program-ps/</guid>
		<description><![CDATA[Whether you&#8217;re building your first homepage or pushing pixels for a living, most of us can improve our Photoshop workflow. This article provides an introduction to customizing Photoshop to meet your needs, as well as providing some freebies and different techniques that may be of interest to designers and developers alike.]]></description>
			<content:encoded><![CDATA[<p><em>*Mac users: All shortcuts are in PC speak (<code>Ctrl==Command</code>), please translate for yourselves.</em></p>
<h3>Code Monkeys &amp; Pixel Pushers</h3>
<p>Code monkeys (developers) love to think of themselves as the essence of efficiency, and compared to many designers, they are. We mere pixel pushers (designers), would be wise to learn from our code orientated brethren and take ten minutes to investigate how our own workflow could be streamlined, especially in the pre-code zone &mdash; Photoshop.</p>
<h3>Play it Again Sam</h3>
<p>Photoshop has the ability to record a set of steps to be repeated later, these are called <i>actions</i>. Anyone looking for actions in <a href="http://xchange.studio.adobe.com/" title="Adobe Studio Exchange">the usual places</a> may be excused for thinking that their intended purpose is to create tacky background and text effects. Actions are, in fact, a fantastic workflow optimization tool when used effectively. The criterion for an action is simple: Any regular procedure that requires more than one click or keystroke is suitable to be replaced by a pre-programmed action. </p>
<h3>Loading Action Sets</h3>
<p><img class="img-right" src="/posts/program-ps/load.gif" alt="The Actions Palette" /> To load an action set (<code>atn</code> file), select the right facing arrow in the top-right corner of the Actions palette. This will initiate a pop-out menu containing all the options for recording, loading and saving actions.</p>
<h3>What About the Freebies?</h3>
<p>Alright, I&#8217;m sure you&#8217;re starting to get edgy by now, so I&#8217;ll bring on the good stuff. The first few action sets are for basic web design practices &mdash; things like progressive blurring, layer orientation and creating CSS-like borders. After that, we&#8217;ll move on to the good stuff &#8211; avoiding all need for the old school &#8216;slice and dice&#8217; method of exporting a layout in favour of an action-packed alternative.</p>
<h3>Method Behind the Madness</h3>
<p>The actions themselves will be explained individually, but this is a good time to introduce the method behind my function key madness. From each set, the action which I believe is the most frequently used is assigned the function key without any alternators (<code>Shift</code> or <code>Ctrl</code>). The second most frequent action is assigned the <code>Shift</code> alternator (<code>Shift + F#</code>), and in the event of a third action per key, the third action is assigned both the <code>Shift</code> and <code>Ctrl</code> alternators. Action sets that use different numeric values for their actions, such as border widths and gaussian blur radii are ordered from smallest to largest &mdash; the smallest gets the function key, the second gets the <code>Shift</code> alternator and the third gets both alternator keys.</p>
<p><img class="img-center" src="/posts/program-ps/f-keys.gif" alt="Function quick reference" /><br />
The above diagram is intended as a <i>cheat sheet</i> for anyone who would like an on screen reminder while they give these actions a test run. </p>
<h4>Set 1 &#8211; Gaussian Blur</h4>
<p>When designing this site, I created every drop shadow manually; a very long and arduous process if you&#8217;re not prepared. Our first action set is to cater for such times, as well for procedures like blurring colour channels when making things like the classic <a href="/posts/program-ps/orb.tif" title="Layered example of an orb">orb</a> (layered .tif example), or Aqua button.</p>
<p><img class="img-right" src="/posts/program-ps/orb.png" alt="the good old photoshop orb" /> This set contains 3 different actions, all assigned to the F8 function key:</p>
<dl class="indent">
<dt>F8 &#8211; Blur 4, 2, 1, 0.5</dt>
<dd>This action applies the gaussian blur filter to the current layer/channel four times: Once at 4px, once at 2px, once at 1px and one last time at 0.5px. Blurring elements in this way ensures that the resulting gradient is as smooth as possible.</dd>
<dt>F8 + Shift &#8211; Blur 6, 3, 1.5, 0.7</dt>
<dd>Same effect as above, only more pronounced as it starts with a higher blur radius.</dd>
<dt>F8 + Shift + Ctrl &#8211; Blur 10, 5, 2.5, 1</dt>
<dd>The most pronounced of the Gaussian blur set, this action is for drastically softening an object.</dd>
</dl>
<p><a href="/posts/program-ps/blur.atn" class="file">Download gaussian-blur.atn</a></p>
<h4>Set 2 &#8211; Flip/Rotate</h4>
<p>Altering the orientation of layers or the canvas has got to be pretty high up on most designers&#8217; lists of frequent actions. So why not take those controls out of the menu system and put them at your fingertips? I&#8217;ve grouped these actions in relation to whether they affect the canvas or the current layer.</p>
<p>This set contains 8 different actions. Two per key for each key between F9 and F12:</p>
<dl class="indent">
<dt>F9</dt>
<dd>Rotate canvas 90&deg; clockwise</dd>
<dt>F9 + Shift</dt>
<dd>Rotate canvas 90&deg; counter-clockwise</dd>
<dt>F10</dt>
<dd>Flip canvas horizontal</dd>
<dt>F10 + Shift</dt>
<dd>Flip canvas vertical</dd>
<dt>F11</dt>
<dd>Rotate layer 90&deg; clockwise</dd>
<dt>F11 + Shift</dt>
<dd>Rotate layer 90&deg; counter-clockwise</dd>
<dt>F12</dt>
<dd>Flip layer horizontal</dd>
<dt>F12 + Shift</dt>
<dd>Flip layer vertical</dd>
</dl>
<p><a href="/posts/program-ps/flip-rotate.atn" class="file">Download flip-rotate.atn</a></p>
<h4>Set 3 &#8211; A Few Essentials</h4>
<p>The F7 key contains the most boring of today&#8217;s actions, image size and canvas size.<br />
These are right up there for common commands, so I decided they deserved a spot on the team.</p>
<dl class="indent">
<dt>F7</dt>
<dd>Image Size</dd>
<dt>F7 + Shift</dt>
<dd>Canvas Size</dd>
</dl>
<p><a href="/posts/program-ps/image-canvas-size.atn" class="file">Download image-canvas-size.atn</a></p>
<h4>Set 4 &#8211; The Good Stuff</h4>
<p>From the outset of this article I hinted towards an alternative to the tried and true <i>slice-dice-export</i> method of producing a graphics intensive web design. To be perfectly honest, that method drives me up the wall every time. There are always tiny alternations to be made down the line, resulting in either:</p>
<ol>
<li>Re-exporting the entire layout from Photoshop, disallowing the replacement of files you wish to keep</li>
<li>Opening ImageReady. The less said about that the better. <img src='http://leftjustified.net/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </li>
</ol>
<p>Don&#8217;t get me wrong, I&#8217;m not saying that there have never been alternatives other than these &mdash; it&#8217;s more that these two options are the most obvious and therefore the most commonly used. Compounding the problematic nature of the old slice-n-dice is that modern CSS layouts have to account for variables such as resizing text. This means we often need to leave overlaps in our background images, allowing the layout to &#8216;grow&#8217;. </p>
<p>Well fear not, because this handy action set contains all you need to ditch the slice tool for good. It contains the following six actions, two per key for each function key between F4+F6:</p>
<dl class="indent">
<dt>F4  Flat copy <em>canvas</em></dt>
<dd>Copies all layers of current canvas and creates a new layer containing the canvas copy. Simple, but useful.</dd>
<dt>F4 + Shift &#8211; New flat copy <em>canvas</em></dt>
<dd>Same effect as above,  except that the flat copy is made into a new image.</dd>
<dt>F5 &#8211; Flat copy <em>selection</em></dt>
<dd>Copies all layers of current selection and creates a new layer containing the canvas copy. This one&#8217;s great for duplicating repeating elements of a design.</dd>
<dt>F5 + Shift &#8211;  New flat copy <em>selection</em></dt>
<dd>Here&#8217;s the slice replacement &#8211; just select the area of your canvas that you wish to slice, hit <code>Shift+F5</code>, hit enter at the prompt and your ready to choose your export format.</dd>
<dt>F6 &#8211; New indexed flat copy <em>canvas</em></dt>
<dd>The same as the flat copy canvas action, except this one takes it one step further and converts the new image to indexed colour.</dd>
<dt>F6 &#8211; New indexed flat copy <em>selection</em></dt>
<dd>Guess what this one does? Go on, I bet you can&#8230;</dd>
</dl>
<p><a href="/posts/program-ps/prepare-4-web.atn" class="file">Download prepare-4-web.atn</a></p>
<h3>Choose Your own Adventure</h3>
<p>The aim of this article was never to say <i>&ldquo;This is how it should be done&rdquo;</i>, nor did I intend to provide a definitive guide to actions. My intention was simply this: </p>
<blockquote><p>To encourage others to take a moment to contemplate how they go about the small, repetitive procedures in their daily work and how they can make things easier for themselves.</p></blockquote>
<p>If you understand the reasoning behind setting something like this up, then surely you can also see the value in making a custom set to meet your own requirements and preferences. An extension on this approach is to have different action sets for different processes; eg. I have another set that are entirely for batch scanning &mdash; the most useful of which is a series of levels and curves tweaks that accounts for my faded old scanner. <b>Very</b> useful!</p>
<p>I hope you&#8217;ve enjoyed my first real article for Left Justified. You must have, or you wouldn&#8217;t have gotten this far! </p>
]]></content:encoded>
			<wfw:commentRss>http://leftjustified.net/journal/2004/08/08/program-ps/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
	</channel>
</rss>

