Re: Any progress with GWT 2.8.0
For more information read the comments https://plus.google.com/104553077953666769660/posts/jHS1YnkR1sM El miércoles, 23 de marzo de 2016, 19:43:40 (UTC+1), steve Zara escribió: > > It's approaching the end of March 2016. The last steering group meeting > was 10th February. So any sign of a release date for GWT 2.8.0? By > 'release' I mean that when I click on the 'Download' button on the GWT > site, I get 'gwt-2.8.0.zip' as against 'gwt-2.7.0.zip'. At that point, I > will be able to use GWT 2.8.0 for substantial commercial projects that need > rigorous justifications for the technologies used. I don't want to have to > start such new projects without the language features of 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: Is there a plan to compile GWT to ECMAScript 6
GWT team is working in J2CL https://groups.google.com/forum/#!topic/google-web-toolkit/-uQICwZUOA0 https://groups.google.com/forum/#!topic/google-web-toolkit-contributors/1t6x_Zg1E8I https://drive.google.com/file/d/0BwVGJUurq6uVa2tpaTRLSzlBMDQ/view El jueves, 3 de marzo de 2016, 3:41:54 (UTC+1), Gourab escribió: > > Hi All, > > Wanted to know if there is a plan for GWT to compile into ES6. > > If not, will there be a situation when browser's deprecate Javascript and > only supports ES6 and there is no way to migrate your application ? May be > 10 years down the line ? > > > Regards > Gourab. > -- 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: Teavm
Source maps from byte code? El martes, 1 de diciembre de 2015, 16:43:44 (UTC+1), Satguru Srivastava escribió: > > So, I recently came across TeaVM (http://teavm.org/) > Similar to GWT but unlike GWT, which compiles Java Source Code to > JavaScript, TeaVM compiles Java Byte Code to JavaScript. > It is an interesting approach. > The big advantage to this approach is that you do not have to create and > maintain your own compiler. > You ride on the back of the JavaC compiler and can take advantage of the > optimizations, latest changes and updates made to the compiler. > So while GWT is working on supporting Java 8 , TeaVM already provides > support for that. > > What do you guys think? > What are the pros/cons of this approach ? > > > > > > -- 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Re: GWT / Spring Roo Integration
Hi Nick, I post this http://forum.springsource.org/showthread.php?117623-About-future-of-GWT-add-ons=008a707a73ae58d0b5717df77f7db287 in roo forum, but I got no response from the team developing the gwt add-on for roo. What version of roo are you using? On 17 nov, 12:14, Nick Thorson thorson.nicho...@gmail.com wrote: Not sure if this is the group to join, but it seemed like at the very least it was a good place to start. I have been building GWT / Spring Roo apps for about a year now, and have several thoughts I would like to share with the development team of the GWT plugin for Spring Roo. For the most part it works great for getting an application up and running. However, if I want to extend an application, I run into several head aches. I have identified work-arounds that I would like to share. Thank you, Nick Thorson -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] About GWT opinion in thoughtworks technology radar july 2011
I posted this in the gwt group, but I think this is a better place. http://www.thoughtworks.com/articles/technology-radar-july-2011#Platforms thoughtworks technology radar july 2011, talk negatively about gwt, these are the 3 reasons: First, in many ways, JavaScript is more powerful and expressive than Java, so we suspect that the generation is going in the wrong direction. more powerfull for that? Secondly, it is impossible to hide a complex abstraction difference like that from event-driven desktop to stateless-web without leaky abstraction headaches eventually popping up I can't comment, I do not know the compilation process. Third, it suffers from the same shortcomings of many elaborate frameworks, where building simple, aligned applications is quick and easy, building more sophisticated but not supported functionality is possible but difficult, and building the level of sophistication required by any non-trivial application becomes either impossible or so difficult it isn’t reasonable. What is meant by functionality not supported?. Program non-trivial applications with GWT is easier than directly in javascript. What do you think? -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
About GWT opinion in thoughtworks technology radar july 2011
http://www.thoughtworks.com/articles/technology-radar-july-2011#Platforms thoughtworks technology radar july 2011, talk negatively about gwt, these are the 3 reasons: First, in many ways, JavaScript is more powerful and expressive than Java, so we suspect that the generation is going in the wrong direction. more powerfull for that? Secondly, it is impossible to hide a complex abstraction difference like that from event-driven desktop to stateless-web without leaky abstraction headaches eventually popping up I can't comment, I do not know the compilation process. Third, it suffers from the same shortcomings of many elaborate frameworks, where building simple, aligned applications is quick and easy, building more sophisticated but not supported functionality is possible but difficult, and building the level of sophistication required by any non-trivial application becomes either impossible or so difficult it isn’t reasonable. What is meant by functionality not supported?. Program non-trivial applications with GWT is easier than directly in javascript What do you think? -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: ValueListBox not focusable
Hi, I have the same problem. why ListBox inherits FocusWidget and ValueListBox don't? any solution? Regards. On Dec 11, 1:30 am, Jakob Mar jakob.runars...@gmail.com wrote: Hi, I can't see that ValueListBox implements Focusable. Dose anybody know a workaround to focus the ValueListBox? Thanks Jakob -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
