Since form_for implicitly writes to the "_erbout" variable via the
config method, the inline button method in my helper, which used to
generate a string which was included in the view using <%=
inline_button(...) %>, now simply takes a passed in output writer (from
the view) and manipulates it directly.
1) The caller (a view) must call this using Ruby eval. tags, <%
inline_button(_erbout, ...) %>
2) The caller (a view) must pass the _erbout variable into the helper,
since both form_for() and concat() expect that variable to be in scope.
3) The parameter in inline_button _must_ be named _erbout for the same
reason as #2.
4) I'm not capturing the yielded form_builder from the call to form_for
because I don't need it.
So it's