In my personal project, I'm going to have to have most things be commentable and ratable, lots of things being taggable.
For comments, I made a show comments tag that listed comments for an object, a entry field if logged in, along with ajax to avoid reloading page after submit. Then just stuck it in the show-page after content if the context responded to comments. Did something similar with tags and ratings. Given I'm probably going to have 20-30 models (and possible more in future) responding to this, really saves me time. acts_as_taggable_on_steroids worked well too. In that case, the polymorphism is hidden away and the added methods (tag cloud generation, etc.) outweigh any disadvantages even for only one thing being taggable IMHO. On Apr 2, 9:09 am, atmorell <[email protected]> wrote: > Thanks for clearing thinks up. > > Best regards. > Asbjørn Morell > > On Apr 2, 4:49 pm, Tom Locke <[email protected]> wrote: > > > > All right. I will only have comments for a few models, so dedicating a > > > table might even be an advantage. Comments on users might get a few > > > extra fields etc. How would you build a tagging system without using > > > polymorphic associations? It makes sense to use the same tables for > > > tagging multiple modules :/ > > > I would only go polymorphic if you need to be able to tag multiple kinds of > > things. Often you're only tagging one thing. > > > Tom > > -- You received this message because you are subscribed to the Google Groups "Hobo Users" 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/hobousers?hl=en.
