Differences

This shows you the differences between two versions of the page.

--- devel:django_introduction [2008/09/25 11:42] – Fix typo. jodal
+++ devel:django_introduction [2010/01/13 11:30] (current) – Add link to django_template blueprint eide
@@ Line 8: / Line 8: @@
 ===== nav.django package =====
-As NAV has not used Django from the very beginning, NAV does not strictly follow the Django convention of multiple apps with their own models, views, etc. To plug NAV into the Django framework some glue is needed. This glue and other common Django-related code is located in the ''nav.django'' Python package, which is located in ''subsystem/lib-python/src/nav/django''.
+As NAV has not used Django from the very beginning, NAV does not strictly follow the Django convention of multiple apps with their own models, views, etc. To plug NAV into the Django framework some glue is needed. This glue and other common Django-related code is located in the ''nav.django'' Python package, which is located in ''subsystem/lib-python/nav/django''.
 ==== Settings ====
@@ Line 18: / Line 18: @@
 ==== URL configuration ====
-In ''nav.django.urls'' the root URL configuration for all things Django in NAV is located. ''nav.django.urls'' is not only a module, but also a package. The ''%%__init__.py%%'' file in the package imports all submodules it can find in the file system, calls ''get_urlpatterns()'' on all the submodules, and combines the results into one ''urlpatterns'' list, as all Django URL configurations does.
+The root URL configuration for all Django-related applications in NAV is located in ''nav.django.urls''. It is not only a module, but also a package. The ''%%__init__.py%%'' file in the package imports all submodules it can find in the directory, calls ''get_urlpatterns()'' on all the submodules, and combines the results into one ''urlpatterns'' list, as all Django URL configurations does.
 When creating a new Django app, create a new submodule for your app in the ''subsystem/your_app/nav/django/urls/'' folder, run ''make install'' in your app to install the module into the ''nav.django.urls'' package, and the NAV installation will find your app. If somebody else installs URLconf glue into ''nav.django.urls'' they will not affect the URL configuration for your app, unless they use exactly the same name for the submodule as you did. For details, check out the ''ipdevinfo'' subsystem and its ''Makefile.in''.
@@ Line 126: / Line 126: @@
 As more parts of NAV are (re)implemented in Django, one should look into replacing the wrapping of Django templates in Cheetah templates with pure Django templates throughout the stack. Even if this may require maintenance of base templates in both Cheetah and Django for quite some time, it would result in much more flexibility with regard to page titles, bread crumb paths, etc. when using Django templates.
+Proposal in [[devel:blueprints:django_template]]
 ==== Unit testing ====