Just like james has pointed out, the way urls are assembled when asked
directly to models can be made relatively independent from the models
themselves. I do so personally by using the "permalink" decorator and
returning just a name for the right view to be matched, using the
built-in named view mechanism. So you can have just a little
information about the view that should be requested, hardcoded in your
models, thus easily share models across projects, just as long as the
name used to identify the view is explicit enough about its use to not
throw ambiguities in.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
