IMHO, semantically you're right, index is a list of objects. But beyond AS creation, "index" page was meant also as the first (or default) page people would like to see. And that way, is why rails routes the "index" action when you ask for some controller but no action. So, as i see (again, IMHO), redirecting to a "list" action, is an excellent way of AS to override the "index" action with a real "default" page in cases where you don't want (or "can't" by authorization filters) to list as default.
On Apr 17, 7:17 pm, Kenny Ortmann <[email protected]> wrote: > I did not write active scaffold but I believe the reasoning behind it is > that the index action normally shows a list of items, the terminology behind > index opposed to list, list just sounds more clear. > > On Fri, Apr 17, 2009 at 11:20 AM, Wes Gamble <[email protected]> wrote: > > > I have always wondered this. > > > Why doesn't AS just generate an "index" view for responses to > > "/resources/index" type requests instead of having this "list" > > action/view construct that is totally separate and simply delegated to > > by index? > > > It's just confusing enough to mess me up when I'm tracking all the way > > through from request beginning to response end. > > > I get how it works, and I'm clear. I just don't understand why not > > dynamically generate "index" stuff they way everything else is done? > > > What is the true purpose of the "list" construct? > > > Thanks, > > Wes > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ActiveScaffold : Ruby on Rails plugin" 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/activescaffold?hl=en -~----------~----~----~----~------~----~------~--~---
