Malcom, > This is still work in progress. Unfinished as yet. I don't think the tag > exists yet, but the django.core.urlresolvers.reverse() and > django.db.models.permalink() methods are part of this. Thanks, I check this out....
> TEMPLATE_DIRS is for project-wide templates, so I'm not sure why an > application would want/need to change that. If you depend on some other > template being available, there should be a way to say that (although a > re-usable app is normally not going to do much beyond extending > base.html or something). Uf you supply templates, then they are in your > own template directory and will thus be available as soon as the app is > installed. Installing templates outside your own application is probably > not particularly maintainable. It is necessary in those cases to follow > something like the directory hierarchy from [1], since otherwise > template name clashes result. > > [1] http://code.djangoproject.com/wiki/DosAndDontsForApplicationWriters OK, I guess should have read ths documentaion more carfully.... > You can do this already, I suspect: Template tags are imported through a > "load" tag in the template. The file that is loaded must be an > importable Python file. So I think it would work to specify this as for > other applications -- "from other_app.templatetags import special_tags" > -- already. Have I overlooked a problem you have in mind here? Looks a bit akware to import something you don't need in your view.model. And the error-message would be a bit messy. But at least a `manage.py validate` would detect the problem. Martin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
