I'm trying to use a lifecycle, because it seems like its probably the right solution, but I can't really seem to get started. This project started with the recipe tutorial in the book, but has moved on past it. I have two models: recipe, and request. At the moment there is no relationship between them, though both belong to user. I'd like to create a lifecycle to start with a request and end up with a recipe. When a user responds to a request, it should take them to a new recipe page. If that recipe is saved (created), then the state of the request should change (:unfulfilled => :fulfilled). I could make a one-to-one relationship between request and recipe, though that seems strange because most requests do not yet have recipes, and many recipes do not have requests.
I could not find any examples of lifecycles in the docs where one model contains the lifecycle, but another model responds to its controller events. Any ideas would be welcome. Mark Sobkowicz -- 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.
