Oh. I had just thought it was a matter of a bare bones vs. many features I will not need for my current project.
It would be helpful if there were an indication that it was intended as a tech demo, perhaps as a notice in the README. On May 7, 12:52 am, "Michael Koziarski" <[EMAIL PROTECTED]> wrote: > Acts as taggable was only intended as a demonstration of how to use > the polymorphic associations. We're not really maintaining it as a > drop-in tagging solution. There are already more complete > implementations out there like: > > http://svn.viney.net.nz/things/rails/plugins/acts_as_taggable_on_ster... > > Thanks for the patch, but I'm not sure it necessarily needs to be applied. > > On 5/7/07, monki <[EMAIL PROTECTED]> wrote: > > > > > > > > > I was working with acts_as_taggable earlier and thought I could make > > it a bit friendlier. > > > I submitted a ticket and patch #8279. Basically, there are three > > differences. > > > 1. Fixed the deprecated :dependent => true > > 2. Added migration generator (it has really specific requirements on > > table layout, so might as well generate it). > > 3. Expanded the README to explain using the migration and to include a > > usage example. > > > Feedback much appreciated. > > -- > Cheers > > Koz- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
