I guess it's all in the design... and the intent of the application... my users tend to stay in the show or edit views for the majority of their time...
My show view has all the detailed information for the individual models that just get a name, a description and a few choice tidbits in the index view. >From 'show', the right nav "context" menu lets the users traverse the model relationships with a simple hyperlink click (Functional Requirement X is related to an Marketing Requirements Document, a Marketing Requirement, one or more Projects, one or more Applications, one or more Test Cases, one or more Scenarios, etc, etc, etc. Following relationships goes from show to show, and from a show, you can create or remove relationships to existing models, or create new models to be related from the context of the current model, generate PDFs, perform a traceability analysis, etc. There is a top nav which lets you get to any index view if you want to navigate to a model "outside" the current context (i.e., not related to the model you're currently looking at). -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
