I started working on a patch 6 months ago to implement App objects,
but unfortunately never got to finish it because at the time I was
swamped at work.
Because of the all the work which has happened on trunk the code is
pretty much useless.
> The following can be addressed with app objects.
>
> 1. Allow multiple instances of an app object to exist
Can you explain how this can be achieved (in regards to API)?
I am currently can't figure out a clean solution or a use case which
would require two installations of the same application.
For example, someone for some reason wants to django.contrib.comments
more than once, so they add to entries to the settings.py
INSTALLED_APPS tuple.
INSTALLED_APPS = (App('django.contrib.comments', name='comments'),
App('django.contrib.comments', name='comments2',
db_prefix='comments2'))
syncdb works, and the two apps are installed. All is well. But for you
to make use of the two applications, all views must become application
aware.
Does the urlpatterns take into account an App instance?
urlpatterns = patterns('',
url(r'^comments/', include('django.contrib.comments.urls'),
app=get_app('comments2')),
)
Does it still require the view to somehow check the application
instance? For example a simple view;
def my_view(request):
comments = Comment.objects.all()
render_to_response("comments/template.html", {"comments":
comments})
How does the view know which app it is? Is it 'comments' or
'comments2'?
Or am I completely confused to what this requested feature is trying
to achieve?
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
