Hobo 0.7 released
Posted by
Tom | December 3, 2007 7 Responses comments

Update:

I said you can pass CSS=y to the rake hobo:fixdryml task to instruct the script to ‘dasherize’ CSS class names. That should have been CLASS=y.

Hobo 0.7 is now available, both as a gem on rubyforge, and in via the repo trunk.

Template tags and non-template tags are now unified. This is really a huge improvement to DRYML. We’ve also switched to dashes instead of underscores for tag and attribute names.

Got any existing DRYML code? It doesn’t work any more. At all :-)

Fortunately, happiness is only a rake task away:

rake hobo:fixdryml

From the changelog:

We’ve switched to Rails 2.0 RC2 for our testing. Be warned – there’s a breaking change in Rails that might absorb some of your time as it did mine. It’s a change to fixtures – the default if you don’t give a value for a created_at or updated_at field, is now Time.now. It used to be nil like any other field.

There’s now only one significant feature that I want to add — fixing themes and CSS — before the push to 1.0 begins.

But before that, next up is beta.hobocentral.net!

Reader Comments Add your comment »

Woho! Great work guys! :)

I love hobo! ..but you already know that.

Awesome! You are on a roll. Can’t wait to see beta.hobocentral.net. That will make a HUGE impact.

Is there any way the community could help out with beta.HC.net?

[...] Hobo Updates Posted on December 12th, 2007 by george. Categories: Rails, Hobo.Well, we’re getting excited about Hobo again. [...]

How is the beta site coming along? I cannot wait :) will be having a long hobo coding effort between Christmas and new year to get some websites done, I think Hobo looks great!

I am anxious to hear about the progress as well. I will be at the in-laws over Christmas…a good time to work on a new website :)

[...] Hobo 0.7 released – Another round of this rapid design extension to Rails. [...]


Write a Comment

Please do not use blog comments for support or reporting bugs.

Please use the hobousers google group for help and support.

Comments are formatted using markdown. To include code, either quote it in `backticks` or indent a code-block by 4 spaces.