Tagging recommendation - acts_as_taggable_on_steroids best?

What's the most popular tagging plugin/gem these days? Is it
acts_as_taggable_on_steroids? Or is something else better?

Dunno. I recently (3 months ago) had to pick and went with acts-as-
taggable-on. Seems to work just fine. Lets you have different "sets"
of tags per model which I don't use, but could be useful.

Setting/Accessing tags is easy... just set "tag_list" in your form as
a text field (assuming 'tag' is the name of your set).

Don't remember why I didn't go with steroids...

Hi

I agree with phillip suggstion.

@max,
Don’t go with steroids as it has limitations for multiple taggings like ( tags, skills, interests ) that were extended in acts_as_taggable_on

Sandip

Sandip Ransing wrote:

Hi

I agree with phillip suggstion.

@max,
Don't go with steroids as it has limitations for multiple taggings like
(
tags, skills, interests ) that were extended in acts_as_taggable_on

Sandip

--
Ruby on Rails Developer
http://funonrails.wordpress.com
www.joshsoftware.com

Thanks for the suggestions guys. We already have some tagging in place,
using machine tags to delineate different kinds of tagging, eg
"note:name=Eb", so i think we would stick with that system. Maybe
that's how acts_as_taggable_on does it under the hood? Anyway i'll look
it that.

thanks!
max

Hi

I agree with phillip suggstion.

@max,
Don't go with steroids as it has limitations for multiple taggings like
(
tags, skills, interests ) that were extended in acts_as_taggable_on

Sandip

--
Ruby on Rails Developer
http://funonrails.wordpress.com
www.joshsoftware.com

Thanks for the suggestions guys. We already have some tagging in place,
using machine tags to delineate different kinds of tagging, eg
"note:name=Eb", so i think we would stick with that system. Maybe
that's how acts_as_taggable_on does it under the hood? Anyway i'll look
it that.

It doesn't. Here's the migrations... It uses the 'context' field.

     create_table :tags do |t|
       t.column :name, :string
     end

     create_table :taggings do |t|
       t.column :tag_id, :integer
       t.column :taggable_id, :integer
       t.column :tagger_id, :integer
       t.column :tagger_type, :string

       # You should make sure that the column created is
       # long enough to store the required class names.
       t.column :taggable_type, :string, :limit => 32
       t.column :context, :string, :limit => 32

       t.column :created_at, :datetime
     end