Rails Obverser Bug Update
My bug report to rails was picked up and fixed. Them boys is fast. Pity that named routes appears to be broken in the current trunk, so I’ll have to leave off updating the rails external. But after fiddling around trying to see why it’s broken, I realised that it didn’t matter. My problem was that I’d been playing with my behaviors in the ”/app/models” directory – but they’re behaviors and should be getting loaded from the ”/app/behaviors” directory anywhere – and those files are loaded before the observer is registered. Doofus.
Haven’t had a chance to progress much further today. Ate more than my fill of indian at lunch, and have spent most of the day struggling to stay awake. I have whipped up a little faux-page object that delegates rendering back to a controller, so I should be able to go about writing the comment handler with all the functionality of a full rails controller. Suprising how easy that was. I’ll probably have the comments working either Monday or, if I have time, sometime this weekend, and then everybody can start telling me what I’m doing wrong (and bombard me with offers for cheap pharmaceuticals – should put some filtering into it).
After that it’s a toss-up between expanding the plugin system for radius (specifically – adding migrations and adding extra admin controllers should be easy for plugins) or pushing ahead with the extra functionality that I need to migrate The Groggy Squirrel over to radiant. I should really do the later, but the former seems like more being more interesting and the fact that it might be really disruptive is a good justification.