I've got to add my two cents here since the "pretty" argument and "CSS designer" bit has irked me over the years.
There is a clear impedance mismatch between what a CSS/HTML designer can kick out from a graphical suite, and what is a truly robust, reusable component. 1. You must protect the CSS namespaces. Just because Mockup A looks good, does not mean it will work well together with Mockup B on Page C. 2. The CSS in mockups can be quite fragile and verbose, not being well suited to componentization (i.e. depending on x:nth-child(4), x:last-child) when you now have N entries and M instance of the widget on the page. 3. Various transitions and UI changes in the mockup should be triggered by changing a single class, not manually applying myriad style changes like "right:33px" and "opacity:0.34". Otherwise the devs need to rework the CSS themselves. Frankly "mockups" can be misleading and make a product look functionally complete, even though as coded they cannot be robustly implemented. Such things however are not a flaw in GWT, but a need to design for reuse and extensiblilty at the mockup stage. So be sure to set some requirements for your designers to be GWT friendly and the code should be easy to implement. Sincerely, Joseph -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/PYLag9cEMRQJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
