<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: How to find image sizes in rails without image science</title>
	<atom:link href="http://pennysmalls.com/2007/12/26/how-to-find-image-sizes-in-rails-without-image-science/feed/" rel="self" type="application/rss+xml" />
	<link>http://pennysmalls.com/2007/12/26/how-to-find-image-sizes-in-rails-without-image-science/</link>
	<description>A blog about Ruby, Rails and other tech.  Mostly.</description>
	<lastBuildDate>Thu, 02 Sep 2010 19:56:26 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: photoshop restoration and retouching</title>
		<link>http://pennysmalls.com/2007/12/26/how-to-find-image-sizes-in-rails-without-image-science/comment-page-1/#comment-5149</link>
		<dc:creator>photoshop restoration and retouching</dc:creator>
		<pubDate>Tue, 11 Aug 2009 05:14:44 +0000</pubDate>
		<guid isPermaLink="false">http://pennysmalls.com/2007/12/26/how-to-find-image-sizes-in-rails-without-image-science/#comment-5149</guid>
		<description>This is absolutely great! Thanks!!</description>
		<content:encoded><![CDATA[<p>This is absolutely great! Thanks!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pennysmalls</title>
		<link>http://pennysmalls.com/2007/12/26/how-to-find-image-sizes-in-rails-without-image-science/comment-page-1/#comment-170</link>
		<dc:creator>Pennysmalls</dc:creator>
		<pubDate>Tue, 19 Aug 2008 07:05:46 +0000</pubDate>
		<guid isPermaLink="false">http://pennysmalls.com/2007/12/26/how-to-find-image-sizes-in-rails-without-image-science/#comment-170</guid>
		<description>[...] do not reside on our rails application server.  I have previously written about how to use the GD library to find image sizes, but this requires fetching the whole file and having it available in the local file [...]</description>
		<content:encoded><![CDATA[<p>[...] do not reside on our rails application server.  I have previously written about how to use the GD library to find image sizes, but this requires fetching the whole file and having it available in the local file [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Damien Tanner</title>
		<link>http://pennysmalls.com/2007/12/26/how-to-find-image-sizes-in-rails-without-image-science/comment-page-1/#comment-12</link>
		<dc:creator>Damien Tanner</dc:creator>
		<pubDate>Mon, 14 Jan 2008 17:04:08 +0000</pubDate>
		<guid isPermaLink="false">http://pennysmalls.com/2007/12/26/how-to-find-image-sizes-in-rails-without-image-science/#comment-12</guid>
		<description>Superb!</description>
		<content:encoded><![CDATA[<p>Superb!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Sykes</title>
		<link>http://pennysmalls.com/2007/12/26/how-to-find-image-sizes-in-rails-without-image-science/comment-page-1/#comment-8</link>
		<dc:creator>Stephen Sykes</dc:creator>
		<pubDate>Thu, 27 Dec 2007 07:50:33 +0000</pubDate>
		<guid isPermaLink="false">http://pennysmalls.com/2007/12/26/how-to-find-image-sizes-in-rails-without-image-science/#comment-8</guid>
		<description>Mike - rubyinline is smart - it compiles once and caches the compiled code.  It usually does this into a directory called .ruby_inline in your home, although it&#039;s configurable (look at the ENV[&#039;INLINEDIR&#039;] setting at the top of this code).

I have had good results with performance by using inline C code - maybe 10 times faster that the same ruby.  But the above example was not done for performance - I used gd for compatibility with my architecture (better than image science) and in order not to have to use a large package like RMagick for such a small task.</description>
		<content:encoded><![CDATA[<p>Mike &#8211; rubyinline is smart &#8211; it compiles once and caches the compiled code.  It usually does this into a directory called .ruby_inline in your home, although it&#8217;s configurable (look at the ENV['INLINEDIR'] setting at the top of this code).</p>
<p>I have had good results with performance by using inline C code &#8211; maybe 10 times faster that the same ruby.  But the above example was not done for performance &#8211; I used gd for compatibility with my architecture (better than image science) and in order not to have to use a large package like RMagick for such a small task.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://pennysmalls.com/2007/12/26/how-to-find-image-sizes-in-rails-without-image-science/comment-page-1/#comment-7</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Wed, 26 Dec 2007 23:41:43 +0000</pubDate>
		<guid isPermaLink="false">http://pennysmalls.com/2007/12/26/how-to-find-image-sizes-in-rails-without-image-science/#comment-7</guid>
		<description>Wow I have never realized you can use C code inside Ruby! 
I wonder, what about the performance of ImageInfo? Does it needs to get compiled every time a new instance is created, or it is compiled once and then can be used without performance decrease for compilation?</description>
		<content:encoded><![CDATA[<p>Wow I have never realized you can use C code inside Ruby!<br />
I wonder, what about the performance of ImageInfo? Does it needs to get compiled every time a new instance is created, or it is compiled once and then can be used without performance decrease for compilation?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
