On Nov 25, 2008, at 4:14 AM, Tom Locke wrote:
> > The other thing that Paul's two "favourite pieces" reminds me about -- > HoboFields (field declarations in the model) is available as a > separate plugin and has been for a while. We've intended for a long > time that DRYML would be too, but we haven't done that work yet. That > would probably make it much easier for people to get into, and maybe > be a stepping stone for full Hobo. > Then again, I though HoboFields would be widely popular - I mean, who > wants to write migrations by hand? But it doesn't seem to be. So go > figure. It may be that people don't get the separation, and think that hobofields needs all the other pieces. The migration generator is nice, but the biggest win for me is the self-documenting aspect; opening up a plain Rails model is a bit of a treasure hunt, digging through a stack of migrations and/or the schema to find the fields for the object. Some things that I'm hoping to add to hobofields shortly: - better handling of habtm join tables; the migration generator currently tries to drop them. At the least, it would be nice to ignore them, but I'd really like to see the migrations generated. - Cleaner support for enumerations - enum_string is great, but I've needed to add extra structure around it to add "human names" for the various states. In the long run, I'd love to see the ideas in Hobofields incorporated into Rails core. Something like that would simplify model plugins significantly (just add the fields to the object, and let the migration generator do the hard work). --Matt Jones --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/hobousers?hl=en -~----------~----~----~----~------~----~------~--~---
