Open GoogleCodeExporter opened 9 years ago
See also Issue 41 [1]
I'm not sure how much of this really belongs in the tagging application itself,
as
it's more about working with generic relations than tags - I have similar code
in a
few other projects which use generic relations to render items with a template
based
on their content type.
I'm wary of pushing people down a particular path when it comes to something not
directly related to tagging - once you've retrieved your TaggedItems, it's
really all
about using generic relations.
Even something like jellyroll [2], which is all about working with lists of
generically related objects, doesn't force you down a particular path when you
want
to render them based on content type.
[1] http://code.google.com/p/django-tagging/issues/detail?id=41
[2] http://code.google.com/p/jellyroll/
Original comment by jonathan.buchanan
on 8 Jan 2008 at 3:11
I just see it as an opportunity to broaden the scope of this great app. This is
because you can apply this patch and use it exactly as you did before. The only
change is that it will be more flexible for those who want tagging to be
universal so
they can retrieve all items with a given tag regardless of model (this is the
real
reason that I wrote this extension).
I do see that the rendering could be changed so that it takes a template name
so you
do not have to have a template for every model/content type.
Original comment by mackenzi...@gtempaccount.com
on 10 Jan 2008 at 5:10
It seems that issues #41 and #58 are somewhat related to this. I also would
like at least some helper methods
for dealing with tags across multiple models.
Original comment by villesyn...@gmail.com
on 12 Jan 2008 at 8:23
Here is an updated patch for this if it is still of interest
Original comment by mackenzi...@gtempaccount.com
on 12 Jan 2008 at 7:22
Attachments:
Original issue reported on code.google.com by
mackenzi...@gtempaccount.com
on 3 Jan 2008 at 7:50Attachments: