[gwt-contrib] Re: HashCode H$ property should be not enumerable

[Slava Pankov]

Even IE11 is not needed anymore for my projects, there is Edge for Windows 
7+, so all my customers are already upgraded.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/bee51470-39b2-47cb-9688-15034d981617o%40googlegroups.com.

Re: Happy to announce general access for J2CL!

[Slava Pankov]

Thank you!

On Tuesday, November 13, 2018 at 5:39:28 PM UTC-8, Goktug Gokdogan wrote:
>
> Dear GWTers!
>
> We are happy to announce that we have opened up J2CL repository for 
> general access:
> http://github.com/google/j2cl
>
> Please see the README for details and instructions.
>
> I also would like to use this opportunity to thank all Googlers who 
> contributed over the years and made this happen.
>
> Enjoy!
>
> Goktug, on behalf of J2CL team
>
> PS: If you are using Windows, you might have a bumpy road but should get 
> better over time with your feedback and contributions.
>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: java.util.Date clientside incorrect timezone

[Slava Pankov]

For properly working with timezones you have to use ZonedDateTime.
It's emulated for GWT, see https://github.com/slavap/gwt-joda-java-time

On Tuesday, October 30, 2018 at 5:49:25 AM UTC-7, Edson Richter wrote:
>
> Did you find a solution?
>
>
>
> Em quinta-feira, 6 de novembro de 2014 10:18:13 UTC-2, Stepan escreveu:
>>
>> hello everyone!
>>
>> I have a strange problem with dates. when i work in dev mode all is ok, 
>> but when i work in web mode i have problems on client side. 
>>
>> i have this code on the client side(App gwt + gxt). 
>>
>> private static Logger log = Logger.getLogger("DateUtils");
>> .
>> log.log(Level.INFO, to + " " + from);
>> return (int) ((to.getTime() - from.getTime()) / MILLIS_IN_DAY);
>>
>> This code write in chrome console when i  am use two dates:
>>
>> Thu Nov 06 14:48:34 GMT+300 2014 DateUtils
>>
>> INFO: Fri Jan 09 00:00:00 GMT+400 2015 Tue Jan 06 00:00:00 GMT+300 2015 
>>
>>
>> in Russia we have transition 26 october and  now in Moscow, we have 
>> always timezone GMT +3 (in the past has been the time zone GMT +4).
>> i am apply to java tzupdater and on server side all it is ok. problem 
>> only on client side in java.util.Date
>>
>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Plug in External Application to GWT

[Slava Pankov]

Just use iframe for hosting external app inside of the panel of your GWT 
app.

On Thursday, October 25, 2018 at 3:25:56 PM UTC-7, Vishal Mistry wrote:
>
>
>
> On Thursday, 25 October 2018 20:12:49 UTC+11, Jens wrote:
>>
>> If that external application produces a HTML page then yes, you could 
>> display this HTML page in an HTML iframe within a GWT application. 
>> Otherwise you must rebuild the UI of the external application in your GWT 
>> app and query the external application for data that you use to fill the UI 
>> of your GWT app. Querying for data can either happen directly from the GWT 
>> app using HTTP requests or indirectly by first querying a HTTP server you 
>> implement which in turn asks your external application somehow to provide 
>> the data.
>>
>> While you program in Java when using GWT, at the end you just get a 
>> JavaScript application. So in GWT you can only do what a Web Browser / 
>> Node.Js allows you to do. Or put differently: If you can't solve your issue 
>> using plain JavaScript + HTML then you can't solve it using GWT.
>>
>> -- J.
>>
>
> Thanks a lot Jens for your quick response on my post...much appreciated  
>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.9 Questions

[Slava Pankov]

Sure, any newer version of CLDR would be even nicer.

Another one is updating embedded jetty, but not sure if it's even started.

On Thursday, September 6, 2018 at 7:03:37 AM UTC-7, Thomas Broyer wrote:
>
> Thanks for the heads up, the issue hadn't been closed so I thought it 
> wasn't done.
> Any idea if we'd want to update to 33.1?
>
> On Thursday, September 6, 2018 at 5:59:21 AM UTC+2, Slava Pankov wrote:
>>
>> IMO even "Update CLDR to version 32.0.1 
>> <https://github.com/gwtproject/gwt/commit/f81fc698d51cf26f89faca5dde7cf4d1276cce85>"
>>  
>> is worth for releasing GWT 2.9
>>
>> On Wednesday, September 5, 2018 at 2:57:34 AM UTC-7, Thomas Broyer wrote:
>>>
>>> Replying to everyone in one go.
>>>
>>> On Wednesday, September 5, 2018 at 9:12:38 AM UTC+2, Josselin B. wrote:
>>>>
>>>> Hi Jens,
>>>>
>>>> Any idea for a release date of GWT 2.x ?
>>>>
>>>
>>> No. You can follow advancement at 
>>> https://github.com/gwtproject/gwt/milestone/19 (it doesn't move much 
>>> though…)
>>> For now, it didn't seem urgent to release a 2.9, as 2.8.2 works great 
>>> for 99.9% of people.
>>>  
>>>
>>>> Will it add better support for java interface default functions ?
>>>>
>>>
>>> What do you mean?
>>> I can't remember issues related to interface default methods (lambdas 
>>> and method references, sure, but not interface default methods)
>>>  
>>>
>>>> Le mer. 5 sept. 2018 à 09:07, Jens  a écrit :
>>>>
>>>>> GWT 2.x will not drop JSNI anytime soon, only GWT 3 will as it uses a 
>>>>> different Java -> JavaScript compiler internally. And yes there is really 
>>>>> no timeline for GWT 3 as most work is done by contributors in free time. 
>>>>> Currently we are trying to migrate GWT 2.x SDK code so it will become GWT 
>>>>> 3 
>>>>> compatible with mostly no breaking changes. This process happens on 
>>>>> Github 
>>>>> and you can see a list of projects being converted here: 
>>>>> ci.vertispan.com . Also some people are working on build plugins to 
>>>>> provide a better experience out of the box.
>>>>>
>>>>> GWT 2.x SNAPSHOT already supports Java 10 syntax, however no Java 9 + 
>>>>> 10 API additions have been emulated yet in GWT SDK, so you can not use 
>>>>> new 
>>>>> Optional methods and such things. Also some Java 8 APIs are still missing.
>>>>>
>>>>> The only syntax addition of Java 11 is using 'var' for lambda 
>>>>> parameters. GWT depends on Eclipse JDT stable release in order to support 
>>>>> new syntax features. If you don't use that feature then you should 
>>>>> probably 
>>>>> be able to run current GWT with Java 11, haven't tried it though. Never 
>>>>> used OpenJDK with GWT but I can't think of a reason why it should not 
>>>>> work.
>>>>>
>>>>
>>> I (almost) exclusively use OpenJDK, and never had any problem.
>>> Also, OpenJDK 11 and Oracle JDK 11 will (finally) be functionally the 
>>> same, so if GWT works with Oracle JDK 11, it *will* work with OpenJDK 
>>> 11.
>>>
>>> GWT 2.8.2 works with OpenJDK 10 and Oracle JDK 10 already, and while I 
>>> haven't tested I see no reason it wouldn't work with JDK 11 (the big change 
>>> was Jigsaw/JPMS in JDK 9).
>>>
>>> Fwiw, my plan (personal and at work, not for GWT proper) is staying on 
>>> OpenJDK 8 for a little while (switching from Oracle JDK 8 to OpenJDK 8 if 
>>> needed). It looks like there will be many OpenJDK packages with LTS support 
>>> (most Linux distros, AdoptOpenJDK, Zulu) so I may switch to OpenJDK 11 at 
>>> some point, but I bet it won't be before a year… (first and foremost, our 
>>> customers clearly aren't ready; some are only just switching off of Java 7 
>>> …up to Java 8)
>>>
>>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.9 Questions

[Slava Pankov]

IMO even "Update CLDR to version 32.0.1 
"
 
is worth for releasing GWT 2.9

On Wednesday, September 5, 2018 at 2:57:34 AM UTC-7, Thomas Broyer wrote:
>
> Replying to everyone in one go.
>
> On Wednesday, September 5, 2018 at 9:12:38 AM UTC+2, Josselin B. wrote:
>>
>> Hi Jens,
>>
>> Any idea for a release date of GWT 2.x ?
>>
>
> No. You can follow advancement at 
> https://github.com/gwtproject/gwt/milestone/19 (it doesn't move much 
> though…)
> For now, it didn't seem urgent to release a 2.9, as 2.8.2 works great for 
> 99.9% of people.
>  
>
>> Will it add better support for java interface default functions ?
>>
>
> What do you mean?
> I can't remember issues related to interface default methods (lambdas and 
> method references, sure, but not interface default methods)
>  
>
>> Le mer. 5 sept. 2018 à 09:07, Jens > 
>> a écrit :
>>
>>> GWT 2.x will not drop JSNI anytime soon, only GWT 3 will as it uses a 
>>> different Java -> JavaScript compiler internally. And yes there is really 
>>> no timeline for GWT 3 as most work is done by contributors in free time. 
>>> Currently we are trying to migrate GWT 2.x SDK code so it will become GWT 3 
>>> compatible with mostly no breaking changes. This process happens on Github 
>>> and you can see a list of projects being converted here: 
>>> ci.vertispan.com . Also some people are working on build plugins to 
>>> provide a better experience out of the box.
>>>
>>> GWT 2.x SNAPSHOT already supports Java 10 syntax, however no Java 9 + 10 
>>> API additions have been emulated yet in GWT SDK, so you can not use new 
>>> Optional methods and such things. Also some Java 8 APIs are still missing.
>>>
>>> The only syntax addition of Java 11 is using 'var' for lambda 
>>> parameters. GWT depends on Eclipse JDT stable release in order to support 
>>> new syntax features. If you don't use that feature then you should probably 
>>> be able to run current GWT with Java 11, haven't tried it though. Never 
>>> used OpenJDK with GWT but I can't think of a reason why it should not work.
>>>
>>
> I (almost) exclusively use OpenJDK, and never had any problem.
> Also, OpenJDK 11 and Oracle JDK 11 will (finally) be functionally the 
> same, so if GWT works with Oracle JDK 11, it *will* work with OpenJDK 11.
>
> GWT 2.8.2 works with OpenJDK 10 and Oracle JDK 10 already, and while I 
> haven't tested I see no reason it wouldn't work with JDK 11 (the big change 
> was Jigsaw/JPMS in JDK 9).
>
> Fwiw, my plan (personal and at work, not for GWT proper) is staying on 
> OpenJDK 8 for a little while (switching from Oracle JDK 8 to OpenJDK 8 if 
> needed). It looks like there will be many OpenJDK packages with LTS support 
> (most Linux distros, AdoptOpenJDK, Zulu) so I may switch to OpenJDK 11 at 
> some point, but I bet it won't be before a year… (first and foremost, our 
> customers clearly aren't ready; some are only just switching off of Java 7 
> …up to Java 8)
>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT2.8 : org.apache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apache.xerces.xni.parser.XMLParserConfiguration

[Slava Pankov]

For me the following helps in my project's pom.xml:


 
  xerces
  xercesImpl
  2.11.0



On Sunday, July 1, 2018 at 12:13:43 AM UTC-7, Leto wrote:
>
>
>
> Am Samstag, 30. Juni 2018 14:35:17 UTC+2 schrieb Thomas Broyer:
>>
>> What's in your classpath? There might probably be ways to avoid those 
>> situations, in GWT, but so few people have run into this that no one 
>> investigated further.
>
>
>
> I stripped down my dependencies to just only a few, and if I omit the 
>
> > 
> -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
> > 
> -Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
>
> arguments, the problem still occurs.
>
> I use the simple Ant script, no Eclipse, no Maven in this setup. And 
> within my Ant script, I print the current classpath, which results in:
>
>
> > D:\[...]\gwt-2.8.2\gwt-user.jar
> > D:\[...]\gwt-2.8.2\gwt-dev.jar
> > D:\[...]\Eclipse\MyGwtApp\src
> > D:\[...]\Eclipse\MyGwtApp\war\WEB-INF\classes
> > D:\[...]\Eclipse\MyGwtApp\war\WEB-INF\lib
> > D:\[...]\Eclipse\MyGwtApp\war\WEB-INF\lib\aopalliance-1.0.jar
> > D:\[...]\Eclipse\MyGwtApp\war\WEB-INF\lib\gin-2.1.2.jar
> > D:\[...]\Eclipse\MyGwtApp\war\WEB-INF\lib\guice-3.0.jar
> > D:\[...]\Eclipse\MyGwtApp\war\WEB-INF\lib\guice-assistedinject-3.0.jar
> > D:\[...]\Eclipse\MyGwtApp\war\WEB-INF\lib\gwt-visualization-1.1.2.jar
> > D:\[...]\Eclipse\MyGwtApp\war\WEB-INF\lib\javax.inject-1.jar 
>
>
>
>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: The elusive J2CL

[Slava Pankov]

@Ivan Markov For some reason I cannot edit my previous message :-( Just 
want to clarify that I'm extremely grateful for your SDBG tool, it's 
beautiful software, and it's really sad to hear that you have some doubts 
about it.

On Monday, June 11, 2018 at 7:35:47 PM UTC-7, Slava Pankov wrote:
>
> @Ivan Markov Please invest some time to SDBG, it's great tool, very 
> convenient. Despite of Chrome dev.tools, I still prefer SDBG as more 
> natural for java developer.
>
> On Thursday, May 31, 2018 at 6:02:43 AM UTC-7, Ivan Markov wrote:
>>
>> Don't you think there could've been 2x or even 3x as much people working 
>> on porting GWT2 stuff over to J2CL if J2CL was released in the first place? 
>> For one, releasing J2CL could've made me reconsider how much time I invest 
>> in my own SDBG pet project. Which - at the current situation is exactly 
>> zero. Or whether to invest time in the abandoned typescript2java effort, 
>> which would bring seamless JSInterop with gazillions of .d.ts'd JS 
>> libraries without the need to manually code JSInterop bindings...
>>
>> Say what you want, but 3 months since my original rant that at the top of 
>> this thread, the "basic Bazel building issues" of Goktug seem still to be a 
>> roadblock and J2CL is still nowhere to be seen.
>>
>> ... and then we had Daniel planning to write a book on J2CL end of 2016, 
>> remember? Come on guys, it is Q3 2018 now... I might now agree with Learner 
>> Evermore on his points 2) to 5), but with point 1) he nailed it:
>> "1. The backing company backed off but kept the crucial new piece secret 
>> - J2CL."
>>
>>
>> On Wednesday, May 30, 2018 at 6:07:25 PM UTC+3, Frank Hossfeld wrote:
>>>
>>> That's not really true. There are a lot of people working on the GWT 
>>> module, getting them out of GWT and moving them to standalone artifacts. 
>>> Doing that, they replace JSNI with JsInterop, replace generators, etc. This 
>>> is all done, to get GWT 2 ready for GWT 3. And if you want to see something 
>>> existing in GWT 3, you can ask vertispan to do the job. 
>>>
>>> With the knowledge about the things, that will change with GWT 3 / J2CL, 
>>> I was able to make mvp4g ready for GWT 3 / J2CL. I replaced the generator 
>>> with APT and remove the dependency to any GWT classes. I created a sample 
>>> application based on the new version (mvp4g2) and Elemental 2. And yes, it 
>>> works with J2CL. 
>>>
>>> And, keep in mind, applications written in GWT in 2010 still work. What 
>>> was the favorite JS framework at that time? I don't remember.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/4018719f-3680-49d9-8e43-a4f00e9024b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: The elusive J2CL

[Slava Pankov]

@Ivan Markov Please invest some time to SDBG, it's great tool, very 
convenient. Despite of Chrome dev.tools, I still prefer SDBG as more 
natural for java developer.

On Thursday, May 31, 2018 at 6:02:43 AM UTC-7, Ivan Markov wrote:
>
> Don't you think there could've been 2x or even 3x as much people working 
> on porting GWT2 stuff over to J2CL if J2CL was released in the first place? 
> For one, releasing J2CL could've made me reconsider how much time I invest 
> in my own SDBG pet project. Which - at the current situation is exactly 
> zero. Or whether to invest time in the abandoned typescript2java effort, 
> which would bring seamless JSInterop with gazillions of .d.ts'd JS 
> libraries without the need to manually code JSInterop bindings...
>
> Say what you want, but 3 months since my original rant that at the top of 
> this thread, the "basic Bazel building issues" of Goktug seem still to be a 
> roadblock and J2CL is still nowhere to be seen.
>
> ... and then we had Daniel planning to write a book on J2CL end of 2016, 
> remember? Come on guys, it is Q3 2018 now... I might now agree with Learner 
> Evermore on his points 2) to 5), but with point 1) he nailed it:
> "1. The backing company backed off but kept the crucial new piece secret - 
> J2CL."
>
>
> On Wednesday, May 30, 2018 at 6:07:25 PM UTC+3, Frank Hossfeld wrote:
>>
>> That's not really true. There are a lot of people working on the GWT 
>> module, getting them out of GWT and moving them to standalone artifacts. 
>> Doing that, they replace JSNI with JsInterop, replace generators, etc. This 
>> is all done, to get GWT 2 ready for GWT 3. And if you want to see something 
>> existing in GWT 3, you can ask vertispan to do the job. 
>>
>> With the knowledge about the things, that will change with GWT 3 / J2CL, 
>> I was able to make mvp4g ready for GWT 3 / J2CL. I replaced the generator 
>> with APT and remove the dependency to any GWT classes. I created a sample 
>> application based on the new version (mvp4g2) and Elemental 2. And yes, it 
>> works with J2CL. 
>>
>> And, keep in mind, applications written in GWT in 2010 still work. What 
>> was the favorite JS framework at that time? I don't remember.
>>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/9ce474a1-e4cd-4629-960e-5177c4693067%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Submit POST data with no callback

[Slava Pankov]

For redirect you need: form.getElement(). cast().setTarget("");

On Thursday, March 22, 2018 at 7:26:54 AM UTC-7, Matthew McLarty wrote:
>
> Okay, for the record, this does not redirect the current page to the URL 
> that is set to the action of the FormPanel. Any idea what I'm doing wrong?
>
> FormPanel form = new FormPanel();
> form.setAction("
> https://www.FAKEDOMAIN.com/my-account/order-complete.html;);
> form.setHeight("1px");
> form.setWidth("1px");
> form.addStyleName(AppController.HIDDEN_CLASS);
> 
> Hidden transactionId = new Hidden();
> transactionId.getElement().setAttribute("name", 
> "transactionId");
> transactionId.setValue(order.getOrder().getQuoteNumber());
> 
> Hidden transactionTotal = new Hidden();
> transactionTotal.getElement().setAttribute("name", 
> "transactionTotal");
> transactionTotal.setValue(order.getTotalAmount().toString
> ());
> 
> Hidden printURL = new Hidden();
> printURL.getElement().setAttribute("name", "printURL");
> printURL.setValue(order.getPrintURL());
> 
> FlowPanel formStuffer = new FlowPanel();
> formStuffer.add(transactionId);
> formStuffer.add(transactionTotal);
> formStuffer.add(printURL);
> 
> form.add(formStuffer);
> view.getPnlTrackingSubmitter().add(form);
> form.submit();
>
>
>
> On Wednesday, March 21, 2018 at 4:19:39 PM UTC-4, Matthew McLarty wrote:
>>
>> Darn, I was really hoping there'd be an cleaner way but if it works, it 
>> works, I guess. Thank you, Slava. :)
>>
>> On Wednesday, March 21, 2018 at 4:16:41 PM UTC-4, Slava Pankov wrote:
>>>
>>> You can have hidden (display: none) FormPanel with method="post". Then:
>>> form.getElement(). cast().setTarget("");
>>> form.setAction(url);
>>> form.submit();
>>>
>>> That will redirect to specified url with POST.
>>>
>>> On Wednesday, March 21, 2018 at 11:48:46 AM UTC-7, Matthew McLarty wrote:
>>>>
>>>> I feel a little silly asking this since it feels like something that 
>>>> should be obvious.
>>>>
>>>> How do I submit data to another URL, via POST (or GET if need be) 
>>>> without it being an ajax request? Do I need to construct a fake FormPanel 
>>>> and make it 1px big to submit the data to a URL? Can I use request builder 
>>>> and set the content-type header? The problem is that I need to browser to 
>>>> advance to that URL where the submission is processed but the GWT methods 
>>>> all seem to expect that to be an asynchronous event.
>>>>
>>>> Please help?
>>>>
>>>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Submit POST data with no callback

[Slava Pankov]

You can have hidden (display: none) FormPanel with method="post". Then:
form.getElement(). cast().setTarget("");
form.setAction(url);
form.submit();

That will redirect to specified url with POST.

On Wednesday, March 21, 2018 at 11:48:46 AM UTC-7, Matthew McLarty wrote:
>
> I feel a little silly asking this since it feels like something that 
> should be obvious.
>
> How do I submit data to another URL, via POST (or GET if need be) without 
> it being an ajax request? Do I need to construct a fake FormPanel and make 
> it 1px big to submit the data to a URL? Can I use request builder and set 
> the content-type header? The problem is that I need to browser to advance 
> to that URL where the submission is processed but the GWT methods all seem 
> to expect that to be an asynchronous event.
>
> Please help?
>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Experiences working with SmartGWT

[Slava Pankov]

Not sure it is a good choice. I would recommend to look at:

https://github.com/GwtMaterialDesign

or https://github.com/Axellience/vue-gwt

or https://github.com/jqm4gwt/jqm4gwt

or any other GWT widget library based on javascript widgets.
 

On Thursday, March 15, 2018 at 9:52:11 AM UTC-7, subroutines wrote:
>
> Hi I am currently looking at SmartGWT to develop our next web tool, and I 
> am curious to know what is the community's opinion on it overall? and any 
> first-hand experiences working with it?
>
>
>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] The elusive J2CL

[Slava Pankov]

Yes, I agree "even basic missing functionalities" sounds scary. And why 
bazel? It's not even close in popularity with Maven and Gradle.

On Friday, March 9, 2018 at 1:52:34 AM UTC-8, Ivan Markov wrote:
>
> Goktug, sorry for being a but stubborn here, but we need a tad more 
> visibility:
>
> {quote}
> The main blocker for releasing J2CL for wider audience is even basic 
> missing functionalities around building it in open-source and seeing at 
> least some output for your compilations.
> {quote}
>
> "even basic missing functionalities" sounds quite worrysome. What is the 
> ETA for implementing these and releasing a preview? If e.g. two months, 
> fine. If we are talking Q4/2018 or 2019, then that's a different 
> proposition altogether. I guess, not just for us. Please don't answer with 
> the "it's done when it is done" slogan. :) That's one of the major pains 
> for this community imo.
>
> Final Q: are all the legal issues for releasing in the open resolved by 
> now? From personal experience, these might take forever to resolve.
>
> On Thursday, March 8, 2018 at 10:51:21 PM UTC+2, Goktug Gokdogan wrote:
>>
>> > There is still tone of work to do for a polished open source experience 
>> but at least we can give access to more people who is really interested.
>>
>> What I meant here; is giving access *after* basic bazel stuff is finished 
>> so there will be something to play with. We don't want to give access to 
>> a broader group for something that is dead on arrival.
>>
>>
>> On Thu, Mar 8, 2018 at 5:31 AM Alberto Mancini  
>> wrote:
>>
>>> Hello, 
>>> yes, definitely I would like to be in. 
>>> I am really interested.
>>>
>>> Cheers,
>>>Alberto. 
>>>
>>>
>>> On Thu, Mar 8, 2018 at 2:21 PM Nándor Előd Fekete  
>>> wrote:
>>>
 I am *really* interested. Can you sign me up?


 On Thursday, March 8, 2018 at 9:13:01 AM UTC+1, Goktug Gokdogan wrote:
>
> The main blocker for releasing J2CL for wider audience is even basic 
> missing functionalities around building it in open-source and seeing at 
> least some output for your compilations. That is blocked on missing 
> functionalities in bazel. After that we can probably finished in more 
> timely manner.
> There is still tone of work to do for a polished open source 
> experience but at least we can give access to more people who is really 
> interested.
>
 -- 
 You received this message because you are subscribed to the Google 
 Groups "GWT Contributors" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to 
 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/8de62b64-4bc8-4158-80d4-b15ef688f523%40googlegroups.com
  
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "GWT Contributors" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com
>>> .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAGv30V%3DfWDpwQ45u9mPVuXY%3D62PJZ%2B9uxearZk5Lq_a0j2yjaA%40mail.gmail.com
>>>  
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/5e3a16fb-2eda-40b0-a59a-6525b87a17d6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Which API for a future, modern JSON library?

[Slava Pankov]

I think it's better to replicate GSON like API on client side. Another 
option is doing better version of RestyGWT without GWT.create()

On Monday, December 11, 2017 at 4:25:04 AM UTC-8, Thomas Broyer wrote:
>
> Hi all,
>
> Following up on 
> https://github.com/gwtproject/gwt/issues/9484#issuecomment-277216304, 
> I've been toying around to build a new JSON library for GWT.
> Note that my goal is to have a lightweight library that could be used both 
> on the client-side with GWT (and then j2cl), and on the server-side or in 
> any JVM; and "mapping" to/from POJOs is (currently) out of scope.
>
> What do you think would be the best API?
>
>
>- Same as com.google.gwt.json.
>This API is IMO verbose, and is based on wrapper objects that add 
>runtime overhead.
>- Same as elemental.json, except for JsonNull which goes away 
>(represented by a Java 'null' and interchangeable with 'undefined').
>Lighter-weight, both in terms of API verbosity and runtime overhead 
>(no wrapper object).
>Based on type coercion (you can ask every JsonValue to be returned as 
>a boolean, double, or String, and value will be coerced accordingly).
>elemental.json "JRE" types are also usable on client-side, and can be 
>transported through GWT-RPC; I believe this is an aspect that we cannot 
>preserve.
>- Similar to jsinterop-base's Any, JsPropertyMap and JsArrayLike (for 
>JsonValue, JsonObject and JsonArray respectively), and using Java String 
>and primitives for other value types; and probably with the addition of a 
>JsonType enum (or isXxx methods) on Any/JsonValue to be able to tell value 
>types apart before you call the (throwing) asXxx methods.
>This is actually similar to elemental.json but without the 
>JsonBoolean, JsonNumber, and JsonString types; and it throws rather than 
>coercing values.
>This could even go farther and directly use JsonValue[] instead of 
>JsonArray.
>- Something else?
>
> One question also is whether this should be used for consuming JSON 
> mostly, or also for creating JSON (you'd generally use POJOs and serialize 
> them to JSON I believe, but there may be cases where you want to create a 
> dynamic structure that you cannot easily represent as a tree of POJOs), 
> and/or "updating/modifying JSON" (parse, update, stringify).
>
> Fwiw, this would also be a good opportunity to shape how a cross-platform 
> library would be developed in terms of project layout and tooling (in both 
> Gradle and Maven).
>
> Wrt the JVM/server-side support, what JSON parsing library should be used? 
> I was heading towards the lightweight Moshi from Square, but I believe 
> there could possibly be several "adapters" for Moshi, GSON, Jackson, etc. 
> (and even org.json's JsonTokenizer/JsonStringer)
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/f0aa4880-8c0a-4a50-bfd3-f59b29f57dbf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Elemental2:1.0.0-beta-3 released

[Slava Pankov]

Why and what for "latest HEAD_SNAPSHOT release of GWT 
"
 
is requered?
I don't see any "serious" changes on GWT github comparing with 2.8.2


On Tuesday, December 5, 2017 at 9:54:28 AM UTC-8, Julien Dramaix wrote:
>
> I've released a Elemental2:1.0.0-beta-3 yesterday in order to fix the 
> maven issue.
>
> As usual, elemental2 is split into small jar files:
>
>  
>
> Jar file
>
> artifact-id
>
> GWT module
>
> elemental2-core.jar 
> 
>
> elemental2-core
>
> elemental2.core.Core
>
> elemental2-promise.jar 
> 
>
> elemental2-promise
>
> elemental2.promise.Promise
>
> elemental2-dom.jar 
> 
>
> elemental2-dom
>
> elemental2.dom.Dom
>
> elemental2-svg.jar 
> 
>
> elemental2-svg
>
> elemental2.svg.Svg
>
> elemental2-webgl.jar 
> 
>
> elemental2-webgl
>
> elemental2.webgl.WebGl
>
> elemental2-media.jar 
> 
>
> elemental2-media
>
> elemental2.media.Media
>
> elemental2-indexeddb.jar 
> 
>
> elemental2-indexeddb
>
> elemental2.indexeddb.IndexedDb
>
> elemental2-webstorage.jar 
> 
>
> elemental2-webstorage
>
> elemental2.webstorage.WebStorage
>
>  
>
>  
>
> You can try them by downloading the jar files or adding Maven dependencies:
>
>  
>
> 
>
> com.google.elemental2
>
> ${artifact-id}
>
> 1.0.0-beta-3
>
> 
>
>  
>
> Then inherit the right gwt module in your gwt.xml file.
>
>  
>
> This beta version works only with the latest HEAD_SNAPSHOT release of GWT 
> 
> .
>
>  
>
> Don’t hesitate to report any bugs, issues, concerns you have on the 
> github bug tracker .
>
>  
>
> Important note: This is a beta releases and future updates (up until the 
> final release) may break code!  
>
>  
>
> -Julien
>
>
> On Wed, Nov 22, 2017 at 5:59 PM Colin Alworth  > wrote:
>
>> It looks like the poms weren't correctly updated - they still depend on 
>> jsinterop-base 1.0.0-beta-1, tickling 
>> https://github.com/google/elemental2/issues/20 again. The gwt2 compiler 
>> fails on this with this sort of error:
>> [INFO][ERROR] Errors in 
>> 'jar:file:/Users/colin/.m2/repository/com/google/elemental2/elemental2-dom/1.0.0-beta-2/elemental2-dom-1.0.0-beta-2.jar!/elemental2/dom/Element.java'
>> [INFO]   [ERROR] Line 260: The method asString(Element.
>> ReplaceWithNodesUnionType) is undefined for the type Js
>> [INFO]   [ERROR] Line 303: The method asBoolean(Element.
>> ScrollIntoViewTopUnionType) is undefined for the type Js
>> [INFO]   [ERROR] Line 326: The method asBoolean(Element.
>> SetAttributeNSValueUnionType) is undefined for the type Js
>> [INFO]   [ERROR] Line 331: The method asDouble(Element.
>> SetAttributeNSValueUnionType) is undefined for the type Js
>> [INFO]   [ERROR] Line 336: The method asString(Element.
>> SetAttributeNSValueUnionType) is undefined for the type Js
>> [INFO]   [ERROR] Line 364: The method asBoolean(Element.
>> SetAttributeValueUnionType) is undefined for the type Js
>> [INFO]   [ERROR] Line 369: The method asDouble(Element.
>> SetAttributeValueUnionType) is undefined for the type Js
>> [INFO]   [ERROR] Line 374: The method asString(Element.
>> SetAttributeValueUnionType) is undefined for the type Js
>>
>> Simple workaround, manually add excludes on jsinterop-base, and inherit 
>> the correct version in your project:
>> 
>>   com.google.elemental2
>>   elemental2-dom
>>   1.0.0-beta-2
>>   
>> 
>>   com.google.jsinterop
>>   base
>> 
>>   
>> 
>> 
>>   com.google.jsinterop
>>   base
>>   1.0.0-beta-3
>> 
>>
>> 

Re: [gwt-contrib] Re: Elemental2:1.0.0-beta-2 released

[Slava Pankov]

So it's going to be compatible with GWT 2.8.2 ?

On Wednesday, November 22, 2017 at 7:45:28 PM UTC-8, Julien Dramaix wrote:
>
> Thanks for this feedback Colin. I'll update the pom accordingly and do a 
> beta-3 release on Tuesday. 
>
> Julien
>
> On Wed, Nov 22, 2017 at 5:59 PM Colin Alworth  > wrote:
>
>> It looks like the poms weren't correctly updated - they still depend on 
>> jsinterop-base 1.0.0-beta-1, tickling 
>> https://github.com/google/elemental2/issues/20 again. The gwt2 compiler 
>> fails on this with this sort of error:
>> [INFO][ERROR] Errors in 
>> 'jar:file:/Users/colin/.m2/repository/com/google/elemental2/elemental2-dom/1.0.0-beta-2/elemental2-dom-1.0.0-beta-2.jar!/elemental2/dom/Element.java'
>> [INFO]   [ERROR] Line 260: The method asString(Element.
>> ReplaceWithNodesUnionType) is undefined for the type Js
>> [INFO]   [ERROR] Line 303: The method asBoolean(Element.
>> ScrollIntoViewTopUnionType) is undefined for the type Js
>> [INFO]   [ERROR] Line 326: The method asBoolean(Element.
>> SetAttributeNSValueUnionType) is undefined for the type Js
>> [INFO]   [ERROR] Line 331: The method asDouble(Element.
>> SetAttributeNSValueUnionType) is undefined for the type Js
>> [INFO]   [ERROR] Line 336: The method asString(Element.
>> SetAttributeNSValueUnionType) is undefined for the type Js
>> [INFO]   [ERROR] Line 364: The method asBoolean(Element.
>> SetAttributeValueUnionType) is undefined for the type Js
>> [INFO]   [ERROR] Line 369: The method asDouble(Element.
>> SetAttributeValueUnionType) is undefined for the type Js
>> [INFO]   [ERROR] Line 374: The method asString(Element.
>> SetAttributeValueUnionType) is undefined for the type Js
>>
>> Simple workaround, manually add excludes on jsinterop-base, and inherit 
>> the correct version in your project:
>> 
>>   com.google.elemental2
>>   elemental2-dom
>>   1.0.0-beta-2
>>   
>> 
>>   com.google.jsinterop
>>   base
>> 
>>   
>> 
>> 
>>   com.google.jsinterop
>>   base
>>   1.0.0-beta-3
>> 
>>
>> Julien, if you do happen to release an updated beta to solve this, 
>> perhaps also update jsinterop-annotations to 1.0.2, the version that was 
>> released with GWT 2.8.2.
>>
>>
>>
>> On Wednesday, November 22, 2017 at 7:13:29 PM UTC-6, Julien Dramaix wrote:
>>>
>>> The beta version of Elemental2 using the JsInterop specification has 
>>> been released on Sonatype today and is available on Maven central. This 
>>> release should be the last beta release and I expect to release the first 
>>> RC in few weeks.
>>>
>>>
>>> This release introduces -- among others:
>>>
>>> - a better granularity for api with numbers. Config files list APIs 
>>> using integer instead of double.
>>>
>>> - usage of wildcard type for more flexibility.
>>>
>>> - support for javascript constructor function 
>>>
>>> - static factory methods for dictionary type.
>>>
>>> Elemental2 is split into small jar files:
>>>
>>>
>>> Jar file
>>>
>>> artifact-id
>>>
>>> GWT module
>>>
>>> elemental2-core.jar 
>>> 
>>>
>>> elemental2-core
>>>
>>> elemental2.core.Core
>>>
>>> elemental2-promise.jar 
>>> 
>>>
>>> elemental2-promise
>>>
>>> elemental2.promise.Promise
>>>
>>> elemental2-dom.jar 
>>> 
>>>
>>> elemental2-dom
>>>
>>> elemental2.dom.Dom
>>>
>>> elemental2-svg.jar 
>>> 
>>>
>>> elemental2-svg
>>>
>>> elemental2.svg.Svg
>>>
>>> elemental2-webgl.jar 
>>> 
>>>
>>> elemental2-webgl
>>>
>>> elemental2.webgl.WebGl
>>>
>>> elemental2-media.jar 
>>> 
>>>
>>> elemental2-media
>>>
>>> elemental2.media.Media
>>>
>>> elemental2-indexeddb.jar 
>>> 
>>>
>>> elemental2-indexeddb
>>>
>>> elemental2.indexeddb.IndexedDb
>>>
>>> elemental2-webstorage.jar 
>>> 
>>>
>>> elemental2-webstorage
>>>
>>> elemental2.webstorage.WebStorage
>>>
>>>

[gwt-contrib] Re: GWT 2.8.2 release => [ERROR] ... XmlRootElement ... XmlElement ... cannot be resolved to a type

[Slava Pankov]

Try to add dependency to your pom.xml:


  javax.xml.bind
  jaxb-api
  2.3.0
  sources
  provided


On Friday, October 20, 2017 at 8:32:02 AM UTC-7, Michael Joyner wrote:
>
> Eh...
>
> I changed my gradle build config to use 2.8.2 and started getting import 
> annotation errors (below).
>
> Switching back 2.8.1 and the errors go away.
>
> The annotations are imports from:
>
> import javax.xml.bind.annotation.XmlAttribute;
> import javax.xml.bind.annotation.XmlElement;
> import javax.xml.bind.annotation.XmlRootElement;
>
> > Task :compileGwt
> Compiling module selenium.RestyGwtCodecTester
>Tracing compile failure path for type 'me.pubz.sitemap.SitemapIndex'
>   [ERROR] Errors in '
> jar:file:/home/michael/git/SHARED-POJOS/SHARED-POJOS/build/libs/SHARED-POJOS-20170711.jar!/me/pubz/sitemap/SitemapIndex.java
> '
>  [ERROR] Line 15: XmlRootElement cannot be resolved to a type
>  [ERROR] Line 45: XmlElement cannot be resolved to a type
>  [ERROR] Line 22: XmlAttribute cannot be resolved to a type
>  [ERROR] Line 8: The import javax.xml.bind cannot be resolved
>  [ERROR] Line 32: XmlAttribute cannot be resolved to a type
>  [ERROR] Line 7: The import javax.xml.bind cannot be resolved
>  [ERROR] Line 9: The import javax.xml.bind cannot be resolved
>  [ERROR] Line 27: XmlAttribute cannot be resolved to a type
> offending code:
>
> package me.pubz.sitemap;
>
>
> import java.util.Date;
> import java.util.List;
>
> import javax.xml.bind.annotation.XmlAttribute;
> import javax.xml.bind.annotation.XmlElement;
> import javax.xml.bind.annotation.XmlRootElement;
>
> /**
>  * Created by AmitG on 20-03-2014.
>  */
>
> @XmlRootElement(name = "sitemapindex")
> public class SitemapIndex {
>
> private String xmlns;
> private List sitemaps;
> private String elapsed;
> 
> @XmlAttribute()
> public Date getGenerated(){
> return new java.util.Date();
> }
>
> @XmlAttribute()
> public String getXmlns() {
> return xmlns;
> }
> 
> @XmlAttribute()
> public String getElapsed(){
> return elapsed;
> }
> 
> public void setElapsed(String elapsed){
> this.elapsed=elapsed;
> }
>
> public void setXmlns(String xmlns) {
> this.xmlns = xmlns;
> }
>
> @XmlElement(name = "sitemap")
> public List getSitemaps() {
> return sitemaps;
> }
>
> public void setSitemaps(List sitemaps) {
> this.sitemaps = sitemaps;
> }
> }
>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/9df8d586-90cc-4443-8cfe-94b53942d2a7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.8.2 release => [ERROR] ... XmlRootElement ... XmlElement ... cannot be resolved to a type

[Slava Pankov]

Try to add dependency to your pom.xml:


  javax.xml.bind
  jaxb-api
  2.3.0
  sources
  provided



On Friday, October 20, 2017 at 8:32:20 AM UTC-7, Michael Joyner wrote:
>
> Eh...
>
> I changed my gradle build config to use 2.8.2 and started getting import 
> annotation errors (below).
>
> Switching back 2.8.1 and the errors go away.
>
> The annotations are imports from:
>
> import javax.xml.bind.annotation.XmlAttribute;
> import javax.xml.bind.annotation.XmlElement;
> import javax.xml.bind.annotation.XmlRootElement;
>
> > Task :compileGwt
> Compiling module selenium.RestyGwtCodecTester
>Tracing compile failure path for type 'me.pubz.sitemap.SitemapIndex'
>   [ERROR] Errors in '
> jar:file:/home/michael/git/SHARED-POJOS/SHARED-POJOS/build/libs/SHARED-POJOS-20170711.jar!/me/pubz/sitemap/SitemapIndex.java
> '
>  [ERROR] Line 15: XmlRootElement cannot be resolved to a type
>  [ERROR] Line 45: XmlElement cannot be resolved to a type
>  [ERROR] Line 22: XmlAttribute cannot be resolved to a type
>  [ERROR] Line 8: The import javax.xml.bind cannot be resolved
>  [ERROR] Line 32: XmlAttribute cannot be resolved to a type
>  [ERROR] Line 7: The import javax.xml.bind cannot be resolved
>  [ERROR] Line 9: The import javax.xml.bind cannot be resolved
>  [ERROR] Line 27: XmlAttribute cannot be resolved to a type
> offending code:
>
> package me.pubz.sitemap;
>
>
> import java.util.Date;
> import java.util.List;
>
> import javax.xml.bind.annotation.XmlAttribute;
> import javax.xml.bind.annotation.XmlElement;
> import javax.xml.bind.annotation.XmlRootElement;
>
> /**
>  * Created by AmitG on 20-03-2014.
>  */
>
> @XmlRootElement(name = "sitemapindex")
> public class SitemapIndex {
>
> private String xmlns;
> private List sitemaps;
> private String elapsed;
> 
> @XmlAttribute()
> public Date getGenerated(){
> return new java.util.Date();
> }
>
> @XmlAttribute()
> public String getXmlns() {
> return xmlns;
> }
> 
> @XmlAttribute()
> public String getElapsed(){
> return elapsed;
> }
> 
> public void setElapsed(String elapsed){
> this.elapsed=elapsed;
> }
>
> public void setXmlns(String xmlns) {
> this.xmlns = xmlns;
> }
>
> @XmlElement(name = "sitemap")
> public List getSitemaps() {
> return sitemaps;
> }
>
> public void setSitemaps(List sitemaps) {
> this.sitemaps = sitemaps;
> }
> }
>
>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.8.2 release

[Slava Pankov]

Thank you!

On Thursday, October 19, 2017 at 1:30:49 PM UTC-7, Colin Alworth wrote:
>
> Today we released the next version of GWT, version 2.8.2. A few quick 
> highlights from this new release:
>
>- GWT can now run on Java 9 (though Java 9 features are not yet 
>supported, coming soon!)
>- Chrome 61 change in getAbsoluteTop/Left has been fixed
>- Errors on the page reported from window.onerror are now reported to 
>your uncaught exception handler
>- GWT now generates CSP compliant dom elements
>
> The release notes can be found at 
> http://www.gwtproject.org/release-notes.html#Release_Notes_2_8_2. Get 
> yours from Maven Central, or from the zip release .
>
> Special thanks to Max Barkley of RedHat who helped lead the release effort 
> this time, and to all of the fantastic testers who helped us ensure that 
> this release was ready to go.
>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Integration between Datatables and GWT

[Slava Pankov]

Integration of data tables in jqm4gwt is made as plugin, so can be easily 
extracted and used in your project. It’s stable, I’m using it in huge 
production project. Though it’s not based on new js interop, but on jsni.

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Typescript annotations to JsInterop java classes automatic generation tool ready

[Slava Pankov]

Great! That will be absolutely must have tool, thank you.

On Thursday, September 28, 2017 at 2:54:05 AM UTC-7, Ltearno wrote:
>
> Hi everyone,
>
> I made up and published today a tool which uses Typescript type 
> definitions (.d.ts) and generates the corresponding JsInterop classes for 
> use inside a GWT application (or JaCL when available).
>
> The tool is here : https://github.com/ltearno/typescript2java
>
> I use it to translate the full Angular 4 API (2000+ classes) into 
> JsInterop and get a working code. It can also generate the standard web api 
> from 'lib.es6.d.ts' and generate something that ressembles Elemental2 a lot!
>
> I am interested to help if people want to use it or have some other use 
> cases (wrapping D3.js or any other library available on 'definitely 
> typed'). So don't hesitate to file an issue on github... Or to answer here!
>
> Thanks
> Arnaud
>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Progressive Web App with Caching and Code Splitting

[Slava Pankov]

It would be really nice if you share details or even code of your 
implementation.

On Monday, August 7, 2017 at 7:21:19 AM UTC-7, Gernot Pansy wrote:
>
> I got it myself working, with a extended Linker and the using of 
> XhrFragementLoader.
>
> On Friday, August 4, 2017 at 12:00:55 AM UTC+2, Gernot Pansy wrote:
>>
>> Hi,
>>
>> I wan't to convert my GWT (2.8.1) application to an progressive web app 
>> and add code splitting. I already build a custom Linker which creates a 
>> service worker file automatically and the caching is working except of the 
>> deferred fragemnts.
>> My service worker is not called if the are loaded, it seems they are 
>> loaded outside of the scope.
>>
>> The same happens in this demo: 
>> http://www.g-widgets.com/2016/08/11/progressive-web-apps-recipes-for-gwt/
>>
>> If you look in the chrome console, all request are loaded trough the 
>> service worker but not the fragments (only once in install phase, because 
>> the are all files cached).
>>
>> Seems that this is the relevant code: 
>> https://github.com/gwtproject/gwt/blob/master/dev/core/src/com/google/gwt/core/ext/linker/impl/runAsync.js
>> Here is still the old language property used on the script tag.
>>
>> Has anyone an idea how to fix that?
>>
>> cheers,
>> gernot
>>
>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: How to recompile the output of GWT compiler with Closure Compiler?

[Slava Pankov]

I've asked similar 
question 
https://groups.google.com/forum/#!msg/google-web-toolkit/k_kjIv9Klsg/LZAZiUf9BAAJ;context-place=forum/google-web-toolkit
No much results though :-(

On Tuesday, July 11, 2017 at 4:57:55 AM UTC-7, Kazik Pogoda wrote:
>
> I already set up the whole toolchain in my project based on maven 
> dependencies:
>
> https://github.com/xemantic/github-users-web
>
> I am using both, GWT and Closure Library. Closure Templates in Incremental 
> DOM mode in particular + jsinterop. Now I would like to combine and 
> minimize all the JavaScript sources in the project, because at the moment 
> it is still loading separately:
>
>- compiled gwt module
>- compiled closure modules
>- material-components-web.js
>
> I already enabled collapse-all-properties in my GWT module to keep just 
> one permutation and it seems to be working with the Closure Compiler. I can 
> also keep GWT compiler output PRETTY and even 
> enable -XclosureFormattedOutput, but I have no idea:
>
> *How to invoke onModuleLoad() method of my GWT module after recompilation,*
>
> nor how to specify proper entry point for the closure compiler?
>
> Any hints are highly appreciated. If the -XclosureFormattedOutput flag is 
> there, then most likely someone is using it for the same purpose I am 
> trying to achieve. I believe that Google Inbox is using these techniques. 
> But the Internet seems completely silent on this topic and I couldn't find 
> any examples.
>
>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Chrome Performance tab only shows minified names

[Slava Pankov]

Did you add "-style PRETTY" to your debug config?

On Wednesday, May 3, 2017 at 5:00:11 AM UTC-7, Anders Forsell wrote:
>
> Hi,
>
> I'm only seeing "minified" names in the new Chrome Performance tab where I 
> would like to see abbreviated names when using SuperDev mode and 
> (-XmethodNameDisplayMode 
> ABBREVIATED)
>
> I reported this as a Chrome issue but not sure if it will end up to the 
> right team...
>
> Anders
>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.8.0 Eclipse

[Slava Pankov]

This one works with GWT 2.8 
perfectly: http://storage.googleapis.com/gwt-eclipse-plugin/v3/release

Sources are here: https://github.com/gwt-plugins/gwt-eclipse-plugin

On Friday, February 17, 2017 at 8:45:25 AM UTC-8, l.s...@behaimits.com 
wrote:
>
> Hi, I have noticed that GWT 2.7 is 3 years old. GWT 2.8 final was released 
> like half a year ago. How should one develop GWT applications - in which 
> IDE? Will there be an update for GWT Eclipse plugin this year?
>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.8 generates code 14% bigger than GWT 2.7

[Slava Pankov]

Still not working for me.

  
  
  
  

[ERROR] The module must not have multiple fragments when using the Single 
Script Linker.

Probably the problem is that I have many languages (i18n) in my app.
Any other ideas?


On Wednesday, November 30, 2016 at 11:08:13 PM UTC-8, Kirill Prazdnikov 
wrote:
>
> Please try single permutation
>   
>
>
> On Thu, Dec 1, 2016 at 1:50 AM, Slava Pankov <pan...@gmail.com 
> > wrote:
>
>> SSO is not working for my project, I cannot successfully compile with it.
>> Put the following to my gwt.xml, but no luck:
>>
>> 
>> 
>> 
>>
>>
>> On Tuesday, November 29, 2016 at 6:44:37 AM UTC-8, Kirill Prazdnikov 
>> wrote:
>>>
>>> Do you use SSO ? SSO script is smaller then no SSO. Did you run CC on it 
>>> ?
>>>
>>> 29 нояб. 2016 г. 17:29 пользователь "Etienne Basso" <ebas...@gmail.com> 
>>> написал:
>>>
>>> Hi Ignacio,
>>>>
>>>> This is not only about loading time over the network, but also about 
>>>> script parsing by the web browser. 
>>>> In 98% of the case this is not an issue, but I have a very specific use 
>>>> case were the code is directly embedded on a special device which doesn't 
>>>> even have a real CPU but an ASIC emulating one. This device is really 
>>>> really not powerful and GWT is the only framework providing decent speed.  
>>>> I noticed significant differences in the script parsing delay as js 
>>>> sources 
>>>> are getting bigger.
>>>>
>>>> In my case 100KB are a huge deal.
>>>>
>>>> Le samedi 26 novembre 2016 09:56:27 UTC+1, Ignacio Baca Moreno-Torres a 
>>>> écrit :
>>>>>
>>>>> But IMO if you really care user experience you have other places to 
>>>>> improve your page. I thinks updating to the last version is always a good 
>>>>> idea, if any security or compatibility blocker problem is detected in 
>>>>> your 
>>>>> version you will need to update, and having a old version won't help. 
>>>>> Also 
>>>>> this helps move forward the community and the lib (GWT), because everyone 
>>>>> focused in the last version, also focus the issues and improvements in 
>>>>> that 
>>>>> version.
>>>>>
>>>>> The small step back eliminating the closure compiler just increase a 
>>>>> bit the code size of your app. But 100k?! did you see the trends and the 
>>>>> average code size of webs? 
>>>>> http://httparchive.org/trends.php?s=All=Nov+15+2014=Nov+1+2016,
>>>>>  
>>>>> you should note that even google.com uses 500k in 13request to load, 
>>>>> and it's ""just"" a text inbox in the center of your window (
>>>>> http://httparchive.org/viewsite.php?pageid=70036564).
>>>>>
>>>>> I might be wrong, but probably trying to embed the app.nocache.js in 
>>>>> your index.html will gain some milliseconds, probably just that dummy 
>>>>> change will get more ms than the cache-ables 100k you have lose without 
>>>>> the 
>>>>> closure pass. If your app is quite big, various MBs, you should take care 
>>>>> than the first split point load a minimum as possible to show something 
>>>>> to 
>>>>> the user. But, in your case, less than a 1M, I think that using split 
>>>>> point 
>>>>> is not a good idea. Your code will get cached, and most of static apps 
>>>>> already has more than 500k of JS, so your single page app having a 
>>>>> 500k-1M 
>>>>> of JS is pretty reasonable.
>>>>>
>>>>> You can go forward and apply the progressive web concepts (
>>>>> https://developers.google.com/web/progressive-web-apps/checklist). 
>>>>> Pretty sure you get there without the closure compiler ;). Service 
>>>>> workers 
>>>>> will allow maximum control to preload other split point or resources, and 
>>>>> to absolutely control how your app caches, so you can use previous 
>>>>> version, 
>>>>> load the next one and in the next page reload the new app version will be 
>>>>> used. This is not easy at all, but... some time we focus on the 
>>>>> optimization we have no control of (like the closure pass) and we don't 
>>>>> apply other we have control 

Re: GWT 2.8 generates code 14% bigger than GWT 2.7

[Slava Pankov]

SSO is not working for my project, I cannot successfully compile with it.
Put the following to my gwt.xml, but no luck:






On Tuesday, November 29, 2016 at 6:44:37 AM UTC-8, Kirill Prazdnikov wrote:
>
> Do you use SSO ? SSO script is smaller then no SSO. Did you run CC on it ?
>
> 29 нояб. 2016 г. 17:29 пользователь "Etienne Basso" <ebas...@gmail.com 
> > написал:
>
>> Hi Ignacio,
>>
>> This is not only about loading time over the network, but also about 
>> script parsing by the web browser. 
>> In 98% of the case this is not an issue, but I have a very specific use 
>> case were the code is directly embedded on a special device which doesn't 
>> even have a real CPU but an ASIC emulating one. This device is really 
>> really not powerful and GWT is the only framework providing decent speed.  
>> I noticed significant differences in the script parsing delay as js sources 
>> are getting bigger.
>>
>> In my case 100KB are a huge deal.
>>
>> Le samedi 26 novembre 2016 09:56:27 UTC+1, Ignacio Baca Moreno-Torres a 
>> écrit :
>>>
>>> But IMO if you really care user experience you have other places to 
>>> improve your page. I thinks updating to the last version is always a good 
>>> idea, if any security or compatibility blocker problem is detected in your 
>>> version you will need to update, and having a old version won't help. Also 
>>> this helps move forward the community and the lib (GWT), because everyone 
>>> focused in the last version, also focus the issues and improvements in that 
>>> version.
>>>
>>> The small step back eliminating the closure compiler just increase a bit 
>>> the code size of your app. But 100k?! did you see the trends and the 
>>> average code size of webs? 
>>> http://httparchive.org/trends.php?s=All=Nov+15+2014=Nov+1+2016,
>>>  
>>> you should note that even google.com uses 500k in 13request to load, 
>>> and it's ""just"" a text inbox in the center of your window (
>>> http://httparchive.org/viewsite.php?pageid=70036564).
>>>
>>> I might be wrong, but probably trying to embed the app.nocache.js in 
>>> your index.html will gain some milliseconds, probably just that dummy 
>>> change will get more ms than the cache-ables 100k you have lose without the 
>>> closure pass. If your app is quite big, various MBs, you should take care 
>>> than the first split point load a minimum as possible to show something to 
>>> the user. But, in your case, less than a 1M, I think that using split point 
>>> is not a good idea. Your code will get cached, and most of static apps 
>>> already has more than 500k of JS, so your single page app having a 500k-1M 
>>> of JS is pretty reasonable.
>>>
>>> You can go forward and apply the progressive web concepts (
>>> https://developers.google.com/web/progressive-web-apps/checklist). 
>>> Pretty sure you get there without the closure compiler ;). Service workers 
>>> will allow maximum control to preload other split point or resources, and 
>>> to absolutely control how your app caches, so you can use previous version, 
>>> load the next one and in the next page reload the new app version will be 
>>> used. This is not easy at all, but... some time we focus on the 
>>> optimization we have no control of (like the closure pass) and we don't 
>>> apply other we have control of, but that requires our effort.
>>>
>>> So,  update to GWT 2.8! it's awesome!, try other solutions to improve 
>>> page loads and share how you do it!
>>>
>>> On Friday, November 25, 2016 at 10:39:44 PM UTC+1, Slava Pankov wrote:
>>>>
>>>> @Jens
>>>>
>>>> I've tried WITHOUT any success to use closure compiler externally with 
>>>> GWT 2.8
>>>> See my question here: 
>>>> https://groups.google.com/forum/#!searchin/google-web-toolkit/closure$20compiler%7Csort:date/google-web-toolkit/k_kjIv9Klsg/LZAZiUf9BAAJ
>>>> Still want to find out exact steps to get it working :-(
>>>>
>>>>
>>>> On Friday, November 25, 2016 at 2:43:11 AM UTC-8, Kirill Prazdnikov 
>>>> wrote:
>>>>>
>>>>> Hi Jens, 
>>>>>
>>>>> What if we have SSO linker ? 
>>>>> Then no hacks is needed, right ?
>>>>> Then just run the Google Closure Compiler on the output.
>>>>>
>>>> -- 
>>
>>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GwtMaterialDesign vs gwt-polymer-elements

[Slava Pankov]

I just don't get this trend with "burying" widgets and UiBinder. Even with 
Errai I don't see any meaningful replacement for composite UI, i.e. design 
simple blocks as ... and then reuse them with 

Though with Polymer it looks like it's possible by defining web component 
for each logical block.


On Wednesday, November 23, 2016 at 2:40:45 PM UTC-8, Amit Munwes wrote:
>
> I decided to go with Polymer:
> 1. Very active framework and not specific to GWT developers - so you can 
> find answers/examples etc. easily as well as a growing set of web 
> components that can be used within your app
> 2. High-end material design components, in browsers as well as mobile 
> devices
> 3. Great documentation
> 4. Future-proofing regarding GWT 3.0, using only JS-Interop with no widgets
> 5. I use Vaadin's generator directly (not the packaged JAR) so we can 
> upgrade Polymer version any time a new version is available
>
> On Friday, November 18, 2016 at 1:45:26 AM UTC+2, tbb wrote:
>>
>> Hi all,
>>
>> I've got a 3 year old enterprise GWT app which also has a mobile app 
>> based on GWT. Our current design style is based on Bootstrap. As things 
>> change, I'd like to freshen the UX by using Material Design. I've seen 2 
>> libraries: GwtMaterialDesign and gwt-polymer-elements. 
>>
>> From what I can see:
>> - Both showcases look great, esp both seem to have an "enterprise" class 
>> table/grid control.
>> - GwtMaterialDesign: Read quite positive things in terms of community.
>> - gwt-polymer-elements: By Vaadin which are quite active in the GWT world 
>> now, based on "real" Polymer elements and the new GWT 2.8 elemental (?)
>>
>> Would be great if anyone could comment on using either of them as I think 
>> once we've decided for one of the libraries, it will be hard to switch.
>>
>> Any feedback would be great!
>>
>> Thanks,
>> Thomas
>>
>>
>>
>>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.8 generates code 14% bigger than GWT 2.7

[Slava Pankov]

No, I have not tried SSO. But in 2.7 it was working fine without SSO, I 
will try SSO and let you know.

On Saturday, November 26, 2016 at 12:55:25 AM UTC-8, Kirill Prazdnikov 
wrote:
>
> Hi
>  
>
>> I've tried WITHOUT any success to use closure compiler externally with 
>> GWT 2.8
>>
>
> Did you try SSO ? Did you run Closure Compiler on SSO output script ?
>
>
>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.8 generates code 14% bigger than GWT 2.7

[Slava Pankov]

@Jens

I've tried WITHOUT any success to use closure compiler externally with GWT 
2.8
See my question 
here: 
https://groups.google.com/forum/#!searchin/google-web-toolkit/closure$20compiler%7Csort:date/google-web-toolkit/k_kjIv9Klsg/LZAZiUf9BAAJ
Still want to find out exact steps to get it working :-(


On Friday, November 25, 2016 at 2:43:11 AM UTC-8, Kirill Prazdnikov wrote:
>
> Hi Jens, 
>
> What if we have SSO linker ? 
> Then no hacks is needed, right ?
> Then just run the Google Closure Compiler on the output.
>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Bug in IE11 with GWT project (White screen after some time)

[Slava Pankov]

I'm using jQuery Datatable and GWT 2.8, and don't have any problems with 
IE11, despite of large (thousands of rows) datasets fetched from the server 
side.
It could be many reasons why your app is failing, try to open web 
development tools, may be something will be logged there during your app 
crash.

On Friday, November 25, 2016 at 8:12:18 AM UTC-8, johan.d...@gmail.com 
wrote:
>
> Our team has a problem when running a GWT application on IE11. After some 
> time, the content of the IE11 browser becomes white.
> One of the characteristic of the problem is that this happens randomly, 
> sometimes after 1.5 hours, sometimes a complete night, sometimes more (one 
> of the requirement of the application is to keep it opened several days).
>
>
>
>
> 
>
>
>
> - GWT 2.8 version (bug is present with 2.7 version too (tested))
> - Datatable (jquery datatable plugin) is in use (via JSNI) but the problem 
> occurs with pure GWT as well,
> - Application is requesting data to the server every 5 seconds via http 
> GET request,
> - To reproduce the bug faster I open 5 windows together (same application 
> same data), after one night some of them are frozen (i.e. blank page) 
> (mainly 2), some of them are still working,
> - I am using local network,
> - The problem does not occur with firefox version 45.4.0 (application for 
> IE11 is compiled with the same user.agent property gecko1_8),
>
> My question is:
> Has anybody else already seen this strange behavior?
> Has anyone any idea what I could try?
> I already tried with enabling/disabling the "Use software rendering 
> instead of GPU rendering*", I already tried with disabling all add-ons.
>
> Thank you.
>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Internet Explorer Google Web Toolkit Plugin Installing but not Working.

[Slava Pankov]

Dev mode works just fine with GWT 2.8 in old Firefox 24 esr and IE11. 
I'm still using it (together with superdev + sdbg), and devmode is quite 
better and "faster to develop with" from Java point of view, because 
variables/expressions tabs in Eclipse are convenient and "live", also hints 
with values are shown on mouse over in editor.

On Monday, November 14, 2016 at 6:15:22 AM UTC-8, Thomas Broyer wrote:
>
>
>
> On Monday, November 14, 2016 at 12:12:01 PM UTC+1, Kirill Prazdnikov wrote:
>>
>> Why not to approve the dev-mode-delete.patch ?
>>
>
> You're right, maybe now is the time. I think we'll discuss this at the 
> next Steering Committee meeting; in the meantime, feedback is welcome (e.g. 
> if DevMode already is broken)
>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: jqm4gwt ver. 1.4.7 released

[Slava Pankov]

I will plan switch to js interop in next release, which will be jQuery 
Mobile 1.5 based.
This 1.4.7 version is quite stable, and I have huge project based on it, so 
decided not to introduce heavy changes, just checked that everything is 
working fine on GWT 2.8

On Saturday, October 29, 2016 at 6:59:36 AM UTC-7, Kirill Prazdnikov wrote:
>
>
>
> On Saturday, October 29, 2016 at 4:12:00 PM UTC+3, Alain wrote:
>>
>>
>> https://github.com/jqm4gwt/jqm4gwt/blob/master/library/src/main/java/com/sksamuel/jqm4gwt/button/JQMButton.java
>>
>> Have not checked the entire code.
>>
>
> Thanks, I see lots of gwt-user dependencies:  Widget, ClickHandler, 
> JavaScriptObject.
> I agree better to have 100% interop solution.
>
>
>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

jqm4gwt ver. 1.4.7 released

[Slava Pankov]

jqm4gwt is an advanced wrapper over the jQuery Mobile framework

GWT 2.8 is supported, see here https://github.com/jqm4gwt/jqm4gwt

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Closure compiler and GWT 2.8.0

[Slava Pankov]

Integrated closure compiler was removed in 2.8.0
So now I'm trying to use external (post-processing) call to closure 
compiler.
SIMPLE mode is working just fine, but gives no improvement over standard 
GWT compilation at all.
ADVANCED mode gives improvement (when GWT compiled in PRETTY mode), but 
produces non-working resulting JS, because it obfuscates $wnd. and __ 
functions/methods.
It could be kind of resolved by providing --externs to closure compiler, 
the problem is it doesn't support regexes, so I have to prepare huge file 
with exact names to be preserved (and it's semi-manual job, I don't know 
how to automate it).

1. So the question is - what is the proper way to get working JS by using 
external closure compiler?
2. There is an option in GWT "-XclosureFormattedOutput", when defined it 
affects resulting JS produced by GWT, but may be it's obsolete or not 
supposed to be used at all?
3. I see pom-gwt.xml added to closure compiler repository on github few 
weeks ago, but cannot figure out what for it supposed to be used? 
https://github.com/google/closure-compiler/blob/master/pom-gwt.xml

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: UiBinder alternative

[Slava Pankov]

UiBinder should not be removed. It's not about widgets, but about 
convenient way of defining UI. And also it's quite similar to Android way 
of developing, so quite comfortable for developers with Android experience. 

On Thursday, September 8, 2016 at 8:25:52 AM UTC-7, Ahmad Bawaneh wrote:
>
> and one more thing
> I think publishing news about the major changes in an API early is a good 
> thing, as long the road map and the upgrade process and the alternatives 
> are known, because if not the uncertin things might cause people to 
> backaway from the API, people like to know what is comming ahead.
> I might be wrong but this is what i think.
>
> On Thursday, September 8, 2016 at 4:41:43 PM UTC+3, Thomas Broyer wrote:
>>
>>
>>
>> On Thursday, September 8, 2016 at 3:00:36 PM UTC+2, Ahmad Bawaneh wrote:
>>>
>>> Hi
>>> Is there any plans or suggestions for the UiBinder alternatives since 
>>> UiBinder will be removed from GWT 3.0?
>>>
>>
>> *might* be removed would be more accurate.
>>
>> Let me repeat one more time: development on GWT 3.0 has not started yet, 
>> not even discussions and preliminary plans (except that Google has been 
>> working on J2Cl and GWT 3.0 will be based on it, and that brings many 
>> changes to the way you'll develop); nobody knows yet what GWT 3.0 will or 
>> won't be (except that it won't have GWT.create() anymore: no more 
>> generators, no more deferred binding)
>> And again, there are reasons why GWT 2.x won't be discontinued as soon as 
>> GWT 3.x will be released.
>>
>> and i wonder why such cool feature should be removed instead of being 
>>> updated to match the new changes?
>>>
>>
>> It has to do with "resource driven" (or "non-java-source driven") code 
>> generation.
>> When code is generated based on Java code, it can be done with an 
>> annotation processor. But when code is generated based on a non-Java 
>> resource, "something" has to trigger the code generation whenever the 
>> resource changes; and in the case of UiBinder (and I18N's 
>> Constants/Messages, and ClientBundle), the code is generated based on 
>> *both* the ui.xml and the Java (so it needs to run as an annotation 
>> processor to easily get access to the Java model, but be triggered when the 
>> ui.xml changes –and the .java not).
>> It's only/mostly a "problem" of tooling (mostly during development). Far 
>> from being insurmontable though.
>>
>>
>>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.8.0-rc1 and closure compiler

[Slava Pankov]

IMO it was a bad idea to eliminate closure compiler from GWT, I've always 
used it and usually get 5-10% smaller output.
It's still possible to use, but "manually". I'm building with PRETTY 
option, then unzip war file, process all *.cache.js with closure compiler 
and put them back to war file.
Not sure it's stable though, still have no enough time to test 
it thoroughly.

On Thursday, August 4, 2016 at 9:33:54 AM UTC-7, Luis Fernando Planella 
Gonzalez wrote:
>
> Em quinta-feira, 4 de agosto de 2016 12:03:04 UTC-3, Thomas Broyer 
> escreveu:
>>
>>
>>
>> On Thursday, August 4, 2016 at 2:21:29 PM UTC+2, Luis Fernando Planella 
>> Gonzalez wrote:
>>>
>>> I've always used the closure compiler with past versions (even with 
>>> 2.8.0-beta1, which we have used in production already).
>>> Now, to my surprise, it is no longer supported in GWT 2.8.0-rc1, as 
>>> there's no mention to it in the release notes (
>>> http://www.gwtproject.org/release-notes.html).
>>>
>>
>> We may want to add a note about it; but that was an experimental feature 
>> and those tend to come and go as experiments prove their value or not.
>> See 
>> https://gwt.googlesource.com/gwt/+/162ccc9c9112a09bf9ea046da95760f5f1886b72%5E%21/
>>  
>> for the rationale.
>>
>
> Ok. In our project, we used to enable the closure compiler because the 
> codebase is quite large, and closure compiler helped in reducing further 
> the code size. I don't have the numbers at hand, but the full code size 
> (including all split points) is about 2.8M, and closure compiler reduced 
> some hundred kilobytes from it.
>  
>
>>  
>>
>>> Now the compiler no longer supports the old closure compiler option, but 
>>> has a new -X[no]closureFormattedOutput option.
>>>
>>
>> It's not really new actually: 
>> https://gwt.googlesource.com/gwt/+/6fa611cf9ad7ffa077a7378a100a7ccbd95e3cb3%5E%21/
>>
>
> I have assumed it was new because it is not present as option in the 
> gwt-maven-plugin (which is updated up to the beta1).
>
>  
>>
>>> I'm guessing closure compiler is no longer integrated in GWT, but it 
>>> still has the option to format for closure to a later (manual) usage of 
>>> closure compiler.
>>> I'm using the gwt-maven-plugin, which still uses beta1, but explicitly 
>>> changing its dependencies to 2.8.0-rc1 for gwt-user, gwt-dev and 
>>> gwt-codeserver artifacts, making it usable already for rc1.
>>> I can't, however, pass the new option (I think there's no way to pass 
>>> arbitrary compiler arguments with gwt-maven-plugin) until the maven plugin 
>>> is updated.
>>>
>>> What are the new instructions to keep using closure compiler?
>>>
>>
>> There aren't (see comment about -XclosureFormattedOutput in the commit 
>> message that introduced it)
>> Do you really *need* it?
>>
>
> I was assuming that flag was needed in order to generate code that 
> complies with the closure compiler limitations (
> https://developers.google.com/closure/compiler/docs/limitations).
> Maybe that is not the case and I can just invoke the closure compiler 
> manually on the generated GWT code? Should I expect any runtime problems by 
> doing this?
>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Dev mode issue after updating to rc1

[Slava Pankov]

If gwt-maven-plugin 2.8beta1 is used with gwt2.8rc1 - does this dependency 
override needed? Looks like it just works without it.

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: What is best IDE for developing GWT applications?

[Slava Pankov]

I don't know why many people are suggesting IntelliJ for GWT. For example 
code completion in ui.xml files is not working in IntelliJ, and I don't 
understand how to develop UI efficiently without it.

On Monday, February 29, 2016 at 2:56:06 PM UTC-8, Stefan Falk wrote:
>
> To be hones I never tried IntelliJ with GWT but maybe I'll give it a try 
> sometime :)
>
> Is there actually some development going on? Either for Eclipse of 
> IntelliJ or are projects like these frozen?
>
>
> On Monday, 29 February 2016 17:46:54 UTC+1, Rogelio Flores wrote:
>>
>> @Stefan
>> You have run configurations for GWT similar to eclipse (with the google 
>> plugin) but better IMO, with SDM as default and you can still run classic 
>> DevMode if you want.
>> You can rename @UiField variables and it will rename all instances in 
>> your Java file and also on your ui.xml file (or vice versa, if you rename 
>> the ui:field on your ui.xml).
>> IntelliJ also comes with a Chrome Browser plugin so your debugging can be 
>> done on the IDE from the javascript + sourcemaps running on your browser.
>> There's also code-completion, syntax highlighting on JSNI javascript code 
>> (not sure if eclipse now has this).
>> I've imported numerous GWT maven-based projects and they just work and 
>> run from IntelliJ as soon as I create a run config which takes a few 
>> seconds.
>>
>> These might not sound like super features or way too different from 
>> eclipse, but consider the fact that I didn't have to get/install any IDE 
>> plugins and even if I did I don't even remember because installing a plugin 
>> is a lot simpler too.
>>
>>
>> #gwtisback ;-)
>>
>> On Sunday, February 28, 2016 at 5:35:45 PM UTC-7, Stefan Falk wrote:
>>>
>>> Somebody has to do it! :P
>>>
>>> #gwtisback
>>>
>>> On Monday, 29 February 2016 01:19:36 UTC+1, Alain wrote:

 "And GWT is such an awesome technology I am simply no getting why it's 
 so underused.."

 Advertissement :)

 On 29 February 2016 at 01:02, Stefan Falk  wrote:

> Well, as for me I am willing to do almost *anything* just for the sake 
> of not having to write too many JavaScript lines :D
>
> And GWT is such an awesome technology I am simply no getting why it's 
> so underused..
>
>
> On Sunday, 28 February 2016 23:15:17 UTC+1, Ed wrote:
>>
>> @Stefan
>> Totally Agree there are some points of concern.
>>
>> I am so used to doing things the "hard" way that I am immune to the 
>> pitfalls.
>>
>> At the end of the day Eclipse give me what I need for my particular 
>> use case.
>>
>> I usually do not use the build in server and deploy to jetty/tomcat 
>> instances for testing.
>>
>> Best Regards,
>>
>> Ed
>>
>>
>> On Sun, Feb 28, 2016 at 12:21 PM, Stefan Falk  
>> wrote:
>>
>>> @Ed: Don't get me wrong. I like Eclipse and I am basically an 
>>> Eclipse-only developer. I would use it to brew coffee if there was a 
>>> plug 
>>> in. :D
>>>
>>> What I'm just missing are some basic support e.g. if I use GWTP I 
>>> want to see some generated code. Java/GWT has some boilerplate code 
>>> that 
>>> could be generated.
>>>
>>> Another thing that annoys me is that @UiField thing. Sometimes it's 
>>> really annoying to keep all the field names up-to-date. Renaming stuff 
>>> is 
>>> sometimes a but nasty.
>>>
>>> Then there's the thing with the code server.. I'd really appreciate 
>>> a better view for the error messages that one gets there. You always 
>>> have 
>>> to search for the actual line that points out what's wrong instead of 
>>> seeing that message in the Eclipse "Markers" view or something.
>>>
>>> One more thing that I miss is a better Project Explorer. The files 
>>> are sorted by type and that means you get A.java B.java A.ui.xml 
>>> B.ui.xml 
>>> instead of A.java A.ui.xml B.java B.ui.xml. 
>>>
>>> Since I am using gwt-maven-archetypes I even have to kill the Code 
>>> Server by hand - I cannot use the Eclipse "Debug" or "Server" view for 
>>> that. 
>>>
>>> Maybe some of that stuff could be avoided or changed but it's not 
>>> supported out of the box by Eclipse afaik.
>>>
>>>
>>> @Gilberto: Yes, that's actually a good point. The plugins can be 
>>> sometimes a bit messy. 
>>>
>>> @Rogelio: What kind of support are we talking here? It happens that 
>>> I might have access to the Ultimate edition for free as a student.
>>>
>>>
>>> On Saturday, 27 February 2016 22:54:35 UTC+1, Rogelio Flores wrote:

 I find IntelliJ to be superior to eclipse, not only in its out of 
 the box (for the Ultimate edition--not free) support for GWT, but for 
 almost everything else. I was too an eclipse user for many years so I 
 

Re: Any JSON library that works in both GWT and non-GWT environments?

[Slava Pankov]

If your server side is going to be implemented on Java, then just use Errai 
JAX-RS (it supports Jackson provider, so can be consumed from any client 
side language).
That way you have your domain classes in shared folder, and they are used 
both server and client side, so you don't have to serialize/deserialize 
them manually.

If you have something different on the server side, then choose from any of 
the following JSON libs: Piriti 
and https://github.com/hpehl/piriti/wiki/Comparison


On Thursday, February 4, 2016 at 2:22:29 PM UTC-8, Matt Campbell wrote:
>
> Hello: 
>
> I want to develop an application that shares code between the browser 
> (via GWT), ANdroid, and iOS (via JJ2ObjC), like Inbox. My application 
> will access JSON-based web APIs, so it needs to be able to parse and 
> serialize JSON. So does anyone know if there's a Java JSON library that 
> works in both GWT and non-GWT environments? I see that GWT has its own 
> JSON package, but that won't work for the other platforms. And a quick 
> look at Gson and Jackson shows that they depend a lot on reflection, 
> which GWT doesn't support. 
>
> Thanks, 
> Matt 
>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Developer Plugin does not work in Chrome

[Slava Pankov]

Use Firefox ESR 24.8.1 or Chromium 39 from Dart distribution (though 
Chromium is not very stable for me, dev mode plugin is hanging up often).
And try superdev mode with SDBG (if you are using Eclipse), it's not 
perfect, but quite usable.

On Friday, January 8, 2016 at 2:29:58 AM UTC-8, lefevr...@gmail.com wrote:
>
> I am attempting to build the 'StockWatcher' sample found at 
> http://www.gwtproject.org/doc/latest/tutorial/index.html
>
> No matter what I do, I keep getting the message '
> Development Mode requires the GWT Developer Plugin'
>
> Its installed and enabled.
>
> Any clue as to what is up?
>

-- 
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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.8 RC1

[Slava Pankov]

Is there any chance to include this fix into 2.8 RC1  
https://gwt-review.googlesource.com/#/c/12990/
This fix is tiny and simple, but prevents a lot of annoyance in my project.


On Wednesday, October 28, 2015 at 11:28:51 AM UTC-7, Goktug Gokdogan wrote:
>
>
>
> On Wed, Oct 28, 2015 at 8:25 AM, Thomas Broyer  > wrote:
>
>>
>>
>> On Wednesday, October 28, 2015 at 4:01:00 PM UTC+1, Jens wrote:
>>>
>>>
>>> The thing is, there's always a level of paranoia about GWT's impending 
 doom and apparent lack of activity shown in the gwt users group, and a 
 release coming at an unknown time helps to fuel that paranoia.

>>>
>>> Maybe we should post everything in 
>>> https://groups.google.com/a/gwtproject.org/forum/#!forum/gwt-reviews 
>>> also to the gwt users group to defeat that paranoia once and for all. You 
>>> would never run short on activity then ;-)
>>>
>>>
>>> That being said I think its fine to have RC builds even with that memory 
>>> issue to get people test the RC. But the final release of 2.8 should have a 
>>> fixed JDT to make sure everyone can use it. I am pretty sure there are 
>>> quite some people who simply can not increase their heap by 50-100%.
>>>
>>
>> Will those people switch to Java 8 at the same time they upgrade to GWT 
>> 2.8? I doubt it.
>> If (as I understand it) the leak only happens when using "-sourceLevel 
>> 8", then I'm fine with a 2.8.0 without waiting for the fix (but a big bold 
>> warning in the release notes), and a 2.8.1 as soon as the fix is available.
>>
>
> People will not be able to use '-sourceLevel 7" once the JRE patches for 
> java 8 starts getting submitted.
> So the idea was to default to -sourceLevel 8. This is ok because what 
> version GWT used to compile source doesn't effect their code so most people 
> wouldn't have noticed it (if there wasn't a memory issue).
>
>  
>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "GWT Contributors" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com 
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/9b8e5adf-6a64-4e4f-b44c-d649f6d5fb58%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/a4111a08-33b2-409d-a59c-022e5ca83c05%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: What is planned release date for GWT 2.8 (with lambdas) ?

[Slava Pankov]

@Jens
 Some days ago in IRC and proposed that GWT should do regular releases 
from the CI server that do not have -SNAPSHOT in their names and have a 
slightly different version number, e.g. major for breaking 
changes.timestamp. These CI releases could probably also be done after 
Google had tested the build against all their internal apps.

This proposal sounds like a good idea to me, it will probably work for my 
projects.

On Monday, August 17, 2015 at 6:54:46 AM UTC-7, Jens wrote:

 I think one issue is that Google builds their apps from GWT master branch. 
 They don't need release versions. That also means that the master branch is 
 stable and its fine to use it in production.

 The company I work for does the same. We have some custom GWT patches and 
 build or own GWT every one or two month based on the master branch. We 
 don't really had any problems with that approach.

 Some days ago in IRC and proposed that GWT should do regular releases from 
 the CI server that do not have -SNAPSHOT in their names and have a 
 slightly different version number, e.g. major for breaking 
 changes.timestamp. These CI releases could probably also be done after 
 Google had tested the build against all their internal apps. 
 That way a new release can be done every one or two month and the 
 enterprise guys are happy because no -SNAPSHOT dependency is in their 
 build file. Maybe that is an acceptable compromise between using SNAPSHOT 
 builds vs. a released version. At least it would more closely match how 
 Google works and Google is the main committer.

 Also some days ago Thomas Broyer said that they do a (roughly) monthly 
 steering group meeting but sometimes they don't release meeting minutes 
 because they contain confidential information (from one or more of the 
 companies in the meeting group). I proposed to just remove such information 
 because it is very likely not relevant to the community at all and then 
 regularly release the meeting minutes. 

 Maybe they pick up both points in the next steering group meeting.

 -- J.


-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Experience with GWT on Mobile

[Slava Pankov]

My applications are working perfectly fine on iOS and Android. But I'm not 
using GWT standard widgets. Instead I'm using jQuery Mobile ones, see 
https://github.com/jqm4gwt/jqm4gwt


On Thursday, August 6, 2015 at 6:34:08 AM UTC-7, nestorjb wrote:

 Hi

 I wanted to know if anyone had experience running GWT on mobile devices. 
 How compatible is the javascript generated with the iOS and Android 
 browsers?

 Regards,

 Nestor


-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Include a GSS file in another GSS file?

[Slava Pankov]

@provide and @require. See 
http://blog.arcbees.com/2015/04/28/managing-your-css-files-with-variables-and-a-theme/


On Friday, May 22, 2015 at 5:53:10 AM UTC-7, Ed wrote:

 How can I include a GSS file in another GSS file ?

 I have mixin and other gss variable declarations in a General.gss file, 
 that is included at many places.
 I want to split this file up in multiple files, but still include it in 
 General.gss, so it wont' break code and overcomes many fragmented @Imports.



-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

New release of jqm4gwt 1.4.6 is available.

[Slava Pankov]

New release of jqm4gwt 1.4.6 is available. It's advanced GWT wrapper over 
jQuery Mobile.
Source: https://github.com/jqm4gwt/jqm4gwt
Demos: http://jqm4gwt.appspot.com/

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT look and feel

[Slava Pankov]

http://jqm4gwt.appspot.com/examples.html
Try it, it's based on jQuery Mobile.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: HTTP Client API for GWT - Requestor (Announcement)

[Slava Pankov]

Sounds great! Thank you.

On Wednesday, January 7, 2015 12:31:19 PM UTC-8, Danilo Reinert wrote:

 Finally, a real HTTP Client API is available for the GWT ecosystem: 
 Requestor.
 It was released today (Jan 7th) under the version 0.1.0 but is being 
 developed for almost a year.
 The project has a great documentation and a showcase application.
 More features and improvements are already planned.
 The initial release is stable and ready for production.
 The community is invited to know and dig deep in the project.

 Following the release notes.


 Requestor - Requesting made easy for GWT

 Requesting is the most common operation in AJAX applications. 
 GWT is an excellent platform for developing AJAX applications, but it 
 still bother us when it comes to requesting.
 Using RequestBuilder, the default GWT way of requesting, is a low-level 
 approach which requires too many steps and manual processing to achieve 
 meaningful data for our application.
 Requestor solves theses issues with a full featured and fluent API for 
 requesting. 
 A real HTTP Client API for GWT, it is made upon modern programming 
 concepts like Promises and Method Chaining, and is designed to be as 
 extensible as possible.
 Carefully crafted, Requestor provides many features while allows the easy 
 configuration and customization of them all.


 Features

 * Promises (integrate any promise library)
 * Fluent API
 * Full support to Form requests (urlencoded or multipart)
 * Full support to raw binary data (File, Blob, ArrayBuffer, Json, Document)
 * Progress monitoring of uploads and downloads
 * BASIC and CORS authentication
 * Support for implementing any custom authentication
 * Nice header manipulation
 * Uri Building
 * Filters (enhance requests and responses)
 * Interceptors (transform payloads)
 * Auto JSON serialization for POJOs, JavaBean Interfaces and Overlay types
 * Integrated to the AutoBean Framework
 * Integrated to gwt-jackson
 * Integrated to TurboGWT
 * Handle multiple serialization of the same java type for different media 
 types
 * Customizable request dispatching (support for caching and 
 synchronization)


 Links

 Repo: https://github.com/reinert/requestor
 Site: http://reinert.io/requestor/latest
 Wiki: https://github.com/reinert/requestor/wiki
 Group: https://groups.google.com/forum/#!forum/requestor
 Showcase: http://reinert.io/requestor/latest/examples/showcase



-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Development Mode will not be supported in Firefox 27+

[Slava Pankov]

Just tiny update. Dev mode is still working just fine on Windows with 
Chromium 38.0.2125.0 (292384) from Dart 1.8.3 distribution.

On Monday, February 3, 2014 4:01:41 PM UTC-8, Brian Slesinsky wrote:

 Mozilla has stopped exporting some C++ symbols that the Firefox plugin 
 relies on [1]. Therefore it's not possible to support Development Mode in 
 any new versions of Firefox starting with 27.

 As a workaround, I am doing one last release to get the plugin working 
 again with Firefox 24.2 (and hopefully newer point releases on the ESR 
 track). If you wish to continue to use Development Mode on Firefox, you 
 will need to download this version from Mozilla [2]. For more details see 
 the issue tracker [3]. 

 Long-term, the plan is to improve Super Dev Mode.

 I apologize for the late notice; when I said at GWT.create that Firefox 
 could stop working with any release, I didn't expect it to be the next one.

 - Brian

 [1] https://bugzilla.mozilla.org/show_bug.cgi?id=920731
 [2] 
 http://download.cdn.mozilla.net/pub/mozilla.org/firefox/releases/24.2.0esr/
 [3] https://code.google.com/p/google-web-toolkit/issues/detail?id=8553



-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

jqm4gwt 1.4.5 released

[Slava Pankov]

 
New version of jqm4gwt 1.4.5 is released. It's advanced wrapper over jQuery 
Mobile framework. 

Source: https://github.com/jqm4gwt/jqm4gwt

Demo is here: http://jqm4gwt.appspot.com/

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: add mobile version to existing GWT app?

[Slava Pankov]

 Ok, but how can you do REST/JSON with a GWT application?

For me RestEasy + Errai JAX-RS is working perfectly fine.

On Wednesday, December 3, 2014 10:16:23 AM UTC-8, Magnus wrote:

 Hi!

 If I'd start the project today, I'd just use plain REST / JSON for both 
 the desktop and mobile versions.


  Ok, but how can you do REST/JSON with a GWT application?
 Would you replace the RPC calls with REST requests, using a servlet or 
 what?

 Thanks
 Magnus


-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.7 and GSS

[Slava Pankov]

Thanks, issue is opened: 
https://code.google.com/p/google-web-toolkit/issues/detail?id=9022


On Wednesday, November 26, 2014 4:37:54 AM UTC-8, Julien Dramaix wrote:

 Ok you try to access the value of the constant via a method of your 
 cssResource interface. Yes unfortunately there is bug there and the 
 generator escape the content of the constant. Please open an issue (
 https://code.google.com/p/google-web-toolkit/issues/entry) for that and I 
 will fix it.

 Otherwise, if you use the constant in your css, it works as expected:

 @def CONTENT_HEADER literal(\27A1);

 .header:before {
content: CONTENT_HEADER;
 }


 On Tue Nov 25 2014 at 11:56:49 PM Slava Pankov pan...@gmail.com 
 javascript: wrote:

 :-) That's exactly what I did, but it's not working. In Java code I'm 
 getting it exactly as String with value \27a1 (length == 5).


 On Tuesday, November 25, 2014 1:07:56 PM UTC-8, Julien Dramaix wrote:

 A space is missing in my previous post:

 @def CONTENT_HEADER \27A1;

 On Tue Nov 25 2014 at 10:07:49 PM Julien Dramaix julien@gmail.com 
 wrote:

 literal method is not needed anymore (and is not supported by GSS).

 Just try:

 @def CONTENT_HEADER\27A1;

 And yes for syntax highlighting, you need to add .gss as extension of 
 css file.

 On Tue Nov 25 2014 at 10:03:35 PM Slava Pankov pan...@gmail.com 
 wrote:

 OK, one of my issues is resolved, so answering to myself :-) For *.gss 
 highlighting in Eclipse see attached screenshot.

 But still no luck with unicode symbol in @def.



 On Monday, November 24, 2014 8:50:10 PM UTC-8, Slava Pankov wrote:

 Another problem: 
 @def CONTENT_HEADER literal(\27A1);
 It was unicode character constant before gss, now I'm getting string 
 literal(\27A1) instead of unicode symbol.

 On Monday, November 24, 2014 7:26:20 PM UTC-8, Slava Pankov wrote:

 What about syntax highlighting for *.gss files in Eclipse? *.css 
 where supported by GPE CSS Resource Editor, but it does NOT support 
 *.gss 

  -- 
 You received this message because you are subscribed to a topic in the 
 Google Groups Google Web Toolkit group.
 To unsubscribe from this topic, visit https://groups.google.com/d/to
 pic/google-web-toolkit/hpb1sz9CPsM/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 google-web-toolkit+unsubscr...@googlegroups.com.

 To post to this group, send email to google-we...@googlegroups.com.


 Visit this group at http://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/d/optout.

  -- 
 You received this message because you are subscribed to a topic in the 
 Google Groups Google Web Toolkit group.
 To unsubscribe from this topic, visit https://groups.google.com/d/
 topic/google-web-toolkit/hpb1sz9CPsM/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 google-web-toolkit+unsubscr...@googlegroups.com javascript:.
 To post to this group, send email to google-we...@googlegroups.com 
 javascript:.
 Visit this group at http://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/d/optout.



-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.7 and GSS

[Slava Pankov]

Also I've added comment about unicode symbols higher than U+ to 
issue#9022


On Wednesday, November 26, 2014 11:54:20 AM UTC-8, Slava Pankov wrote:

 Thanks, issue is opened: 
 https://code.google.com/p/google-web-toolkit/issues/detail?id=9022


 On Wednesday, November 26, 2014 4:37:54 AM UTC-8, Julien Dramaix wrote:

 Ok you try to access the value of the constant via a method of your 
 cssResource interface. Yes unfortunately there is bug there and the 
 generator escape the content of the constant. Please open an issue (
 https://code.google.com/p/google-web-toolkit/issues/entry) for that and 
 I will fix it.

 Otherwise, if you use the constant in your css, it works as expected:

 @def CONTENT_HEADER literal(\27A1);

 .header:before {
content: CONTENT_HEADER;
 }


 On Tue Nov 25 2014 at 11:56:49 PM Slava Pankov pan...@gmail.com wrote:

 :-) That's exactly what I did, but it's not working. In Java code I'm 
 getting it exactly as String with value \27a1 (length == 5).


 On Tuesday, November 25, 2014 1:07:56 PM UTC-8, Julien Dramaix wrote:

 A space is missing in my previous post:

 @def CONTENT_HEADER \27A1;

 On Tue Nov 25 2014 at 10:07:49 PM Julien Dramaix julien@gmail.com 
 wrote:

 literal method is not needed anymore (and is not supported by GSS).

 Just try:

 @def CONTENT_HEADER\27A1;

 And yes for syntax highlighting, you need to add .gss as extension of 
 css file.

 On Tue Nov 25 2014 at 10:03:35 PM Slava Pankov pan...@gmail.com 
 wrote:

 OK, one of my issues is resolved, so answering to myself :-) For *.gss 
 highlighting in Eclipse see attached screenshot.

 But still no luck with unicode symbol in @def.



 On Monday, November 24, 2014 8:50:10 PM UTC-8, Slava Pankov wrote:

 Another problem: 
 @def CONTENT_HEADER literal(\27A1);
 It was unicode character constant before gss, now I'm getting string 
 literal(\27A1) instead of unicode symbol.

 On Monday, November 24, 2014 7:26:20 PM UTC-8, Slava Pankov wrote:

 What about syntax highlighting for *.gss files in Eclipse? *.css 
 where supported by GPE CSS Resource Editor, but it does NOT support 
 *.gss 

  -- 
 You received this message because you are subscribed to a topic in 
 the Google Groups Google Web Toolkit group.
 To unsubscribe from this topic, visit https://groups.google.com/d/to
 pic/google-web-toolkit/hpb1sz9CPsM/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 google-web-toolkit+unsubscr...@googlegroups.com.

 To post to this group, send email to google-we...@googlegroups.com.


 Visit this group at http://groups.google.com/group/google-web-toolkit
 .
 For more options, visit https://groups.google.com/d/optout.

  -- 
 You received this message because you are subscribed to a topic in the 
 Google Groups Google Web Toolkit group.
 To unsubscribe from this topic, visit https://groups.google.com/d/
 topic/google-web-toolkit/hpb1sz9CPsM/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 google-web-toolkit+unsubscr...@googlegroups.com.
 To post to this group, send email to google-we...@googlegroups.com.
 Visit this group at http://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/d/optout.



-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.7 and GSS

[Slava Pankov]

OK, one of my issues is resolved, so answering to myself :-) For *.gss 
highlighting in Eclipse see attached screenshot.

But still no luck with unicode symbol in @def.


On Monday, November 24, 2014 8:50:10 PM UTC-8, Slava Pankov wrote:

 Another problem: 
 @def CONTENT_HEADER literal(\27A1);
 It was unicode character constant before gss, now I'm getting string 
 literal(\27A1) instead of unicode symbol.

 On Monday, November 24, 2014 7:26:20 PM UTC-8, Slava Pankov wrote:

 What about syntax highlighting for *.gss files in Eclipse? *.css where 
 supported by GPE CSS Resource Editor, but it does NOT support *.gss 



-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT dev plugin stopped working on Chrome 39

[Slava Pankov]

SuperDevMode debugging is not so convenient as DevMode, but with SDBG 
https://github.com/sdbg/sdbg it's almost OK for me. 
Also with new GPE it's very easy to switch between SuperDevMode and DevMode 
debugging, so I use both of them now.

On Tuesday, November 25, 2014 5:49:40 AM UTC-8, jonl wrote:

 Search Portable Chrome, make sure it's the 32 bit version.

 Since its another year away, I wonder what the possibility of getting one 
 more build of the browser DevMode plugin?  Maybe plug some memory leaks and 
 recompile it so it will work with 64 bit Chrome, where possible?

 On Tuesday, November 25, 2014 3:21:28 AM UTC-7, Igor Zubchenok wrote:

 Thank you Jens, this make a sense!

 SuperDevMode has ugly debugging. Unforutnately...
 Do you know where Chrome 38 OSX can be downloaded?

 Chrome is now 64 bit on OS X and the plugin is only 32 bit.

 So you have to use a different/older browser or use SuperDevMode.



-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.7 and GSS

[Slava Pankov]

:-) That's exactly what I did, but it's not working. In Java code I'm 
getting it exactly as String with value \27a1 (length == 5).

On Tuesday, November 25, 2014 1:07:56 PM UTC-8, Julien Dramaix wrote:

 A space is missing in my previous post:

 @def CONTENT_HEADER \27A1;

 On Tue Nov 25 2014 at 10:07:49 PM Julien Dramaix julien@gmail.com 
 javascript: wrote:

 literal method is not needed anymore (and is not supported by GSS).

 Just try:

 @def CONTENT_HEADER\27A1;

 And yes for syntax highlighting, you need to add .gss as extension of css 
 file.

 On Tue Nov 25 2014 at 10:03:35 PM Slava Pankov pan...@gmail.com 
 javascript: wrote:

 OK, one of my issues is resolved, so answering to myself :-) For *.gss 
 highlighting in Eclipse see attached screenshot.

 But still no luck with unicode symbol in @def.



 On Monday, November 24, 2014 8:50:10 PM UTC-8, Slava Pankov wrote:

 Another problem: 
 @def CONTENT_HEADER literal(\27A1);
 It was unicode character constant before gss, now I'm getting string 
 literal(\27A1) instead of unicode symbol.

 On Monday, November 24, 2014 7:26:20 PM UTC-8, Slava Pankov wrote:

 What about syntax highlighting for *.gss files in Eclipse? *.css where 
 supported by GPE CSS Resource Editor, but it does NOT support *.gss 

  -- 
 You received this message because you are subscribed to a topic in the 
 Google Groups Google Web Toolkit group.
 To unsubscribe from this topic, visit https://groups.google.com/d/
 topic/google-web-toolkit/hpb1sz9CPsM/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 google-web-toolkit+unsubscr...@googlegroups.com javascript:.
 To post to this group, send email to google-we...@googlegroups.com 
 javascript:.
 Visit this group at http://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/d/optout.



-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.7 and GSS

[Slava Pankov]

What about syntax highlighting for *.gss files in Eclipse? *.css where 
supported by GPE CSS Resource Editor, but it does NOT support *.gss 

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.7 and GSS

[Slava Pankov]

Another problem: 
@def CONTENT_HEADER literal(\27A1);
It was unicode character constant before gss, now I'm getting string 
literal(\27A1) instead of unicode symbol.

On Monday, November 24, 2014 7:26:20 PM UTC-8, Slava Pankov wrote:

 What about syntax highlighting for *.gss files in Eclipse? *.css where 
 supported by GPE CSS Resource Editor, but it does NOT support *.gss 


-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Customer specific locales

[Slava Pankov]

Yes, you have to. I'm using customer specific locales, and third part is 
5-8 chars.

On Friday, August 15, 2014 5:25:10 AM UTC-7, Developer wrote:

 Some of our customers want some special labels for some of our GUI 
 elements. Therefore I would like to define some customer specific locales 
 in order to use customer specific Resources.
 I tried to define the locale de_DE_ABC, but GWT tells me that the locale 
 format is not valid as the extension bit (ABC) has to be 5 to 8 characters 
 according to the BCP47 standard. Do I really have to use locales with 
 variants consisting of 5 to 8 chars or am I doing something complete wrong?


-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

New version 1.4.3 of jqm4gwt is available, check it out.

[Slava Pankov]

 
New version 1.4.3 of jqm4gwt is available. It's extended wrapper over 
jQuery Mobile.
In some sense it's alternative for mgwt, and could be used for 
Tablet/Mobile development in pure Java.
Demos http://jqm4gwt.appspot.com/  and source code 
https://github.com/jqm4gwt/jqm4gwt

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: unable to use external javascript in GWT

[Slava Pankov]

public folder should be on the same level as gwt.xml file. superdev mode 
doesn't allow usage of script in gwt.xml, you have to include it in your 
application html file (it will be copied from public folder to target). You 
still can inject your scripts in onModuleLoad() of your library, but it's 
quite tricky.

On Wednesday, July 30, 2014 2:20:06 AM UTC-7, Sandeep Poonia wrote:

 Thanks Jim and Thomas, $wnd worked for me. But i am facing problem when i 
 changed the location of the go.js , I moved it to the folder where gwt.xml 
 file is present using  script src=go.js/ but i am getting the following 
 message. 

 14:40:05.077 [ERROR] [opsdashboardlocal] The Cross-Site-Iframe linker does 
 not support script tags in the gwt.xml files, but the gwt.xml file (or 
 the gwt.xml files which it includes) contains the following script tags: 
 go.js
 In order for your application to run correctly, you will need to include 
 these tags in your host page directly. In order to avoid this error, you 
 will need to remove the script tags from the gwt.xml file, or add this 
 property to the gwt.xml file: set-configuration-property 
 name='xsiframe.failIfScriptTag' value='FALSE'/

 And I am also confused about public folder. Should i create a public 
 folder under my project or under src dir? 

 On Monday, July 28, 2014 2:43:47 AM UTC+5:30, Thomas Broyer wrote:



 On Sunday, July 27, 2014 10:11:22 AM UTC+2, Sandeep Poonia wrote:

 Hi ,
 I want to use goJS with GWT. I downloaded GOJS javascript and put it in 
 the sampleproject folder under war where sampleproject.nocache.js 
 and sampleproject.devmode.js is present. In sampleproject*.html i 
 added *
 script type=text/javascript language=javascript 
 src=sampleproject/go.js/script


 You shouldn't put the file there. The sampleproject/ folder will be 
 cleared by the GWT Compiler.
 Either put your script in your public path so it gets copied there by 
 the GWT Compiler [1], or put it outside the sampleproject/ folder.
  
 [1] see 
 http://www.gwtproject.org/doc/latest/DevGuideOrganizingProjects.html

 In one of the view i used 
 public static native void initGo() /*-{
 var $$ = go.GraphObject.make;
 }-*/;
 when i call this function , exception is thrown:

 com.google.gwt.event.shared.UmbrellaException: Exception caught: 
 (ReferenceError) @com.amazon.ops.client.OpsMenuView::initGo()([]): go is 
 not defined.

 Can anyone please help me with this?


 As Jim already said, you need to use $wnd to escape the sandbox GWT is 
 running in and into the context of the web page, where your script is 
 loaded.
 See http://www.gwtproject.org/doc/latest/DevGuideCodingBasicsJSNI.html 



-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Development Mode will not be supported in Firefox 27+

[Slava Pankov]

Also on Windows it's still possible to use Chrome 36 with devmode. Download 
Dart (I'm using 1.5.3 distribution), and use Chromium from there (it's 
portable, just copy it to any folder). Also you need 
GWT-Developer-Plugin_v1.0.11357.crx of course, see previous post.

On Friday, July 11, 2014 3:35:24 PM UTC-7, Alex Epshteyn wrote:

 As of now, quite sadly, the GWT plugin is no longer supported in the 
 latest of versions of Firefox nor Chrome (starting with 35). I've been 
 using GWT since 2006, and I think it's a sad state of affairs that after so 
 much work went into GWT's OOPHM (a.k.a Development Mode), we're back to 
 Internet Explorer being the only browser that can be used for GWT debugging 
 on Windows.  I think that SuperDevMode goes against the original do 
 everything from your IDE spirit of GWT, but I digress...

 The main reason I'm posting this is to describe my workaround to save some 
 time for anyone who still wants to use dev mode under Chrome and Firefox 
 (which I'm guessing is the majority of the people here):

 The hack I came up with (for Windows) was to install portable versions 
 of Chromium and Firefox.

 Portable Firefox 24: 
 http://portableapps.com/apps/internet/firefox-portable-esr
 Portable Chromium 35: http://crportable.sourceforge.net/

 Then you need to manually install the GWT plugin into Chromium, since it's 
 now disabled on the Chrome Web Store:
 1. download the file GWT-Developer-Plugin_v1.0.11357.crx from 
 http://chrome-extension-downloader.com/ (entering ID number 
 jpjpnpmbddbjkfaccnmhnkdgjideieim into the search field)
 2. drag and drop the downloaded file into the chrome://extensions/ tab to 
 install the plugin

 The good thing about this Chromium build is that it seems to be immune 
 from Google's auto-updater, but for a limited time, you can also still get 
 Google Chrome 35 Portable at 
 http://portableapps.com/apps/internet/google_chrome_portable, and follow 
 the same procedure for manually installing the GWT plugin.

 I'm hoping that this hack will allow many of us to keep using the old dev 
 mode for a long time to come, and I'm also hoping that the GWT project 
 members will not abandon dev mode support.  

 Question for GWT project members: I understand that both FF and Chrome are 
 getting rid of the NSAPI, which enabled the GWT plugin.  Are there really 
 no other ways to keep supporting dev mode on the latest versions of those 
 browsers?  Has anyone looked into Native Client (
 https://developer.chrome.com/native-client)?

 Best,
 Alex


-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Using GWT for mobile and tablet apps?

[Slava Pankov]

I'm using jqm4gwt for mobile development, see 
https://github.com/jqm4gwt/jqm4gwt
It's wrapper over jQuery Mobile, but you can write Java only code of course.
This week I'm planning to release new version based on the latest JQM 1.4.3

On Monday, July 14, 2014 7:09:26 AM UTC-7, dhoffer wrote:

 I'm inquiring what's the current status of GWT's support for mobile 
 devices, phones and tablets.  I have a use case that has to run on mobile 
 devices and I'm wondering if I can use GWT for this.  Is mgwt the way to go 
 here?  What are the best options for GWT and mobile and how viable is this?


-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT distributed builds

[Slava Pankov]

Use collapse-all-properties / in your gwt.xml when making development 
builds. Or use superdev mode.

On Wednesday, July 9, 2014 1:56:54 PM UTC-7, Jens wrote:

 Well, we fully rebuild our application because it's quite big, and is 
 developed more or less actively. So if we have enough resources (and we do 
 have them), we can build it in parallel and the question is, does anybody 
 has success story?


 Not sure what kind of a story you want to hear? If you have 23 
 permutations and 23 hosts available then its like just compiling one 
 permutation + some overhead because of data distribution and fetching.
 But during development nearly everybody works with a single permutation 
 only. Full builds are most likely done on a CI server as a nightly job or 
 when you do a release.

 The wiki page gives you all the information you need to distribute the GWT 
 compilation. How you design your distributed build environment is up to 
 you. Could be as easy as a set of shell scripts + scp + ssh remote script 
 execution.

 There are some projects building on top of what GWT provides but I don't 
 know how well they work. You will easily find them using google search. 

 -- J.


-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Best approach from consuming REST(Jetty) webservice

[Slava Pankov]

Or use Errai JAX-RS https://docs.jboss.org/author/display/ERRAI/Errai+JAX-RS

On Tuesday, July 8, 2014 7:12:06 AM UTC-7, Thomas Broyer wrote:



 On Tuesday, July 8, 2014 10:11:11 AM UTC+2, Santhosh Thadaka wrote:

 I have my backend with EJB and REST webservice and I want to consume the 
 REST service with GWT as a front end can any one suggest with which is the 
 best approach 

 RPC
 RequestFactory
 RequestBuilder

 and I am not allowed to use any external api's. Please let me know what 
 all should be taken care.


 GWT-RPC is an RPC protocol and API, and RequestFactory is a protocol too.

 If you want to consume REST services, you'll have to use either 
 RequestBuilder or XMLHttpRequest (the former wraps the latter).
 If the data you exchange is JSON, then you can either use JsonUtils and 
 overlay types (unfortunately only works for parsing for now –stringify is 
 being added as I write–, but you can defer to JSONObject for 
 serialization), JSONParser and friends, or AutoBeans.
  


-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Developer Plugin

[Slava Pankov]

Firefox ESR 24.6 has portable version, so you can use it specifically for 
devmode http://portableapps.com/apps/internet/firefox-portable-esr

On Monday, July 7, 2014 9:19:26 AM UTC-7, Rade Martinović wrote:

 AFAIK is internet slang for As Far As I Know :)

 -- Rade

 On Thursday, July 3, 2014 4:15:23 PM UTC+2, Francesco Viscomi wrote:

 What do you mean, can please be more accurate?
 SuperDevMode is another plugin with the same functionality? 
 AFAIK what is that and where i can find it?

 thanks really a lot


 2014-07-03 15:18 GMT+02:00 manstis michael...@gmail.com:

 Or use SuperDevMode

 Support for DevMode browser plugins is, AFAIK, coming to an end...

 On Wednesday, 2 July 2014 16:18:37 UTC+1, Francesco Viscomi wrote:

 Hi all

 i need to use GWT Developer Plugin and I have windows 8 at 64bit

 either chrome and firefox i'm not able to use the plugin;

 when i try to download it i get:

 (firefox)
 Sorry, the GWT Developer Plugin only supports Firefox 3.0 - 26.0.
 Perhaps download Firefox 24 
 http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/24.3.0esr/?

 (chrome)
 start to download but a pop up inform me that the installation has been 
 disabled because it is necessary plugin NPAPI;

 how i can resolve this issue? thanks a lot
 Francesco

  -- 
 You received this message because you are subscribed to a topic in the 
 Google Groups Google Web Toolkit group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/google-web-toolkit/t1N2wpHjD54/unsubscribe
 .
 To unsubscribe from this group and all its topics, send an email to 
 google-web-toolkit+unsubscr...@googlegroups.com.
 To post to this group, send email to google-we...@googlegroups.com.
 Visit this group at http://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/d/optout.




 -- 
 Ing. Viscomi Francesco 



-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Best server communication

[Slava Pankov]

Try Errai JAX-RS, it works perfectly for my development.

On Saturday, June 21, 2014 10:50:19 AM UTC-7, mamadou lakhassane cisse 
wrote:

 Hi people I'm a newbie in GWT. I've made some apps but still using RPC. I 
 was wondering now if there were a better way than that for server 
 communication. Thanks in advance.


-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT ways to speedup UI development

[Slava Pankov]

Once again. If data bindings are used, i.e. clear separation between view 
and model/viewModel, then complex validation scenarios are quite easy to 
implement and support.

On Monday, May 26, 2014 2:17:19 AM UTC-7, Mariusz Lewandowski wrote:

 Thank you all for the hints! I definitely go into the Errai documentation 
 and find out more!

 Actually, the idea of GWT composite widget and using is as a reusable 
 widget in ui.xml is well known to me.

 I am looking for some ways to fasten the development, for instance maybe 
 there is some tool to handle complex validation scenario and generate code?
 By the way, how do you handle validation in GWT - not the simple one, but 
 complex, tough scenarios?

 Making UI in GWT is always a big pain due to time.. 


 W dniu sobota, 24 maja 2014 02:45:29 UTC+2 użytkownik Slava Pankov napisał:

 For me combination of UiBinder templates and Errai data bindings works 
 perfectly fine.
 With UiBinder you can create reusable blocks/frames/components (I cannot 
 find a proper description), i.e. for example FlowPanel with some different 
 widgets can be considered as whole UI block. Then in other UiBinder 
 templates just reuse this block as composite widget.

 On Friday, May 23, 2014 8:03:41 AM UTC-7, Mariusz Lewandowski wrote:

 Hello guys,

 I am doing intensive research for the question How to speedup forms 
 development in GWT?. The figures shows itself, that most time consuming 
 tasks are those related to UI building. 
 I have a lot of form components (fields, listbox, textbox, calendards, 
 etc.) and some custom validation framework.
 Once a time there is a not standard business requirement to provide some 
 specific behavior in component, it could be field dependency (visibility or 
 validation dependencies).
 Moreover, all logic is compacted in one library used by many application 
 so I must be careful with changes due to the fact, that business requires 
 just change in aplication X leaving Y,Z and V untouched.

 I tried:
 - GWT plugin for Eclipse, but without luck
 - Some XForms standard to include in GWT project, but without luck.

 Have you got some standard in UI development? Or some usefull tools, 
 procedures?
 I am still suffering from consuming UI dev including not only GWT, but 
 also CSS, UI.XML etc.

 I am looking forward for asnwer, Cheers.



-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT ways to speedup UI development

[Slava Pankov]

For me combination of UiBinder templates and Errai data bindings works 
perfectly fine.
With UiBinder you can create reusable blocks/frames/components (I cannot 
find a proper description), i.e. for example FlowPanel with some different 
widgets can be considered as whole UI block. Then in other UiBinder 
templates just reuse this block as composite widget.

On Friday, May 23, 2014 8:03:41 AM UTC-7, Mariusz Lewandowski wrote:

 Hello guys,

 I am doing intensive research for the question How to speedup forms 
 development in GWT?. The figures shows itself, that most time consuming 
 tasks are those related to UI building. 
 I have a lot of form components (fields, listbox, textbox, calendards, 
 etc.) and some custom validation framework.
 Once a time there is a not standard business requirement to provide some 
 specific behavior in component, it could be field dependency (visibility or 
 validation dependencies).
 Moreover, all logic is compacted in one library used by many application 
 so I must be careful with changes due to the fact, that business requires 
 just change in aplication X leaving Y,Z and V untouched.

 I tried:
 - GWT plugin for Eclipse, but without luck
 - Some XForms standard to include in GWT project, but without luck.

 Have you got some standard in UI development? Or some usefull tools, 
 procedures?
 I am still suffering from consuming UI dev including not only GWT, but 
 also CSS, UI.XML etc.

 I am looking forward for asnwer, Cheers.


-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: How to access a web page in Frame

[Slava Pankov]

I've used native method to get frame content, and it's working just fine in 
case it's from the same domain.

private native String getFrameContent(Element frame) /*-{
return $wnd.$(frame).contents().find(html).html();
}-*/;

On Tuesday, April 1, 2014 8:47:37 PM UTC-7, Leon wrote:

 I used a proxy servlet so the url for Frame is the same origin (same 
 scheme, host, and port) as widget. But Document.getElementsByTagName(div) 
 still returns an empty NodeList.

 Please help!

 Leon

 On Tuesday, April 1, 2014 3:29:43 AM UTC-4, Slava Pankov wrote:

 Perhaps you have cross domain problem. Is URL in your iframe from the 
 same domain as main application? If not you need something like proxy 
 servlet to simulate you getting data from your server side.

 On Monday, March 31, 2014 7:23:17 PM UTC-7, Leon wrote:


 com.google.gwt.dom.client.Document.getElementsByTagName(body) returns 
 one Node. I can cast it into Element and do some style changes in Java 
 code. Any style changes in Java code is not reflected in html code that is 
 confirmed by Firebug. 


 com.google.gwt.dom.client.Document.getElementsByTagName(div) still 
 returns an empty NodeList.




 On Monday, March 31, 2014 9:26:31 PM UTC-4, Leon wrote:

 I don't know why 
 com.google.gwt.dom.client.Document.getElementsByTagName(div) returns 
 an empty NodeList.

 Is there a solution how to get a element in terms of tag name?

 Leon


 On Monday, March 31, 2014 5:59:47 AM UTC-4, Jens wrote:

 Document iframeDoc = ((IFrameElement) 
 frame.getElement()).getContentDocument();

 If you need that more often then you should probably extend GWTs Frame 
 class and make a public method to access the content document.

 Keep in mind that you should wait until the frame is loaded using 
 frame.addLoadHandler().

 -- J.



-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Development Mode will not be supported in Firefox 27+

[Slava Pankov]

DevMode is working just fine in Firefox 26 (not 24). And probably will work 
till Firefox ESR becomes 27 (it's only 24.4 now). So there is a time frame 
for normally working DevMode at least till the end of 2014. I hope SDM will 
be much better then. 
What I'm concerned about that GWT team don't broke DevMode in 2.7 and 3.0 
releases. Also it would be really nice to ask Mozilla team return back 
needed functionality for DevMode (but allow/enable it only if you run 
Firefox with specific command line parameters). I think it's completely 
possible to talk to them and explain the situation, nobody benefits from 
the situation, when GWT developers are refusing/disabling Firefox updates 
after 26 version.


-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: How to access a web page in Frame

[Slava Pankov]

Perhaps you have cross domain problem. Is URL in your iframe from the same 
domain as main application? If not you need something like proxy servlet to 
simulate you getting data from your server side.

On Monday, March 31, 2014 7:23:17 PM UTC-7, Leon wrote:


 com.google.gwt.dom.client.Document.getElementsByTagName(body) returns 
 one Node. I can cast it into Element and do some style changes in Java 
 code. Any style changes in Java code is not reflected in html code that is 
 confirmed by Firebug. 


 com.google.gwt.dom.client.Document.getElementsByTagName(div) still 
 returns an empty NodeList.




 On Monday, March 31, 2014 9:26:31 PM UTC-4, Leon wrote:

 I don't know why 
 com.google.gwt.dom.client.Document.getElementsByTagName(div) returns 
 an empty NodeList.

 Is there a solution how to get a element in terms of tag name?

 Leon


 On Monday, March 31, 2014 5:59:47 AM UTC-4, Jens wrote:

 Document iframeDoc = ((IFrameElement) 
 frame.getElement()).getContentDocument();

 If you need that more often then you should probably extend GWTs Frame 
 class and make a public method to access the content document.

 Keep in mind that you should wait until the frame is loaded using 
 frame.addLoadHandler().

 -- J.



-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Is there any chance to fix this issue in upcoming 2.6.1?

[Slava Pankov]

I've found nasty bug when using ui:import in UiBinder template. 
Looks like the solution is very simple/tiny change in UiBinderParser.java, 
is it possible to include it to upcoming GWT 2.6.1?

http://code.google.com/p/google-web-toolkit/issues/detail?id=8641


-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.