I am curious to the reaction of the gwt dev team member. Maybe you should drop this in the contributor gwt forum.
I like your approach, especially in my experience of the last 7 years with gwt, css/html should be put as much as possible outside of gwt, a bit like RedHat errai is using. Some advantages: 1) Flexibility: changing html/css with changing code. 2) Css/Html experts are much easier to find. 3) Faster changing of css. Css changes in gwt are not always fast because java isn't well suited for it, java is verbose, especially when working with themes (references from css to static methods for example). 4) Better integration/binding of the html/css with existing published cms files (json/xml) ... This results in a much higher productivity, especially when you have all clients wanting their own themes/styling, and gwt developers are very hard to find. I would love to see that GWT core incorporate some of the Errai templating/binding mechanisms in the future. (I am planning to play with some of the errai mechanism and make it work with my current cms xml files I use... I just have to find some time :( just my 50 cents. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
