On 5/11/2014 3:04 AM, Dave wrote:
I'm trying to understand how using django for development works. Can a
backend developer begin with just a wireframe?
Yes. Start with your models and give them methods and fields you know
will be needed. Importantly you should write unit tests to prove your
methods do what is intended. Then write a clean() method for each model
to carry as much business validation logic as you can. Raise your own
business rule violation exceptions as required.
You don't even need a live database. By that I mean it isn't necessary
to "manage.py syncdb" to create your database (don't know about Django
1.7 here - I'm using 1.6) because when you run your unit tests
("manage.py test") the test database is created from your models not
copied from the real database.
You can't get any more "wireframe" than that.
At some stage you will have to introduce html if you want a website but
even then, your templates can be very simple until your design team says
precisely what they want.
Isn't it possible to
develop scripts while someone else is writing the html/css code? (like
working on the front end and back end at the same time)
Yes. I think it is a very good idea to do that. If you know what the
system will look like before you build the back end it will give proper
focus to your work.
For example: Creating a forum. Can't the backend develop the features
like creating a community, managing the community and storing the
information in the DB and then once the integration begins, take the
html/css and combine it?
Yes. Django comes with a front end called the Admin. It lets you expose
your database to the outside world via your models complete with your
business logic built into your clean() methods. It isn't supposed to
replace the user interface you design for your users but it lets you
quickly and easily put essential data into your wireframe.
So yes, there is enough to begin.
Good luck
Mike
--
You received this message because you are subscribed to the Google
Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to django-users+unsubscr...@googlegroups.com
<mailto:django-users+unsubscr...@googlegroups.com>.
To post to this group, send email to django-users@googlegroups.com
<mailto:django-users@googlegroups.com>.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/2d084bf3-0c89-4922-a45d-394e19bcbe6f%40googlegroups.com
<https://groups.google.com/d/msgid/django-users/2d084bf3-0c89-4922-a45d-394e19bcbe6f%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/545945A1.7020705%40dewhirst.com.au.
For more options, visit https://groups.google.com/d/optout.
