<div>I would infact group those controllers in modules</div>
<div> </div>
<div>For example </div>
<div>app/controller/blog</div>
<div>app/controller/forum<br><br> </div>
<div><span class="gmail_quote">On 1/31/06, <b class="gmail_sendername">Ian Harding</b> <<a href="mailto:harding.ian@gmail.com">harding.ian@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">This is a good question. You probably don't want one controller for<br>each table. I thought of my app in terms of the major objects that
<br>get operated on, and created a controller for each. That ended up<br>being 3, for about the same number of tables you have.<br><br>For a manufacturing app, for example, you might have controllers for<br>Jobs, Components, Bills of Material, Equipment, etc.
<br><br>The way the scaffold is set up is pretty quickly left behind.<br><br>On 1/31/06, Peter Jagielski <<a href="mailto:pjagielski@gmail.com">pjagielski@gmail.com</a>> wrote:<br>> Fellow Railers,<br>><br>> Is there anything, anywhere, that I can read that discusses overall RoR
<br>> app design? I have the Agile RoR book, which is great for learning the<br>> details of RoR, but unfortunately doesn't cover the overall issue of<br>> creating a large, complex RoR app.<br>><br>> My staff and I are still in the process of getting up to speed on Ruby
<br>> and RoR, but we also need to begin thinking about the best approach to<br>> converting our very large and complex Win32 (Delphi) DB app over to RoR.<br>> For (simple) example, our app currently has 42 DB tables. Would it be
<br>> considered bad design in RoR to have 42 separate controllers, or should<br>> we create one generic controller that handles all the basic CRUD for all<br>> the tables?<br>><br>> I believe there are some new RoR books coming out later this year, which
<br>> may help, but we could really use some help *right now*.<br>><br>> Thanks to all who respond!<br>><br>> P.S. I see that the 37Signals guys are putting on a workshop where they<br>> discuss things such as big-picture design. Sounds like maybe something
<br>> I should attend...<br>><br>> --<br>> Posted via <a href="http://www.ruby-forum.com/">http://www.ruby-forum.com/</a>.<br>> _______________________________________________<br>> Rails mailing list<br>
> <a href="mailto:Rails@lists.rubyonrails.org">Rails@lists.rubyonrails.org</a><br>> <a href="http://lists.rubyonrails.org/mailman/listinfo/rails">http://lists.rubyonrails.org/mailman/listinfo/rails</a><br>><br><br>
<br>--<br>"Her faults were those of her race and sex; her virtues were her own.<br>Farewell, and if for ever - "<br><br>-- "Travels with a Donkey in the Cevennes" by Robert Louis Stevenson<br>_______________________________________________
<br>Rails mailing list<br><a href="mailto:Rails@lists.rubyonrails.org">Rails@lists.rubyonrails.org</a><br><a href="http://lists.rubyonrails.org/mailman/listinfo/rails">http://lists.rubyonrails.org/mailman/listinfo/rails</a>
<br></blockquote></div><br><br clear="all"><br>-- <br><br>Rgds,<br>--Siva Jagadeesan<br><a href="http://www.varcasa.com/">http://www.varcasa.com/</a><br>My First Rails Project. Powered by Typo and soon by RForum too