On Sun, 2006-08-13 at 09:13 -0700, Karen Tracey wrote:
> I'm working through the tutorial, applying its lessons to my own
> database. So for example where it covers writing a detail view for the
> Poll model, I think really I'm going to want a detail view for each of
> the models in my database, and they're all going to be the same except
> for the name of the model and the actual stuff that gets output, which
> will be controlled by the model-specific template.
>
> So I come up with a url mapping that looks like this:
>
> urlpatterns = patterns('kmt.crossword.views',
> (r'^(?P<model_name>\w+)/(?P<id>\d+)/$', 'detail'),
> )
>
> and my views.py is very simple:
>
> from django.db.models import get_model
> from django.shortcuts import render_to_response, get_object_or_404
>
> def detail(request, model_name, id):
> model = get_model('crossword', model_name)
> instance = get_object_or_404(model, pk=id)
> return render_to_response(model_name + '_detail.html', {'instance':
> instance})
>
> This works nicely, but I have a few niggling questions. First I found
> that useful get_model function not in the documentation, but by looking
> around in the Django code. Is this something I should be using, or is
> it really only intended for Django internal use? If it's not something
> I should be using, where should I be looking to figure out how to
> accomplish the kind of thing it does for me?
I don't see a lot of problem with using that function if you really need
to. It exists to provide the functionality you are using it for to the
Django core.
> Second, it seems a bit inelegant to hardcode my own app name
> ('crossword') here. Seems like there should be some way for my
> kmt.crossword.views code to figure out that its own app name is
> 'crossword', but how to do that is eluding me.
With that particular view setup, you could look at the __file__
attribute (every module has one -- try printing it out to see that it's
just a standard file path, so os.path.* can be used to work on it) and
work it out from there (go to the name aboves the 'views/' component).
In general, though, this is an impossible problem based on the
information the view has available to it. Since the view is just a
Python function, it could be located anywhere at all. Multiple
directories down, or in an entirely different part of your filesystem.
So either the view module has to know its position relative to your
application directory (the case at the start of this paragraph), or you
have to pass in the application name to the view somehow. Otherwise it
simply does not have enough information.
You might think "well, my views will always be under the app directory"
and they may well be in this case. However, that's not a universal
truth. For example, as Don pointed out, generic views are useful in some
cases and they live somewhere entirely different. Sometimes you will
write an app that only consists of views and uses models from other
applications (so they present a different outlook on the data). And so
on and so forth.
Regards,
Malcolm
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
