» MVC in Ruby on Rails : Pensieri di un lunatico minore
March 31st, 2006
Nice pictures (and thoughts) at » MVC in Ruby on Rails : Pensieri di un lunatico minore.
In my experience, it's even worse: you're bound to end up with several controllers that access the same view. Say, for example, a search: you have a "search" view (with the fields you want to search on), then you have "list" view (containing all found matches), and after selecting one, you have the "edit" view (showing the object you just selected). Each transition is handled by a controller.
Now comes (warning: flandrism) the cat on the cord: when you have exactly one search result, you want to go to the edit view for that object immediately. So the edit view is accessed by two different controllers: the one handling the "search" view, and the one handling the "list" view. The spaghetti in the pictures only becomes worse.
Or differenlty said: even minor lunatics can be optimist :-)
(This scenario, by the way, was one of our reasons to start with Spring Web Flow. Highly recommended.)
1 Response to “» MVC in Ruby on Rails : Pensieri di un lunatico minore”
Sorry, comments are closed for this article.
April 21st, 2008 at 10:18 PM I think this is also why continuation-based frameworks (like Seaside) hold such promise for complex applications where the flow isn't obvious. Regardless of your religious affiliation, it's worth taking a look at Seaside to see what can be done in one conceptual idea, and see whether some of that applies to what you're doing in Java. Spring Web Flow looks to be solving the same basic idea. PS: Your trackaback worked, but the URL gets munged... it looks like it's because of the fancy first character I use... blah stupid WWW. I'll see about changing that.