Wednesday, February 3, 2010

[Rails] Re: Nested Rails Views

Raymond O'Connor wrote:
> Thanks for the help so far. Here's a more concrete example of what I'm
> talking about. I have an app used for warehousing and fulfillment.
> Some of the controller domains are:
>
> Receiving
> Locating Items
> Shipping Out Items
> Finance Related Stuff
> Shipment Tracking
>
>
> Within just the Receiving controller there are dozens of view files
> because it's become larger and larger over the years. You need to be
> able to receive a shipment, then receiving individual items in a
> shipment, track exception cases, edit previous check in data, etc. I'd
> really like a way to organize some of those files such that I have
> /receiving/shipment_check_in/..., /receiving/exceptions/....,
> /receiving/item_check_in/...
>
> All my controllers are getting to this size or are already there. I was
> just wondering if there was an easy way to refractor and organize
> projects of these size.

Your controllers are *far* too big and general. Receiving should not be
one controller. You'd probably want a ShipmentsController, an
ExceptionCasesController, and so on.

You could probably benefit from redesigning your controllers to follow a
RESTful pattern. You needn't adhere slavishly to it, but using REST as
a guideline will give you a better idea of what controllers are normally
expected to do.

Best,
-- 
Marnen Laibow-Koser
http://www.marnen.org
marnen@marnen.org
--
Posted via http://www.ruby-forum.com/.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home


Real Estate