On 24/11/2010, at 12:13 PM, Nicholas Faiz wrote: > Using mockup tools like Balsamiq help a great deal, especially if your > customer is happy to use it to help visualize the application you're > building. The designer can also work from that too, but the customer > understands that the rougher looking app is modelled off a prototype. > It can increase confidence while waiting for the final design to be > implemented. > > There isn't a lot of work when refactoring a HTML design into Rails > helpers, etc.. I just make sure I *don't* use HAML for such projects > (I generally don't use HAML anyway), because it's foolish to rewrite > all of your HTML files into another format.
Great design is a process that goes all the way from idea to execution and back again, whether it's code or UI. Having HTML thrown over the fence isn't a process I'd recommend for Rails dev, I've been on a project or two like that and the end result was always terrible. To the original question… On 24/11/2010, at 11:07 AM, dnagir wrote: > I am just wondering how you guys deal with working from having UI > design to the actual Rails implementation? > (e.g.: 37signals - Interface First) 37signals have a designer working and collaborating on each team during build, not just at the start handing over photoshops or HTML. Don't think interface *first* development, think interface *driven* development. – tim -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" 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/rails-oceania?hl=en.
