<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><atom:link rel="hub" href="http://tumblr.superfeedr.com/" xmlns:atom="http://www.w3.org/2005/Atom"/><description></description><title>imgstack development blog</title><generator>Tumblr (3.0; @imgstack)</generator><link>http://blog.imgstack.com/</link><item><title>It's Alive!</title><description>&lt;p&gt;&lt;img/&gt; stack has been something I’ve been working on for a while.  It was originally built back in 2006 when I started developing Cupid’s Lab (&lt;a href="http://www.cupidslab.com"&gt;&lt;a href="http://www.cupidslab.com"&gt;http://www.cupidslab.com&lt;/a&gt;&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;I was solving the problem of my inability to design user interfaces.  Typically I would prototype a UI in the platform I was building.  It would start as a basic HTML page with content linearly running down the page in a waterfall of text and images.  Over time I would tweak and mold the html to present the data in some sort of organized form.&lt;/p&gt;
&lt;p&gt;Most of the time I was tweaking the size of cells and images on a page.  This would often lead me to have to recut or batch process images to fit the new size.  That’s a workflow nightmare.  Especially for someone like me who is indecisive and will change something hundreds of times before I think it’s _right_.&lt;/p&gt;
&lt;p&gt;This brought about the creation of &lt;img/&gt; stack.  I wanted to simply request the image based on how I needed it for the page and just expect it to be there.  Cropped, resized, centered… I didn’t want to have to go back and forth between photoshop and batch processing scripts.&lt;/p&gt;
&lt;p&gt;So now I’ve decided to take a few hours and build a standalone service of the tool set I created for Cupid’s Lab.  I hope you enjoy it!&lt;/p&gt;</description><link>http://blog.imgstack.com/post/74258253</link><guid>http://blog.imgstack.com/post/74258253</guid><pubDate>Fri, 30 Jan 2009 03:22:08 -0500</pubDate></item></channel></rss>
