The Direction of Monkeybars

I've pretty much taken the reigns in terms of Monkeybars maintenance. I've been adding in the cool new View Bindings (many more have been added since that post). However, I realized that Monkeybars has a small following, and that I should listen to what they feel is missing from Monkeybars. I didn't get many responses. Perhaps this is great. No news is good news!

My users said two things: more documentation and automatic builds (to make Ruby debugging easier). Can do.

We have a wiki up, and our users have been filling it nicely. As a maintainer who is much more intimiate with the project, I should be doing a lot of those docs as well. I shall commit to doing one wiki page a week. I think that's fairly reasonable.

Automated builds is very interesting. It should would make doing the occasional rawr:jar even faster if there was a background process that compiled stuff as you changed it. It'll need some work in Rawr. The big advantage with doing this is that you can create your Monkeybars project as a Ruby Project (right now we recommend a Java project). Ruby projects can be debugged as Ruby. Netbeans, as I understand, has a pretty decent debugger for Ruby, but that's something that's sorely lacking in other projects.

If you have something you'd like to see on Monkeybars, this thread should be open as long as the mailing list is open.