Any suggestions on how to do theming, ie. to allow a new theme to be created in the future as a separate css file that can be switched on/off at runtime. I also don't want just global CSS though, I want CSS scope as local as possible but I want to be able to expose some CSS to be themable. Here's my idea about how to organize our CSS to do this:
1) Shared CSS file - contain some styles that are shared across all widgets like fonts 2) Local CSS stuff - stuff that applies only to 1 widget or so, this will be inside the widget's ui.xml file, or in a separate css file and referened from the ui.xml file 3) Theme CSS file - there will be several, all of which extend from some interface that defines classes that can be then modified by a theme's css file So within any one ui.xml file I might be referring to some local css, the shared css, or the theme's css. Any comments? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@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.
