i have project involved genealogy. starts asking questions (current user), same questions father, same questions mother , goes on until grandparents of both sides. unfortunately, have tried 3 different approaches , implementations, each time correcting past mistakes pretty new rails. i recommendation/guidance community regarding best design approach should follow having design problems. so think best way come different tables benefit later when need put info in single family tree. so, 1 table current user, 1 father, mother, etc having model each table using single controller because have same html.erb form , each time changes headers adapt sibling question. i had created flow , actions such new, create, show etc problem following: the flow of questions consecutive, , @ end shows family tree. therefore when user clicks continue, data saved in equivalent table of database , flow continues next table. i stuck more 8 hours on how make create method change father mother h...
Comments
Post a Comment