Proxy changes not picked up in SDM incremental compile when using Editor framework

I'm using the GWT editor framework and made a typo in one of the proxy accessor methods causing the changes in the editor not being propagated. When I fixed the typo in the proxy and did an incremental compile, the editor context was not being re-generated so the problem was still there. Only a

RequestFactory -> ClassNotFound: JsonException but gwt-dev in WEB-INF/lib

Hi, I get the following exception when I try to run my compiled gwt project with a tomcat server: Feb 12, 2015 12:34:03 AM org.apache.catalina.core.StandardWrapperValve invoke SEVERE: Servlet.service() for servlet [requestFactoryServlet] in context with path [/gwtproj] threw exception [Servlet

Re: GWT compiler is confused by class and package name that differ by capitalization only

If you use GWT 2.7 Final release this should be fixed: https://gwt-review.googlesource.com/#/c/9661/ https://code.google.com/p/google-web-toolkit/issues/detail?id=8716 -- J. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe

Re: SDM from multiple source folders

Dammit, why didn't i tried that. Thank you so much. It works just like in my dreams. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+uns

Re: GWT compiler is confused by class and package name that differ by capitalization only

Which gwt version? On 11 February 2015 at 18:25, wrote: > I'm trying to compile some existing Java code to share with GWT code. I > can't modify the existing Java code, so don't even ask. > > I have a package called "com.foo.bar". > > I also have a class called "com.foo.Bar". > > When I run the

GWT compiler is confused by class and package name that differ by capitalization only

I'm trying to compile some existing Java code to share with GWT code. I can't modify the existing Java code, so don't even ask. I have a package called "com.foo.bar". I also have a class called "com.foo.Bar". When I run the GWT compiler on code that imports the class com.foo.Bar, it complains

Re: SDM from multiple source folders

-src can be passed more than once, so you can write "-src folderPath1 -src folderPath2". I recently added such support/use for my gwt-maven-plugin: https://github.com/tbroyer/gwt-maven-plugin/commit/b49b186e5d17e90442dd7ba4387cd3c70fce6ec6 On Wednesday, February 11, 2015 at 4:10:37 PM UTC+1, Fa

Re: Widget Updating Content Of Another Panel

No, it's added to the main layout and then exposed through a getter(), which is passed into activityManager.setDisplay(template.getAppPanel()); Those are the only references to it. On Tuesday, February 10, 2015 at 2:56:19 PM UTC-6, Juan Pablo Gardella wrote: > > Do you use 'appPanel' in diffe

Re: GWT and Material Design

Awesome project ! I did a couple of examples in my gwt.create presentation to demo how gquery can help with things like material design [1] [2], I'm about to release a better css3 animation plugin for gquery which allows inject css frames, etc. Contact me for any help you need. - Manolo [1] http:

SDM from multiple source folders

Hi guys, I wonder if it's possible to run the SDM (com.google.gwt.dev.codeserver.CodeServer) from multiple source directory. The goal is to recompile the GWT when I make changes on a library from a multi-module project. I tried to pass -src folderPath1;folderPath2 and somme other things, but

Re: gwt-google-api support

I think most of these gwt wrappers around google-apis are not maintained anymore. So people started to create their own wrappers (i.e gwt-charts instead of gwt-viszualization). So the best thing is probably to extend it yourself. Should be much easier once the JsInterops lands in GWT. On Tuesd

Re: GWT RPC or Errai or RequestBuilder?

Hi Mohammed. If you're looking for a replacement for RequestBuilder, which is a low-level approach for requesting, with all its flexibility, you would better go with a high level http client api. To fulfill exactly this need, I developed Requestor , which

Re: Using GWT for front-end code only

Hi Blake, just as a tip for dealing with the communication, you can try Requestor . I created this project initially motivated by this same need (GWT front-end only apps). Cheers Em domingo, 8 de fevereiro de 2015 11:07:50 UTC-3, Blake escreveu: > > Greetin

Re: GWT and Material Design

Thanks for sharing!!! On 11 February 2015 at 03:04, mark kevin ringor wrote: > Hi, > > I forgot to give you the Repository :) > > The source code is available here you can check it out: > https://code.google.com/p/gwt-material/source/checkout > > Best Regards: > Kevin > > On Wed, Feb 11, 2015 at

Re: Documentation site on github

On Wednesday, February 11, 2015 at 9:50:34 AM UTC+1, rhmoller wrote: > > I just tried this out, but it seems there is a difference in the way > github and gwtproject renders markdown. > > I saw that the bullets on the UIBinder page were not rendered properly, > but on github they look right. >

Re: Documentation site on github

I just tried this out, but it seems there is a difference in the way github and gwtproject renders markdown. I saw that the bullets on the UIBinder page were not rendered properly, but on github they look right. https://github.com/gwtproject/gwt-site/pull/45 /Rene Den onsdag den 21. januar 20