Hi,
I have just completed a first draft of the NAV+Django introduction, available at [1]. I know some of you would for sure had benefit of having this documentation available in June. I'm sorry about that, but now it's finally here.
I would very much appreciate if those of you which have been using Django in NAV or elsewhere could take the time to read through the introduction and give some feedback. Both general feedback here at the mailing list and changes directly in the wiki are welcome, especially with regards to the future enhancements section.
Hope the docs will be useful to some :-)
[1] http://metanav.uninett.no/devel:django_introduction
Hi,
Hi!
I have just completed a first draft of the NAV+Django introduction, available at [1]. I know some of you would for sure had benefit of having this documentation available in June. I'm sorry about that, but now it's finally here.
Good stuff :-)
I would very much appreciate if those of you which have been using Django in NAV or elsewhere could take the time to read through the introduction and give some feedback. Both general feedback here at the mailing list and changes directly in the wiki are welcome, especially with regards to the future enhancements section.
I only have one issue about how things are done; During development is a real hassle having a global urls.py, especially if there are more than one developer working on the same instance. I dont really know of any good ways to work around this without doing something really nasty like searching for other urls.py in the pythonpath (yuk!)
Any ideas?
- K
On Tue, Aug 19, 2008 at 11:24:54AM +0200, Kristian Klette wrote:
I only have one issue about how things are done; During development is a real hassle having a global urls.py, especially if there are more than one developer working on the same instance. I dont really know of any good ways to work around this without doing something really nasty like searching for other urls.py in the pythonpath (yuk!)
Any ideas?
http://metanav.uninett.no/hg/default/rev/568c58e718f8 fixes this :)
Hi,
Hi!
I have just completed a first draft of the NAV+Django introduction, available at [1]. I know some of you would for sure had benefit of having this documentation available in June. I'm sorry about that, but now it's finally here.
Good stuff :-)
I would very much appreciate if those of you which have been using Django in NAV or elsewhere could take the time to read through the introduction and give some feedback. Both general feedback here at the mailing list and changes directly in the wiki are welcome, especially with regards to the future enhancements section.
I only have one issue about how things are done; During development is a real hassle having a global urls.py, especially if there are more than one developer working on the same instance. I dont really know of any good ways to work around this without doing something really nasty like searching for other urls.py in the pythonpath (yuk!)
Any ideas?
- K
stein.magnus.jodal@uninett.no wrote:
Hi,
I have just completed a first draft of the NAV+Django introduction, available at [1].
Much appreciated, Stein Magnus. I have read the whole thing and only had to correct to typos - and btw don't ask me how much I understood ;)
Looks rock solid to me. The 1.0 release was also discussed on the last meeting btw.
I have also registered bug fixes and more - keep it coming :)
- Vidar
-
Kristian Klette -
Kristian Klette -
stein.magnus.jodal＠uninett.no -
Thomas K. Adamcik -
Vidar Faltinsen