I was wondering how what you do when you have some serious client-side work to do on a Rails app.
Good practice tells us to start from testing, so let's say we either: 1) Have Implement a bare-bones html (non-ajax) version of the feature using an outside-in testing process already. 2) We don't (argh) have or follow a test-driven process. Anyway, the point is, once you have the basic done, you then want to focus on the GUI. The client wants it to look and behave in a specific way, and you go and start putting your awesome client-side skills into action. Form my experience, if the application is still small, it's a no brainer to just go and modify the ERB/HAML/CSS/SASS as needed. However, when the app gets stuffed with more objects, doing client-side work is just too painful (requests can take several seconds). What I like to do when a lot of client-side work is expected is to create a separate folder with styles and the view(s) needed copied (erb removed, of course), use placeholder data where needed (I might also test-drive the javascript), and focus on the client-side only. You then remove Rails out of the equation, which makes the process smoother. How do you do it? Cheers, - Marcelo. -- 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 rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
