On Wednesday, June 22, 2016 at 8:57:30 AM UTC+2, Hristo Stoyanov wrote:
>
> Another idea:
> Can we create a *gwtcompile.jar* for GWT 2.8, which is basically going to
> be the same as *gwt-dev.jar* , minus all jetty jars? With GWT compilation
> being so slow, eliminating tons of unrelated jars w
Ye I think it is very weird that GWT complains. But the workaround of just
placing the com.google.errorprone.annotations GWT module file in our own
jar seems to work fine, thanks for the quick reply!
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group
Thanks for the reply, ye I think it is very weird that GWT complains. But
the workaround of just placing the com.google.errorprone.annotations GWT
module file in our own jar seems to work find, thanks for the fast reply!
On Tuesday, June 21, 2016 at 4:06:49 PM UTC+2, Thomas Broyer wrote:
>
>
>
Thats how Modernizr does it:
https://github.com/Modernizr/Modernizr/blob/master/feature-detects/touchevents.js
However read the comments in that file and especially the linked articles.
-- J.
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To un
Also... You should probably read the first line on in the readme.md of the
library I posted : "You probably shouldn't use this library unless you
absolutely have to."
Op woensdag 22 juni 2016 11:03:08 UTC+2 schreef Frank:
>
>
>
> Op dinsdag 21 juni 2016 20:38:44 UTC+2 schreef Thomas Broyer:
>>
Op dinsdag 21 juni 2016 20:38:44 UTC+2 schreef Thomas Broyer:
>
> What about laptops with touch screens? (Surface, Chrome Pixel, etc.) Maybe
> the user will use the mouse primarily in those? Maybe not?
>
> I seem to remember that touch-enabled couldn't be detected, because one
> could also just
