Is there an example bazel WORKSPACE and BUILD file that pulls in
elemental2? I tried for a good while to figure out how to add it and
didn't get anywhere. The instructions on the project page seems out of
date: https://github.com/google/elemental2
Thanks,
John
On Tuesday, November 13, 2018
I agree about preferring "bean" style properties. It's not a clear choice,
but using bean style properties is more familiar to java programmers and
makes the library fit in much better with the wider java ecosystem. Also
it would make conversions from elemental 1 much easier (though that is
I tried this out by converting a small project that was using elemental 1
to elemental 2. I was able to get it to compile both in dev mode and in a
production compile. But my event listeners weren't firing at all when I
ran it.
Some feedback:
1) Lambda event listeners have to be cast into
I built GWT trunk locally today and I'm trying to compile my app that uses
Java 8 lambdas along with guava-gwt-18.0,jar. When I compile I get an
error thrown because of guava:
[java]Tracing compile failure path for type
'com.google.common.collect.GwtPlatform'
[java]
I think you have to escape the css attributes that start with a dash
like this:
\-moz-box-shadow: 2px 2px 5px #000;
You should be getting a warning about it in dev mode if you are not -
making sure you having logging on at a good level.
John
On Dec 17, 6:03 am, nicolas.deloof
+1 Databinding
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
