On 24/03/2012, at 4:05 AM, Roy McElmurry IV wrote: > I would like to participate in Google summer of code. I am proposing > the following contribution and would like to get some feedback about > ways to improve and refine the design and proposal. I have created a > UML diagram of an initial design viewable here > https://docs.google.com/open?id=0B9C40Ej8YB9Ja0IzMVo2Q3JUZkt0dk5vYVAzak43UQ. > A naive implementation can be demoed from the users perspective at > projectnomnom.herokuapp.com.
> Django Dynamic List Fields > Roy McElmurry > > Problem: Many web applications need to store or gather information in > a list format from users. Furthermore this list is deeply associated > with a model object. The context in which I encountered this problem > is a prime example. A recipe website would like to offer the ability > for users to enter new recipes. In order to do this a dynamic form is > needed that will allow users to give as many ingredients or > instructions as needed. This data is tightly associated with the model > and would therefore be best represented as a single field within the > form. Sorry to be the bearer of bad news, but I'm afraid I can't make head nor tail of this proposal. You use the phrase "Dynamic list form" and "dynamic form" as if it's some sort of commonly understood term for a specific feature or function. However, as a result of reading your proposal, I still don't have a clear idea of what specific feature it is you're proposing to add. You say "A good example exists on stack overflow", but you don't provide a link to that post. You say "Partial homebrew solutions exist", but you don't reference any of them. The UML diagram doesn't provide any useful illumination of what you're proposing. You've provided a naive implementation for demo, but you've put it behind a Facebook login. In short -- this proposal isn't very compelling to me at all. If you want to try again, you'll need to focus on giving an *extremely* clear explanation of what you mean by a "Dynamic form", providing links to any relevant examples. This is doubly important because you're proposing something that isn't on Django's suggested GSoC projects list. Not only do you need to propose a clearly defined project -- you need to convince us that the idea you're proposing is something that Django wants to pursue at a project level. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en.
