You'll find the perfect way for you to approach each stage of it I'm
sure.
I'm always into figuring out Use Cases the very first thing. I like
to establish at least 4 or 5 different major tasks that a user would
need/want to do, and then get these out of my head into a concrete
form (currently this means the Treepad outliner in a "use case"
branch).
This first step naturally, without too much mental effort, steers me
next into making decisions about what screens I will need, and what
models I will need to read/write in each of those screens.
----------------------------------------------------------------------
So my first step is 1.) sketching what I need highlevel-wise,
2. ) Then deciding what those urls will be, going into urls.py to
write three or four mappings (for only read operation functions such
as getScores or whatever, i'll worry later about writing the write
operations when I start writing the html forms in the views )
3. ) And then start writing the models I know I will need. When I'm
finished with about 80% of the models I know I will need, I use the
Python shell to check things. When I'm satisfied that all of the
related tables give me the right result on the shell console by
manually running model.objects.all(), etc.., the next step
4. ) I go into views.py and write three or four functions that do some
reading
5.) Then the views - write the tags for retrieving database results.
.. and then I view a Djangocon speaker on youtube and realize how much
I have to learn when it comes to performance, and all of the different
areas to look at:
check out: http://www.youtube.com/watch?v=D-4UN4MkSyI
Seriously, not that we will all have sites that demand that type of
bandwidth, but it is definitely educational.
On Jan 11, 7:03 pm, AlexiPoliski <szczecinmeis...@gmail.com> wrote:
> 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
-~----------~----~----~----~------~----~------~--~---
