After I started this thread, a new article has come up on the GWT blog which talks about how the folks at studyblue.com approached the styling issue. Here is the link to the post: http://googlewebtoolkit.blogspot.com/2008/12/gwt-no-need-to-shortchange-your-style.html
On Dec 6, 10:02 am, Chii <[EMAIL PROTECTED]> wrote: > I think the underlying issue here is that the paradym of gwt > programming is not the same as the traditional web-app development, > where the coder hands to the designer a bunch of "variables" to which > the designer inserts into a template (velocity, freemarker, jsp, you > name it). > > GWT brings to the table the developer as a UI creator. The designer no > longer makes the product, but actually designs the blue-print, and > that blue print is followed by the developer. I.e., the developer now > needs to know about DOM, CSS and HTML (though not to the extend that a > designer might). GWT tries to abstract html from making a web UI. > Thats my 2 cents anyway. > > On Dec 3, 4:36 pm,Nizam<[EMAIL PROTECTED]> wrote: > > > Are there any best practices in bringing together a multi-disciplinary > > team of Java developers and HTML/CSS designers in developing a > > commercial GWT application? Our Java guys cannot do CSS and our HTML/ > > CSS guys prefer working in DreamWeaver. I haven't seen any material > > that talks about the team collaboration aspect. Any thoughts? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
