It is super easy to add a polymorphic form to a hobo model:
class CommentsController < ApplicationController
hobo_model_controller
auto_actions :all
end
Application.dryml:
<extend tag="show-page" for="Painting">
<old-show-page merge>
<append-collection-section:>
<form for="Comment" with="&this.comments.new">
<field-list: fields="body" />
<actions: />
</form>
</append-collection-section:>
</old-show-page>
</extend>
Best regards.
Asbjørn Morell
On Apr 2, 7:42 pm, Owen <[email protected]> wrote:
> Never mind...saw the example of generating a cloud:
>
> http://github.com/mattetti/acts_as_taggable_on_steroids
>
> Thanks for that, Kevin!
>
> On Apr 2, 1:39 pm, Owen Dall <[email protected]> wrote:
>
> > Yep, I would agree in that case. acts_as_taggable_on_steroids sounds very
> > useful. Does it have the JS to display the tag cloud as well, or are you
> > using something else? That would be a great recipe for us.
>
> > -Owenb
>
> > On Fri, Apr 2, 2010 at 1:24 PM, kevinpfromnm <[email protected]> wrote:
> > > 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]<hobousers%[email protected]>
> > > .
> > > For more options, visit this group at
> > >http://groups.google.com/group/hobousers?hl=en.
>
> > --
> > Thanks,
> > - Owen
--
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.
