Thank you for your reply David. On Wed, May 02, 2007 at 03:13:06PM -0700, DHH wrote : > I personally don't think this approach is worth the trouble unless you > have a scenario where you have many HTML UIs accessing the same base > model. Basically, this is the two-step view as defined by > http://www.martinfowler.com/eaaCatalog/twoStepView.html.
Actually it really cleans up your code, even in small 'standalone' (with few HTML UIs) applications. Considering REST just like the way to write your CRUD actions seems somewhat weak. You might end up using the scaffold_resource as a starting point for your controller and mess it up with actions that they don't really fit in this scheme (ignoring the concept of 'resource'). The presentation layer in web applications is as important as the interaction with your DB. Emphasis should be on both side and the code separated. Anyway, that's interesting how the 'view' part seems always to be painful. Compare the way you test your views compared to unit testing for example ;) > The common use case given is a airline ticketing system that's shared > by multiple airlines in an alliance. All use the same fundamental > system, but they each implement their own UI layer on top of it. For example. But (sorry if I repeat myself) I'm convinced it helps even in small applications to tidy up your code. > I don't see this as a generally applicable model for Rails. As in not > something "most people need most of the time". But do wrap this up as > a plugin that extends Rails in the points you feel are necessary to > support this better. Sure, I will since I have recieved emails from people interested by the idea. See you in Portland, -- ,========================. | Pierre-Alexandre Meyer | | email : [EMAIL PROTECTED] | `========================' --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
