So, wow, rails is really cool. Ruby itself seems pretty cool too.
So, since you were into trying out an ezabel rails incarnation, I thought I'd give it a try myself.
First question:
Should there be a separate controller for each model?
I have a User model and a News model right now. I made a controller called "EZabelController" for User and scaffold setup index, list, show, new, create, edit, update, and destroy, but it's all User specific. Should I really have a UserController, and a NewsController?
and, sheesh, the eZabel schema needs a lot of cleaning up to work well with rails. but in a good way
yeah? don't forget about single table inheritance!
not familiar with this, yet. does this have something to do with that reserved word "type" for database columns? i got some error about that because i had a CATEGORY.TYPE column. had to rename it.
yes. I remember you have like a generic table that contains data for either an Article, an Journal, a Thread.
if those are subclasses of a generic "Content" class, then the name of the table would be "contents" and an article would have "Article" in the 'type' column (rails places this value when you create and save a "Article" object)
this is single-table-inheritance.
if you get more interested in this, you should check out the book: "Agile Web Development with Rails"
cool. I never got around to making an ezabel rails app. too busy.
If you want to use scaffold to create your controllers then yes, you would create multiple controllers, one for each model.
but you *could* put all the functionality into one controller (manually) if you wanted to. you'd just have actions like "create_user", "create_news". just keep in mind the naming conventions though, because then you'd need .rhtml files that correspond to the action names.
its really up to you, off hand, I think you'd want to have seperate controllers, just to keep functionality seperate.