Re: Important videos from GWT Meet-up 2015
On thing I'd like to see on GWT 3.0 and beyond is the reduction (or complete avoidance) of the Not invented here syndrome from Google: - Using a standard build tool which integrates well with Maven repositories - and don't force the end user to switch build tools just because - Using GitHub for pull requests - and nothing more than that - to allow easy community contributions - Allow the user to integrate with any CSS processor he wants, such as less, sass or any other - A HTML template engine that uses input as close as possible to the real HTML (like Errai does) -- 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: Important videos from GWT Meet-up 2015
Hi, we have heavy invested our time into GWT to build the product which will be available for at least next 5 years (ERP in cloud). But I think the direction they have made is really necessary and only reasonable. And it should be done year or two before (after SDM and GSS), because some promising technologies (Elemental 2.0, next JSNI, also Java 8 support) and now buzz for more then two years. Regards, Matic On Sunday, June 21, 2015 at 12:38:24 AM UTC+2, Jens wrote: GWT 2.8 will be a long supported and maintained branch of GWT. It's just that you can not use the new compiler if you use some of the current GWT library stuff. Upcoming things like Singular, Elemental 2.0, Java 8, JsInterop can all be used with GWT 2.8. You are not forced to upgrade your possibly large app to be compatible with the GWT 3.0 compiler and the GWT 2.8 branch is not considered obsolete/deprecated anytime soon. I do not expect that GWT 3.0 will be adopted quickly for existing apps. However for new apps it will probably be pretty great to use. I also expect GWT 3.0 to be a bit clunky at release because it needs some decent build system integration and things like Bazel do not have great IDE support yet. -- 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: Important videos from GWT Meet-up 2015
On Monday, June 22, 2015 at 5:28:36 AM UTC+9:30, Jens wrote: Yeah I think finalizing JsInterop including all the pieces to make Elemental 2.0 possible is one of the most important point which should actually have higher priority than the new compiler itself. That way other people can figure out how to migrate existing GWT library stuff while the new compiler is being developed. -- J. Great point -- 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: Important videos from GWT Meet-up 2015
Thanks Thomas. Good point on getting started experimenting before the compiler is made available. I've been building a few of libraries using APT for code generation recently, making use of the wonderful google square libraries like auto and javapoet. I think it'd be pretty straightforward to build an annotation processor for a few existing libraries e.g. i18n. However, I'm really hoping to make use of GWT compiler level solutions to overcome some current APT challenges; in particular, invoking the processor when non-java files are changed such as ui.xml files. Daniel mentioned in his talk that there might be a general solution for this which would be pretty awesome to use. I was probably too specific in asking for early access to the compiler. Early access to elemental 2.0 and jsinterop 2.0 would be really helpful to try and figure out how to port JSNI/JSO code over to jsinterop. In general my experience with GWT + APT for my own libraries has been really good, so I'm quite positive about the plans for GWT 3.0. Hopefully, with a clear migration story, the community will be able to smooth any rough edges that the core GWT team can't take on. On Sun, Jun 21, 2015 at 11:18 AM Thomas Broyer t.bro...@gmail.com wrote: On Sunday, June 21, 2015 at 11:17:50 AM UTC+2, James Horsley wrote: Also worth noting that, outside of GWT-RPC, I think that many of the current major GWT features (widgets, uibinder, etc.) could be ported by the community such that only minor code changes are necessary. I would even hazard a guess that companies like Vaadin might be interested in supporting or at least contributing to a 3.0 based port things like the widget library. I'd rather bet on Sencha for widgets. (note: I have absolutely no information about whether this will happen and who would make it happen) As I've said in other emails though, I think the migration/transition story from 2.8 - 3.0 needs work and open communication. Based on what's in the videos from the meetup, I don't think it has to be as radical of a change as is feared. To make it smoother, hopefully there will be early access to the compiler API such that the community can start thinking about building 3.0 versions of libraries we want available. You don't need access to the new compiler for that, you can start experimenting right now: given that the idea is that the GWT.create() magic will be removed and things would have to be generated upfront using JavaC and annotation processors, that means the generated code has no GWT magic (besides possibly JSNI, which would have to eventually change to JsInterop or JSNI 2.0) and can still be compiled using the current compiler (or 2.8.0-SNAPSHOT if you need System.getProperty(user.agent)). Disclaimer: I haven't yet tried it though. Note that if you'd like to start experimenting with annotation processors, I highly suggest you use auto-common's BasicAnnotationProcessor and other utilities: https://github.com/google/auto/tree/master/common -- 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. -- 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: Important videos from GWT Meet-up 2015
I was probably too specific in asking for early access to the compiler. Early access to elemental 2.0 and jsinterop 2.0 would be really helpful to try and figure out how to port JSNI/JSO code over to jsinterop. Yeah I think finalizing JsInterop including all the pieces to make Elemental 2.0 possible is one of the most important point which should actually have higher priority than the new compiler itself. That way other people can figure out how to migrate existing GWT library stuff while the new compiler is being developed. -- 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: Important videos from GWT Meet-up 2015
Also worth noting that, outside of GWT-RPC, I think that many of the current major GWT features (widgets, uibinder, etc.) could be ported by the community such that only minor code changes are necessary. I would even hazard a guess that companies like Vaadin might be interested in supporting or at least contributing to a 3.0 based port things like the widget library. As I've said in other emails though, I think the migration/transition story from 2.8 - 3.0 needs work and open communication. Based on what's in the videos from the meetup, I don't think it has to be as radical of a change as is feared. To make it smoother, hopefully there will be early access to the compiler API such that the community can start thinking about building 3.0 versions of libraries we want available. On Sun, Jun 21, 2015 at 3:19 AM David jim.p...@gmail.com wrote: When is GWT 3 available? On Sunday, June 21, 2015 at 6:38:50 AM UTC+8, Paul Robinson wrote: I suspect most people here just haven't quite realised the magnitude of what's planned. The plans are quite reasonable for anybody that can start from scratch (which doesn't include me). Anybody invested in GWT will have a problem. That includes Google, although there are no obvious plans for a migration path. It might mean GWT forks, although I can't see anybody new to GWT adopting GWT 2.8 once 3.0 is out, and the current plans will put people off adopting GWT now. Paul -- 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. -- 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: Important videos from GWT Meet-up 2015
On Sunday, June 21, 2015 at 11:17:50 AM UTC+2, James Horsley wrote: Also worth noting that, outside of GWT-RPC, I think that many of the current major GWT features (widgets, uibinder, etc.) could be ported by the community such that only minor code changes are necessary. I would even hazard a guess that companies like Vaadin might be interested in supporting or at least contributing to a 3.0 based port things like the widget library. I'd rather bet on Sencha for widgets. (note: I have absolutely no information about whether this will happen and who would make it happen) As I've said in other emails though, I think the migration/transition story from 2.8 - 3.0 needs work and open communication. Based on what's in the videos from the meetup, I don't think it has to be as radical of a change as is feared. To make it smoother, hopefully there will be early access to the compiler API such that the community can start thinking about building 3.0 versions of libraries we want available. You don't need access to the new compiler for that, you can start experimenting right now: given that the idea is that the GWT.create() magic will be removed and things would have to be generated upfront using JavaC and annotation processors, that means the generated code has no GWT magic (besides possibly JSNI, which would have to eventually change to JsInterop or JSNI 2.0) and can still be compiled using the current compiler (or 2.8.0-SNAPSHOT if you need System.getProperty(user.agent)). Disclaimer: I haven't yet tried it though. Note that if you'd like to start experimenting with annotation processors, I highly suggest you use auto-common's BasicAnnotationProcessor and other utilities: https://github.com/google/auto/tree/master/common -- 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: Important videos from GWT Meet-up 2015
When is GWT 3 available? On Sunday, June 21, 2015 at 6:38:50 AM UTC+8, Paul Robinson wrote: I suspect most people here just haven't quite realised the magnitude of what's planned. The plans are quite reasonable for anybody that can start from scratch (which doesn't include me). Anybody invested in GWT will have a problem. That includes Google, although there are no obvious plans for a migration path. It might mean GWT forks, although I can't see anybody new to GWT adopting GWT 2.8 once 3.0 is out, and the current plans will put people off adopting GWT now. Paul -- 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: Important videos from GWT Meet-up 2015
I'm a bit surprised that there hasn't been more comment on the direction the GWT team plan to take GWT in 3.0. I've been involved in a GWT project over the last 18 months or so where we're developing a large line-of-business app which we expect to have a lifetime of potentially a decade or more. Most of the GWT tech we've used (UIBinder, GWT-RPC, gwt-user stuff, CssResource, etc - basically all the best practices advice from the last few years) is going, so by the time we're ready to deploy, and GWT 3.0 comes along, our app is obsolete. Right now I'm not too sure if the there's any value in continuing with GWT. The value proposition (using Java front to back) seems to be going away. Where does the new web asm stuff just announced by all the browser vendors fit in ? Javascript will no longer need to be the transpile target. -- 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: Important videos from GWT Meet-up 2015
Sitting here thinking the same. I m having hard time understanding why people think this is the right direction GWT should take. Our apps will most likely not move beyond 2.8 On 20 June 2015 at 23:35, Bryan Buchanan bry...@webbtide.com wrote: I'm a bit surprised that there hasn't been more comment on the direction the GWT team plan to take GWT in 3.0. I've been involved in a GWT project over the last 18 months or so where we're developing a large line-of-business app which we expect to have a lifetime of potentially a decade or more. Most of the GWT tech we've used (UIBinder, GWT-RPC, gwt-user stuff, CssResource, etc - basically all the best practices advice from the last few years) is going, so by the time we're ready to deploy, and GWT 3.0 comes along, our app is obsolete. Right now I'm not too sure if the there's any value in continuing with GWT. The value proposition (using Java front to back) seems to be going away. Where does the new web asm stuff just announced by all the browser vendors fit in ? Javascript will no longer need to be the transpile target. -- 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. -- Alain Ekambi Co-Founder Ahomé Innovation Technologies http://www.ahome-it.com/ http://ahome-it.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: Important videos from GWT Meet-up 2015
GWT 2.8 will be a long supported and maintained branch of GWT. It's just that you can not use the new compiler if you use some of the current GWT library stuff. Upcoming things like Singular, Elemental 2.0, Java 8, JsInterop can all be used with GWT 2.8. You are not forced to upgrade your possibly large app to be compatible with the GWT 3.0 compiler and the GWT 2.8 branch is not considered obsolete/deprecated anytime soon. I do not expect that GWT 3.0 will be adopted quickly for existing apps. However for new apps it will probably be pretty great to use. I also expect GWT 3.0 to be a bit clunky at release because it needs some decent build system integration and things like Bazel do not have great IDE support yet. -- 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: Important videos from GWT Meet-up 2015
I suspect most people here just haven't quite realised the magnitude of what's planned. The plans are quite reasonable for anybody that can start from scratch (which doesn't include me). Anybody invested in GWT will have a problem. That includes Google, although there are no obvious plans for a migration path. It might mean GWT forks, although I can't see anybody new to GWT adopting GWT 2.8 once 3.0 is out, and the current plans will put people off adopting GWT now. Paul -- 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: Important videos from GWT Meet-up 2015
Well the question could also be why not java ? On 12 June 2015 at 11:21, Phineas Gage phineas...@gmail.com wrote: I thought I'd share this link to a series of important videos from the recent GWT Meet-up 2015, which was posted on G+ and in the GWT Contributors group: https://www.youtube.com/playlist?list=PL1yReUCGwGvrqscLu1EAyYRPrr0ceEHLE *Summary:* For anyone who wasn't already aware, there are seismic changes coming for GWT. Basically, gwt-user and everything in it will be gradually mothballed, so widgets, GWT-RPC, UiBinder, CssResource, etc. While we're at it, the GWT compiler will probably go too. If the plan stays as presented, everything is going, sooner or later. It looks as though a much simpler and faster Java to JS transpiler is proposed, maybe under a different project name, with optimizations handled by Closure. I welcome corrections if I've got something wrong here. *Editorial:* Having used GWT for a number of years, I think this is a massive but needed change. It looks like a great direction, that maybe could have been taken even sooner. But personally, I now can't see using GWT for new projects until it appears in its new form. We're in a kind of purgatory now where anything you write in GWT may not be easy to maintain, but the new vision is currently just a hope for the future. As for myself, since I've got a project in its early stages, I'll probably be porting everything I have to JavaScript, until I can count on a stable Java to JS transpiler. At that point, I can decide to move some of the code back to Java, if it's not too painful and the benefits to doing so are clear. At the same time, even with years of Java experience, I have to ask myself, why Java? If it's a better language that compiles to JavaScript that we want, there are many: Dart is coming along, and there are more options than there were before. It's speculation to say what an open source Swift will mean, but the external forces affecting these options can play themselves out while JavaScript will likely continue to be stable for years to come. So rather than drag it out, I'd like to see these changes happen ASAP. As it's sometimes said, if you find yourself in a hole, stop digging. I believe that if a stable and fast Java to JS transpiler were released, the community would chip in to help complete JRE emulation or other needed projects, and I'm glad to hear that much of the GWT team is being diverted to compiler work. Thanks to the GWT team for sharing these plans with the community! -- 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. -- Alain Ekambi Co-Founder Ahomé Innovation Technologies http://www.ahome-it.com/ http://ahome-it.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.
Important videos from GWT Meet-up 2015
I thought I'd share this link to a series of important videos from the recent GWT Meet-up 2015, which was posted on G+ and in the GWT Contributors group: https://www.youtube.com/playlist?list=PL1yReUCGwGvrqscLu1EAyYRPrr0ceEHLE *Summary:* For anyone who wasn't already aware, there are seismic changes coming for GWT. Basically, gwt-user and everything in it will be gradually mothballed, so widgets, GWT-RPC, UiBinder, CssResource, etc. While we're at it, the GWT compiler will probably go too. If the plan stays as presented, everything is going, sooner or later. It looks as though a much simpler and faster Java to JS transpiler is proposed, maybe under a different project name, with optimizations handled by Closure. I welcome corrections if I've got something wrong here. *Editorial:* Having used GWT for a number of years, I think this is a massive but needed change. It looks like a great direction, that maybe could have been taken even sooner. But personally, I now can't see using GWT for new projects until it appears in its new form. We're in a kind of purgatory now where anything you write in GWT may not be easy to maintain, but the new vision is currently just a hope for the future. As for myself, since I've got a project in its early stages, I'll probably be porting everything I have to JavaScript, until I can count on a stable Java to JS transpiler. At that point, I can decide to move some of the code back to Java, if it's not too painful and the benefits to doing so are clear. At the same time, even with years of Java experience, I have to ask myself, why Java? If it's a better language that compiles to JavaScript that we want, there are many: Dart is coming along, and there are more options than there were before. It's speculation to say what an open source Swift will mean, but the external forces affecting these options can play themselves out while JavaScript will likely continue to be stable for years to come. So rather than drag it out, I'd like to see these changes happen ASAP. As it's sometimes said, if you find yourself in a hole, stop digging. I believe that if a stable and fast Java to JS transpiler were released, the community would chip in to help complete JRE emulation or other needed projects, and I'm glad to hear that much of the GWT team is being diverted to compiler work. Thanks to the GWT team for sharing these plans with the community! -- 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: Important videos from GWT Meet-up 2015
There's no technical reason why not Java the language, but as for the infrastructure available for compiling Java to JavaScript and getting convenient bidirectional access to the JavaScript universe for use in a web application, there are more questions now. Let's say you want to use GWT 2.8 and JsInterop with Polymer. You still have to use JSNI to instantiate JavaScript objects, but that's now discouraged because it will go away. Even when GWT 2.8 is released, the implementation of JsInterop itself will change if the GWT compiler is abandoned in favor of the transpiler. JsInterop annotations may then have to change again due to unforeseen circumstances, but that is speculation. Meanwhile, what do you do about RPC, or i18n, for example? You can push more and more functionality into JavaScript, but then you lose some of the benefits of Java. Anything that depends on gwt-user is to be avoided. There is a nice video suggesting what direction to take (https://www.youtube.com/watch?v=0flgI0AMJjkindex=8list=PL1yReUCGwGvrqscLu1EAyYRPrr0ceEHLE), but it's worth thinking through just how different applications will look that are written to these recommendations vs a standard GWT application today. On Friday, June 12, 2015 at 11:42:37 AM UTC+2, Alain wrote: Well the question could also be why not java ? -- 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: Important videos from GWT Meet-up 2015
First video, GWT 2.8 and Beyond, starting around 17:20... I'd also like to hear if I misstated or misunderstood something. I listened to all of the videos and in the discussion I heard more about re-writing and renaming than keeping much of anything. On Friday, June 12, 2015 at 3:20:03 PM UTC+2, Thomas Lefort wrote: Is the phasing out of gwt-user something you heard when attending the meetings? It may be a question of interpretation but I don't read the same from the slides. Sounds more like a fork of GWT to me. Of course if all efforts go to the new project, then it is in effect the same thing ;-) may be some clarifications from the GWT contributors would help. -- 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: Important videos from GWT Meet-up 2015
Someone in the video commented that there needs to be a very clear messaging around how to best protect/future proof yourself. The Modernizing GWT video was obviously a step in that direction but I'd love to see something more concrete e.g. if UiBinder won't be supported, what should we be using? I had a specific question regarding the recommendation to use Elemental. My understanding was that Elemental 2.0 was going to be released with GWT 3.0. Is it safe to use Elemental in it's current state or will there be significant enough changes that we should wait? On 12 June 2015 at 15:29, jchimene jchim...@gmail.com wrote: Thanks for the link . To those who've generously uploaded the videos: any possibility of also uploading the slides? The technical presentations are pretty much useless w/o the slides. TIA, jec On Friday, June 12, 2015 at 2:21:49 AM UTC-7, Phineas Gage wrote: I thought I'd share this link to a series of important videos from the recent GWT Meet-up 2015, which was posted on G+ and in the GWT Contributors group: https://www.youtube.com/playlist?list=PL1yReUCGwGvrqscLu1EAyYRPrr0ceEHLE *Summary:* For anyone who wasn't already aware, there are seismic changes coming for GWT. Basically, gwt-user and everything in it will be gradually mothballed, so widgets, GWT-RPC, UiBinder, CssResource, etc. While we're at it, the GWT compiler will probably go too. If the plan stays as presented, everything is going, sooner or later. It looks as though a much simpler and faster Java to JS transpiler is proposed, maybe under a different project name, with optimizations handled by Closure. I welcome corrections if I've got something wrong here. *Editorial:* Having used GWT for a number of years, I think this is a massive but needed change. It looks like a great direction, that maybe could have been taken even sooner. But personally, I now can't see using GWT for new projects until it appears in its new form. We're in a kind of purgatory now where anything you write in GWT may not be easy to maintain, but the new vision is currently just a hope for the future. As for myself, since I've got a project in its early stages, I'll probably be porting everything I have to JavaScript, until I can count on a stable Java to JS transpiler. At that point, I can decide to move some of the code back to Java, if it's not too painful and the benefits to doing so are clear. At the same time, even with years of Java experience, I have to ask myself, why Java? If it's a better language that compiles to JavaScript that we want, there are many: Dart is coming along, and there are more options than there were before. It's speculation to say what an open source Swift will mean, but the external forces affecting these options can play themselves out while JavaScript will likely continue to be stable for years to come. So rather than drag it out, I'd like to see these changes happen ASAP. As it's sometimes said, if you find yourself in a hole, stop digging. I believe that if a stable and fast Java to JS transpiler were released, the community would chip in to help complete JRE emulation or other needed projects, and I'm glad to hear that much of the GWT team is being diverted to compiler work. Thanks to the GWT team for sharing these plans with the community! -- 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. -- 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: Important videos from GWT Meet-up 2015
One thing I may have overstated is that there's a slide discussing what *may* be ported forward (Modernizing GWT Applications https://www.youtube.com/watch?v=0flgI0AMJjklist=PL1yReUCGwGvrqscLu1EAyYRPrr0ceEHLEindex=8, around 18:45), which *may* include GSS and ClientBundles, i18n (since that's in a different module from gwt-user), UiBinder, SafeHtmlTemplates and PlaceHistoryMapperGenerator. But then at 32:30 in the same video a mention of probably not with UiBinder, so UiBinder may not stay, particularly if Singular is available which looks like be a much better solution (and they're looking for contributions to that). A name change for GWT is discussed in GWT 2.8 and Beyond https://www.youtube.com/watch?v=ltqWRoJ0S-olist=PL1yReUCGwGvrqscLu1EAyYRPrr0ceEHLEindex=1, 30:35. Not clear what the result of that will be, but if so much changes, a name change would probably be good to shed the baggage. I also like 32:35 in the same video: Any other questions? Is anybody like scared, or, uh, shocked? :) At some point someone discussed making a table of what will and will not be brought forward, so that would be useful for the community to see. And again, I'm really looking forward to seeing the evolution, but it feels like we're still a ways away from that, so knowing what to do in development now is challenging. On Friday, June 12, 2015 at 3:40:59 PM UTC+2, Phineas Gage wrote: I'd also like to hear if I misstated or misunderstood something. I listened to all of the videos and in the discussion I heard more about re-writing and renaming than keeping much of anything. -- 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: Important videos from GWT Meet-up 2015
To those who've generously uploaded the videos: any possibility of also uploading the slides? The technical presentations are pretty much useless w/o the slides. The Youtube playlist has a link at the top pointing to a Google Drive containing the slides. -- 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: Important videos from GWT Meet-up 2015
Thanks, Jens! @Brandon: would you please check your slides? The Copy of ... isn't loading, and I don't see the slides for the Contributing to Eclipse... presentation. tia, jec On Friday, June 12, 2015 at 7:55:05 AM UTC-7, Jens wrote: To those who've generously uploaded the videos: any possibility of also uploading the slides? The technical presentations are pretty much useless w/o the slides. The Youtube playlist has a link at the top pointing to a Google Drive containing the slides. -- 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: Important videos from GWT Meet-up 2015
Is the phasing out of gwt-user something you heard when attending the meetings? It may be a question of interpretation but I don't read the same from the slides. Sounds more like a fork of GWT to me. Of course if all efforts go to the new project, then it is in effect the same thing ;-) may be some clarifications from the GWT contributors would help. On Friday, 12 June 2015 11:21:49 UTC+2, Phineas Gage wrote: I thought I'd share this link to a series of important videos from the recent GWT Meet-up 2015, which was posted on G+ and in the GWT Contributors group: https://www.youtube.com/playlist?list=PL1yReUCGwGvrqscLu1EAyYRPrr0ceEHLE *Summary:* For anyone who wasn't already aware, there are seismic changes coming for GWT. Basically, gwt-user and everything in it will be gradually mothballed, so widgets, GWT-RPC, UiBinder, CssResource, etc. While we're at it, the GWT compiler will probably go too. If the plan stays as presented, everything is going, sooner or later. It looks as though a much simpler and faster Java to JS transpiler is proposed, maybe under a different project name, with optimizations handled by Closure. I welcome corrections if I've got something wrong here. *Editorial:* Having used GWT for a number of years, I think this is a massive but needed change. It looks like a great direction, that maybe could have been taken even sooner. But personally, I now can't see using GWT for new projects until it appears in its new form. We're in a kind of purgatory now where anything you write in GWT may not be easy to maintain, but the new vision is currently just a hope for the future. As for myself, since I've got a project in its early stages, I'll probably be porting everything I have to JavaScript, until I can count on a stable Java to JS transpiler. At that point, I can decide to move some of the code back to Java, if it's not too painful and the benefits to doing so are clear. At the same time, even with years of Java experience, I have to ask myself, why Java? If it's a better language that compiles to JavaScript that we want, there are many: Dart is coming along, and there are more options than there were before. It's speculation to say what an open source Swift will mean, but the external forces affecting these options can play themselves out while JavaScript will likely continue to be stable for years to come. So rather than drag it out, I'd like to see these changes happen ASAP. As it's sometimes said, if you find yourself in a hole, stop digging. I believe that if a stable and fast Java to JS transpiler were released, the community would chip in to help complete JRE emulation or other needed projects, and I'm glad to hear that much of the GWT team is being diverted to compiler work. Thanks to the GWT team for sharing these plans with the community! -- 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: Important videos from GWT Meet-up 2015
Thanks for the link . To those who've generously uploaded the videos: any possibility of also uploading the slides? The technical presentations are pretty much useless w/o the slides. TIA, jec On Friday, June 12, 2015 at 2:21:49 AM UTC-7, Phineas Gage wrote: I thought I'd share this link to a series of important videos from the recent GWT Meet-up 2015, which was posted on G+ and in the GWT Contributors group: https://www.youtube.com/playlist?list=PL1yReUCGwGvrqscLu1EAyYRPrr0ceEHLE *Summary:* For anyone who wasn't already aware, there are seismic changes coming for GWT. Basically, gwt-user and everything in it will be gradually mothballed, so widgets, GWT-RPC, UiBinder, CssResource, etc. While we're at it, the GWT compiler will probably go too. If the plan stays as presented, everything is going, sooner or later. It looks as though a much simpler and faster Java to JS transpiler is proposed, maybe under a different project name, with optimizations handled by Closure. I welcome corrections if I've got something wrong here. *Editorial:* Having used GWT for a number of years, I think this is a massive but needed change. It looks like a great direction, that maybe could have been taken even sooner. But personally, I now can't see using GWT for new projects until it appears in its new form. We're in a kind of purgatory now where anything you write in GWT may not be easy to maintain, but the new vision is currently just a hope for the future. As for myself, since I've got a project in its early stages, I'll probably be porting everything I have to JavaScript, until I can count on a stable Java to JS transpiler. At that point, I can decide to move some of the code back to Java, if it's not too painful and the benefits to doing so are clear. At the same time, even with years of Java experience, I have to ask myself, why Java? If it's a better language that compiles to JavaScript that we want, there are many: Dart is coming along, and there are more options than there were before. It's speculation to say what an open source Swift will mean, but the external forces affecting these options can play themselves out while JavaScript will likely continue to be stable for years to come. So rather than drag it out, I'd like to see these changes happen ASAP. As it's sometimes said, if you find yourself in a hole, stop digging. I believe that if a stable and fast Java to JS transpiler were released, the community would chip in to help complete JRE emulation or other needed projects, and I'm glad to hear that much of the GWT team is being diverted to compiler work. Thanks to the GWT team for sharing these plans with the community! -- 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.
