Re: how to manage creation of many-to-one (child) objects on separate page during creation of object
I can't say for sure that it does, I didn't need such a feature but I think it can be customized to support that. On Mon, May 16, 2011 at 7:40 PM, br wrote: > Cool. I'll have to look at that. Does this support nonlinear form > flows (i.e., you go from Form1 to Form2 back to Form1 and then hit > submit) or is there another app for that? > > > On May 16, 7:50 am, Lucian Nicolescu wrote: >> Did you check out the form wizard that Django comes >> with?http://docs.djangoproject.com/en/dev/ref/contrib/formtools/form-wizard/ >> Sounds like this is what you are looking for ... multipage forms. >> >> Lucian >> >> >> >> >> >> >> >> On Mon, May 16, 2011 at 4:46 PM, br wrote: >> > I have not written this yet, so am not posting code (yet). Also, I am >> > implementing a client facing interface (not using django admin for >> > this part). >> >> > I am sure this is common thing to do, in fact, I beleive it is done in >> > django admin, but I am somewhat confused as to the best or standard >> > way to do it. Here is the scenario. >> >> > I am creating a page for editing and/or creating an object. (we'll >> > call it a poll, to be consistent with tutorial.) >> > The page provides a place for user to enter or edit the fields for the >> > poll corresponding to the model fields. >> > The Poll model has another model with a foreign key to it. (e.g. >> > Choice) >> > On the poll page, I want to show a list of the choices for the poll, >> > where each choice has a link to edit the choice, and there is also a >> > link to add a new choice. (for a new poll, there wouldn't be any >> > choices to start) >> > The link takes you to a choice page (or pops out a window page) where >> > you can edit or create the choice. >> > You hit OK on the choice page to come back to the poll page, which has >> > a list of choices that is updated with the new choice or the edited >> > choice. >> > You don't want to save the choice to the database until the poll is >> > saved (i.e. they can hit cancel and the poll and any changes to >> > choices are not saved.) >> >> > How to accomplish this "transaction" back and forth between the two >> > pages, where neither poll nor choices is saved until the Save button >> > is hit on the Poll page? Specifically, how to pass the data between >> > the two pages without explicitly saving each choice to the DB? Seems >> > like there is probably a standard mechanism for doing this. >> >> > Thanks, >> >> > Ben >> >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "Django users" group. >> > To post to this group, send email to django-users@googlegroups.com. >> > To unsubscribe from this group, send email to >> > django-users+unsubscr...@googlegroups.com. >> > For more options, visit this group >> > athttp://groups.google.com/group/django-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: how to manage creation of many-to-one (child) objects on separate page during creation of object
Cool. I'll have to look at that. Does this support nonlinear form flows (i.e., you go from Form1 to Form2 back to Form1 and then hit submit) or is there another app for that? On May 16, 7:50 am, Lucian Nicolescu wrote: > Did you check out the form wizard that Django comes > with?http://docs.djangoproject.com/en/dev/ref/contrib/formtools/form-wizard/ > Sounds like this is what you are looking for ... multipage forms. > > Lucian > > > > > > > > On Mon, May 16, 2011 at 4:46 PM, br wrote: > > I have not written this yet, so am not posting code (yet). Also, I am > > implementing a client facing interface (not using django admin for > > this part). > > > I am sure this is common thing to do, in fact, I beleive it is done in > > django admin, but I am somewhat confused as to the best or standard > > way to do it. Here is the scenario. > > > I am creating a page for editing and/or creating an object. (we'll > > call it a poll, to be consistent with tutorial.) > > The page provides a place for user to enter or edit the fields for the > > poll corresponding to the model fields. > > The Poll model has another model with a foreign key to it. (e.g. > > Choice) > > On the poll page, I want to show a list of the choices for the poll, > > where each choice has a link to edit the choice, and there is also a > > link to add a new choice. (for a new poll, there wouldn't be any > > choices to start) > > The link takes you to a choice page (or pops out a window page) where > > you can edit or create the choice. > > You hit OK on the choice page to come back to the poll page, which has > > a list of choices that is updated with the new choice or the edited > > choice. > > You don't want to save the choice to the database until the poll is > > saved (i.e. they can hit cancel and the poll and any changes to > > choices are not saved.) > > > How to accomplish this "transaction" back and forth between the two > > pages, where neither poll nor choices is saved until the Save button > > is hit on the Poll page? Specifically, how to pass the data between > > the two pages without explicitly saving each choice to the DB? Seems > > like there is probably a standard mechanism for doing this. > > > Thanks, > > > Ben > > > -- > > You received this message because you are subscribed to the Google Groups > > "Django users" group. > > To post to this group, send email to django-users@googlegroups.com. > > To unsubscribe from this group, send email to > > django-users+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/django-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: how to manage creation of many-to-one (child) objects on separate page during creation of object
Did you check out the form wizard that Django comes with? http://docs.djangoproject.com/en/dev/ref/contrib/formtools/form-wizard/ Sounds like this is what you are looking for ... multipage forms. Lucian On Mon, May 16, 2011 at 4:46 PM, br wrote: > I have not written this yet, so am not posting code (yet). Also, I am > implementing a client facing interface (not using django admin for > this part). > > I am sure this is common thing to do, in fact, I beleive it is done in > django admin, but I am somewhat confused as to the best or standard > way to do it. Here is the scenario. > > I am creating a page for editing and/or creating an object. (we'll > call it a poll, to be consistent with tutorial.) > The page provides a place for user to enter or edit the fields for the > poll corresponding to the model fields. > The Poll model has another model with a foreign key to it. (e.g. > Choice) > On the poll page, I want to show a list of the choices for the poll, > where each choice has a link to edit the choice, and there is also a > link to add a new choice. (for a new poll, there wouldn't be any > choices to start) > The link takes you to a choice page (or pops out a window page) where > you can edit or create the choice. > You hit OK on the choice page to come back to the poll page, which has > a list of choices that is updated with the new choice or the edited > choice. > You don't want to save the choice to the database until the poll is > saved (i.e. they can hit cancel and the poll and any changes to > choices are not saved.) > > How to accomplish this "transaction" back and forth between the two > pages, where neither poll nor choices is saved until the Save button > is hit on the Poll page? Specifically, how to pass the data between > the two pages without explicitly saving each choice to the DB? Seems > like there is probably a standard mechanism for doing this. > > Thanks, > > Ben > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
how to manage creation of many-to-one (child) objects on separate page during creation of object
I have not written this yet, so am not posting code (yet). Also, I am implementing a client facing interface (not using django admin for this part). I am sure this is common thing to do, in fact, I beleive it is done in django admin, but I am somewhat confused as to the best or standard way to do it. Here is the scenario. I am creating a page for editing and/or creating an object. (we'll call it a poll, to be consistent with tutorial.) The page provides a place for user to enter or edit the fields for the poll corresponding to the model fields. The Poll model has another model with a foreign key to it. (e.g. Choice) On the poll page, I want to show a list of the choices for the poll, where each choice has a link to edit the choice, and there is also a link to add a new choice. (for a new poll, there wouldn't be any choices to start) The link takes you to a choice page (or pops out a window page) where you can edit or create the choice. You hit OK on the choice page to come back to the poll page, which has a list of choices that is updated with the new choice or the edited choice. You don't want to save the choice to the database until the poll is saved (i.e. they can hit cancel and the poll and any changes to choices are not saved.) How to accomplish this "transaction" back and forth between the two pages, where neither poll nor choices is saved until the Save button is hit on the Poll page? Specifically, how to pass the data between the two pages without explicitly saving each choice to the DB? Seems like there is probably a standard mechanism for doing this. Thanks, Ben -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
