First: the web-browser plugin ting was just an idea, but like you mentioned wasn't crazy about it ;)
I recognize your setup but it's still "hard" to realize in practice with complex sites. For example: having different kind of forms depending on it's surroundings... It will result in a difficult to maintain one-size fits all css file (my experience at least)..
I also use a lib of app components that are available through factories.
I also didn't use GWT Resource at first, didn't see the need and find it pointless... Buttt it takes time to come around, and now it's the other way around ;)... Found them verrrrry useful, handy, fast, maintenable, sprting, code splitting, etc..... My experience: it takes some time to understand them well, especially the @Import construction...
Basically I split up the web designer's css file in to smaller ones for the concerning components... Yes, it's a bit more work, but I think it's worth it, you get a lot in return...
Thanks for sharing.
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 google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
No comments:
Post a Comment