<?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>Ben&#039;s blog and portfolio &#187; jpg</title>
	<atom:link href="http://benthinkin.net/tag/jpg/feed" rel="self" type="application/rss+xml" />
	<link>http://benthinkin.net</link>
	<description>Website design by Ben Gremillion</description>
	<lastBuildDate>Sat, 21 Jan 2012 20:10:02 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>How to manage a controlled collision of type and imagery</title>
		<link>http://benthinkin.net/articles/imagery/how-to-manage-a-controlled-collision-of-type-and-imagery</link>
		<comments>http://benthinkin.net/articles/imagery/how-to-manage-a-controlled-collision-of-type-and-imagery#comments</comments>
		<pubDate>Thu, 15 Jul 2010 13:49:47 +0000</pubDate>
		<dc:creator>Ben</dc:creator>
				<category><![CDATA[Imagery]]></category>
		<category><![CDATA[how-to]]></category>
		<category><![CDATA[jpg]]></category>
		<category><![CDATA[png]]></category>
		<category><![CDATA[typography]]></category>
		<category><![CDATA[WDD]]></category>

		<guid isPermaLink="false">http://test.benthinkin.net/?p=69</guid>
		<description><![CDATA[Setting images into text mixes words&#8217; straightforward communication with photos&#8217; emotional implications. Words state; photos express. But conflicts result when the images get lost or the text becomes muddled. Or both. Images and text can successfully mix&#8212;if we follow some guidelines that balance readability in both text and images.]]></description>
			<content:encoded><![CDATA[<p>
	Setting images into text mixes words&#8217; straightforward communication with photos&#8217; emotional implications. Words state; photos express. But conflicts result when the images get lost or the text becomes muddled. Or both. Images and text can successfully mix&#8212;if we follow some guidelines that balance readability in both text and images.
</p>
<p>
	<a href="http://www.webdesignerdepot.com/2010/07/mixing-type-and-imagery-how-to-manage-a-controlled-collision/"><span>Read the full article I wrote at Webdesigner Depot.</span></a>
</p>
<p>
	<img src="/content_resources/051-images-into-text/cut-outs.jpg" alt="insetting photos into type" />
</p>
<p>
	Above: Turning block-shaped photos into text means cutting into the image. The more cuts made, the greater a chance for cutting out something important.
</p>
<p>
	<img src="/content_resources/051-images-into-text/active-summer-2.jpg" alt="insetting photos into type" /></p>
]]></content:encoded>
			<wfw:commentRss>http://benthinkin.net/articles/imagery/how-to-manage-a-controlled-collision-of-type-and-imagery/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Save-for-web feature comparisons</title>
		<link>http://benthinkin.net/articles/imagery/save-for-web-feature-comparisons</link>
		<comments>http://benthinkin.net/articles/imagery/save-for-web-feature-comparisons#comments</comments>
		<pubDate>Mon, 05 Jul 2010 16:26:43 +0000</pubDate>
		<dc:creator>bbb</dc:creator>
				<category><![CDATA[Imagery]]></category>
		<category><![CDATA[acorn]]></category>
		<category><![CDATA[jpg]]></category>
		<category><![CDATA[photoshop]]></category>
		<category><![CDATA[pixelmator]]></category>
		<category><![CDATA[png]]></category>

		<guid isPermaLink="false">http://test.benthinkin.net/?p=7</guid>
		<description><![CDATA[Photoshop may be popular, but does it save the best web images? I compared it to Acorn and Pixelmator 1.5.1 to find out.]]></description>
			<content:encoded><![CDATA[<p>
	Photoshop may dominate the image editing business, but it doesn&#8217;t stand alone. This week I looked at <a href="http://flyingmeat.com/acorn/"><span>Acorn</span></a> and <a href="http://www.pixelmator.com/"><span>Pixelmator</span></a>, two lightweight image editors for the Mac.
</p>
<p>
	This posts asks the question: Which app saves the best images for websites? I tested two images with Acorn 2.3.1, Photoshop CS3 (v10.0.1) and Pixelmator 1.5.1 to find out.
</p>
<p><img src="/content_resources/049-save-for-web-tests/save-for-web-teaser.jpg" alt="save for web in various apps" /> </p>
<h2>
	JPG file size<br />
</h2>
<p>
	Image dimensions: 500&#215;220 pixels.
</p>
<p><img src="/content_resources/049-save-for-web-tests/set2_source.jpg" alt="source image 2" /> </p>
<p>
	Image dimensions: 800&#215;533 pixels.
</p>
<p><img src="/content_resources/049-save-for-web-tests/set1_source.jpg" alt="source image 1" /> <img src="/content_resources/049-save-for-web-tests/chart-1.png" alt="" /> <img src="/content_resources/049-save-for-web-tests/chart-2.png" alt="" /> </p>
<p>
	These charts show how small each app compressed two images. Acorn created the largest files at 100% and the most erratic results overall, but did well for in the teens, a size I commonly aim for on the web.
</p>
<p>
	Photoshop&#8217;s files tended to be the most predictable. Its files were most efficient when highly compressed.
</p>
<p>
	For both files, Pixelmator produced the smallest file sizes between 40% and 100%. But its file sizes doubled—or more—between 90% and 100%.
</p>
<h2>
	JPG quality<br />
</h2>
<p>
	File size is only part of the equation. How do the final images look? Samples from 0% compression show how each app&#8217;s artifacts—the changes it makes to improve file size—vary from each other.
</p>
<p>
	The results are subjective, but Photoshop seems to sacrifice the most detail, especially in the shingles and stone walls. However, at 0% compression Photoshop&#8217;s file is about 25% smaller than Pixelmator&#8217;s and 36% smaller than Acorn&#8217;s.
</p>
<p>
	<img src="/content_resources/049-save-for-web-tests/samples.jpg" alt="samples up-close" />
</p>
<p>
	Based more on gradients than organic textures, the difference in quality for the second image was harder to spot. Pixelmator&#8217;s artifacts seem to match Photoshop&#8217;s more than Acorn&#8217;s, though it&#8217;s only apparent when the samples are overlaid onto each other.
</p>
<p>
	<img src="/content_resources/049-save-for-web-tests/samples-2.jpg" alt="samples up-close" />
</p>
<h2>
	PNG<br />
</h2>
<p>
	Saving PNG files is a different story. Acorn can only save 24-bit PNGs, which result in enormous (if flawless) images. Pixelmator can save both 8- and 24-bit PNGs, but lacked the precision found in Photoshop. Photoshop enables users to choose the number of colors in a PNG, the type and amount of dithering, and the ability to manually change individual colors in the palette. Pixelmator, however, only has a slider for choosing the number of colors.
</p>
<p>
	Pixelmator&#8217;s PNG resembled Photoshop&#8217;s PNG, sans-dithering. Pixelmator&#8217;s image was slightly larger than Photoshop&#8217;s non-dithered file, but significantly smaller than either of Photoshop&#8217;s dithered files. Pixelmator&#8217;s PNGs are better suited for images with relatively few colors—graphics and icons over illustrations.
</p>
<p>
	<img src="/content_resources/049-save-for-web-tests/ps-0-dither.png" alt="" /><br />
	Photoshop, no dither: 12,805KB
</p>
<p>
	<img src="/content_resources/049-save-for-web-tests/ps-88-dither.png" alt="" /><br />
	Photoshop, 88% dither (default): 15,554KB
</p>
<p>
	<img src="/content_resources/049-save-for-web-tests/pxm.png" alt="" /><br />
	Pixelmator: 13,812KB
</p>
<p>
	<img src="/content_resources/049-save-for-web-tests/ps-100-dither.png" alt="" /><br />
	Photoshop, 100% dither: 17,386KB
</p>
<p></p>
<h2>
	Overall results<br />
</h2>
<p>
	Even before <a href="http://www.wired.com/techbiz/media/news/2005/04/67259"><span>Adobe bought their competition</span></a>, Photoshop was the favorite choice for image editing. Its 20+ years of development keep it ahead of the newcomers like Pixelmator and Acorn. Still, I&#8217;m looking forward to seeing how these low-cost, high-performance apps develop.
</p>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://benthinkin.net/articles/imagery/save-for-web-feature-comparisons/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

