<?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: PaperClip: An Alternative Attachment / File Upload Plugin for Rails</title>
	<atom:link href="http://www.railsinside.com/plugins/149-paperclip-file-attachment-image-upload-plugin-for-rails.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.railsinside.com/plugins/149-paperclip-file-attachment-image-upload-plugin-for-rails.html</link>
	<description>Daily Rails news, views, tips, and joy</description>
	<lastBuildDate>Sat, 13 Mar 2010 09:39:30 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dragonfly: Image Handling For Champions</title>
		<link>http://www.railsinside.com/plugins/149-paperclip-file-attachment-image-upload-plugin-for-rails.html/comment-page-1#comment-1465</link>
		<dc:creator>Dragonfly: Image Handling For Champions</dc:creator>
		<pubDate>Thu, 11 Mar 2010 23:40:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.railsinside.com/plugins/149-paperclip-file-attachment-image-upload-plugin-for-rails.html#comment-1465</guid>
		<description>[...] – another one?!”.. I hear you exclaim. While using Dragonfly in Rails is similar to using, say, Paperclip, a significant difference is that images are generated on the fly, as opposed to when uploaded. [...]</description>
		<content:encoded><![CDATA[<p>[...] – another one?!”.. I hear you exclaim. While using Dragonfly in Rails is similar to using, say, Paperclip, a significant difference is that images are generated on the fly, as opposed to when uploaded. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Povess</title>
		<link>http://www.railsinside.com/plugins/149-paperclip-file-attachment-image-upload-plugin-for-rails.html/comment-page-1#comment-1212</link>
		<dc:creator>Povess</dc:creator>
		<pubDate>Mon, 07 Dec 2009 23:30:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.railsinside.com/plugins/149-paperclip-file-attachment-image-upload-plugin-for-rails.html#comment-1212</guid>
		<description>Yeah Paperclip is cool if you need a quick uploader tool. I&#039;m building an app now that transcodes video files and a lot of other stuff - thumbnails, screen grabs, transfer the files to a CDN, etc. after upload. I thought Paperclip would be cool because the processors in Paperclip give you a place to do that but it&#039;s a freaking pain. I&#039;ve ended up writing my own methods in my models to deal with all the functionality I need. Things like deleting the files, thumbnailing, naming, etc. Yeah it may remove the file attachment but leaves folders and the others files I create on upload. So almost all the benefits of it have been lost. I&#039;m in process of just creating my own file management methods too. So once that&#039;s done goodbye paperclip. But I still would use it for quick image uploads. I do recommend it for that. The problem I see is that there a lot of cool plugins out there that get you going quick, but when you really look at the real functionality you need - upload a file, move it to a directory, and name it....do you really need a plugin?</description>
		<content:encoded><![CDATA[<p>Yeah Paperclip is cool if you need a quick uploader tool. I'm building an app now that transcodes video files and a lot of other stuff - thumbnails, screen grabs, transfer the files to a CDN, etc. after upload. I thought Paperclip would be cool because the processors in Paperclip give you a place to do that but it's a freaking pain. I've ended up writing my own methods in my models to deal with all the functionality I need. Things like deleting the files, thumbnailing, naming, etc. Yeah it may remove the file attachment but leaves folders and the others files I create on upload. So almost all the benefits of it have been lost. I'm in process of just creating my own file management methods too. So once that's done goodbye paperclip. But I still would use it for quick image uploads. I do recommend it for that. The problem I see is that there a lot of cool plugins out there that get you going quick, but when you really look at the real functionality you need - upload a file, move it to a directory, and name it....do you really need a plugin?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jose HG</title>
		<link>http://www.railsinside.com/plugins/149-paperclip-file-attachment-image-upload-plugin-for-rails.html/comment-page-1#comment-167</link>
		<dc:creator>Jose HG</dc:creator>
		<pubDate>Fri, 28 Nov 2008 18:09:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.railsinside.com/plugins/149-paperclip-file-attachment-image-upload-plugin-for-rails.html#comment-167</guid>
		<description>I&#039;ve tried PaperClip but I can&#039;t say goodbye to A-fu.

PaperClip doesn&#039;t work as reliably as A-fu with files other than images.

I need to upload PDF and Word docs, just to name a couple.  PaperClip crashes with PDFs.

So for handling a wide-range of file formats and dependable performance, A-fu is still the way to go for me.</description>
		<content:encoded><![CDATA[<p>I've tried PaperClip but I can't say goodbye to A-fu.</p>
<p>PaperClip doesn't work as reliably as A-fu with files other than images.</p>
<p>I need to upload PDF and Word docs, just to name a couple.  PaperClip crashes with PDFs.</p>
<p>So for handling a wide-range of file formats and dependable performance, A-fu is still the way to go for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Akhil Bansal</title>
		<link>http://www.railsinside.com/plugins/149-paperclip-file-attachment-image-upload-plugin-for-rails.html/comment-page-1#comment-143</link>
		<dc:creator>Akhil Bansal</dc:creator>
		<pubDate>Mon, 17 Nov 2008 11:34:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.railsinside.com/plugins/149-paperclip-file-attachment-image-upload-plugin-for-rails.html#comment-143</guid>
		<description>Hi,

I have used paper clip too, for one of my project. Its worth using it if you don&#039;t have much image handelling. :)</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I have used paper clip too, for one of my project. Its worth using it if you don't have much image handelling. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Timothy Johnson</title>
		<link>http://www.railsinside.com/plugins/149-paperclip-file-attachment-image-upload-plugin-for-rails.html/comment-page-1#comment-126</link>
		<dc:creator>Timothy Johnson</dc:creator>
		<pubDate>Mon, 10 Nov 2008 14:22:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.railsinside.com/plugins/149-paperclip-file-attachment-image-upload-plugin-for-rails.html#comment-126</guid>
		<description>I&#039;ve been using Paperclip as my default for over a year now, and I can tell you it is well worth it. I have even switched old applications over from A-fu to using Paperclip because of its simplicity and utility.

For everyone who asks the question: How do you have many attachments to a model like Attachment-fu does? Well easily enough you can make a separate Model with a has_many relationship (like A-fu does by default) and define your Paperclip attachment there, instead of in the model directly. I find this to be the win, that I can just define a has_one attachment directly in the model, or break it out into its own class with all the attributes it needs.</description>
		<content:encoded><![CDATA[<p>I've been using Paperclip as my default for over a year now, and I can tell you it is well worth it. I have even switched old applications over from A-fu to using Paperclip because of its simplicity and utility.</p>
<p>For everyone who asks the question: How do you have many attachments to a model like Attachment-fu does? Well easily enough you can make a separate Model with a has_many relationship (like A-fu does by default) and define your Paperclip attachment there, instead of in the model directly. I find this to be the win, that I can just define a has_one attachment directly in the model, or break it out into its own class with all the attributes it needs.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
