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

Question

Do you have a working example of a Rails3 mvc application?

How will it be organized?

I hope something like:

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

Can app1 use a model from app2? Will "routes" file be deprecated?

reference:

[h ttp://yehudakatz.com/2009/07/19/rails-3-the-great-decoupling][1]

[h ttp://files.me.com/wycats/o2snu8][2]

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

Answer 1

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 the same way.

Answer 2

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

Answer 3

You should check out the Rails 3 screencasts at http://rubyonrails.org/screencasts/rails3. They're a great introduction to the structure of a Rails 3 app and how it's changed from Rails 2!