As a start, I do like the idea of rewriting the Plugins guide to emphasize the creation of a gem for an extension but still give the option (way down at the bottom) of writing a plugin. It might also be nice to give some instructions on how to convert a plugin to a gem.
This will get people thinking in the right direction. Then when the plugin code becomes a thorn in Rails' side it will be easier to remove. I will volunteer to help rewrite the Guide to emphasize the gem creation and put something in about upgrading plugins to gems. On Dec 8, 7:17 am, Daniel Morrison <[email protected]> wrote: > Personally, I have no reason to use plugins anymore. Bundler has made > this a moot point. > > However, I spend a lot of time teaching Rails, and (unfortunately) > many people don't have git installed, and it frankly doesn't make > sense for them to just for the :git option in a Gemfile. I think we > need a quick way to install gems/plugins without requiring git before > we can fully rely on bundler. Maybe a new form of script/plugin > install that just adds an appropriate line to the Gemfile with :path > would suffice. It would make it easier for the newcomers. > > The last couple times I've taught, showing off plugins has seemed a > bit archaic. In the absence of git, however, they are still easier > than any alternatives. -- 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.
