My first thought is for this to really work DRYly, lifecycles will need a new kind of transition. At least for the case where you can move back and forth between steps but not past the highest. For the case where you have a hard set list of steps with no vary in order, it'd work fine as is.
Otherwise, it might be better to make a wizard model, that can take information and store as a hash and when complete, create the new object from the hash. The tricky bit with that is how to handle validating of a partial field list. Though, with this style, a serialized hash and a target object and maybe another table to describe what fields in each step you could have something that a user could generate their own wizard inputs. -- 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.
