I really don't understand the practical need for .ensureInjected(). Why would I not want all my CSS to exist always? After all, it is (and only is) a static resource. It should just be there, waiting for me to use it. (And I would assume it's not a data issue; the "raw" CSS has to transfer to the client anyways, in order to be injected.)
Remembering to add the boilerplate of .ensureInjected() to the top of any styled class is wacky. It becomes increasingly wacky if you are taking styles from several resources. Why are these static resources not just injected on app load, ready to be used? Is it a performance issue? Some craziness with deferred binding? Please set me straight! -- 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.
