Rails3 structure, engines, plugins, fragments, gems, modules ..?

Do you have a working example Rails3 mvc application?

How will this be organized?

Hope something like:

-app --controller --views -plugins --myapp1 ---app ---controller ---views ---... 

Can app1 use the model from app2? Will the "routes" file become obsolete?

link:

https://web.archive.org/web/20170704120345/http://yehudakatz.com/2009/07/19/rails-3-the-great-decoupling

https://www.slideshare.net/jacobian/django-in-the-real-world-1750000

+4
source share
3 answers

You should check out the Rails 3 screencasts at http://rubyonrails.org/screencasts/rails3 . This is a great introduction to the Rails 3 application framework and its change from Rails 2!

+1
source

Many of your questions will probably be answered in the Rails 3 Release Notes .

0
source

Try creating a weblog in 15 minutes with Rails 2. "Some of the code is outdated, but for the most part everything is still organized in the same way.

-1
source

All Articles