Merb 0.4.2 released.

Posted by ezmobius Fri, 14 Dec 2007 08:53:00 GMT

Merb 0.4.2 is released as a gem. This release polishes up a number of rough spots and vastly improves performance in some areas. Should be a simple upgrade for anyone on 0.4.0 or later.

Here is the changelog:

== 0.4.2 “Surf’s up.” 2007-12-14
  • Super-huge speed boost for rendering Erubis templates with partials
  • Windows-specific fixes to Merb’s Rakefile
  • Blocking write is called when in development, test, Windows and jRuby environments and platforms.
  • merb_helpers: form field labels are now explicit, huge documentation update, added select, fieldset, more helpers
  • Fixed merb.show_routes within merb -i
  • Fixed image_tag, css_include_tag, and js_include_tag to work with path_prefix
  • Adds spec helper methods with_route and dispatch_to
  • fix rakefile cfor cygwin
  • add count with collection to partial()
  • Form control mixin is deprecated Use merb_helpers plugin.
  • add redirect matcher to rspec test helpers
  • allow r.resource(:foo, :myparam => 42) resource routes pass on params to underlying match() call
  • spit out error and help message if you call merb with no args
  • get rid of dependency on mongrel for escape and unescape
  • make sure not to use write_nonblock when logging to STDOUT
  • Fixed image_tag, css_include_tag, and js_include_tag to work with path_prefix
  • fix set_status to actually work, add docs,
  • config/merb.yml is now correctly loaded from Rake and test environment – using Merb::Server.load_config
  • added config option to disable loading of the JSON gem – still enabled by default
  • don’t raise if names local on a partial is nil
  • Use svn export instead of checkout upon merb:freeze_from_svn
  • Extracted url and other general methods out of ControllerMixin into GeneralControllerMixin
  • fix caching of @_buffer in render, form_for
  • Seperates spec helpers into the Merb::Test namespace to prevent spec methods leaking into specs
  • Changes the spec url helper method to the same used in the controller
  • Made Request#parse_multipart return an empty hash instead of nil if the request is not multipart
  • Changes throw_content so that it can be called without a block
  • Added :namespace option to routes.

Tags  | 3 comments

Comments

Leave a response

  1. Brian said about 5 hours later:
    I keep meaning to check out merb. The one question I have is how hard would it be to port plugins from rails to merb? Granted it really depends on the plugin and whether you still use active record, but as a general rule, how hard is it? Also could you still use activesupport in merb or would it not mess with the implementation of merb?
  2. Matthijs Langenberg said 2 days later:
    Brian, the time it will take to port a plugin totally depends on the type of plugin, I don't think you can put a number on it. Since the internals of merb quite differ with Rails (except for ActiveRecord) you will need to re-implement the plugin's functionality again instead of simply adapting the code for a new API. But since the specifications are already there, and the merb code is a beauty, porting some rails plugin should be a walk in the park.
  3. Garth said 7 days later:
    How ready is merb for production? I have a Rails app which involves a fair amount of uploading to the server and I'm considering porting to merb - I'm not keen the rails bloat, plus the threading issue of uploads etc. Is there a proposed naming convention for merb plugins? For instance, acts_as_taggable for activerecord/rails. What would you suggest for the merb equivalent?

RSS feed for this post trackback uri

(leave url/email »)

   Preview comment