You've done the Django Tutorial, what next?
?
0 likes?815 views
This document provides recommendations for next steps after completing the Django tutorial. It discusses setting up a Django project including base templates, context processors, render shortcuts, and middleware. It recommends writing models and using fixtures, migrations, and South for database management. The document also suggests using signals for decoupling code, named URLs, and class-based views. It advises avoiding generic views, complicated templates, and some contrib apps. Finally, it lists debugging tools like pdb, IPython, ipdb, the Django Debug Toolbar, and command extensions.
You've done the Django Tutorial, what next?
- 1. You¨ve done the Django tutorial. What next? Andy McKay Clearwind Consulting @clearwind
- 3. my opinions, likely wrong
- 4. 1. Setting up 2. Writing models 3. Middle years 4. Avoid 5. Tools
- 5. Part I: Setting up
- 6. app vs project vs...
- 7. past caring
- 10. (b). context processor http://docs.djangoproject.com/en/dev/ref/templates/api/#writing-your-own- context-processors
- 11. def context(request): data = {} return data
- 12. (c). render shortcuts eg: http://www.djangosnippets.org/snippets/1022/
- 14. (e) your middleware http://docs.djangoproject.com/en/1.1/topics/http/middleware/#writing-your- own-middleware
- 15. (f) your auth. backend http://docs.djangoproject.com/en/dev/topics/auth/#topics-auth
- 16. (g) base classes
- 17. model base class
- 18. class Base(models.Model): class Meta: abstract = True
- 19. form base class
- 20. class Form(forms.Form): ! pass class ModelForm(forms.ModelForm): ! pass
- 21. Part 2: Writing models
- 22. (a) ?xtures
- 23. not just for testing
- 24. create data in admin
- 26. (b) migration
- 29. drop db, create db, syncdb, load ?xtures, start up server etc...
- 30. my work?ow
- 31. 1. create app within project 2. de?ne models 3. access admin 4. smoke test models 5. alter, run ＾reset￣ 6. access admin (back to 4 until happy) 7. enter sample data 8. dump data to ?xtures 9. add ?xture loading to ＾reset￣ 10. continue... write tests and retail view
- 32. at some point... beta?
- 34. Part 3: The middle years
- 35. (a) signals
- 38. custom signals http://docs.djangoproject.com/en/dev/topics/signals/#de?ning-and-sending- signals
- 39. (b) URLs
- 40. always use named urls http://docs.djangoproject.com/en/dev/topics/http/urls/#url
- 41. urlpatterns = patterns('', url(/slideshow/youve-done-the-django-tutorial-what-next/3393961/r&), ... )
- 43. {% url main-view %}
- 44. (c) class based views http://www.slideshare.net/simon/ classbased-views-with-django
- 45. def boring(request): ... return some_html
- 46. class boring: def get(request): ... return some_html
- 47. Part 4: Avoid these
- 49. push logic into urls, always need rewriting
- 50. custom template tags (maybe)
- 52. {% div %} {% dl %} {% dt %}Name{% enddt %} {% dd %}Definition{% enddd %} {% enddl %} {% enddiv %}
- 54. comments
- 55. Part 5: Debug Tools
- 57. pdb http://docs.python.org/library/pdb.html (not optional)
- 66. arecibo http://areciboapp.com (disclaimer)
- 67. Fin. Questions? Andy McKay Clearwind Consulting @clearwind