stouset/twitter_bootstrap_form_for — pull request #29 by kylecodes (2011-11-29 06:02:18+00:00)
Title: Different solution to inline elements

Howdy,
I saw that you just fixed the attribute nesting error, but I was working on another alternative before you pushed those changes. Probably should have said something, but, you know how that goes sometimes.
Anyway, one of the problems for me, at least, with returning a default rails builder is that I have subclasses your TwitterBootstrapFormFor::FormBuilder form builder so that I can do nifty things like automatically marking fields as required, populating dropdowns, etc. In inline forms, I lose all the stuff that I do in my subclassed form builder because it returns the default builder, which is no fun for me. Instead, I have it just yield the current instance of the form builder class that way we still have access to all the same nifty things from the form builder we are using.
So, ya, there you go. Let me know what you think.