On Sunday, September 9, 2012 9thanks a :28:17 PM UTC+3, Jens wrote:
> In your module you could set the property "storageSupport" to "no" to disable
> storage (see Storage.gwt.xml).
>
>
> -- J.
Thanks Jen, it works perfectly!
--
You received this message because you are subscribed to the Goo
In your module you could set the property "storageSupport" to "no" to
disable storage (see Storage.gwt.xml).
-- J.
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/
Hi
We use gwt's Storage class to persist data.
our code calls Storage.getLocalStorageIfSupported(); before each try.
Is there an easy way to create a mock of Storage so
that Storage.getLocalStorageIfSupported() returns false all the time?
We thought about extending it and using on our module, b
Make sure that you do a full release compile (using GWT compile from the
Google menu) once before running the code server the first time. Of
course, the source code server MUST be running for the bookmarklets to work
at all.
On Saturday, September 8, 2012 9:02:48 PM UTC-7, Paul Stockley wrote:
I've played around with web workers on GWT, but it's not a lot of fun. You
can't use normal GWT devmode on them (though maybe superdevmode would
work?). So you essentially have to write the worker, compile it, and then
call it from your non-worker code and hope it does what you want.
On Saturda
On Sunday, September 9, 2012 6:02:48 AM UTC+2, Paul Stockley wrote:
>
> Every time I click the compile button from the 'Dev Mode On' bookmarklet,
> I get the 'GWT module '..' may need to be (re)compiled' alert. It works
> fine after that but it's kind of annoying. Anyone have an idea why this
>
