[gwt-contrib] Help with testing GWT 2.7 RC1
Hi all, we are looking for help with testing GWT 2.7 RC1. We are in need of people testing the release on these platforms (others are already covered): - Windows 7/8, IE10 - some Windows, IE8 Please reach out to me directly if you want to get involved. -Daniel -- Google Germany GmbH *Dienerstr. 12* *80331 München* Registergericht und -nummer: Hamburg, HRB 86891 Sitz der Gesellschaft: Hamburg Geschäftsführer: Graham Law, Katherine Stephens -- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiqAKZrx1swV29wA7xC9O9x%3DU3pgBqL7owhyHF%3DcA%3Dx%3DVg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: GWT 2.7 SDM incremental output too large
One option is to get source-map support improved directly in Eclipse/IntelliJ, so that the Javascript-based developer tools are not used, rather, the IDEs connect to the Browsers via remote debugging protocols, but the SourceMap/indexing/navigation is done by Eclipse/IntelliJ. A shameless plug: this is anyway what SDBG does already now... Blink's remote debugging protocol has no idea what a sourcemap is, aside from one little string hint telling me what is the name of the sourcemap file associated with script XYZ (which is btw very useful as it saves me from fetching the huge GWT JS output and scanning //# sourceMappingURL=). All the sourcemap parsing and indexing is happening in Eclipse. Of course it is another topic that as of now, SDBG still only supports Chrome. -- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/fb484556-ef5c-43de-aaaf-cd55856837be%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: Code for GSS support (GssResource) pushed. Please review.
Just to summarize: - GSS will be available in GWT 2.7 - GSS will use the CssResource interface and your file needs to end with the .gss extension - GSS will not be enabled by default. To enable it: add set-configuration-property name=CssResource.enableGss value=true / in your module file. - Once enabled, all the CssResource interfaces will be generated by the new GssResourceGenerator - If your app uses still old css file compatible with the GWT-CSS syntax you will need to enable the automatic conversion of these files to GSS. To do that: add set-configuration-property name=CssResource.legacy value=true / in your module file. - The GSS parser and compiler is more strict than the old one. If you meet some issue in this automatic conversion, you can also enable the lenient mode: set-configuration-property name=CssResource.conversionMode value=lenient / - When GSS is enabled, we have to use an attribute gss=true in your uibinder inline style (ui:style) in order to enable GSS We decide to go with the memory conversion because it is the way to move forward. The goal is to enable GSS (with the automatic conversion not enabled by default) and remove the CssResourceGenerator in the next release. So we want people test this strategy in order to fix possible issue and ensure that the automatic conversion is stable. On Wednesday, October 8, 2014 1:49:37 AM UTC+2, Goktug Gokdogan wrote: Can you also summarize why we need in memory conversion as opposed to simpler alternative? So it is documented for the next time when we will have similar discussion :) On Tue, Oct 7, 2014 at 4:00 PM, Daniel Kurka dank...@google.com javascript: wrote: Hi all, summarizing the discussion I just had with Julien: We want to have the in memory conversion in GWT 2.7 (even if it is not battle tested yet), since this is the way to move foward. We can even do a followup release (2.8) as soon as google is using it in production and we sorted all issues out. If GSS is turned on we will: - We will make a decision which generator to use based on file extension - You can not mix gss / css on the same interface - In UiBinder we will add a new attribute to tell that this interface needs gss (default css) - If lib has gss in it the app using that lib needs to have it enabled. I think there is good value in including this in GWT 2.7 since we can ask for external feedback as well, while at the same time making sure its mature within google. -Daniel On Tuesday, October 7, 2014 8:55:27 AM UTC-7, Goktug Gokdogan wrote: I didn't take notes in the meetup so I cannot recall all the reasons (perhaps someone else did?) but I think one of the reasons to introduce in memory conversion was to get rid of the CSS generator code with the GSS release and another one was the possible complications of coexisting css and gss in the same page (e.g. name collisions). Given that we cannot get rid of the CSS generator in 2.7 and if you think everything would be fine with css/gss mixed together (e.g. with prefixes), I'm totally fine with kicking in-memory conversion out and it is definitely not required for 2.7 even if we decide to keep it. However, arguably there might be still value in having an experimental flag to enable GSS as it is not well tested yet. On Tue, Oct 7, 2014 at 1:37 AM, Julien Dramaix julien@gmail.com wrote: I think we are making the things too complex. Initially, we wanted to remove the code of the existing generator for the CssResource and deprecated the existing syntax. It's why we have introduced the in-memory automatic conversion. Now, we've decided to keep the existing generator in GWT 2.7. So I think that we had better to remove this automatic conversion and choose the right generator in fonction of the file extension. People that want to use GSS have to use files with .gss extension. Old files with .css extension will continue to work because the current generator will be used for these kind of files. For the uibinder, we add a temporary attributes (and/or we can foreseen an configuration property that enable GSS by default in UiBinder.) That simplify a lot the implementation, removes three configuration properties (CssResource.enableGss, CssResource.legacy, CssResource.conversionMode) and we support all uses cases of application using third party libraries that will result of a mix of GSS and CSS. So it's simpler for the user and simpler for us. In the next release of GWT, when we remove the code for the existing generator, we will be able to reintroduce this automatic in-memory conversion if we want still to support the old syntax. Now I think we have to mark the current syntax of CssResource as deprecated in favor of GSS. In order to able to remove the generator in the next releases. Another idea: In order to ease the conversion of existing CssResource to GSS, we could maybe during the compilation
[gwt-contrib] Re: Help with testing GWT 2.7 RC1
I'll do some testing, let me know what and how? -- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/f6bab5cf-a9e8-4fbb-b6a2-36f29607d695%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Re: GWT 2.7.0 beta1
It seems that the com.google.gwt.widget.client.TextButton class is no longer packaged in the v2.7.0-beta1 of gwt-user.jar. Where can I find this class ? On Saturday, 18 October 2014 19:54:40 UTC+2, Daniel Kurka wrote: Hi all, since we are adding major features to GWT, we decided to change our release process for GWT 2.7. I just published GWT 2.7.0-beta1 to maven central and our file storage http://goo.gl/pr7km3. We are doing this beta to get external feedback on incremental compilation and GSS. Incremental compilation is now default with GWT 2.7 and replaces, together with Super dev mode, the regular old dev mode. Inside of Google we are already using it for a while now and most of the issues should have already been dealt with, however we also want to make sure that external users that might have slightly different use cases will have a working 2.7.0 release. So please start testing with beta1 and give us lots of feedback on the contributor list https://groups.google.com/forum/#!forum/Google-Web-Toolkit-Contributors or on the issue tracker https://code.google.com/p/google-web-toolkit/issues/list. Please keep in mind that we did not do any release testing on beta1, so there might be issues that you do not expect from a release candidate. Our current plan is to wait until the end of next week for any feedback. If we do not find any serious external issues we will start the testing process for an actual release candidate. -Daniel -- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/9de6bff0-56c2-4c27-80da-d9cfbffca481%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: GWT 2.7.0 beta1
com.google.gwt.widget.* was deprecated and removed in the 2.7 release. You can get a copy of the files here: https://code.google.com/p/google-web-toolkit/source/browse/trunk/user/src/com/google/gwt/widget/client?r=9884 On Thu, Oct 23, 2014 at 7:57 AM, Stefan Lecho stle...@gmail.com wrote: It seems that the com.google.gwt.widget.client.TextButton class is no longer packaged in the v2.7.0-beta1 of gwt-user.jar. Where can I find this class ? On Saturday, 18 October 2014 19:54:40 UTC+2, Daniel Kurka wrote: Hi all, since we are adding major features to GWT, we decided to change our release process for GWT 2.7. I just published GWT 2.7.0-beta1 to maven central and our file storage http://goo.gl/pr7km3. We are doing this beta to get external feedback on incremental compilation and GSS. Incremental compilation is now default with GWT 2.7 and replaces, together with Super dev mode, the regular old dev mode. Inside of Google we are already using it for a while now and most of the issues should have already been dealt with, however we also want to make sure that external users that might have slightly different use cases will have a working 2.7.0 release. So please start testing with beta1 and give us lots of feedback on the contributor list https://groups.google.com/forum/#!forum/Google-Web-Toolkit-Contributors or on the issue tracker https://code.google.com/p/google-web-toolkit/issues/list. Please keep in mind that we did not do any release testing on beta1, so there might be issues that you do not expect from a release candidate. Our current plan is to wait until the end of next week for any feedback. If we do not find any serious external issues we will start the testing process for an actual release candidate. -Daniel -- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/9de6bff0-56c2-4c27-80da-d9cfbffca481%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/9de6bff0-56c2-4c27-80da-d9cfbffca481%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA1fo-jiP1sQy4GMkV95EuWxk%2Bk8Y6zWomrzT%3DLL-iSHPg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: GWT 2.7.0 beta1
Thanks for pointing me to the source code. If I want to use v2.7.0-beta1, with which classes should I replace them ? On Friday, 24 October 2014 07:01:27 UTC+2, Goktug Gokdogan wrote: com.google.gwt.widget.* was deprecated and removed in the 2.7 release. You can get a copy of the files here: https://code.google.com/p/google-web-toolkit/source/browse/trunk/user/src/com/google/gwt/widget/client?r=9884 On Thu, Oct 23, 2014 at 7:57 AM, Stefan Lecho stl...@gmail.com javascript: wrote: It seems that the com.google.gwt.widget.client.TextButton class is no longer packaged in the v2.7.0-beta1 of gwt-user.jar. Where can I find this class ? On Saturday, 18 October 2014 19:54:40 UTC+2, Daniel Kurka wrote: Hi all, since we are adding major features to GWT, we decided to change our release process for GWT 2.7. I just published GWT 2.7.0-beta1 to maven central and our file storage http://goo.gl/pr7km3. We are doing this beta to get external feedback on incremental compilation and GSS. Incremental compilation is now default with GWT 2.7 and replaces, together with Super dev mode, the regular old dev mode. Inside of Google we are already using it for a while now and most of the issues should have already been dealt with, however we also want to make sure that external users that might have slightly different use cases will have a working 2.7.0 release. So please start testing with beta1 and give us lots of feedback on the contributor list https://groups.google.com/forum/#!forum/Google-Web-Toolkit-Contributors or on the issue tracker https://code.google.com/p/google-web-toolkit/issues/list. Please keep in mind that we did not do any release testing on beta1, so there might be issues that you do not expect from a release candidate. Our current plan is to wait until the end of next week for any feedback. If we do not find any serious external issues we will start the testing process for an actual release candidate. -Daniel -- 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 javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/9de6bff0-56c2-4c27-80da-d9cfbffca481%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/9de6bff0-56c2-4c27-80da-d9cfbffca481%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/e342662b-7fcd-47a0-9b48-ae09eb80bec1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
