Re: [gwt-contrib] Re: GWT 2.7 release plan
Hi, There are a bunch of Elemental patches which fix some issues, some of them manifested when running its test suite which was not enabled, and the others to use elemental json as a replacement of the controversial org.json. I know elemental 2.0 would be redesigned or rewritten for 3.0, but I think we could leave a little bit better version of elemental 1.0 in 2.7.0. Could anyone take a look to those patches? There is no official maintainer of it, so maybe Ray is the most suitable reviewer? Thanks - Manolo On Thu, Oct 2, 2014 at 3:22 AM, 'Brian Slesinsky' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: It's experimental and hidden behind a flag, but it's there. On Wed, Oct 1, 2014 at 6:20 PM, Cristian Rinaldi csrina...@gmail.com wrote: - JsInterop Preview is part of the release? El miércoles, 1 de octubre de 2014 16:15:26 UTC-3, Daniel Kurka escribió: Hi all, we just settled on a GWT 2.7 release plan: - We *code freeze* on *October 7th* and branch for GWT 2.7. - As soon as we have the *remaining patches submitted*, we put out a beta1 build, this should be no later than *October 7th.* - Putting out a *beta1 externally* allows us to collect feedback on the new super dev mode integration externally as well. - We are going to *flip incremental to default* tomorrow and *wait for 1-2 weeks* for google internal feedback, if there is no serious issues we are going to *put out RC1* - GWT 2.7 will still be compatible with Java 6. Patches / Fixes that need to go in: - Recompile on reload: https://gwt-review.googlesource.com/#/c/9323/ ( dankurka) - Sending the wrong permutation to the client in SDM, if no files have changed (dankurka). - Investigate why some people are seeing errors with incremental not restricting to one permutation (dankurka). - Public directories are not copied o the war directory when using SDM (skybrian). - Restore Java 6 compatibility (skybrian). - Document limitations of JsonUtils.safeEval and discourage usage (goktug) (promote Json.parse) Patches that are nice to have: - Improve exception logging in SDM (goktug). *If you have any outstanding patches that you thing need to go into GWT 2.7, please bring them to our attention, by replying to this thread or adding me as a reviewer on Gerrit and setting the topic to GWT2.7.* -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/1d5a4369-e03d-47ba-b8dd-5031e5460751%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/1d5a4369-e03d-47ba-b8dd-5031e5460751%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/CA%2B%2BRBT-M5mAXmj5Ox8iQihjzFFinLM%2Bc57tmdD1JGwEMxKJHAw%40mail.gmail.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2B%2BRBT-M5mAXmj5Ox8iQihjzFFinLM%2Bc57tmdD1JGwEMxKJHAw%40mail.gmail.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/CAM28XAvDLRsQFsWV320q2%3Dpvw_oH46N47OvcpCp%3D07wkYbMhgw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] bug with the new snapshot
This morning, I've updated my GWT snapshot to the last one and I'm not able
to run the super dev mode (with the flag -superDevMode) for my applications.
The problem comes from that the .nocache.js tries to add the compilation
dialog to the body before the body is initialized.
Error:
Uncaught TypeError: Cannot read property 'appendChild' of null
in:
Dialog.prototype.show = function() {
$doc.body.appendChild(this.__overlay);
$doc.body.appendChild(this.__dialog);
};
$doc.body is null when the method is called. This method should be called
when the html is fully loaded.
If I include the nocache.js script at the end of the body instead of in the
head of the html, it works fine.
Julien
--
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/CABb_3%3D5%3DMU8--RcXrHwjM8ZSPvB%2B2MG-7nAvF1Sq8BjDEeJ5Kw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: -src in DevMode EntryPoint
There are already some arguments not needed for DevMode which are passed to the codeserver like -XjsInteropMode, so to me makes sense to add it as well. On Tue, Sep 30, 2014 at 1:50 AM, Colin Alworth niloc...@gmail.com wrote: Its possible that we can get away without an explicit way to add this (like classic Dev Mode has done so far), but -src makes multi-project development so much saner. No longer do you need to depend on your IDE to do the Right Thing (i.e. use *that* project as a jar from local maven repo, but *that* one over there should be raw sources, since the one former has generated content but the latter is being edited constantly). Leaving this out puts the onus on the IDE tooling to get it right every time, or provide an alternate mechanism - you can get pretty close with the (often wrong but at least easy to customize) Eclipse Run Configuration wiring, but on the other hand the (totally un-customizable, but at least right 80% of the time) IDEA Run Configurations that are shipped with Ultimate have to be right out of the box, or you are just stuck (as is true for 12, 13, and the 14 EAP). I can't speak for Netbeans (though I've seen a recent resurgence of GWT users making use of it!). Is there a reason that CodeServer has this feature but DevMode doesn't? Should DevMode have had it all along, or was this just a hack in CodeServer that should be phased out? -- 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/fc562a17-0f4c-4573-9f18-9b5ea13ad723%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/fc562a17-0f4c-4573-9f18-9b5ea13ad723%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/CAM28XAux-mHZB%2Bm4o8rFMyGBROtEi7kXWsyrU%3D6feVgeXdRZFQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Compiler Faiure
On Thu, Oct 2, 2014 at 12:28 AM, 'Ray Cromwell' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: We kind of knew this sort of incompatibility would happen, but I still think GWT should continue get out of the business of rebasing everything. We should even have a version of the JAR that can use dynamic dependencies. I think this is a good option. Can we go with it? On Wed, Oct 1, 2014 at 3:16 PM, Manuel Carrasco Moñino man...@apache.org wrote: Thank Roberto, that is the key, everything works if I exclude the asm transitive dependency in my pom dependency groupIdorg.eclipse.jetty/groupId artifactIdjetty-annotations/artifactId exclusions exclusion artifactIdorg.objectweb.asm/artifactId groupIdorg.eclipse.jetty.orbit/groupId /exclusion /exclusions On Wed, Oct 1, 2014 at 11:46 PM, 'Roberto Lublinerman' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: This seems to be the error: java.lang.IncompatibleClassChangeError: class com.google.gwt.dev.javac.asm.CollectMethodData has interface org.objectweb.asm.MethodVisitor as super class and the problem seems to be that you have ASM 5 in your class path. (It seems that MethodVisitor was an interface in ASM 4 and is now an abstract class. 2.7 no longer rebases ASM On Wed, Oct 1, 2014 at 2:33 PM, Manuel Carrasco Moñino man...@apache.org wrote: Hi all, Do anyone knows what could change lately which makes the compiler fail if jetty annotations is in your classpath. The way to reproduce is compiling any project which jetty-annotations.jar before before gwt-dev.jar. Attached trace. -- 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/CAM28XAtxtLYTr43FBqwm7-CLFMkGVcS2Oi9-vPP6MdpkqqPw_w%40mail.gmail.com . 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/CAC7T7gmTDSDYfCPzVg5o1AEXzHNcrXhLL91iWv_n%2BJsVJ-oNxA%40mail.gmail.com . 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/CAM28XAvmpneRqr1LLry_C612U7PsdY-raj9fPo_5ysAJ3qoGaw%40mail.gmail.com . 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/CAPVRV7fUFGt8ksPPoPTwhxUN2xBjVLLoJ%2B%3DbooMpDoy6cN5wWg%40mail.gmail.com . 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/CAM28XAsJLT%2BGtNnx8i3%2Bj6W6L98Dpo1gbEfTjZi_SrfK2AMphQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Compiler Faiure
On Thursday, October 2, 2014 2:33:29 PM UTC+2, Manuel Carrasco Moñino wrote: On Thu, Oct 2, 2014 at 12:28 AM, 'Ray Cromwell' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: We kind of knew this sort of incompatibility would happen, but I still think GWT should continue get out of the business of rebasing everything. We should even have a version of the JAR that can use dynamic dependencies. I think this is a good option. Can we go with it? I'm currently updating the scripts that push JARs to Maven to unbundle ASM, along with the POMs to add the dependency on ASM. I'll also add dependencyManagement to com.google.gwt:gwt and com.google.web.bindery:requestfactory (aka make them bills of material) so you could use them with scopeimport/scope in your dependencyManagement to make sure you use everything with the same version, even when some deps are transitive (e.g. you use a lib that depends on gwt-dev with a version different than the one you use for gwt-user; dependencyManagement helps solve these issues). Other deps we could easily replace with non-rebased ones are Guava and Protobuf. -- 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/7b0c9a48-094a-4782-a362-52828a9505ee%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Spam logs: Could not find an exact match rule. Using 'closest' rule
Reverting the binding sounds good to me. Please add a comment to the binding; it might probably be bound to something else but not tested. On Wed, Oct 1, 2014 at 9:39 PM, Colin Alworth niloc...@gmail.com wrote: It looks like changes to a few rebind rules are generating some new logspam when any GWT app compiles. Specifically, I'm seeing FocusImpl and LayoutImpl, though its possible there are others I haven't seen yet. From the dynatable example we can see the FocusImpl spam: gwtc: [java] Compiling module com.google.gwt.sample.dynatable.DynaTable [java]Computing all possible rebind results for 'com.google.gwt.user.client.ui.impl.FocusImpl' [java] Rebinding com.google.gwt.user.client.ui.impl.FocusImpl * [java] Could not find an exact match rule. Using 'closest' rule replace-with class='com.google.gwt.user.client.ui.impl.FocusImplIE6'/ based on fall back values. You may need to implement a specific binding in case the fall back behavior does not replace the missing binding* [java]Compiling 5 permutations [java] Compiling permutation 0... [java] Process output [java] Compiling [java] Compiling permutation 1... [java] Compiling permutation 2... [java] Compiling permutation 3... First, the rules themselves: !-- Firefox uses a hidden input to set accesskeys -- replace-with class=com.google.gwt.user.client.ui.impl.FocusImplStandard when-type-is class=com.google.gwt.user.client.ui.impl.FocusImpl/ when-property-is name=user.agent value=gecko1_8/ /replace-with !-- Safari uses a hidden input to set accesskeys and -- !-- fires focus/blur after a timeout -- replace-with class=com.google.gwt.user.client.ui.impl.FocusImplSafari when-type-is class=com.google.gwt.user.client.ui.impl.FocusImpl/ when-property-is name=user.agent value=safari/ /replace-with !-- IE's implementation traps exceptions on invalid setFocus() -- replace-with class=com.google.gwt.user.client.ui.impl.FocusImplIE6 when-type-is class=com.google.gwt.user.client.ui.impl.FocusImpl/ all any when-property-is name=user.agent value=ie6/ when-property-is name=user.agent value=ie8/ /any none when-property-is name=user.agent value=ie9/ /none /all /replace-with No express binding of FocusImpl to itself, or to Standard (interestingly Standard really seems to mean Gecko, at least according to that comment, calling out a FF specific issue). I can't comment much on that just yet, though I might make a suggestion later. This code is as a result of https://gwt-review.googlesource.com/#/c/5055/ (or https://gwt.googlesource.com/gwt/+/040b3e4392186e48689a6fc1f19cdf294f2b5651 if you like), ostensibly to make IE9+ use FocusImpl instead of FocusImplIE6 (or Standard, for example). [java]Computing all possible rebind results for 'com.google.gwt.user.client.ui.impl.FocusImpl' ... [java] Found better fallback match for replace-with class='com.google.gwt.user.client.ui.impl.FormPanelImpl'/ [java] Checking rule replace-with class='com.google.gwt.user.client.ui.impl.FocusImplIE6'/ [java] Checking if all subconditions are true (all) [java]when-type-is class='com.google.gwt.user.client.ui.impl.FocusImpl'/ [java] Yes, the requested type was an exact match [java]Checking if all subconditions are true (all) [java] Checking if any subcondition is true (any) [java] when-property-is name='user.agent' value='ie8'/ [java] Property value is '*ie9*' [java] Property value 'ie8' is the fallback of '[[ie9]]' [java] No, the value did not match [java] No: All subconditions were false [java] No: One or more subconditions was false [java]No: One or more subconditions was false [java] Rule did not match [java] Found better fallback match for replace-with class='com.google.gwt.user.client.ui.impl.FocusImplIE6'/ [java] Checking rule replace-with class='com.google.gwt.user.client.ui.impl.FocusImplSafari'/ [java] Checking if all subconditions are true (all) [java]when-type-is class='com.google.gwt.user.client.ui.impl.FocusImpl'/ [java] Yes, the requested type was an exact match [java]when-property-is name='user.agent' value='safari'/ [java] Property value is 'ie9' [java] No, the value did not match [java]No: One or more subconditions was false [java] Rule did not match [java] Checking rule replace-with class='com.google.gwt.user.client.ui.impl.FocusImplStandard'/ [java]
Re: [gwt-contrib] Compiler Faiure
Thank Thomas for fixing this. On Thu, Oct 2, 2014 at 3:26 PM, Thomas Broyer t.bro...@gmail.com wrote: On Thursday, October 2, 2014 2:33:29 PM UTC+2, Manuel Carrasco Moñino wrote: On Thu, Oct 2, 2014 at 12:28 AM, 'Ray Cromwell' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: We kind of knew this sort of incompatibility would happen, but I still think GWT should continue get out of the business of rebasing everything. We should even have a version of the JAR that can use dynamic dependencies. I think this is a good option. Can we go with it? I'm currently updating the scripts that push JARs to Maven to unbundle ASM, along with the POMs to add the dependency on ASM. I'll also add dependencyManagement to com.google.gwt:gwt and com.google.web.bindery:requestfactory (aka make them bills of material) so you could use them with scopeimport/scope in your dependencyManagement to make sure you use everything with the same version, even when some deps are transitive (e.g. you use a lib that depends on gwt-dev with a version different than the one you use for gwt-user; dependencyManagement helps solve these issues). Other deps we could easily replace with non-rebased ones are Guava and Protobuf. -- 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/7b0c9a48-094a-4782-a362-52828a9505ee%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/7b0c9a48-094a-4782-a362-52828a9505ee%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/CAM28XAvun71Xkf2rQc%2BDsJj5%3DiW3LjAQ%3D9gqejzAGXz5TJCkGQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: GWT 2.7 release plan
On Thu, Oct 2, 2014 at 12:41 AM, Manuel Carrasco Moñino man...@apache.org wrote: Hi, There are a bunch of Elemental patches which fix some issues, some of them manifested when running its test suite which was not enabled, and the others to use elemental json as a replacement of the controversial org.json. I know elemental 2.0 would be redesigned or rewritten for 3.0, but I think we could leave a little bit better version of elemental 1.0 in 2.7.0. Could anyone take a look to those patches? There is no official maintainer of it, so maybe Ray is the most suitable reviewer? Ray might not have the time. I'm proposing t.broyer to approve these changes. Thanks - Manolo On Thu, Oct 2, 2014 at 3:22 AM, 'Brian Slesinsky' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: It's experimental and hidden behind a flag, but it's there. On Wed, Oct 1, 2014 at 6:20 PM, Cristian Rinaldi csrina...@gmail.com wrote: - JsInterop Preview is part of the release? El miércoles, 1 de octubre de 2014 16:15:26 UTC-3, Daniel Kurka escribió: Hi all, we just settled on a GWT 2.7 release plan: - We *code freeze* on *October 7th* and branch for GWT 2.7. - As soon as we have the *remaining patches submitted*, we put out a beta1 build, this should be no later than *October 7th.* - Putting out a *beta1 externally* allows us to collect feedback on the new super dev mode integration externally as well. - We are going to *flip incremental to default* tomorrow and *wait for 1-2 weeks* for google internal feedback, if there is no serious issues we are going to *put out RC1* - GWT 2.7 will still be compatible with Java 6. Patches / Fixes that need to go in: - Recompile on reload: https://gwt-review.googlesource.com/#/c/9323/ ( dankurka) - Sending the wrong permutation to the client in SDM, if no files have changed (dankurka). - Investigate why some people are seeing errors with incremental not restricting to one permutation (dankurka). - Public directories are not copied o the war directory when using SDM (skybrian). - Restore Java 6 compatibility (skybrian). - Document limitations of JsonUtils.safeEval and discourage usage (goktug) (promote Json.parse) Patches that are nice to have: - Improve exception logging in SDM (goktug). *If you have any outstanding patches that you thing need to go into GWT 2.7, please bring them to our attention, by replying to this thread or adding me as a reviewer on Gerrit and setting the topic to GWT2.7.* -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/1d5a4369-e03d-47ba-b8dd-5031e5460751%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/1d5a4369-e03d-47ba-b8dd-5031e5460751%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/CA%2B%2BRBT-M5mAXmj5Ox8iQihjzFFinLM%2Bc57tmdD1JGwEMxKJHAw%40mail.gmail.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2B%2BRBT-M5mAXmj5Ox8iQihjzFFinLM%2Bc57tmdD1JGwEMxKJHAw%40mail.gmail.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/CAM28XAvDLRsQFsWV320q2%3Dpvw_oH46N47OvcpCp%3D07wkYbMhgw%40mail.gmail.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAvDLRsQFsWV320q2%3Dpvw_oH46N47OvcpCp%3D07wkYbMhgw%40mail.gmail.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%3DyUA26-pLPVd1%2BYjm55BRSubEngmxz_%3D31YtZq8%2BMcsudyhg%40mail.gmail.com. For more
Re: [gwt-contrib] Removal of IE6/7 specific code from the code base
There are still 80+ references to IE6 in the code base. Still looking for more patches... On Sat, Jul 12, 2014 at 6:15 AM, Jens jens.nehlme...@gmail.com wrote: Michael, you should track https://gwt-review.googlesource.com/#/c/5304/ so you don't do the same work again. -- J. -- 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/6eb89ab9-5109-4658-9dae-95e14072dd3c%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/6eb89ab9-5109-4658-9dae-95e14072dd3c%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%3DyUA2G8PvQOe2Uguay0YJquojixb89kfbxdTPPv0kMsrXa2w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Spam logs: Could not find an exact match rule. Using 'closest' rule
Sorry Goktug, I don't follow - what should the comment indicate? In the old code, IE9 was expressly bound to the IE6 imp, in the new (to be reverted) code, it was expressly *not* bound to the IE6 impl, but it was the closest fallback anyway. Are you suggesting that the comment should point out that IE9 probably shouldn't be bound in that way (though it works, and may not work if differently bound)? Thanks for any clarification, Colin On Thu, Oct 2, 2014 at 11:05 AM, 'Goktug Gokdogan' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: Reverting the binding sounds good to me. Please add a comment to the binding; it might probably be bound to something else but not tested. On Wed, Oct 1, 2014 at 9:39 PM, Colin Alworth niloc...@gmail.com wrote: It looks like changes to a few rebind rules are generating some new logspam when any GWT app compiles. Specifically, I'm seeing FocusImpl and LayoutImpl, though its possible there are others I haven't seen yet. From the dynatable example we can see the FocusImpl spam: gwtc: [java] Compiling module com.google.gwt.sample.dynatable.DynaTable [java]Computing all possible rebind results for 'com.google.gwt.user.client.ui.impl.FocusImpl' [java] Rebinding com.google.gwt.user.client.ui.impl.FocusImpl * [java] Could not find an exact match rule. Using 'closest' rule replace-with class='com.google.gwt.user.client.ui.impl.FocusImplIE6'/ based on fall back values. You may need to implement a specific binding in case the fall back behavior does not replace the missing binding* [java]Compiling 5 permutations [java] Compiling permutation 0... [java] Process output [java] Compiling [java] Compiling permutation 1... [java] Compiling permutation 2... [java] Compiling permutation 3... First, the rules themselves: !-- Firefox uses a hidden input to set accesskeys -- replace-with class=com.google.gwt.user.client.ui.impl.FocusImplStandard when-type-is class=com.google.gwt.user.client.ui.impl.FocusImpl/ when-property-is name=user.agent value=gecko1_8/ /replace-with !-- Safari uses a hidden input to set accesskeys and -- !-- fires focus/blur after a timeout -- replace-with class=com.google.gwt.user.client.ui.impl.FocusImplSafari when-type-is class=com.google.gwt.user.client.ui.impl.FocusImpl/ when-property-is name=user.agent value=safari/ /replace-with !-- IE's implementation traps exceptions on invalid setFocus() -- replace-with class=com.google.gwt.user.client.ui.impl.FocusImplIE6 when-type-is class=com.google.gwt.user.client.ui.impl.FocusImpl/ all any when-property-is name=user.agent value=ie6/ when-property-is name=user.agent value=ie8/ /any none when-property-is name=user.agent value=ie9/ /none /all /replace-with No express binding of FocusImpl to itself, or to Standard (interestingly Standard really seems to mean Gecko, at least according to that comment, calling out a FF specific issue). I can't comment much on that just yet, though I might make a suggestion later. This code is as a result of https://gwt-review.googlesource.com/#/c/5055/ (or https://gwt.googlesource.com/gwt/+/040b3e4392186e48689a6fc1f19cdf294f2b5651 if you like), ostensibly to make IE9+ use FocusImpl instead of FocusImplIE6 (or Standard, for example). [java]Computing all possible rebind results for 'com.google.gwt.user.client.ui.impl.FocusImpl' ... [java] Found better fallback match for replace-with class='com.google.gwt.user.client.ui.impl.FormPanelImpl'/ [java] Checking rule replace-with class='com.google.gwt.user.client.ui.impl.FocusImplIE6'/ [java] Checking if all subconditions are true (all) [java]when-type-is class='com.google.gwt.user.client.ui.impl.FocusImpl'/ [java] Yes, the requested type was an exact match [java]Checking if all subconditions are true (all) [java] Checking if any subcondition is true (any) [java] when-property-is name='user.agent' value='ie8'/ [java] Property value is '*ie9*' [java] Property value 'ie8' is the fallback of '[[ie9]]' [java] No, the value did not match [java] No: All subconditions were false [java] No: One or more subconditions was false [java]No: One or more subconditions was false [java] Rule did not match [java] Found better fallback match for replace-with class='com.google.gwt.user.client.ui.impl.FocusImplIE6'/ [java] Checking rule replace-with class='com.google.gwt.user.client.ui.impl.FocusImplSafari'/ [java] Checking if all
Re: [gwt-contrib] Spam logs: Could not find an exact match rule. Using 'closest' rule
The comment is just to indicate that IE9 is bound to legacy FocusImplIE6 only because we didn't test is with a more modern implementation. So later when somebody looks at the code for cleanup will not think that we carefully tested and decided to use the Iegacy implementation. On Thu, Oct 2, 2014 at 10:07 AM, Colin Alworth niloc...@gmail.com wrote: Sorry Goktug, I don't follow - what should the comment indicate? In the old code, IE9 was expressly bound to the IE6 imp, in the new (to be reverted) code, it was expressly *not* bound to the IE6 impl, but it was the closest fallback anyway. Are you suggesting that the comment should point out that IE9 probably shouldn't be bound in that way (though it works, and may not work if differently bound)? Thanks for any clarification, Colin On Thu, Oct 2, 2014 at 11:05 AM, 'Goktug Gokdogan' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: Reverting the binding sounds good to me. Please add a comment to the binding; it might probably be bound to something else but not tested. On Wed, Oct 1, 2014 at 9:39 PM, Colin Alworth niloc...@gmail.com wrote: It looks like changes to a few rebind rules are generating some new logspam when any GWT app compiles. Specifically, I'm seeing FocusImpl and LayoutImpl, though its possible there are others I haven't seen yet. From the dynatable example we can see the FocusImpl spam: gwtc: [java] Compiling module com.google.gwt.sample.dynatable.DynaTable [java]Computing all possible rebind results for 'com.google.gwt.user.client.ui.impl.FocusImpl' [java] Rebinding com.google.gwt.user.client.ui.impl.FocusImpl * [java] Could not find an exact match rule. Using 'closest' rule replace-with class='com.google.gwt.user.client.ui.impl.FocusImplIE6'/ based on fall back values. You may need to implement a specific binding in case the fall back behavior does not replace the missing binding* [java]Compiling 5 permutations [java] Compiling permutation 0... [java] Process output [java] Compiling [java] Compiling permutation 1... [java] Compiling permutation 2... [java] Compiling permutation 3... First, the rules themselves: !-- Firefox uses a hidden input to set accesskeys -- replace-with class=com.google.gwt.user.client.ui.impl.FocusImplStandard when-type-is class=com.google.gwt.user.client.ui.impl.FocusImpl/ when-property-is name=user.agent value=gecko1_8/ /replace-with !-- Safari uses a hidden input to set accesskeys and -- !-- fires focus/blur after a timeout -- replace-with class=com.google.gwt.user.client.ui.impl.FocusImplSafari when-type-is class=com.google.gwt.user.client.ui.impl.FocusImpl/ when-property-is name=user.agent value=safari/ /replace-with !-- IE's implementation traps exceptions on invalid setFocus() -- replace-with class=com.google.gwt.user.client.ui.impl.FocusImplIE6 when-type-is class=com.google.gwt.user.client.ui.impl.FocusImpl/ all any when-property-is name=user.agent value=ie6/ when-property-is name=user.agent value=ie8/ /any none when-property-is name=user.agent value=ie9/ /none /all /replace-with No express binding of FocusImpl to itself, or to Standard (interestingly Standard really seems to mean Gecko, at least according to that comment, calling out a FF specific issue). I can't comment much on that just yet, though I might make a suggestion later. This code is as a result of https://gwt-review.googlesource.com/#/c/5055/ (or https://gwt.googlesource.com/gwt/+/040b3e4392186e48689a6fc1f19cdf294f2b5651 if you like), ostensibly to make IE9+ use FocusImpl instead of FocusImplIE6 (or Standard, for example). [java]Computing all possible rebind results for 'com.google.gwt.user.client.ui.impl.FocusImpl' ... [java] Found better fallback match for replace-with class='com.google.gwt.user.client.ui.impl.FormPanelImpl'/ [java] Checking rule replace-with class='com.google.gwt.user.client.ui.impl.FocusImplIE6'/ [java] Checking if all subconditions are true (all) [java]when-type-is class='com.google.gwt.user.client.ui.impl.FocusImpl'/ [java] Yes, the requested type was an exact match [java]Checking if all subconditions are true (all) [java] Checking if any subcondition is true (any) [java] when-property-is name='user.agent' value='ie8'/ [java] Property value is '*ie9*' [java] Property value 'ie8' is the fallback of '[[ie9]]' [java] No, the value did not match [java] No: All subconditions were false [java] No: One or more subconditions was false
Re: [gwt-contrib] Spam logs: Could not find an exact match rule. Using 'closest' rule
Maybe someone wants to mark one of the issues as duplicated since some time ago I also created an issue for it as I haven't seen the one that Colin has found. However in our compiles it is not only FocusImpl and LayoutImpl but also InternalJsHashCodeMap and InternalJsStringMap, see: https://code.google.com/p/google-web-toolkit/issues/detail?id=8848 -- J. -- 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/a1fef739-ef78-429f-848e-5190ba14770d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Starting super dev mode in debug : performance very bad
Hi, I've tried to run the super dev mode (dev mode with flag -superDevMode) in debug in order to debug my server side code. The problem is that the superdevmode server is also started in debug mode and the time needed for the initial compilation is very very bad. This is an example of time needed by the first compilation with a small application: Linking per-type JS with 3891 new types. prelink JS size = 8177175 prelink sourcemap = 8177175 bytes and 194766 lines postlink JS size = 8054573 postlink sourcemap = 8054573 bytes and 191812 lines Source Maps Enabled Compile of permutations succeeded Compilation succeeded -- 418,016s Linking into /var/folders/qc/ktqtdtdx6790j436xz3jqw3rgn/T/gwt-codeserver-5506406643949710211.tmp/com.caerus.kaam.KaamSdm/compile-3/war/kaam; Writing extras to /var/folders/qc/ktqtdtdx6790j436xz3jqw3rgn/T/gwt-codeserver-5506406643949710211.tmp/com.caerus.kaam.KaamSdm/compile-3/extras/kaam Link succeeded Linking succeeded -- 10,692s 430,813s total -- Compile completed If you don't change anything to the code and recompilation of the application takes 2,147s. For your info, the same application running not in debug mode takes 20s for the initial compilation. That makes simply the debug mode impossible to use and you are not able to debug your server side code anymore. The workaround is to run two separate processes, one with -superDevMode and --nostartServer flags and another without the -superDevMode flag that you can start in debug mode. I don't know if we can do something on the superdevmode side, maybe the solution can come from the IDE directly where the superdevmode process is never launched in debug mode ? Any thought ? Julien PS: I'm using Intellij13 -- 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/CABb_3%3D7DgGmkkQVe3mQgXxT%2B7rjbM%2BMOCv7TVjRPa08h%3DDPiEw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Starting super dev mode in debug : performance very bad
Hey I don't think there's anything special we're doing that would be particularly slow in a JVM debugger. Maybe this is a stupid question but, do you have any conditional breakpoints set? Those can be particularly slow. Also maybe the debug process costs extra RAM, putting the JVM at it's RAM limit, then causing a lot of really slow GCs? You could try raising the RAM. On Thu, Oct 2, 2014 at 12:37 PM, Julien Dramaix julien.dram...@gmail.com wrote: Hi, I've tried to run the super dev mode (dev mode with flag -superDevMode) in debug in order to debug my server side code. The problem is that the superdevmode server is also started in debug mode and the time needed for the initial compilation is very very bad. This is an example of time needed by the first compilation with a small application: Linking per-type JS with 3891 new types. prelink JS size = 8177175 prelink sourcemap = 8177175 bytes and 194766 lines postlink JS size = 8054573 postlink sourcemap = 8054573 bytes and 191812 lines Source Maps Enabled Compile of permutations succeeded Compilation succeeded -- 418,016s Linking into /var/folders/qc/ktqtdtdx6790j436xz3jqw3rgn/T/gwt-codeserver-5506406643949710211.tmp/com.caerus.kaam.KaamSdm/compile-3/war/kaam; Writing extras to /var/folders/qc/ktqtdtdx6790j436xz3jqw3rgn/T/gwt-codeserver-5506406643949710211.tmp/com.caerus.kaam.KaamSdm/compile-3/extras/kaam Link succeeded Linking succeeded -- 10,692s 430,813s total -- Compile completed If you don't change anything to the code and recompilation of the application takes 2,147s. For your info, the same application running not in debug mode takes 20s for the initial compilation. That makes simply the debug mode impossible to use and you are not able to debug your server side code anymore. The workaround is to run two separate processes, one with -superDevMode and --nostartServer flags and another without the -superDevMode flag that you can start in debug mode. I don't know if we can do something on the superdevmode side, maybe the solution can come from the IDE directly where the superdevmode process is never launched in debug mode ? Any thought ? Julien PS: I'm using Intellij13 -- 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/CABb_3%3D7DgGmkkQVe3mQgXxT%2B7rjbM%2BMOCv7TVjRPa08h%3DDPiEw%40mail.gmail.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D7DgGmkkQVe3mQgXxT%2B7rjbM%2BMOCv7TVjRPa08h%3DDPiEw%40mail.gmail.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/CAFw3gJ8tiSVZPm5XV08TPK%3Dm6v6cKxdFeLZ0QUZ_iYHPGTZcBA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Starting super dev mode in debug : performance very bad
yep sorry, that was due to a old breakpoint I've put in the ClientBundleGenerator... Thanks! On Thu, Oct 2, 2014 at 10:43 PM, 'John Stalcup' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: Hey I don't think there's anything special we're doing that would be particularly slow in a JVM debugger. Maybe this is a stupid question but, do you have any conditional breakpoints set? Those can be particularly slow. Also maybe the debug process costs extra RAM, putting the JVM at it's RAM limit, then causing a lot of really slow GCs? You could try raising the RAM. On Thu, Oct 2, 2014 at 12:37 PM, Julien Dramaix julien.dram...@gmail.com wrote: Hi, I've tried to run the super dev mode (dev mode with flag -superDevMode) in debug in order to debug my server side code. The problem is that the superdevmode server is also started in debug mode and the time needed for the initial compilation is very very bad. This is an example of time needed by the first compilation with a small application: Linking per-type JS with 3891 new types. prelink JS size = 8177175 prelink sourcemap = 8177175 bytes and 194766 lines postlink JS size = 8054573 postlink sourcemap = 8054573 bytes and 191812 lines Source Maps Enabled Compile of permutations succeeded Compilation succeeded -- 418,016s Linking into /var/folders/qc/ktqtdtdx6790j436xz3jqw3rgn/T/gwt-codeserver-5506406643949710211.tmp/com.caerus.kaam.KaamSdm/compile-3/war/kaam; Writing extras to /var/folders/qc/ktqtdtdx6790j436xz3jqw3rgn/T/gwt-codeserver-5506406643949710211.tmp/com.caerus.kaam.KaamSdm/compile-3/extras/kaam Link succeeded Linking succeeded -- 10,692s 430,813s total -- Compile completed If you don't change anything to the code and recompilation of the application takes 2,147s. For your info, the same application running not in debug mode takes 20s for the initial compilation. That makes simply the debug mode impossible to use and you are not able to debug your server side code anymore. The workaround is to run two separate processes, one with -superDevMode and --nostartServer flags and another without the -superDevMode flag that you can start in debug mode. I don't know if we can do something on the superdevmode side, maybe the solution can come from the IDE directly where the superdevmode process is never launched in debug mode ? Any thought ? Julien PS: I'm using Intellij13 -- 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/CABb_3%3D7DgGmkkQVe3mQgXxT%2B7rjbM%2BMOCv7TVjRPa08h%3DDPiEw%40mail.gmail.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D7DgGmkkQVe3mQgXxT%2B7rjbM%2BMOCv7TVjRPa08h%3DDPiEw%40mail.gmail.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/CAFw3gJ8tiSVZPm5XV08TPK%3Dm6v6cKxdFeLZ0QUZ_iYHPGTZcBA%40mail.gmail.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAFw3gJ8tiSVZPm5XV08TPK%3Dm6v6cKxdFeLZ0QUZ_iYHPGTZcBA%40mail.gmail.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/CABb_3%3D6tp1Z_9Dd2vFv5HFkJBqZe4to%2BcVyPX0h-5iccRZuO1A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: GWT 2.7 release plan
How can JsInterop be activated in GWT 2.7? What flag does it? Am Donnerstag, 2. Oktober 2014 03:22:56 UTC+2 schrieb Brian Slesinsky: It's experimental and hidden behind a flag, but it's there. On Wed, Oct 1, 2014 at 6:20 PM, Cristian Rinaldi csri...@gmail.com javascript: wrote: - JsInterop Preview is part of the release? El miércoles, 1 de octubre de 2014 16:15:26 UTC-3, Daniel Kurka escribió: Hi all, we just settled on a GWT 2.7 release plan: - We *code freeze* on *October 7th* and branch for GWT 2.7. - As soon as we have the *remaining patches submitted*, we put out a beta1 build, this should be no later than *October 7th.* - Putting out a *beta1 externally* allows us to collect feedback on the new super dev mode integration externally as well. - We are going to *flip incremental to default* tomorrow and *wait for 1-2 weeks* for google internal feedback, if there is no serious issues we are going to *put out RC1* - GWT 2.7 will still be compatible with Java 6. Patches / Fixes that need to go in: - Recompile on reload: https://gwt-review.googlesource.com/#/c/9323/ ( dankurka) - Sending the wrong permutation to the client in SDM, if no files have changed (dankurka). - Investigate why some people are seeing errors with incremental not restricting to one permutation (dankurka). - Public directories are not copied o the war directory when using SDM (skybrian). - Restore Java 6 compatibility (skybrian). - Document limitations of JsonUtils.safeEval and discourage usage (goktug) (promote Json.parse) Patches that are nice to have: - Improve exception logging in SDM (goktug). *If you have any outstanding patches that you thing need to go into GWT 2.7, please bring them to our attention, by replying to this thread or adding me as a reviewer on Gerrit and setting the topic to GWT2.7.* -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/1d5a4369-e03d-47ba-b8dd-5031e5460751%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/1d5a4369-e03d-47ba-b8dd-5031e5460751%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/48e8f729-b645-4534-af9d-c5a9947dffd2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: GWT 2.7 release plan
-XjsInteropMode JS On Thu, Oct 2, 2014 at 2:46 PM, confile michael.gorsk...@googlemail.com wrote: How can JsInterop be activated in GWT 2.7? What flag does it? Am Donnerstag, 2. Oktober 2014 03:22:56 UTC+2 schrieb Brian Slesinsky: It's experimental and hidden behind a flag, but it's there. On Wed, Oct 1, 2014 at 6:20 PM, Cristian Rinaldi csri...@gmail.com wrote: - JsInterop Preview is part of the release? El miércoles, 1 de octubre de 2014 16:15:26 UTC-3, Daniel Kurka escribió: Hi all, we just settled on a GWT 2.7 release plan: - We *code freeze* on *October 7th* and branch for GWT 2.7. - As soon as we have the *remaining patches submitted*, we put out a beta1 build, this should be no later than *October 7th.* - Putting out a *beta1 externally* allows us to collect feedback on the new super dev mode integration externally as well. - We are going to *flip incremental to default* tomorrow and *wait for 1-2 weeks* for google internal feedback, if there is no serious issues we are going to *put out RC1* - GWT 2.7 will still be compatible with Java 6. Patches / Fixes that need to go in: - Recompile on reload: https://gwt-review.googlesource.com/#/c/9323/ ( dankurka) - Sending the wrong permutation to the client in SDM, if no files have changed (dankurka). - Investigate why some people are seeing errors with incremental not restricting to one permutation (dankurka). - Public directories are not copied o the war directory when using SDM (skybrian). - Restore Java 6 compatibility (skybrian). - Document limitations of JsonUtils.safeEval and discourage usage (goktug) (promote Json.parse) Patches that are nice to have: - Improve exception logging in SDM (goktug). *If you have any outstanding patches that you thing need to go into GWT 2.7, please bring them to our attention, by replying to this thread or adding me as a reviewer on Gerrit and setting the topic to GWT2.7.* -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/1d5a4369-e03d- 47ba-b8dd-5031e5460751%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/1d5a4369-e03d-47ba-b8dd-5031e5460751%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/48e8f729-b645-4534-af9d-c5a9947dffd2%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/48e8f729-b645-4534-af9d-c5a9947dffd2%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/CAFw3gJ_CC8ZdaEMie2QTvqRkKT0T-e0K%2BqzN%2BGyUx6jt2kJCVg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Re: GWT 2.7 release plan
I miss the following sources in the current GWT 2.7 SnapShot: com.google.gwt.user.client.impl.HistoryImpl Why is this missing? Am Mittwoch, 1. Oktober 2014 21:15:26 UTC+2 schrieb Daniel Kurka: Hi all, we just settled on a GWT 2.7 release plan: - We *code freeze* on *October 7th* and branch for GWT 2.7. - As soon as we have the *remaining patches submitted*, we put out a beta1 build, this should be no later than *October 7th.* - Putting out a *beta1 externally* allows us to collect feedback on the new super dev mode integration externally as well. - We are going to *flip incremental to default* tomorrow and *wait for 1-2 weeks* for google internal feedback, if there is no serious issues we are going to *put out RC1* - GWT 2.7 will still be compatible with Java 6. Patches / Fixes that need to go in: - Recompile on reload: https://gwt-review.googlesource.com/#/c/9323/ (dankurka) - Sending the wrong permutation to the client in SDM, if no files have changed (dankurka). - Investigate why some people are seeing errors with incremental not restricting to one permutation (dankurka). - Public directories are not copied o the war directory when using SDM (skybrian). - Restore Java 6 compatibility (skybrian). - Document limitations of JsonUtils.safeEval and discourage usage (goktug) (promote Json.parse) Patches that are nice to have: - Improve exception logging in SDM (goktug). *If you have any outstanding patches that you thing need to go into GWT 2.7, please bring them to our attention, by replying to this thread or adding me as a reviewer on Gerrit and setting the topic to GWT2.7.* -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/f4b6d1ec-20b4-4b39-8f6c-4c220db29464%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: GWT 2.7 release plan
What is the difference between -XjsInteropMode JS and -XjsInteropMode CLOSURE? Am Donnerstag, 2. Oktober 2014 23:49:17 UTC+2 schrieb John Stalcup: -XjsInteropMode JS On Thu, Oct 2, 2014 at 2:46 PM, confile michael@googlemail.com javascript: wrote: How can JsInterop be activated in GWT 2.7? What flag does it? Am Donnerstag, 2. Oktober 2014 03:22:56 UTC+2 schrieb Brian Slesinsky: It's experimental and hidden behind a flag, but it's there. On Wed, Oct 1, 2014 at 6:20 PM, Cristian Rinaldi csri...@gmail.com wrote: - JsInterop Preview is part of the release? El miércoles, 1 de octubre de 2014 16:15:26 UTC-3, Daniel Kurka escribió: Hi all, we just settled on a GWT 2.7 release plan: - We *code freeze* on *October 7th* and branch for GWT 2.7. - As soon as we have the *remaining patches submitted*, we put out a beta1 build, this should be no later than *October 7th.* - Putting out a *beta1 externally* allows us to collect feedback on the new super dev mode integration externally as well. - We are going to *flip incremental to default* tomorrow and *wait for 1-2 weeks* for google internal feedback, if there is no serious issues we are going to *put out RC1* - GWT 2.7 will still be compatible with Java 6. Patches / Fixes that need to go in: - Recompile on reload: https://gwt-review.googlesource.com/#/c/9323/ (dankurka) - Sending the wrong permutation to the client in SDM, if no files have changed (dankurka). - Investigate why some people are seeing errors with incremental not restricting to one permutation (dankurka). - Public directories are not copied o the war directory when using SDM (skybrian). - Restore Java 6 compatibility (skybrian). - Document limitations of JsonUtils.safeEval and discourage usage (goktug) (promote Json.parse) Patches that are nice to have: - Improve exception logging in SDM (goktug). *If you have any outstanding patches that you thing need to go into GWT 2.7, please bring them to our attention, by replying to this thread or adding me as a reviewer on Gerrit and setting the topic to GWT2.7.* -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+unsubscribe@ googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/ msgid/google-web-toolkit-contributors/1d5a4369-e03d- 47ba-b8dd-5031e5460751%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/1d5a4369-e03d-47ba-b8dd-5031e5460751%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 javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/48e8f729-b645-4534-af9d-c5a9947dffd2%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/48e8f729-b645-4534-af9d-c5a9947dffd2%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/56e45472-2d5f-4b52-94d1-1ecdd2023d2f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: GWT 2.7 release plan
Code size explodes when using GWT 2.7 with -XjsInteropMode JS I compiled the same code with GWT 2.6.1 and GWT 2.7 with argument strict code size GWT 2.6.1 1.351 MB code size GWT 2.7 1.361 MB Then I compiled the same code with -XjsInteropMode JS flag on GWT 2.7 code size 1.601 MB Why does GWT 2.7 increases the code size in every case and with Interop even by 300 kb? Am Freitag, 3. Oktober 2014 00:18:22 UTC+2 schrieb confile: What is the difference between -XjsInteropMode JS and -XjsInteropMode CLOSURE? Am Donnerstag, 2. Oktober 2014 23:49:17 UTC+2 schrieb John Stalcup: -XjsInteropMode JS On Thu, Oct 2, 2014 at 2:46 PM, confile michael@googlemail.com wrote: How can JsInterop be activated in GWT 2.7? What flag does it? Am Donnerstag, 2. Oktober 2014 03:22:56 UTC+2 schrieb Brian Slesinsky: It's experimental and hidden behind a flag, but it's there. On Wed, Oct 1, 2014 at 6:20 PM, Cristian Rinaldi csri...@gmail.com wrote: - JsInterop Preview is part of the release? El miércoles, 1 de octubre de 2014 16:15:26 UTC-3, Daniel Kurka escribió: Hi all, we just settled on a GWT 2.7 release plan: - We *code freeze* on *October 7th* and branch for GWT 2.7. - As soon as we have the *remaining patches submitted*, we put out a beta1 build, this should be no later than *October 7th.* - Putting out a *beta1 externally* allows us to collect feedback on the new super dev mode integration externally as well. - We are going to *flip incremental to default* tomorrow and *wait for 1-2 weeks* for google internal feedback, if there is no serious issues we are going to *put out RC1* - GWT 2.7 will still be compatible with Java 6. Patches / Fixes that need to go in: - Recompile on reload: https://gwt-review.googlesource.com/#/c/9323/ (dankurka) - Sending the wrong permutation to the client in SDM, if no files have changed (dankurka). - Investigate why some people are seeing errors with incremental not restricting to one permutation (dankurka). - Public directories are not copied o the war directory when using SDM (skybrian). - Restore Java 6 compatibility (skybrian). - Document limitations of JsonUtils.safeEval and discourage usage (goktug) (promote Json.parse) Patches that are nice to have: - Improve exception logging in SDM (goktug). *If you have any outstanding patches that you thing need to go into GWT 2.7, please bring them to our attention, by replying to this thread or adding me as a reviewer on Gerrit and setting the topic to GWT2.7.* -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+unsubscribe@ googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/ msgid/google-web-toolkit-contributors/1d5a4369-e03d- 47ba-b8dd-5031e5460751%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/1d5a4369-e03d-47ba-b8dd-5031e5460751%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/48e8f729-b645-4534-af9d-c5a9947dffd2%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/48e8f729-b645-4534-af9d-c5a9947dffd2%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/fc3a33e8-dc46-4c3f-a22b-9d3b96362a11%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] bug with the new snapshot
Hi Julien,
I think this is related to us not waiting for the body to be loaded before
injecting the recompile.nocache.js.
Can you try: https://gwt-review.googlesource.com/#/c/9451/ and let me know
if this fixes your issue?
-Daniel
On Thu, Oct 2, 2014 at 4:34 AM, Julien Dramaix julien.dram...@gmail.com
wrote:
This morning, I've updated my GWT snapshot to the last one and I'm not
able to run the super dev mode (with the flag -superDevMode) for my
applications.
The problem comes from that the .nocache.js tries to add the compilation
dialog to the body before the body is initialized.
Error:
Uncaught TypeError: Cannot read property 'appendChild' of null
in:
Dialog.prototype.show = function() {
$doc.body.appendChild(this.__overlay);
$doc.body.appendChild(this.__dialog);
};
$doc.body is null when the method is called. This method should be called
when the html is fully loaded.
If I include the nocache.js script at the end of the body instead of in
the head of the html, it works fine.
Julien
--
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/CABb_3%3D5%3DMU8--RcXrHwjM8ZSPvB%2B2MG-7nAvF1Sq8BjDEeJ5Kw%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D5%3DMU8--RcXrHwjM8ZSPvB%2B2MG-7nAvF1Sq8BjDEeJ5Kw%40mail.gmail.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
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/CALLujiqQnryHwbPUYRV1Uyborxpd31sFNHxSUkz063k7otE5Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
