Rails - Jul 2013 - Form objects vs nested attributes in 1 to many association

Recently I have been reading about form objects and have been wondering its 
use in 1 to many assocation.

Let''s say I have a model of project with many tasks and the user edits
the
project along with the tasks in one big form.

Is nested attributes using cocoon gem better suited than using 
reform/virtus or other form objects?  Any examples of using form objects in 
this context?

-- 
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit
https://groups.google.com/d/msgid/rubyonrails-talk/baa315e4-238c-4324-8da2-85c824344866%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.