Re: Java 7
I invite you to contribute the java support 7. You can do this together with your teammates Why not? It's all a matter of priorties, vote an issue in the issue tracker and it will get a higher priority Wouldn't it be nice that you could latter say that you were responsibly for the jdk 7 support in gwt? On Tue, Apr 16, 2013 at 7:28 AM, Gilberto gilberto.torre...@gmail.comwrote: It's just my opinion, but in my mind making the JDK compliance to 1.6 and call that fully compatible with JDK 7 is not... well... what I was expecting (at least). I understand that tweaking the compiler to actually and truly support Java 7 is not easy and demand time. But Java 7 is around for ... uh... years? (since July - 2011 according to Wikipedia). I understand that GWT is now handled by a committee, since last year. And still, there's no public roadmap of when we are going to have the real Java 7 support (and I'm not even talking about Java 8). So, eh, am I wrong on asking such things? Should I recommend other frameworks to my teammates for new projects or still wait for news from GWT? I understand we have to wait till you guys commit the code to Gerrit/GitHub, to organize the project, to mavenize it, to deal with contributors, Google itself and so on. But till when? Sorry for my impatience, but at this stage I don't really feel comfortable with the situation. Maybe it's only me. On Wednesday, April 3, 2013 5:09:35 AM UTC-3, Thomas Broyer wrote: On Wednesday, April 3, 2013 8:15:03 AM UTC+2, Max Völkel wrote: How well does this play together with AppEngine 1.7.7? From their release notes: The Java runtime now defaults to Java7. If you still need to use the Java6 runtime, please use the --use_java6 flag when deploying your app. We encourage you to move to Java7 as soon as possible. It sounds I should compile for a 1.7 target. So I should *not* set maven.compiler.source to 1.6, right? I don't know how AppEngine's Java runtime works, but my 7 and 8 JREs are very well capable of running classes compiled with -target 1.6 or earlier, and mixing classes compiled with different -target (you'd never be able to use Maven, or pretty much any third-party dependency actually, if that wasn't the case; btw GWT is compiled with -target 1.6 and is fully compatible with a JDK 7, and we haven't yet heard of anyone having issues using RPC or RequestFactory on AppEngine) -- 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/dM8D9imIvAI/unsubscribe?hl=en . 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-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Java 7
Java 6 is still used a lot in enterprise developments, I am actually more looking forward to Java 8 support due to project lambda which could have a very nice impact on readability of all these async operations we tend to chain together in GWT client applications. On Tuesday, April 16, 2013 9:12:55 AM UTC+2, Ed wrote: I invite you to contribute the java support 7. You can do this together with your teammates Why not? It's all a matter of priorties, vote an issue in the issue tracker and it will get a higher priority Wouldn't it be nice that you could latter say that you were responsibly for the jdk 7 support in gwt? On Tue, Apr 16, 2013 at 7:28 AM, Gilberto gilberto...@gmail.comjavascript: wrote: It's just my opinion, but in my mind making the JDK compliance to 1.6 and call that fully compatible with JDK 7 is not... well... what I was expecting (at least). I understand that tweaking the compiler to actually and truly support Java 7 is not easy and demand time. But Java 7 is around for ... uh... years? (since July - 2011 according to Wikipedia). I understand that GWT is now handled by a committee, since last year. And still, there's no public roadmap of when we are going to have the real Java 7 support (and I'm not even talking about Java 8). So, eh, am I wrong on asking such things? Should I recommend other frameworks to my teammates for new projects or still wait for news from GWT? I understand we have to wait till you guys commit the code to Gerrit/GitHub, to organize the project, to mavenize it, to deal with contributors, Google itself and so on. But till when? Sorry for my impatience, but at this stage I don't really feel comfortable with the situation. Maybe it's only me. On Wednesday, April 3, 2013 5:09:35 AM UTC-3, Thomas Broyer wrote: On Wednesday, April 3, 2013 8:15:03 AM UTC+2, Max Völkel wrote: How well does this play together with AppEngine 1.7.7? From their release notes: The Java runtime now defaults to Java7. If you still need to use the Java6 runtime, please use the --use_java6 flag when deploying your app. We encourage you to move to Java7 as soon as possible. It sounds I should compile for a 1.7 target. So I should *not* set maven.compiler.source to 1.6, right? I don't know how AppEngine's Java runtime works, but my 7 and 8 JREs are very well capable of running classes compiled with -target 1.6 or earlier, and mixing classes compiled with different -target (you'd never be able to use Maven, or pretty much any third-party dependency actually, if that wasn't the case; btw GWT is compiled with -target 1.6 and is fully compatible with a JDK 7, and we haven't yet heard of anyone having issues using RPC or RequestFactory on AppEngine) -- 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/dM8D9imIvAI/unsubscribe?hl=en . 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.comjavascript: . Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Java 7
On Tuesday, April 16, 2013 7:28:17 AM UTC+2, Gilberto wrote: It's just my opinion, but in my mind making the JDK compliance to 1.6 and call that fully compatible with JDK 7 is not... well... what I was expecting (at least). I understand that tweaking the compiler to actually and truly support Java 7 is not easy and demand time. But Java 7 is around for ... uh... years? (since July - 2011 according to Wikipedia). I understand that GWT is now handled by a committee, since last year. And still, there's no public roadmap of when we are going to have the real Java 7 support (and I'm not even talking about Java 8). So, eh, am I wrong on asking such things? Should I recommend other frameworks to my teammates for new projects or still wait for news from GWT? I understand we have to wait till you guys commit the code to Gerrit/GitHub, to organize the project, to mavenize it, to deal with contributors, Google itself and so on. But till when? Sorry for my impatience, but at this stage I don't really feel comfortable with the situation. Maybe it's only me. Java 7 (language) support is coming: https://gwt-review.googlesource.com/2361 Java 8 will have to wait 'til the Eclipse compiler supports it. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Java 7
It's just my opinion, but in my mind making the JDK compliance to 1.6 and call that fully compatible with JDK 7 is not... well... what I was expecting (at least). I understand that tweaking the compiler to actually and truly support Java 7 is not easy and demand time. But Java 7 is around for ... uh... years? (since July - 2011 according to Wikipedia). I understand that GWT is now handled by a committee, since last year. And still, there's no public roadmap of when we are going to have the real Java 7 support (and I'm not even talking about Java 8). So, eh, am I wrong on asking such things? Should I recommend other frameworks to my teammates for new projects or still wait for news from GWT? I understand we have to wait till you guys commit the code to Gerrit/GitHub, to organize the project, to mavenize it, to deal with contributors, Google itself and so on. But till when? Sorry for my impatience, but at this stage I don't really feel comfortable with the situation. Maybe it's only me. On Wednesday, April 3, 2013 5:09:35 AM UTC-3, Thomas Broyer wrote: On Wednesday, April 3, 2013 8:15:03 AM UTC+2, Max Völkel wrote: How well does this play together with AppEngine 1.7.7? From their release notes: The Java runtime now defaults to Java7. If you still need to use the Java6 runtime, please use the --use_java6 flag when deploying your app. We encourage you to move to Java7 as soon as possible. It sounds I should compile for a 1.7 target. So I should *not* set maven.compiler.source to 1.6, right? I don't know how AppEngine's Java runtime works, but my 7 and 8 JREs are very well capable of running classes compiled with -target 1.6 or earlier, and mixing classes compiled with different -target (you'd never be able to use Maven, or pretty much any third-party dependency actually, if that wasn't the case; btw GWT is compiled with -target 1.6 and is fully compatible with a JDK 7, and we haven't yet heard of anyone having issues using RPC or RequestFactory on AppEngine) -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Java 7
How well does this play together with AppEngine 1.7.7? From their release notes: The Java runtime now defaults to Java7. If you still need to use the Java6 runtime, please use the --use_java6 flag when deploying your app. We encourage you to move to Java7 as soon as possible. It sounds I should compile for a 1.7 target. So I should *not* set maven.compiler.source to 1.6, right? I hope AppEngine and GWT remain compatible. Do you know more on this? On Thursday, February 21, 2013 2:55:24 PM UTC+1, Thomas Broyer wrote: On Thursday, February 21, 2013 1:32:44 PM UTC+1, Seamus McMorrow wrote: Hi, Sorry for resurrecting a slightly old thread. JDK 1.6 is EOL end of this month, so I am thinking of migrating my GWT project to JDK7 I am using GWT 2.5, and wondering if many people are using JDK7 in their GWT projects. Is it okay to do so and if so, what are the gotchas? GWT 2.5 is fully compatible with JDK 7 (see https://developers.google.com/web-toolkit/release-notes#Release_Notes_2_5_0_RC2 ). Just make sure you only use Java 6 constructs in your client code (in Eclipse, Project properties → Java Compiler, set “JDK Compliance” to 1.6; in Maven, set “maven.compiler.source” and “maven.compiler.target” to 1.6 or 6). -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Java 7
On Wednesday, April 3, 2013 8:15:03 AM UTC+2, Max Völkel wrote: How well does this play together with AppEngine 1.7.7? From their release notes: The Java runtime now defaults to Java7. If you still need to use the Java6 runtime, please use the --use_java6 flag when deploying your app. We encourage you to move to Java7 as soon as possible. It sounds I should compile for a 1.7 target. So I should *not* set maven.compiler.source to 1.6, right? I don't know how AppEngine's Java runtime works, but my 7 and 8 JREs are very well capable of running classes compiled with -target 1.6 or earlier, and mixing classes compiled with different -target (you'd never be able to use Maven, or pretty much any third-party dependency actually, if that wasn't the case; btw GWT is compiled with -target 1.6 and is fully compatible with a JDK 7, and we haven't yet heard of anyone having issues using RPC or RequestFactory on AppEngine) -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Java 7
Hi, Sorry for resurrecting a slightly old thread. JDK 1.6 is EOL end of this month, so I am thinking of migrating my GWT project to JDK7 I am using GWT 2.5, and wondering if many people are using JDK7 in their GWT projects. Is it okay to do so and if so, what are the gotchas? Thanks, S On Monday, 1 October 2012 14:59:51 UTC+1, Konstantin Solomatov wrote: And what about JDK8? I think, implementing closures support in GWT makes a lot of sense since you can translate them to native javascript closures. On Wednesday, September 26, 2012 1:21:26 AM UTC+4, Brian Slesinsky wrote: GWT 2.5 rc2 should run on a JDK 7 virtual machine (there was a recent fix to make dev mode work). We've occasionally talked about supporting Java 7 features, but there's no concrete plan or schedule to implement them. - Brian On Tuesday, September 25, 2012 4:38:28 AM UTC-7, Benjamin Wolff wrote: Hi, sorry for gravedigging, but the title of this thread seems suitable. Since Java 6 reaches its End-Of-Life cycle at the beginning of next year, does the GWT team has concrete plans to support Java 7? See: http://www.oracle.com/technetwork/java/eol-135779.html Cheers, Ben -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Java 7
Em quinta-feira, 21 de fevereiro de 2013 09h32min44s UTC-3, Seamus McMorrow escreveu: Sorry for resurrecting a slightly old thread. JDK 1.6 is EOL end of this month, so I am thinking of migrating my GWT project to JDK7 I am using GWT 2.5, and wondering if many people are using JDK7 in their GWT projects. Is it okay to do so and if so, what are the gotchas? We are using JDK7 with GWT -- UiBinder, ClientBundle, GWT-RPC -- and Eclipse 4.2. No gotchas so far. -- P. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Java 7
On Thursday, February 21, 2013 1:32:44 PM UTC+1, Seamus McMorrow wrote: Hi, Sorry for resurrecting a slightly old thread. JDK 1.6 is EOL end of this month, so I am thinking of migrating my GWT project to JDK7 I am using GWT 2.5, and wondering if many people are using JDK7 in their GWT projects. Is it okay to do so and if so, what are the gotchas? GWT 2.5 is fully compatible with JDK 7 (see https://developers.google.com/web-toolkit/release-notes#Release_Notes_2_5_0_RC2 ). Just make sure you only use Java 6 constructs in your client code (in Eclipse, Project properties → Java Compiler, set “JDK Compliance” to 1.6; in Maven, set “maven.compiler.source” and “maven.compiler.target” to 1.6 or 6). -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Java 7
And what about JDK8? I think, implementing closures support in GWT makes a lot of sense since you can translate them to native javascript closures. On Wednesday, September 26, 2012 1:21:26 AM UTC+4, Brian Slesinsky wrote: GWT 2.5 rc2 should run on a JDK 7 virtual machine (there was a recent fix to make dev mode work). We've occasionally talked about supporting Java 7 features, but there's no concrete plan or schedule to implement them. - Brian On Tuesday, September 25, 2012 4:38:28 AM UTC-7, Benjamin Wolff wrote: Hi, sorry for gravedigging, but the title of this thread seems suitable. Since Java 6 reaches its End-Of-Life cycle at the beginning of next year, does the GWT team has concrete plans to support Java 7? See: http://www.oracle.com/technetwork/java/eol-135779.html Cheers, Ben -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/XnxLqk0C7LkJ. 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: Java 7
When does 2.5 rc2 will be available to download? Thanks, Krzysztof On Tuesday, 25 September 2012 22:21:26 UTC+1, Brian Slesinsky wrote: GWT 2.5 rc2 should run on a JDK 7 virtual machine (there was a recent fix to make dev mode work). We've occasionally talked about supporting Java 7 features, but there's no concrete plan or schedule to implement them. - Brian On Tuesday, September 25, 2012 4:38:28 AM UTC-7, Benjamin Wolff wrote: Hi, sorry for gravedigging, but the title of this thread seems suitable. Since Java 6 reaches its End-Of-Life cycle at the beginning of next year, does the GWT team has concrete plans to support Java 7? See: http://www.oracle.com/technetwork/java/eol-135779.html Cheers, Ben -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/nfvfcGOGkfoJ. 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: Java 7
Hi, sorry for gravedigging, but the title of this thread seems suitable. Since Java 6 reaches its End-Of-Life cycle at the beginning of next year, does the GWT team has concrete plans to support Java 7? See: http://www.oracle.com/technetwork/java/eol-135779.html Cheers, Ben -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/buQJiZhy3m4J. 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: Java 7
GWT 2.5 rc2 should run on a JDK 7 virtual machine (there was a recent fix to make dev mode work). We've occasionally talked about supporting Java 7 features, but there's no concrete plan or schedule to implement them. - Brian On Tuesday, September 25, 2012 4:38:28 AM UTC-7, Benjamin Wolff wrote: Hi, sorry for gravedigging, but the title of this thread seems suitable. Since Java 6 reaches its End-Of-Life cycle at the beginning of next year, does the GWT team has concrete plans to support Java 7? See: http://www.oracle.com/technetwork/java/eol-135779.html Cheers, Ben -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/5Ylnu5MPnZAJ. 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: Java 7 - Diamond Operator
On Thursday, June 14, 2012 12:49:55 PM UTC+2, Albert Attard wrote: Question: 1. Does GWT support Java 7 features? No. Not yet. Though it will likely take some time. 1. What changed do I need to perform in order to have the Java 7 code working without having to change the source? In terms of what should be done *within GWT* to make it support Java 7? Well, first and foremost upgrade ECJ to a version that supports Java 7. Hopefully that would be enough to support the diamond operator, and possibly all other Java 7 features. Switch on strings would hwoever greatly benefit from a specific handling in GWT, to compile it to an equivalent switch in JS. 1. What other features from the latest Java 7 GWT does not support? No single one. GWT uses a Java 6 parser, so it only supports Java 6. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/MJiQklnvo2YJ. 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: Java 7 - Diamond Operator
Thanks for your reply. Albert On Thursday, June 14, 2012 12:57:36 PM UTC+2, Thomas Broyer wrote: On Thursday, June 14, 2012 12:49:55 PM UTC+2, Albert Attard wrote: Question: 1. Does GWT support Java 7 features? No. Not yet. Though it will likely take some time. 1. What changed do I need to perform in order to have the Java 7 code working without having to change the source? In terms of what should be done *within GWT* to make it support Java 7? Well, first and foremost upgrade ECJ to a version that supports Java 7. Hopefully that would be enough to support the diamond operator, and possibly all other Java 7 features. Switch on strings would hwoever greatly benefit from a specific handling in GWT, to compile it to an equivalent switch in JS. 1. What other features from the latest Java 7 GWT does not support? No single one. GWT uses a Java 6 parser, so it only supports Java 6. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/QdwYFrC4TR0J. 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: Java 7 - Diamond Operator
The page ( https://developers.google.com/web-toolkit/doc/latest/DevGuideCodingBasicsCompatibility) only mentions support for Java 1.5. Sorry for the trouble, I missed it before. I was looking for diamond operator before and found nothing, where my search criteria had to be different :(. There are plenty of posts about this. Thanks again, Albert Attard On Thursday, June 14, 2012 12:57:36 PM UTC+2, Thomas Broyer wrote: On Thursday, June 14, 2012 12:49:55 PM UTC+2, Albert Attard wrote: Question: 1. Does GWT support Java 7 features? No. Not yet. Though it will likely take some time. 1. What changed do I need to perform in order to have the Java 7 code working without having to change the source? In terms of what should be done *within GWT* to make it support Java 7? Well, first and foremost upgrade ECJ to a version that supports Java 7. Hopefully that would be enough to support the diamond operator, and possibly all other Java 7 features. Switch on strings would hwoever greatly benefit from a specific handling in GWT, to compile it to an equivalent switch in JS. 1. What other features from the latest Java 7 GWT does not support? No single one. GWT uses a Java 6 parser, so it only supports Java 6. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/3C3uGa67GKUJ. 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: Java 7
Just stumbled on that: Note: As of GWT 1.5, GWT compiles the Java language syntax that is compatible with J2SE 1.5 or earlier. Versions of GWT prior to GWT 1.5 are limited to Java 1.4 source compatibility. For example, GWT 2.0 supports generics, whereas GWT 1.4 does not. — *Source: * http://code.google.com/webtoolkit/doc/latest/DevGuideCodingBasicsCompatibility.html And the warning about support for Java 1.5 being deprecated since GWT 2.2 is done by checking at the current JVM: http://code.google.com/p/google-web-toolkit/source/detail?r=9636 This is different from what GWT accepts as input, which then *officially* doesn't support Java 6 (even though it emulates java.lang.String.isEmpty() and accepts @Override on interface-method's implementations, which makes it practically usable with (most) Java 6 source files). -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/QU38WfzTl0sJ. 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: Java 7
On Jul 5, 1:21 am, Magno Machado magn...@gmail.com wrote: Is there any current work on supporting java 7 syntax on gwt? Will it be available on GWT 2.4? I think this question is of general interest. But as nobody replied yet, I suppose not :( -Alex -- 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: Java 7
Well, GWT uses Eclipse's JDT (a patched version AFAIK), so it would first have to be updated to a version that supports Java 7, and then GWT code updated to support the changes (such as mapping switch on strings to the same switch on strings construct in JavaScript). …but Eclipse's JDT support for Java7 is still in beta, so… See http://wiki.eclipse.org/JDT/Eclipse_Java_7_Support_(BETA) and http://wiki.eclipse.org/JDT_Core/Java7 Also, GWT added support for Java 5 when Java 1.4 reached EOL, and Java 6 was already released, and GWT does not officially support Java 6 (that's going to change, and a few features are already there, such as @Override on implementations of interface methods, and String#isEmpty); let's hope it'll be faster for Java 7, but don't be too impatient IMO. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/7Cg33qsKa0gJ. 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: Java 7
Also, GWT added support for Java 5 when Java 1.4 reached EOL, and Java 6 was already released, and GWT does not officially support Java 6 (that's going to change, and a few features are already there, such as @Override on implementations of interface methods, and String#isEmpty); let's hope it'll be faster for Java 7, but don't be too impatient IMO. Are you sure this is true? I thought 1.6 is supported as of 2.3, but not required. 1.6 will be required in future releases of GWT however (it may be required for 2.3, i'm not sure) but I know commits to trunk are going in with @Override on interface methods, so in order to get stuff to compile 1.6 will be required. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/Laj9dlhZOe8J. 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: Java 7
GWT requiring a Java6 JVM is different from officially supporting Java 6 language features in what the GWT Compiler accepts as input ;-) (I believe Java 6 is supported –as I said, at least some features already are, for quite some time, and I've almost always been using Java 6 compliance level in Eclipse without any issue–, what I don't know is whether we can call it official support for Java 6 –a couple features might not be enough for that claim, or maybe they are?–) -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/3RqkCd6MYPIJ. 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: Java 7 And Closures
Hi, well, without wanting to be destructive: where is the big difference compared to the command pattern? I really like GWT's stability and maturity. I'd like to keep it as simple and straightforward as possible. It would be great if that stays as the design goal - and whether or not J7 closures come in, I still like the command pattern... Regards Sebastian On Jul 19, 8:15 pm, dolcra...@gmail.com dolcra...@gmail.com wrote: I think GWT should refrain from including Java 7 features until it is released at least... On Jul 19, 1:48 pm, Daniel Simons daniel.simo...@gmail.com wrote: Hey Guys, I was wondering if there have been plans centered around including Java 7 features such as closures to future versions of GWT. Thanks, Daniel -- 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.
Re: Java 7 And Closures
from what I read about Closures, it won't change the way you use command
pattern at all, it'll simplify greatly the way you write nested classes.
ex:
Before closure
command.execute(new myasynccallback() {
void onSuccess(Result result) {
doSomething
}
}
With closure
command.execute(new myasynccallback() {
doSomething()
}
Thus removing some boiler plate. If you asking me about onFail... I usually
have MyAsyncCallback extends AsyncCallback and deal with errors here.
There's a lot more to Closure than this, but at least, you'll know that
it'll change nothing to the way you use command pattern, it'll only simplify
it.
Cheers,
On Tue, Jul 20, 2010 at 10:03 AM, Sebastian Rothbucher
sebastian.rothbuc...@clarities.de wrote:
Hi, well, without wanting to be destructive: where is the big
difference compared to the command pattern? I really like GWT's
stability and maturity. I'd like to keep it as simple and
straightforward as possible. It would be great if that stays as the
design goal - and whether or not J7 closures come in, I still like the
command pattern...
Regards
Sebastian
On Jul 19, 8:15 pm, dolcra...@gmail.com dolcra...@gmail.com wrote:
I think GWT should refrain from including Java 7 features until it is
released at least...
On Jul 19, 1:48 pm, Daniel Simons daniel.simo...@gmail.com wrote:
Hey Guys,
I was wondering if there have been plans centered around including Java
7
features such as closures to future versions of GWT.
Thanks,
Daniel
--
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.comgoogle-web-toolkit%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
--
Christian Goudreau
--
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.
Re: Java 7 And Closures
I guess GWT has been in great need of Closures. Just look at all the async callbacks. So i think we'll see a quick adoption of Closures, at least. Nabeel On Mon, Jul 19, 2010 at 10:48 PM, Daniel Simons daniel.simo...@gmail.comwrote: Hey Guys, I was wondering if there have been plans centered around including Java 7 features such as closures to future versions of GWT. Thanks, Daniel -- 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.comgoogle-web-toolkit%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- 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.
Re: Java 7 And Closures
I think GWT should refrain from including Java 7 features until it is released at least... On Jul 19, 1:48 pm, Daniel Simons daniel.simo...@gmail.com wrote: Hey Guys, I was wondering if there have been plans centered around including Java 7 features such as closures to future versions of GWT. Thanks, Daniel -- 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.
