This is a call for opinion based on experience :) I'm in the process of creating the models for my very first Django application in my very first project. I have read the book up to and including chapter 7 (everything i need to know to get started).
Naturally I have the design of the system I want fairly well figured out, and have moved on to do most of the work for the models (primarily as far as the database is concerned). Currently I am wondering what the next stages are going to be, and I'm not too sure what I would like to do as a matter of process. I remember reading a section in the book highlighting that you could do it either way, depending perhaps on your own programming preference or the situation. I've given it some thought, but I'll keep my current inclination for what I would prefer to myself for now; I'm still undecided anyway. If the decision is 50/50 and absolutely depends on what you are developing, then let me know what cases illustrate the deciding factors. I would imagine that experienced developers would have a predominant preference by now and THAT is what I would really like to hear about :) --- tldr; What I would like to ask is, from more experienced Django developers, what way do you prefer to create your applications? Models then views then templates? Models then templates then views? Or models then views AND templates concurrently. If there has been a discussion that addresses this subject already then I would appreciate a link to that just as much. Thank you, -Alex --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
