Em 05-06-2012 15:05, Luiz Felipe Garcia Pereira escreveu:
One word: Modularity
If it's a simple plugin, it doesn't need to be a Railtie and inserted
in rails
Could you please explain the differences about this and a regular Ruby gem?
If it's something that extends rails/AR it can be a Railtie and take
advantage of that.
If it's an engine then it makes sense to add the Engine and have the
extra tools Rails::Engine provides.
What kind of improvements/benefits would you expect by using the former
instead of the latter?
If there is no real benefit, it would be better to always create an
engine and avoid user's confusion.
--
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 rubyonrails-core@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
