Colin Law wrote: > On 7 October 2010 18:40, gezope <[email protected]> wrote: >> Hi, >> >> Your task is cannot be that complicated, but for first reading it >> seemed, and a bit long. >> >> Try to draw it first! >> First you have to find out: the user experience! It will make clear >> what datas you need, so what models, > > I disagree here, the models required should not be based upon the user > experience required but on the underlying objects in the real world - > users, companies and so on in this particular case. Unless I > misunderstand what is meant by 'user experience'.
I agree with Zoltan -- and I suspect you do too -- in this sense: when I put together an application, I usually think first about how I want it to present itself to the user and what the user should be able to accomplish (and write Cucumber scenarios accordingly). Only as a result of making those scenarios reality do I write model classes or anything else. In other words: first define what you want the user to do, and only then figure out the code to make it happen. > > Colin Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- 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.
