Regdel on Ruby on Rails is Coming Right Along

I’m really pleased with Ruby on Rails 3.1… its my favorite version of Rails yet! And I’m pleased to report that progress of Regdel upon it is coming along very nicely.

Here are a few parts I’ve been working on lately:

  • A memcached interface for caching certain parts of the logic during development mode. What I’ve done so far won’t be necessary in production as the classes get cached, but I’ll probably add something that will benefit from getting cached in production at some point. (See this interesting post about undefined module / classes when using Memcached).
  • Better user interface! A lot of work was done on the user interface of the Sinatra version of Regdel, and some of that is working now. I’m changing the way entries will get displayed so that they are more contextual, like checks and transfers, and I plan to port the old general journal entry form to the new version, too. I had to make some changes in the regdel.sass file, but nothing major. I actually really like the updated sass syntax.
  • Tests! I actually setup Regdel to be continuously tested with Travis and while I was able to get it to pass last night, I don’t think it will regularly - only because of problems with gems - specifically Rails 3.1 is pulled from github and AFAIK Travis can’t do that yet.
  • Integration with awesome gems! I’m using state_machine, nested_set, and inherited_resources. They are all amazing gems and so far are working quite well with Rails 3.1.
  • Organization of models. Wow - this took a long time, too. Sort of related to the issue I mention with memcached, putting some models in a sub-folder without making them namespaced was a serious PITA. To make it happen, I added this in config/application.rb:
config.autoload_paths += Dir["#{config.root}/app/models/accounts"]

That, plus the loader in the application controller I mention here seem to do the trick.

Remember, at this time, Regdel is seriously unstable. I make changes to existing migrations on the reg, then trash my db, migrate and seed it again, so don’t expect any upgrade compatibility for quite some time.

If you are interested in collaborating, please let me know on gituhub!

By Albert on August 14, 2011 11:34 AM

Categories:

Categories