Here is how I "debug" CSS: I start my application in Hosted Mode. Then I invoke "compile/ browse", which starts up IE in my case. Then I can patch CSS files right in my project (where they are version controlled; don't forget CM when doing important projects;-), refresh the browser, and get immediate gratification...well, immediate feedback anyway. There is never a cacheing delay in this setup.
Walden On Sep 22, 8:41 pm, p4r1tyb1t <[EMAIL PROTECTED]> wrote: > We are currently using GWT for a medium size project. Currently we are > facing couple of issues one issue has to deal with CSS cache, when our > Interface developer team try to debug a certain CSS issue and they > modify the CSS on deployed war, they don't see the result of changes > right away rather it takes few minutes to see the result. My question > is does GWT has some sort of cache mechanism? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
