As you may know, Django boasts reusability of apps. This means you can just copy one app from one project, plug it into another and it would still work the same way. Neat, huh? Well, admittedly, till now we've only focused on getting out projects to run. But now that we know the basics of creating a working Django project, it's time to delve deeper and take advantage of Django's rich features.
Let's start with URLs. Till now, we just went on adding URLs to the main urls.py as we developed the project. But when the number of URLs starts going into the triple digits, the urls.py file can become massive and difficult to keep track of. So let's see how to create a urls.py file in each app and direct the main file to this new one.
In the main urls.py file, add a pattern that will point to the app:
url (r'^myapp/', include('myproject.myapp.urls')),
This tells Django that whenever someone access the /myapp/ URL they should be directed to the urls.py file in that app. From here on in, all the views rendered in this app will have URLs like /myapp/foo/bar. This makes them easier to manage. There's also another advantage: you no longer need unique URLs; you can have /home/ in multiple apps. That is, /myapp1/home and /myapp2/home have the same sub URL, but are still unique as a whole.
Now, create a urls.py in the concerned app. In it:
from django.conf.urls.defaults import *
(This imports all patterns from the original urls.py file)
urlpatterns = patterns ('myproject.myapp.views',
url(r'^foo/', 'bar'),
)
Another advantage: you don't have to type the entire path to the view; just the name suffices. Hence, from the above example, when someone accesses the /myapp/foo/ URL, the bar view from myproject.myapp.views will be rendered.
To summarize, this makes handling URLs very easy. We'll see more examples of reusability in the following tutorials.
Let's start with URLs. Till now, we just went on adding URLs to the main urls.py as we developed the project. But when the number of URLs starts going into the triple digits, the urls.py file can become massive and difficult to keep track of. So let's see how to create a urls.py file in each app and direct the main file to this new one.
In the main urls.py file, add a pattern that will point to the app:
url (r'^myapp/', include('myproject.myapp.urls')),
This tells Django that whenever someone access the /myapp/ URL they should be directed to the urls.py file in that app. From here on in, all the views rendered in this app will have URLs like /myapp/foo/bar. This makes them easier to manage. There's also another advantage: you no longer need unique URLs; you can have /home/ in multiple apps. That is, /myapp1/home and /myapp2/home have the same sub URL, but are still unique as a whole.
Now, create a urls.py in the concerned app. In it:
from django.conf.urls.defaults import *
(This imports all patterns from the original urls.py file)
urlpatterns = patterns ('myproject.myapp.views',
url(r'^foo/', 'bar'),
)
Another advantage: you don't have to type the entire path to the view; just the name suffices. Hence, from the above example, when someone accesses the /myapp/foo/ URL, the bar view from myproject.myapp.views will be rendered.
To summarize, this makes handling URLs very easy. We'll see more examples of reusability in the following tutorials.
No comments:
Post a Comment