Re: GWT Editor with Custom Composites

Thanks Thomas, that was really helpful. I was able to get it working using generics. Here is a sample code if anyone else is interested (here Input is a Composite encapsulating an input element): public class InputEditor extends Input implements LeafValueEditor { @UiConstructor public

Re: [gwt-contrib] POC: Replace Speedtracer with Opentracing.io

Nice! But just FYI, I'm not sure how up to date the loggings in the compiler are so the results might be misleading. On Mon, Apr 24, 2017 at 5:07 PM, Jens wrote: > I stumbled upon opentracing.io some time ago and while it is primarily > designed to trace distributed

[gwt-contrib] POC: Replace Speedtracer with Opentracing.io

I stumbled upon opentracing.io some time ago and while it is primarily designed to trace distributed services you can also use it to trace a single process obviously. GWT compiler can produce speedtracer logs but you can not easily visualize them because the Chrome plugin does not work

[gwt-contrib] Re: GWT 2.8.1 release testers required!

Colin, How does one reference this version in Maven/Gradle projects: HEAD-SNAPSHOT or 2.8.1-SNPASHOT? The later seems pretty old (November 216)? Thanks. On Thursday, April 13, 2017 at 4:51:08 PM UTC-7, Colin Alworth wrote: > > We're about ready to release GWT 2.8.1, a bugfix release a variety

GWT 2.8 - Issue with Javadoc and com.google.web.bindery.event.shared.Event

Hi there, I'm working on transitioning to GWT 2.8 and I'm encountering an odd error that I have not seen in previous GWT versions when generating javadocs for my project: [javadoc] bad source file:

Re: Replacing StorageImpl with itself?

OK this is starting to make sense to me now. It sounds like defaulting to StorageImplNonNativeEvents is intended to avoid browser compatibility problems since some browsers have not fully

Re: GWT/Maven development cycle takes much too long

You need to "rebuild" the webapp when you make changes to it (but not recompile the GWT app), so "mvn package -Dgwt.compiler.skip"; then "reload web server". -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop

Re: GWT/Maven development cycle takes much too long

Not so sure. I can refactor across projects in eclipse... On Mon, Apr 24, 2017 at 8:00 PM, Magnus wrote: > However, now that the error disappeared, I'll come back to the original >>> question and see how it speeds up the development process. >>> >> >> Now that you can

Re: GWT/Maven development cycle takes much too long

> > However, now that the error disappeared, I'll come back to the original >> question and see how it speeds up the development process. >> > > Now that you can have "resolve dependencies from the workspace" enabled in > Eclipse, the GWT Eclipse Plugin should automatically configure the launch

Re: GWT/Maven development cycle takes much too long

On Monday, April 24, 2017 at 5:30:14 PM UTC+2, Magnus wrote: > > Friends, > > it seems as if I could solve the problem by adding this to the pom.xml: > > >org.apache.maven.plugins >maven-war-plugin >2.6 > > > As you can see in the error message, version 2.2.

Re: GWT/Maven development cycle takes much too long

> I am happy to have a solution, but I wonder what was going on. Why istn't > the newest plugin used by default? I have seen that there already is a > version 3.0.0 of the plugin. > Should I hardcode the version in the pom.xml? > To get a reproducible build the version of all your

Re: GWT/Maven development cycle takes much too long

Friends, it seems as if I could solve the problem by adding this to the pom.xml: org.apache.maven.plugins maven-war-plugin 2.6 As you can see in the error message, version 2.2. is used by default. By changing it to 2.6 the error disappeared! I am happy to

Re: GWT/Maven development cycle takes much too long

But please, use the tbroyer plugin, it's much better, makes no sense start a new project using the old one. I also think that using maven makes a pretty reasonable development lifecycle, I just use the IDE to run the maven goals, works perfectly, much easier to configure and get it work. The

Re: GWT Polymer

On Mon, Apr 24, 2017 at 3:27 PM, David wrote: > I noticed Vaadin TouchKit is a Apache licensed open source project. If I > want to develop a mobile application, should I use TouchKit or Vaadin GWT > polymer elements? I do appreciate your feedback about how to develop mobile

Re: GWT Polymer

I noticed Vaadin TouchKit is a Apache licensed open source project. If I want to develop a mobile application, should I use TouchKit or Vaadin GWT polymer elements? I do appreciate your feedback about how to develop mobile application using Vaadin technology. David On Saturday, April 22, 2017

Re: GWT/Maven development cycle takes much too long

Magnus, if you still have a problem to run it - I can create a small "hello world" to show you how to do that with maven -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an

Re: GWT/Maven development cycle takes much too long

Yes, I do everything from command line with maven to run war file - mvn jetty:run-war -Djetty.port=8095 -DskipTests=true to run code server - mvn gwt:run-codeserver gwt maven plugin settings org.codehaus.mojo gwt-maven-plugin ${VERSION.GWT} MyPage.html

Re: Downloading Older Versions of the SDK

Just deployed. So links should work now. - Manolo On Mon, Apr 24, 2017 at 10:29 AM, Manuel Carrasco Moñino wrote: > Yes, it's not deployed yet. The problem is that I tried to deploy after > merging and I got some problems in the process. I need to figure out what > is

Re: Downloading Older Versions of the SDK

Yes, it's not deployed yet. The problem is that I tried to deploy after merging and I got some problems in the process. I need to figure out what is happening with the uploader script, I will do when find a time slot. On Wed, Apr 19, 2017 at 9:39 AM, Thomas Broyer wrote: >