Hobo - the web application builder for Rails

On Friday I released three new Hobo gems: 1.0.2, 1.1.0.pre0 and 1.1.0.pre2. (1.1.0.pre1 was a glitch).

Here are the notes for 1.0.2 from CHANGES.txt:

1.0.2 is almost identical to 1.0.1 except that it updates the version requirements to exclude Rails3. (Rails3 support is being worked on in the 1.3 branch).

A few very minor bug fixes have also been included. See the github log for more details.

1.1.0.pre0 is essentially a packaging of Hobo trunk as it existed a month ago. (So it does not include the improvements added for 1.0.2) This version has been stable for people, and has been known to be used in production use.

The biggest difference between 1.0.X and 1.1.X is that Dryml has been split out into its own gem. There are also some very minor incompatibilities that affect things like CSS class names. The delta between 1.0.2 and 1.1.0.pre2 can be viewed on github

1.1.0.pre2 merges in fixes that have accumulated on several vendor branches of Hobo, as well as the 1.0.2 fixes. 1.1.0.pre2 requires the “–pre” option to be installed:

gem install hobo -v 1.1.0.pre2 --pre

As always when upgrading hobo versions, you will probably want to run

ruby script/generate hobo_rapid

or

rake hobo:symlink_assets

to ensure that you get the latest versions of the javascript and CSS files copied into your application.

Which version of Hobo should you use?

If you are currently using 1.0.0 or 1.0.1 in production, you only need to upgrade to 1.0.2 if you are also upgrading your version of Ruby or Rails or need one of the bugfixes listed here

If you have a Rails 2.3 project currently under active development, we recommend 1.1.0.pre2 (or the github master branch). Hopefully we have 1.1.0 released before you go to production — but even if we don’t, we do not believe that there are any issues that would prevent 1.1.0.pre2 from being usable in production.

If you are developing a new project and/or wish to use Rails 3, the 1.3 branch of Hobo currently being developed by Domizio is definitely stabilizing and becoming useful. The major issues preventing the release of 1.3 are all related to documentation.