I'm trying to envision how our project layout can best take advantage of the ClientBundle feature coming in GWT 2.0. As I understand it, you have to manually use StyleSheetInjector to ensure styles are available for particular code.
Let's say your you have functionality spread out over several libraries. Each of these provide either a collection of widgets or some complex views for parts of your app. Is it recommended to not have the module itself inject it's own styles? I know this is how widgets in gwt-incubator work. What's the reasoning? I was hoping stylesheets would function just like code and unused stylesheets would get optimized out, but this doesn't seem to be the case. Also, I thought there was a mode where the stylesheets would be combined and written out as an MD5.cache.css file to be included in the conventional way. I realize it's early but we're considering following Google Wave's lead and using the trunk to help improve our code and accelerate development. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
