> Unfortunately such designs often do not follow a lot of Rails > conventions (REST is ignored, Flash messages are not used, Validation > errors presented in an absolutely different way etc).
No, what they're ignoring is the fact that one screen has many states. E.g.: when showing notices and when not, when a user is logged in and when not, etc, etc. You either have one mockup per screen state (not hard to do), or you have one PSD /AI file (if you or your designer uses Adobe tools, but could as well be Pixelmator) and layers that you can trigger their visibility to show/hide different states. So sure, if you can, get them to understand Rails or what have you. But the problem can also be solved by you telling the designers all the possible states of a screen. -- http://awesomebydesign.com -- 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.
