Nearly there…
Posted by
Tom | March 31, 2008 6 Responses comments

So here I am at the Ruby Fools conference in Copenhagen, and I did say we were going to try and have some new stuff ready by now. We’re nearly there. Stay tuned over the next few days.

First off though, I better deflate your expectations a bit. I don’t know if this was my fault for wording the last blog post badly, but a few people seem to have gained some pretty wild expectations about what’s coming. Terms like “fully documented” and even (gasp) “version 1.0″ have been bouncing around. Sorry folks, there’s good stuff coming but I never meant to give you that idea. Apologies for any confusion.

What is coming is this — we are turning the corner and focussing our energy on making Hobo into something everyone can use. That means breaking it up into parts, and writing more documentation and tests. The process has begun, and the first installment is on the way. Here’s what we’re about to put out. (If you know where to look you’ll know that some of these things are in fact available already. We’re just holding off from the ‘official’ release so we can promote the new stuff properly in a few places).

  • Hobo 0.7.4
  • HoboSupport as a separate gem (core Ruby extensions). With full docs!
  • HoboFields plugin. This is something a lot of people have asked for — the migration generator as a separate plugin. HoboFields will be well documented too :-)
  • Significant improvements to the current Hobo tutorial (the POD classified ads application)
  • An entirely new tutorial — this is the one I delivered today at the conference. It goes through the full development of an app for tracking an agile development process (sort of a mini Mingle). Runs to 13 pages when printed.
  • A DRYML guide covering all of the basic facilities that DRYML provides.
  • A revamped hobocentral.net
  • Very nice online access to the source-code and commit log (from a service you may have heard of)
  • A very nice ticketing system that won’t drown in spam like the last one (also from a service you may know)
  • Possibly some other stuff I’ve forgotten because this is all off the top of my head and it’s kinda late.

So it’s not 1.0 and it’s not fully documented but I hope it’s enough to demonstrate that we’re serious about moving Hobo in the right direction now. And like I said, it’s nearly ready. Watch this space.

Reader Comments Add your comment »

Thanks again for all your work on this. I really like Hobo and it is s super accelerator for me.

I am writing to recommend against holding off release for promotional purposes. As I read the forums, there are plenty of people excited about Hobo but burning out for a lack of documentation.

A few more success stories from happy customers will have greater benefits than the drama of an unveiling. And frankly, I’d be happy to have my apps be among those success stories.

I suggest the release of whatever you believe is ready as soon as it is ready.

Thanks again, and best wishes.

Pd

Online access to the source code and commit log might be related to http://github.com/tablatom …

As for an issue tracker, would that be your Agile demo? Or are you thinking lighthouseapp or something like it?

As always, can’t wait. Hobo is really starting to look good.

Paul - We definitely don’t want to hold back docs that are already useful. Everything is online in at github.com/tablatom. It’s just that the new website that links it all up nicely isn’t finished yet

sounds very nice :)
thank you guys

Tom,

I am really looking forward to the doc and new screencasts. As you have seen, many of us see the potential, but lack of documnetation and version issues have limited implementation.

The goal of my team is to provide our clients with an alternative to JSF applications in the US federal sector. We MUST improve our productivity. I have been developing applications for over 25 years and have seen web-oriented development slow down mission-critical application development to a crawl compared to repository-based thick-client tools of the 1990’s. Tools like Hobo and Rails appear to have the potential to reverse this trend.

Please keep up the momentum…

Good news! We are waiting!


Write a Comment

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