I'm still a newbie to django but I think I want to start working on my first real project and I'm kind of confused about extending another application's features without creating overhead.
I started to investigate flat pages because I planned to have a few flat pages however I wanted to add a few fields like meta keywords and a meta description. In this post: http://stackoverflow.com/questions/1021487/add-functionality-to-django-flatpages-without-changing-the-original-django-app One of the comment authors said that doing it this way will create some overhead and from a newbie's POV the original method listed seemed like the most intuitive solution. It pretty much follows the same path as most of the tutorials/books. Then I decided to poke around the contrib.FlatPages app and realized the meat of the functionality is just a basic model. That makes me believe that perhaps I should just roll my own FlatPages, maybe even with a parent->child structure for menu items (future projects). But then I thought I can see myself wanting to use meta keywords/ description in every single page, no question about it. Then I asked myself what the real difference is between adding those options directly in the django source and extending it and I couldn't answer it beyond the obvious problems like upgrading django may cause problems, so I'm posting it here. The comment author hinted that it creates a new table for all extended options but I'm curious why the new model fields can't just be added to the original table when you sync db? -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
