I’m happy to announce a new minor release of file_column. It contains
two small fixes.
You can now serialize objects that have a file_column again, which
is important if you want to store these objects into the flash or the
If you want to use the RMagick integration and you’ve installed
RMagick yourself (instead of as a gem) it should work right out of the
Apart from these fixes, the plugin is finally available at a public
svn repository, so that you can use the cool new plugin script, rails
features in its latest release candidate. The repository is at:
Installation is as easy as typing
(you can still get an archive at
in your project’s directory. Warning: The trunk can be unstable. You
can find stable releases in the tags directory. Is there a standard
way of telling the plugin script about which version to use? I’m a bit
confused here, because the standard layout of plugin repositories does
not seem to contain the standard tags or branches directories. Can
somebody educate me about the repository conventions for plugins? How
do you make sure as a plugin developer, that your users only use
stable versions by default?
On a different note, I need some input on the future directions of
file_column, so that it suits your needs as well as possible. I have
already discussed some of these ideas with Kyle M… Thanks a lot
for your input, Kyle!
Basically I want to keep file_column as lean and general as possible,
while providing some more features that have been requested often and
making it easy for you to implement your more exotic needs. So here
are two points, where I’d be happy about feedback:
Right now, I’m using the RMagick library to use the imagemagick
toolkit. Is it hard to get this working under Windows? Would you
prefer file_column calling the imagemagick commands directly? I’d like
to keep the dependency on the RMagick library as it allows for much
more beautiful code and easier handling of images.
The versions feature allows you to declare in the model, that
several different sizes of an image should be stored that can
subsequently be accessed from your view. Kyle and I feel that this
information doesn’t really belong into the model, so Kyle suggested
that you can specify a geometry string in the view’s
url_for_file_column method. If an image does not exist in these
dimensions already, it will be created transparently and stored so
that it can be used again in the next request.
What do you think about this feature? Does it make sense? Should it
replace the declaration of versions in the model completely or should
it be an additional feature?
Thanks for all the encouranging feedback I have received so far!