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 Tra
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 controll
Since you don't have many details posted, I'll suggest a generic
solution that worked for me:
Use partials. You can populate them based on sub-categories within
your actions or groups or whatever your 'parent' classification is.
You can implement whatever heirarchy you like - each level would have
Raymond O'Connor wrote:
> Marnen Laibow-Koser wrote:
>> Raymond O'Connor wrote:
>>> I'm at the point where I have a lot of view files for each controller in
>>> my app.
>>
>> Why do you have so many? It's rare to have more than about 5 views per
>> controller.
>>
>>> I'd like to be able to add
Marnen Laibow-Koser wrote:
> Raymond O'Connor wrote:
>> I'm at the point where I have a lot of view files for each controller in
>> my app.
>
> Why do you have so many? It's rare to have more than about 5 views per
> controller.
>
>> I'd like to be able to add another level or two of directori
Raymond O'Connor wrote:
> I'm at the point where I have a lot of view files for each controller in
> my app.
Why do you have so many? It's rare to have more than about 5 views per
controller.
> I'd like to be able to add another level or two of directories
> in my view folders just for organiz
6 matches
Mail list logo
