[gwt-contrib] Re: Reminder: Branching GWT 2.6 later today
In the mean time though, I think I successfully pushed 2.6.0-SNAPSHOT to https://oss.sonatype.org/content/repositories/google-snapshots/. On Tue, Nov 5, 2013 at 12:04 AM, Matthew Dempsky mdemp...@google.comwrote: As promised, I created the release/2.6 branch for tracking development towards 2.6. At this point, development can continue on master towards the next release. If you think a change should be made for 2.6, please propose it against master, and then notify me to cherry pick it onto release/2.6. Setting up the 2.6 release branch took longer than expected due to some last minute changes and technical issues. I plan to finish preparing the 2.6rc1 snapshot tomorrow morning, and push them out. I'll send an announcement when that's ready. Thanks for your patience and sorry for the slight delay. On Mon, Nov 4, 2013 at 1:58 PM, Matthew Dempsky mdemp...@google.comwrote: As a reminder, I'm going to create the GWT 2.6 branch later today and prepare a 2.6rc1 snapshot. There's still some time to propose and submit patches, but it's down to hours remaining now. Don't fret if you miss the deadline: there will be more releases in the future! -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] Re: Reminder: Branching GWT 2.6 later today
Thanks Mathew! 2013/11/5 Matthew Dempsky mdemp...@google.com In the mean time though, I think I successfully pushed 2.6.0-SNAPSHOT to https://oss.sonatype.org/content/repositories/google-snapshots/. On Tue, Nov 5, 2013 at 12:04 AM, Matthew Dempsky mdemp...@google.comwrote: As promised, I created the release/2.6 branch for tracking development towards 2.6. At this point, development can continue on master towards the next release. If you think a change should be made for 2.6, please propose it against master, and then notify me to cherry pick it onto release/2.6. Setting up the 2.6 release branch took longer than expected due to some last minute changes and technical issues. I plan to finish preparing the 2.6rc1 snapshot tomorrow morning, and push them out. I'll send an announcement when that's ready. Thanks for your patience and sorry for the slight delay. On Mon, Nov 4, 2013 at 1:58 PM, Matthew Dempsky mdemp...@google.comwrote: As a reminder, I'm going to create the GWT 2.6 branch later today and prepare a 2.6rc1 snapshot. There's still some time to propose and submit patches, but it's down to hours remaining now. Don't fret if you miss the deadline: there will be more releases in the future! -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] Deprecating DeRPC classes
Hi Stephan, Could you please let me know is there any patch available to check the impact of removing de rpc calls. Thanks in advance.. Have a good day. Regards, Naresh Yakkala. On Thursday, 20 September 2012 20:18:39 UTC+5:30, Stephen Haberman wrote: Or should I go ahead and propose a patch that deprecates it or even removes it? That seems like a great idea to me; I would say go ahead and submit a patch to remove it. I suppose it is inevitable that some internal Google projects still use it, but it would be nice to at least know, and I think Ray/Brian submitting a patch and letting their build system figure it out what breaks is the quickest way to know. If anything we can queue it up for the eventual non-google trunk where hopefully we have a bit more freedom with this sort of stuff. - Stephen -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Re: Deprecating and moving AsyncProxy out of SDK
Never used it because I didn't like the API. It hides the async behavior completely which makes it easy to fall into traps. IMHO its just too much hiding. Once GWT supports Java 8 and once GWT provides additional API methods that play nicely together with lambda/method references there is no need to hide asynchronous behavior. -- J. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] Deprecating DeRPC classes
Hi Naresh, Could you please let me know is there any patch available to check the impact of removing de rpc calls. I'm glad you're interested in looking in to this. Unfortunately, I don't really know much about DeRPC. There are probably others on the gwt-contrib list who do though...we'll see if anyone can point you in the right direction. - Stephen -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] Re: Deprecating and moving AsyncProxy out of SDK
Never used it Same here, so +1 to your plans to extract it. - Stephen -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] Deprecating DeRPC classes
The first step would be to delete com.google.gwt.rpc and the HybridServiceServlet, and then remove all the hooks in RPC that were added to make deRPC possible (there's at least one in RemoteServiceServlet), and probably others in the RPC generator. On Tuesday, November 5, 2013 5:26:21 PM UTC+1, Stephen Haberman wrote: Hi Naresh, Could you please let me know is there any patch available to check the impact of removing de rpc calls. I'm glad you're interested in looking in to this. Unfortunately, I don't really know much about DeRPC. There are probably others on the gwt-contrib list who do though...we'll see if anyone can point you in the right direction. - Stephen -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] Deprecating DeRPC classes
Just curious, is there a particular impetus to removing DeRPC at this time? E.g., is it causing code bloat or slowness, or making new development more difficult? I'm fine with marking the class as @Deprecated, but unfortunately we [Google] still have an internal customer using DeRPC and so far I haven't been successful in convincing them to prioritize moving off of it. (I did manage to remove our other internal uses of DeRPC.) Alternatively, if there's an easy way for us to split DeRPC out of GWT core and maintain it separately, I'm happy to do that (e.g., we're already doing that for GWTShell). But it sounds like DeRPC is heavily entangled into GWT-RPC? On Tue, Nov 5, 2013 at 9:45 AM, Thomas Broyer t.bro...@gmail.com wrote: The first step would be to delete com.google.gwt.rpc and the HybridServiceServlet, and then remove all the hooks in RPC that were added to make deRPC possible (there's at least one in RemoteServiceServlet), and probably others in the RPC generator. On Tuesday, November 5, 2013 5:26:21 PM UTC+1, Stephen Haberman wrote: Hi Naresh, Could you please let me know is there any patch available to check the impact of removing de rpc calls. I'm glad you're interested in looking in to this. Unfortunately, I don't really know much about DeRPC. There are probably others on the gwt-contrib list who do though...we'll see if anyone can point you in the right direction. - Stephen -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] Deprecating DeRPC classes
DeRPC was essentially an experiment that didn't work out, it was supposed to improve the speed of IE6. It added a lot of hacks to the compiler to make it work, @ArtificialRescue, ability to invoke client-side methods from server emitted functions, which actually requires clever hacks in some classes to prevent inlining (see java/lang/Class emulation code) It would be good to remove it. If you want really fast RPC, go with something like JAXRS + JSOs. Parsing is blistering fast with JSON.parse() on today's browsers, and there's no need to deserialize/copy. RestyGWT is one possibility. On Tue, Nov 5, 2013 at 10:07 AM, Matthew Dempsky mdemp...@google.comwrote: Just curious, is there a particular impetus to removing DeRPC at this time? E.g., is it causing code bloat or slowness, or making new development more difficult? I'm fine with marking the class as @Deprecated, but unfortunately we [Google] still have an internal customer using DeRPC and so far I haven't been successful in convincing them to prioritize moving off of it. (I did manage to remove our other internal uses of DeRPC.) Alternatively, if there's an easy way for us to split DeRPC out of GWT core and maintain it separately, I'm happy to do that (e.g., we're already doing that for GWTShell). But it sounds like DeRPC is heavily entangled into GWT-RPC? On Tue, Nov 5, 2013 at 9:45 AM, Thomas Broyer t.bro...@gmail.com wrote: The first step would be to delete com.google.gwt.rpc and the HybridServiceServlet, and then remove all the hooks in RPC that were added to make deRPC possible (there's at least one in RemoteServiceServlet), and probably others in the RPC generator. On Tuesday, November 5, 2013 5:26:21 PM UTC+1, Stephen Haberman wrote: Hi Naresh, Could you please let me know is there any patch available to check the impact of removing de rpc calls. I'm glad you're interested in looking in to this. Unfortunately, I don't really know much about DeRPC. There are probably others on the gwt-contrib list who do though...we'll see if anyone can point you in the right direction. - Stephen -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Re: Reminder: Branching GWT 2.6 later today
It looks like while I can get maven from the command line to get along with that repo, IntelliJ isn't having it - it is getting confused by the fact that the latest gwt-user snapshot 2.6.0-20131105.081128-3 only has a sources jar and a pom, no actual jar with compiled code in it. The -1 jar is only the compiled code, the -2 is only javadoc, and the -3 is, as mentioned, sources. The maven/push-gwt.sh patch I put up should resolve this - for now this setup is good for maven builds, but not for IDEs that expect to have sources and javadocs available in the 'same' snapshot. On Tuesday, November 5, 2013 2:18:30 AM UTC-6, Matthew Dempsky wrote: In the mean time though, I think I successfully pushed 2.6.0-SNAPSHOT to https://oss.sonatype.org/content/repositories/google-snapshots/. On Tue, Nov 5, 2013 at 12:04 AM, Matthew Dempsky mdem...@google.comjavascript: wrote: As promised, I created the release/2.6 branch for tracking development towards 2.6. At this point, development can continue on master towards the next release. If you think a change should be made for 2.6, please propose it against master, and then notify me to cherry pick it onto release/2.6. Setting up the 2.6 release branch took longer than expected due to some last minute changes and technical issues. I plan to finish preparing the 2.6rc1 snapshot tomorrow morning, and push them out. I'll send an announcement when that's ready. Thanks for your patience and sorry for the slight delay. On Mon, Nov 4, 2013 at 1:58 PM, Matthew Dempsky mdem...@google.comjavascript: wrote: As a reminder, I'm going to create the GWT 2.6 branch later today and prepare a 2.6rc1 snapshot. There's still some time to propose and submit patches, but it's down to hours remaining now. Don't fret if you miss the deadline: there will be more releases in the future! -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] Deprecating DeRPC classes
Sorry, let me clarify: I know what DeRPC is and why we'd want to get rid of it. I'm asking why we're discussing getting rid of it *now*. Like I said, Google has an internal user for it still, so someone (most likely me) would need to invest time in helping them transition off before we can delete it. I want to make sure that effort is well spent. On Tue, Nov 5, 2013 at 5:00 PM, Ray Cromwell cromwell...@google.com wrote: DeRPC was essentially an experiment that didn't work out, it was supposed to improve the speed of IE6. It added a lot of hacks to the compiler to make it work, @ArtificialRescue, ability to invoke client-side methods from server emitted functions, which actually requires clever hacks in some classes to prevent inlining (see java/lang/Class emulation code) It would be good to remove it. If you want really fast RPC, go with something like JAXRS + JSOs. Parsing is blistering fast with JSON.parse() on today's browsers, and there's no need to deserialize/copy. RestyGWT is one possibility. On Tue, Nov 5, 2013 at 10:07 AM, Matthew Dempsky mdemp...@google.comwrote: Just curious, is there a particular impetus to removing DeRPC at this time? E.g., is it causing code bloat or slowness, or making new development more difficult? I'm fine with marking the class as @Deprecated, but unfortunately we [Google] still have an internal customer using DeRPC and so far I haven't been successful in convincing them to prioritize moving off of it. (I did manage to remove our other internal uses of DeRPC.) Alternatively, if there's an easy way for us to split DeRPC out of GWT core and maintain it separately, I'm happy to do that (e.g., we're already doing that for GWTShell). But it sounds like DeRPC is heavily entangled into GWT-RPC? On Tue, Nov 5, 2013 at 9:45 AM, Thomas Broyer t.bro...@gmail.com wrote: The first step would be to delete com.google.gwt.rpc and the HybridServiceServlet, and then remove all the hooks in RPC that were added to make deRPC possible (there's at least one in RemoteServiceServlet), and probably others in the RPC generator. On Tuesday, November 5, 2013 5:26:21 PM UTC+1, Stephen Haberman wrote: Hi Naresh, Could you please let me know is there any patch available to check the impact of removing de rpc calls. I'm glad you're interested in looking in to this. Unfortunately, I don't really know much about DeRPC. There are probably others on the gwt-contrib list who do though...we'll see if anyone can point you in the right direction. - Stephen -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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 . For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] Re: Reminder: Branching GWT 2.6 later today
Thanks for testing, Colin! I'll try another push tonight using your scripts. On Tue, Nov 5, 2013 at 5:14 PM, Colin Alworth niloc...@gmail.com wrote: It looks like while I can get maven from the command line to get along with that repo, IntelliJ isn't having it - it is getting confused by the fact that the latest gwt-user snapshot 2.6.0-20131105.081128-3 only has a sources jar and a pom, no actual jar with compiled code in it. The -1 jar is only the compiled code, the -2 is only javadoc, and the -3 is, as mentioned, sources. The maven/push-gwt.sh patch I put up should resolve this - for now this setup is good for maven builds, but not for IDEs that expect to have sources and javadocs available in the 'same' snapshot. On Tuesday, November 5, 2013 2:18:30 AM UTC-6, Matthew Dempsky wrote: In the mean time though, I think I successfully pushed 2.6.0-SNAPSHOT to https://oss.sonatype.org/content/repositories/google-snapshots/. On Tue, Nov 5, 2013 at 12:04 AM, Matthew Dempsky mdem...@google.comwrote: As promised, I created the release/2.6 branch for tracking development towards 2.6. At this point, development can continue on master towards the next release. If you think a change should be made for 2.6, please propose it against master, and then notify me to cherry pick it onto release/2.6. Setting up the 2.6 release branch took longer than expected due to some last minute changes and technical issues. I plan to finish preparing the 2.6rc1 snapshot tomorrow morning, and push them out. I'll send an announcement when that's ready. Thanks for your patience and sorry for the slight delay. On Mon, Nov 4, 2013 at 1:58 PM, Matthew Dempsky mdem...@google.comwrote: As a reminder, I'm going to create the GWT 2.6 branch later today and prepare a 2.6rc1 snapshot. There's still some time to propose and submit patches, but it's down to hours remaining now. Don't fret if you miss the deadline: there will be more releases in the future! -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
