[gwt-contrib] Re: GWT 2.7.0-RC1 is available
When I use GWT 2.7RC1 with GTW-PhoneGap and run the codeserver I get the following output from the code server: Turning off precompile in incremental mode. Super Dev Mode starting up workDir: /var/folders/xh/1xkfq26532j97q23qw5pdhs4gn/T/gwt-codeserver-7573159147938212004.tmp Does this mean anything? Is it a problem if precompile is turned off or does it mean that incremental compile is not working? Best Michael Am Donnerstag, 30. Oktober 2014 01:04:15 UTC+1 schrieb Daniel Kurka: Hi all, I just build the GWT 2.7.0 RC1 and pushed it to maven central. The complete SDK is also available from here http://goo.gl/npqEUR. Please start testing and let us know if you run into any trouble. You can either reply to this thread on gwt-contrib https://groups.google.com/forum/#!forum/google-web-toolkit-contributors or file a bug https://code.google.com/p/google-web-toolkit/issues/entry. We are planing to release this as GWT 2.7.0 if we do not here about any serious issues within the next two weeks. The release notes http://www.gwtproject.org/release-notes.html#Release_Notes_2_7_0_RC1 for RC1 will be made available shortly after this notice, in the mean time you can take a look at the review for the release notes https://gwt-review.googlesource.com/#/c/10031/. Daniel, on behalf of the GWT team -- 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/48ac86bf-3422-4472-9532-574442707f4d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Upgrade 2.7 beta1 to rc1 - browser refresh and change detection not working
Hi, I have just update to RC1 and now if I click refresh button (Chrome), code change on disk is not detected and recompile (increment compile) is not performed. We also have compile link on our start page to perform SDM recompile (base on Brien suggestion from GWT.create) and it still works - recompile is done with increment compile. Any idea how to debug what's wrong? Thank you. Regards, Matic -- 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/a2a650e1-3148-47ae-a3c1-a3e05a07670c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Re: GWT 2.7 JsInterop Handle static JavaScript Functions
I have been testing JsInterop for a while, and is very promising ... The issue of static functions is something I have asked, and we have to wait Java support 8 and the new JSNI too. @confile, if you want to look at a couple of projects on which I am working: - gwt-jscore https://github.com/workingflows/gwt-jscore - gwt-jquery https://github.com/workingflows/gwt-jquery - gwt-playground https://github.com/csrinaldi/samples-of-gwt/tree/master/gwt-playground probably when Elemental 2.0 has been implemented, gwt-jscore will not be necessary. gwt-used-playgroud use jscore and a simple implementation of gwt-jquery, with suport of Event and Promise... For create object I use for the moment a Factory Class, and for emulate static method, by example, Object.observe, I have a two interface, see: JS Factory Class https://github.com/workingflows/gwt-jscore/blob/master/src/main/java/com/workingflows/js/jscore/client/factory/JS.java and Browser Factory Class https://github.com/workingflows/gwt-jscore/blob/master/src/main/java/com/workingflows/js/jscore/client/factory/Browser.java, if not the best solution, but until this all implemented works for me. Hope you helps. El sábado, 4 de octubre de 2014 12:18:08 UTC-3, confile escribió: Consider the following static JavaScript function: THREE.ImageUtils = { loadTexture: function (url) { ... } } The way I use to create the static function with JsInterop is to create an interface for ImageUtils and then create an inner abstract class MyStatic which contains the static methods implemented with JSNI. Here is an example of the above class: @JsType public interface ImageUtils { public static abstract class MyStatic { public static native Texture create(String url) /*-{ return new $wnd.THREE.ImageUtils.loadTexture(url); }-*/; } } I don't think this is the best solution. Is there a better way to handle static functions with JsInterop? -- 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/c8c8404e-addb-43e6-8560-b2a48cfca93e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Re: GWT 2.7.0-RC1 is available
Turning off precompile in incremental mode. Super Dev Mode starting up workDir: /var/folders/xh/1xkfq26532j97q23qw5pdhs4gn/T/gwt-codeserver-7573159147938212004.tmp Does this mean anything? Is it a problem if precompile is turned off or does it mean that incremental compile is not working? That's fine. Precompilation is turned off intentionally as it can sometimes cause SDM to not detect just a single permutation. -- 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/c471fef0-a36d-4b55-924d-a532515cd601%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Re: Upgrade 2.7 beta1 to rc1 - browser refresh and change detection not working
I assume you have deployed an old module.nocache.js file. Try a clean start by deleting your /war/modulename folder and restart DevMode. A new module.nocache.js file should be generated (could take a bit as the CodeServer needs to start before this file gets generated) which automatically recompiles your app each time you refresh the browser. -- 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/0254ed3a-fbff-4b8f-b7f3-31997d32c2d4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: Upgrade 2.7 beta1 to rc1 - browser refresh and change detection not working
It is also possible that there is a stale copy of .java resources on your classpath, such as in target/classes/ for a maven project - we've seen that get in the way as well. Make sure that either target/classes/ isn't on your classpath, or that it doesn't have another (stale) copy of whatever you are trying to compile. On Thu Oct 30 2014 at 10:40:52 AM Jens jens.nehlme...@gmail.com wrote: I assume you have deployed an old module.nocache.js file. Try a clean start by deleting your /war/modulename folder and restart DevMode. A new module.nocache.js file should be generated (could take a bit as the CodeServer needs to start before this file gets generated) which automatically recompiles your app each time you refresh the browser. -- 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/0254ed3a-fbff-4b8f-b7f3-31997d32c2d4%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/0254ed3a-fbff-4b8f-b7f3-31997d32c2d4%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/CADcXZMwR3WUSpEvVoGfW%2BYo%2B2LW_vMinRKJyxUsu4bW_hHROjQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: Certain gwtar files seem to be way too large in GWT 2.7
On Wednesday, October 29, 2014 8:58:07 PM UTC+1, Daniel Kurka wrote: Jens and I talked offline. Since gwttars are only relevant for the prod compile and do not impact SDM compile times, we don't really need them anymore. They are not used within Google and we do not want to maintain them going foward. So I suggest we deprecate them with GWT 2.7 and disable them and remote them going forward. I think I already proposed it some time ago (after someone told me that Google doesn't actually use them) and got some feedback that they make their build faster. A quick search in the groups gave me https://groups.google.com/d/msg/google-web-toolkit/O8HaPzExxhc/X16AnKZI2JAJ, but nothing more. -- 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/9088707a-5e74-4d31-a9d1-bc700ce81b7e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Cell widgets and GSS
I think we should not provide these files as of yet. If someone wants to make the transition right now they can easily use the converter with these files and convert them to gss themselves. I think we want to make that transition once GSS is default (or about to be default) inside of Google as a testing ground. -Daniel On Thu, Oct 30, 2014 at 3:51 PM, Julien Dramaix julien.dram...@gmail.com wrote: If GSS was the default, we would have shipped only .gss files. What I want is to provide the .gss files for people using GSS and want to override some style class of cell widgets. We have this case at Arcbees where css guys want to use their existing mixins to style CellTable. On Wed Oct 29 2014 at 6:49:46 PM 'Goktug Gokdogan' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: The original idea to make the GSS default was to ship .gss files next to .css files and let the generator automatically use the file with the gss extension. We can probably ship the gss files but I think it is optional at this point. On Wed, Oct 29, 2014 at 5:50 AM, Julien Dramaix julien.dram...@gmail.com wrote: Now that GSS will be shipped in GWT 2.7 as an experimental feature, I'm wondering if we shouldn't provide GSS files for all existing CssResource interfaces present in GWT. The idea is to keep the associated .css files and use them by default but also to provide GSS files in order that people can use GSS to style their widgets. Let take the cell widgets (CelTable, CellList...) as example. If you want to override default style, you do something like: public interface TableResources extends CellTable.Resources { interface Style extends CellTable.Style { } @Override @Source({ CellTable.Style.DEFAULT_CSS, css/table.css}) Style cellTableStyle(); } In this case, it's impossible to use GSS because you cannot mix .css and .gss files on the same resource. So the only mean to use GSS is to first convert manually the default css file to gss and include it in your application or start from scratch. So I would like that GWT provides these gss files that user can use in their @Source annotations in order to override the default style. What do you guys think ? 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%3D6To8pLn%3D0EmgLRQdByrx_m0-CURafkr7FhZRMwxGXbqg%40mail.gmail.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D6To8pLn%3D0EmgLRQdByrx_m0-CURafkr7FhZRMwxGXbqg%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%3DyUA3wT52nZHx-9BZ3PcgjXAXMaPQZLdD4gJcnb%2BJpAsOxhw%40mail.gmail.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA3wT52nZHx-9BZ3PcgjXAXMaPQZLdD4gJcnb%2BJpAsOxhw%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%3D7vYxNejFdDC1jZnDHe-ft6xjsrP39jT%2Bf0zCnpgxVsxQ%40mail.gmail.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D7vYxNejFdDC1jZnDHe-ft6xjsrP39jT%2Bf0zCnpgxVsxQ%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/CALLujipc1i4hYFt%3D8Oan%3DfFDjspvFk6uYbOuYk-YJXC4Ce3R6Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: Certain gwtar files seem to be way too large in GWT 2.7
I think I already proposed it some time ago (after someone told me that Google doesn't actually use them) and got some feedback that they make their build faster. A quick search in the groups gave me https://groups.google.com/d/msg/google-web-toolkit/O8HaPzExxhc/X16AnKZI2JAJ, but nothing more. Does anybody know how much compile time is actually saved by using gwtar files? I have no idea and generally I don't care if a production compile takes 10 or 15 minutes. It is just a bit unfortunate that the build file needs to be in sync with GWT module inheritance but maybe it is possible to write a gwtar tool that always does the right thing based on the given module inheritance (naive thoughts: generate a gwtar per graph clique or start with a defined module and do a breadth first traversal to generate one gwtar per module). Then users who want to use that feature could run the tool, but the GWT build would not do so by default. Or GWT does continue to generate them but packages the result in a different jar that is an optional dependency. At the end I am only interested in having small SDK download sizes as I use SNAPSHOT builds in private projects. So I am also fine with just getting rid of gwtar files. -- 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/a137e122-7e2e-45dc-9e04-76fca0270e59%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Cell widgets and GSS
ok. I will do that in an external third party library On Thu Oct 30 2014 at 6:19:58 PM 'Daniel Kurka' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: I think we should not provide these files as of yet. If someone wants to make the transition right now they can easily use the converter with these files and convert them to gss themselves. I think we want to make that transition once GSS is default (or about to be default) inside of Google as a testing ground. -Daniel On Thu, Oct 30, 2014 at 3:51 PM, Julien Dramaix julien.dram...@gmail.com wrote: If GSS was the default, we would have shipped only .gss files. What I want is to provide the .gss files for people using GSS and want to override some style class of cell widgets. We have this case at Arcbees where css guys want to use their existing mixins to style CellTable. On Wed Oct 29 2014 at 6:49:46 PM 'Goktug Gokdogan' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: The original idea to make the GSS default was to ship .gss files next to .css files and let the generator automatically use the file with the gss extension. We can probably ship the gss files but I think it is optional at this point. On Wed, Oct 29, 2014 at 5:50 AM, Julien Dramaix julien.dram...@gmail.com wrote: Now that GSS will be shipped in GWT 2.7 as an experimental feature, I'm wondering if we shouldn't provide GSS files for all existing CssResource interfaces present in GWT. The idea is to keep the associated .css files and use them by default but also to provide GSS files in order that people can use GSS to style their widgets. Let take the cell widgets (CelTable, CellList...) as example. If you want to override default style, you do something like: public interface TableResources extends CellTable.Resources { interface Style extends CellTable.Style { } @Override @Source({ CellTable.Style.DEFAULT_CSS, css/table.css}) Style cellTableStyle(); } In this case, it's impossible to use GSS because you cannot mix .css and .gss files on the same resource. So the only mean to use GSS is to first convert manually the default css file to gss and include it in your application or start from scratch. So I would like that GWT provides these gss files that user can use in their @Source annotations in order to override the default style. What do you guys think ? 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%3D6To8pLn%3D0EmgLRQdByrx_m0-CURafkr7FhZRMwxGXbqg%40mail.gmail.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D6To8pLn%3D0EmgLRQdByrx_m0-CURafkr7FhZRMwxGXbqg%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%3DyUA3wT52nZHx-9BZ3PcgjXAXMaPQZLdD4gJcnb%2BJpAsOxhw%40mail.gmail.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA3wT52nZHx-9BZ3PcgjXAXMaPQZLdD4gJcnb%2BJpAsOxhw%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%3D7vYxNejFdDC1jZnDHe-ft6xjsrP39jT%2Bf0zCnpgxVsxQ%40mail.gmail.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D7vYxNejFdDC1jZnDHe-ft6xjsrP39jT%2Bf0zCnpgxVsxQ%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
Re: [gwt-contrib] Cell widgets and GSS
On Thu, Oct 30, 2014 at 7:51 AM, Julien Dramaix julien.dram...@gmail.com wrote: If GSS was the default, we would have shipped only .gss files. That's not true. We will still have a release where GSS is default and css is supported but deprecated that requires css files to be there. What I want is to provide the .gss files for people using GSS and want to override some style class of cell widgets. We have this case at Arcbees where css guys want to use their existing mixins to style CellTable. On Wed Oct 29 2014 at 6:49:46 PM 'Goktug Gokdogan' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: The original idea to make the GSS default was to ship .gss files next to .css files and let the generator automatically use the file with the gss extension. We can probably ship the gss files but I think it is optional at this point. On Wed, Oct 29, 2014 at 5:50 AM, Julien Dramaix julien.dram...@gmail.com wrote: Now that GSS will be shipped in GWT 2.7 as an experimental feature, I'm wondering if we shouldn't provide GSS files for all existing CssResource interfaces present in GWT. The idea is to keep the associated .css files and use them by default but also to provide GSS files in order that people can use GSS to style their widgets. Let take the cell widgets (CelTable, CellList...) as example. If you want to override default style, you do something like: public interface TableResources extends CellTable.Resources { interface Style extends CellTable.Style { } @Override @Source({ CellTable.Style.DEFAULT_CSS, css/table.css}) Style cellTableStyle(); } In this case, it's impossible to use GSS because you cannot mix .css and .gss files on the same resource. So the only mean to use GSS is to first convert manually the default css file to gss and include it in your application or start from scratch. So I would like that GWT provides these gss files that user can use in their @Source annotations in order to override the default style. What do you guys think ? 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%3D6To8pLn%3D0EmgLRQdByrx_m0-CURafkr7FhZRMwxGXbqg%40mail.gmail.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D6To8pLn%3D0EmgLRQdByrx_m0-CURafkr7FhZRMwxGXbqg%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%3DyUA3wT52nZHx-9BZ3PcgjXAXMaPQZLdD4gJcnb%2BJpAsOxhw%40mail.gmail.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA3wT52nZHx-9BZ3PcgjXAXMaPQZLdD4gJcnb%2BJpAsOxhw%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%3D7vYxNejFdDC1jZnDHe-ft6xjsrP39jT%2Bf0zCnpgxVsxQ%40mail.gmail.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D7vYxNejFdDC1jZnDHe-ft6xjsrP39jT%2Bf0zCnpgxVsxQ%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%3DyUA0NPT7BoVbnVDaazqi%2B5raebnKLn89pRzb%3DVnhtCb71Dw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: GWT 2.7.0-RC1 is available
There seems that some assertions in UnifyAST are not being satisfied in incremental SDM but it runs fine (and correctly) if you turn off assertions. On Wed, Oct 29, 2014 at 10:53 PM, jay j...@thegindins.com wrote: I grabbed the RC and switched to use it from my IntelliJ project. When starting my run configuration using SDM, all seems well until the compiler dies (see below). What can I do to provide more information to help track this down? (Sorry, I cannot make the code available...) // Lots and lots of: // Resolving ... //Found type '' // Resolving method ... Finding entry point classes Assimilating generated source Generated source files... com.google.gwt.lang.com_00046ao_00046foo_ 00046MyGwtModule_00045DEV__EntryMethodHolder Adding '1' new generated units Compiling... Compilation completed in 0.00 seconds Added 1 units to cache since last cleanup. Removing invalidated units Wrote 1 units to persistent cache. [ERROR] Unexpected internal compiler error java.lang.AssertionError at com.google.gwt.dev.jjs.impl.UnifyAst.instantiate(UnifyAst.java:1407) at com.google.gwt.dev.jjs.impl.UnifyAst.instantiate(UnifyAst.java:1414) at com.google.gwt.dev.jjs.impl.UnifyAst.instantiate(UnifyAst.java:1414) at com.google.gwt.dev.jjs.impl.UnifyAst.fullFlowIntoType(UnifyAst.java: 1186) at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst. java:1020) at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java: 1595) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1733) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1747) at com.google.gwt.dev.jjs.impl.UnifyAst.flowInto(UnifyAst.java:1226) at com.google.gwt.dev.jjs.impl.UnifyAst.fullFlowIntoType(UnifyAst.java: 1191) at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst. java:1020) at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java: 1595) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1733) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1747) at com.google.gwt.dev.jjs.impl.UnifyAst.flowInto(UnifyAst.java:1226) at com.google.gwt.dev.jjs.impl.UnifyAst.fullFlowIntoType(UnifyAst.java: 1191) at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst. java:1020) at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java: 1595) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645) at com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552) at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst. java:1010) at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java: 1595) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1733) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1747) at com.google.gwt.dev.jjs.impl.UnifyAst.flowInto(UnifyAst.java:1206) at com.google.gwt.dev.jjs.impl.UnifyAst.fullFlowIntoType(UnifyAst.java: 1188) at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst. java:1020) at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java: 1595) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645) at com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552) at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst. java:1010) at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java: 1595) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645) at com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552) at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst. java:1010) at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java: 1595) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645) at com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552) at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst. java:1010) at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java: 1595) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645) at com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552) at
Re: [gwt-contrib] Re: Upgrade 2.7 beta1 to rc1 - browser refresh and change detection not working
Jens Colin Thank you for your help. The problem is really module.nocache.js file (or batter - generated js files), the behaviour is for my a litter strange : 1) my Ant file looks like this : target name=superdevmode_main depends=javac description=Run Super Dev Mode java failonerror=true fork=true classname=com.google.gwt.dev.codeserver.CodeServer ... arg value=-workDir/ arg value=./war/ arg value=com.mycompany.mymodule/ /java /target Because I set workDir parameter, I think at first startup I should get mymodule folder inside war folder and two basic files (metakockamain.nocache.js, metakockamain.recompile.nocache.js) for first startup. Unfortunately I still get temporary folder com.mycompany.mymodule/compile-1/ with expected files. No /war/mymodule/ folder. 2) OK, I manually copy com.mycompany.mymodule/compile-1/war/mymodule/* into /war/mymodule/ 3) We are using ImageBundle and we need image sprite files. That is why I copy com.mycompany.mymodule/compile-2/war/mymodule/* into /war/mymodule/ and now browser refresh has stop working. Two thinks in upper description does not compute for me : (1) why *.js files are not generated in workDir folder (3) if I copy *.js files from after increment compile folder into /war/mymodule/, whay browser refresh has stop working. Thank you, Regards, Matic On Thursday, October 30, 2014 4:43:14 PM UTC+1, Colin Alworth wrote: It is also possible that there is a stale copy of .java resources on your classpath, such as in target/classes/ for a maven project - we've seen that get in the way as well. Make sure that either target/classes/ isn't on your classpath, or that it doesn't have another (stale) copy of whatever you are trying to compile. On Thu Oct 30 2014 at 10:40:52 AM Jens jens.ne...@gmail.com javascript: wrote: I assume you have deployed an old module.nocache.js file. Try a clean start by deleting your /war/modulename folder and restart DevMode. A new module.nocache.js file should be generated (could take a bit as the CodeServer needs to start before this file gets generated) which automatically recompiles your app each time you refresh the browser. -- 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 javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/0254ed3a-fbff-4b8f-b7f3-31997d32c2d4%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/0254ed3a-fbff-4b8f-b7f3-31997d32c2d4%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/e917eb3a-2c5d-4df2-b1fe-174e62f000c5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: Upgrade 2.7 beta1 to rc1 - browser refresh and change detection not working
Jens Colin Thank you for your help. The problem is really module.nocache.js file (or batter - generated js files), the behaviour is for my a litter strange : 1) my Ant file looks like this : target name=superdevmode_main depends=javac description=Run Super Dev Mode java failonerror=true fork=true classname=com.google.gwt.dev.codeserver.CodeServer ... arg value=-workDir/ arg value=./war/ arg value=com.mycompany.mymodule/ /java /target Because I set workDir parameter, I think at first startup I should get mymodule folder inside war folder and two basic files (mymodule.nocache.js, mymodule.recompile.nocache.js) for first startup. Unfortunately I still get temporary folder com.mycompany.mymodule/compile-1/ with expected files. No /war/mymodule/ folder. 2) OK, I manually copy com.mycompany.mymodule/compile-1/war/mymodule/* into /war/mymodule/ 3) We are using ImageBundle and we need image sprite files. That is why I copy com.mycompany.mymodule/compile-2/war/mymodule/* into /war/mymodule/ and now browser refresh has stop working. Two thinks in upper description does not compute for me : (1) why *.js files are not generated in workDir folder (3) if I copy *.js files from after increment compile folder into /war/mymodule/, whay browser refresh has stop working. Thank you, Regards, Matic On Thursday, October 30, 2014 4:43:14 PM UTC+1, Colin Alworth wrote: It is also possible that there is a stale copy of .java resources on your classpath, such as in target/classes/ for a maven project - we've seen that get in the way as well. Make sure that either target/classes/ isn't on your classpath, or that it doesn't have another (stale) copy of whatever you are trying to compile. On Thu Oct 30 2014 at 10:40:52 AM Jens jens.ne...@gmail.com javascript: wrote: I assume you have deployed an old module.nocache.js file. Try a clean start by deleting your /war/modulename folder and restart DevMode. A new module.nocache.js file should be generated (could take a bit as the CodeServer needs to start before this file gets generated) which automatically recompiles your app each time you refresh the browser. -- 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 javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/0254ed3a-fbff-4b8f-b7f3-31997d32c2d4%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/0254ed3a-fbff-4b8f-b7f3-31997d32c2d4%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/a6055f65-85f6-483c-9db0-832d8e19ea17%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: GWT 2.7.0-RC1 is available
I'll give that a try... Will the issue be handled before the final release? jay On Thursday, October 30, 2014 11:47:54 AM UTC-7, Roberto Lublinerman wrote: There seems that some assertions in UnifyAST are not being satisfied in incremental SDM but it runs fine (and correctly) if you turn off assertions. On Wed, Oct 29, 2014 at 10:53 PM, jay j...@thegindins.com javascript: wrote: I grabbed the RC and switched to use it from my IntelliJ project. When starting my run configuration using SDM, all seems well until the compiler dies (see below). What can I do to provide more information to help track this down? (Sorry, I cannot make the code available...) // Lots and lots of: // Resolving ... //Found type '' // Resolving method ... Finding entry point classes Assimilating generated source Generated source files... com.google.gwt.lang.com_00046ao_00046foo_ 00046MyGwtModule_00045DEV__EntryMethodHolder Adding '1' new generated units Compiling... Compilation completed in 0.00 seconds Added 1 units to cache since last cleanup. Removing invalidated units Wrote 1 units to persistent cache. [ERROR] Unexpected internal compiler error java.lang.AssertionError at com.google.gwt.dev.jjs.impl.UnifyAst.instantiate(UnifyAst.java:1407) at com.google.gwt.dev.jjs.impl.UnifyAst.instantiate(UnifyAst.java:1414) at com.google.gwt.dev.jjs.impl.UnifyAst.instantiate(UnifyAst.java:1414) at com.google.gwt.dev.jjs.impl.UnifyAst.fullFlowIntoType(UnifyAst.java: 1186) at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst. java:1020) at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java: 1595) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1733) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1747) at com.google.gwt.dev.jjs.impl.UnifyAst.flowInto(UnifyAst.java:1226) at com.google.gwt.dev.jjs.impl.UnifyAst.fullFlowIntoType(UnifyAst.java: 1191) at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst. java:1020) at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java: 1595) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1733) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1747) at com.google.gwt.dev.jjs.impl.UnifyAst.flowInto(UnifyAst.java:1226) at com.google.gwt.dev.jjs.impl.UnifyAst.fullFlowIntoType(UnifyAst.java: 1191) at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst. java:1020) at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java: 1595) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645) at com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552) at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst. java:1010) at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java: 1595) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1733) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1747) at com.google.gwt.dev.jjs.impl.UnifyAst.flowInto(UnifyAst.java:1206) at com.google.gwt.dev.jjs.impl.UnifyAst.fullFlowIntoType(UnifyAst.java: 1188) at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst. java:1020) at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java: 1595) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645) at com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552) at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst. java:1010) at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java: 1595) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645) at com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552) at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst. java:1010) at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java: 1595) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645) at com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552) at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst. java:1010) at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java: 1595) at
[gwt-contrib] Re: GWT 2.7.0-RC1 is available
I compared my GWT-PhoneGap written in GWT 2.6.1 which switching to GWT 2.7beta. Here are my experience. I feel that loading of data especially images are much slower in GWT 2.7 than in GWT 2.6.1. I tested it on an iPhone 5. Due to the delay in loading the app feels slow and scrolling does not work smouth. Michael Am Donnerstag, 30. Oktober 2014 16:37:38 UTC+1 schrieb Jens: Turning off precompile in incremental mode. Super Dev Mode starting up workDir: /var/folders/xh/1xkfq26532j97q23qw5pdhs4gn/T/gwt-codeserver-7573159147938212004.tmp Does this mean anything? Is it a problem if precompile is turned off or does it mean that incremental compile is not working? That's fine. Precompilation is turned off intentionally as it can sometimes cause SDM to not detect just a single permutation. -- 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/9574bc95-abd7-4c08-bf6d-58f20c2fa6f3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Re: GWT 2.7 JsInterop Handle static JavaScript Functions
@Christian: 1. What does gwt-jscore do? 2. as Ray Cromwell suggested in this post In general, native DOM elements == no $wnd prefix, JS libraries loaded in host page == $wnd prefix This means your JQueryElement https://github.com/workingflows/gwt-jquery/blob/master/src/main/java/com/workingflows/js/jquery/client/api/JQueryElement.java should be: @JsType(prototype = $wnd.jQuery) public interface JQueryElement { ... } What do you think? Am Donnerstag, 30. Oktober 2014 16:27:17 UTC+1 schrieb Cristian Rinaldi: I have been testing JsInterop for a while, and is very promising ... The issue of static functions is something I have asked, and we have to wait Java support 8 and the new JSNI too. @confile, if you want to look at a couple of projects on which I am working: - gwt-jscore https://github.com/workingflows/gwt-jscore - gwt-jquery https://github.com/workingflows/gwt-jquery - gwt-playground https://github.com/csrinaldi/samples-of-gwt/tree/master/gwt-playground probably when Elemental 2.0 has been implemented, gwt-jscore will not be necessary. gwt-used-playgroud use jscore and a simple implementation of gwt-jquery, with suport of Event and Promise... For create object I use for the moment a Factory Class, and for emulate static method, by example, Object.observe, I have a two interface, see: JS Factory Class https://github.com/workingflows/gwt-jscore/blob/master/src/main/java/com/workingflows/js/jscore/client/factory/JS.java and Browser Factory Class https://github.com/workingflows/gwt-jscore/blob/master/src/main/java/com/workingflows/js/jscore/client/factory/Browser.java, if not the best solution, but until this all implemented works for me. Hope you helps. El sábado, 4 de octubre de 2014 12:18:08 UTC-3, confile escribió: Consider the following static JavaScript function: THREE.ImageUtils = { loadTexture: function (url) { ... } } The way I use to create the static function with JsInterop is to create an interface for ImageUtils and then create an inner abstract class MyStatic which contains the static methods implemented with JSNI. Here is an example of the above class: @JsType public interface ImageUtils { public static abstract class MyStatic { public static native Texture create(String url) /*-{ return new $wnd.THREE.ImageUtils.loadTexture(url); }-*/; } } I don't think this is the best solution. Is there a better way to handle static functions with JsInterop? -- 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/eca70063-0bfa-4725-b959-bb5692c81545%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: GWT 2.7.0-RC1 is available
Yes. Will be fixed before final release. On Thu, Oct 30, 2014 at 2:23 PM, jay j...@thegindins.com wrote: I'll give that a try... Will the issue be handled before the final release? jay On Thursday, October 30, 2014 11:47:54 AM UTC-7, Roberto Lublinerman wrote: There seems that some assertions in UnifyAST are not being satisfied in incremental SDM but it runs fine (and correctly) if you turn off assertions. On Wed, Oct 29, 2014 at 10:53 PM, jay j...@thegindins.com wrote: I grabbed the RC and switched to use it from my IntelliJ project. When starting my run configuration using SDM, all seems well until the compiler dies (see below). What can I do to provide more information to help track this down? (Sorry, I cannot make the code available...) // Lots and lots of: // Resolving ... //Found type '' // Resolving method ... Finding entry point classes Assimilating generated source Generated source files... com.google.gwt.lang.com_00046ao_00046foo_ 00046MyGwtModule_00045DEV__EntryMethodHolder Adding '1' new generated units Compiling... Compilation completed in 0.00 seconds Added 1 units to cache since last cleanup. Removing invalidated units Wrote 1 units to persistent cache. [ERROR] Unexpected internal compiler error java.lang.AssertionError at com.google.gwt.dev.jjs.impl.UnifyAst.instantiate(UnifyAst.java:1407) at com.google.gwt.dev.jjs.impl.UnifyAst.instantiate(UnifyAst.java:1414) at com.google.gwt.dev.jjs.impl.UnifyAst.instantiate(UnifyAst.java:1414) at com.google.gwt.dev.jjs.impl.UnifyAst.fullFlowIntoType(UnifyAst.java: 1186) at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst. java:1020) at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java: 1595) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1733) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1747) at com.google.gwt.dev.jjs.impl.UnifyAst.flowInto(UnifyAst.java:1226) at com.google.gwt.dev.jjs.impl.UnifyAst.fullFlowIntoType(UnifyAst.java: 1191) at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst. java:1020) at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java: 1595) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1733) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1747) at com.google.gwt.dev.jjs.impl.UnifyAst.flowInto(UnifyAst.java:1226) at com.google.gwt.dev.jjs.impl.UnifyAst.fullFlowIntoType(UnifyAst.java: 1191) at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst. java:1020) at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java: 1595) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645) at com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552) at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst. java:1010) at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java: 1595) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1733) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1747) at com.google.gwt.dev.jjs.impl.UnifyAst.flowInto(UnifyAst.java:1206) at com.google.gwt.dev.jjs.impl.UnifyAst.fullFlowIntoType(UnifyAst.java: 1188) at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst. java:1020) at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java: 1595) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645) at com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552) at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst. java:1010) at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java: 1595) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645) at com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552) at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst. java:1010) at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java: 1595) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653) at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645) at com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552) at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst. java:1010) at
Re: [gwt-contrib] Re: GWT 2.7.0-RC1 is available
Release notes are here: http://www.gwtproject.org/release-notes.html#Release_Notes_2_7_0_RC1 -- 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_uQFBC4AxBZSLdrmCixZH8b0VWNfsE1PU%3DWzwdW3MdNA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: GWT 2.7.0-RC1 is available
I am not aware of any changes in 2.7 that should effect performance loading images. Are you running on iOS7 or iOS8? Daniel would probably be best able to help you. Are you talking about SuperDevMode loading performance, or fully optimized compile loading performance? On Thu, Oct 30, 2014 at 2:27 PM, confile michael.gorsk...@googlemail.com wrote: I compared my GWT-PhoneGap written in GWT 2.6.1 which switching to GWT 2.7beta. Here are my experience. I feel that loading of data especially images are much slower in GWT 2.7 than in GWT 2.6.1. I tested it on an iPhone 5. Due to the delay in loading the app feels slow and scrolling does not work smouth. Michael Am Donnerstag, 30. Oktober 2014 16:37:38 UTC+1 schrieb Jens: Turning off precompile in incremental mode. Super Dev Mode starting up workDir: /var/folders/xh/1xkfq26532j97q23qw5pdhs4gn/T/gwt-codeserver-7573159147938212004.tmp Does this mean anything? Is it a problem if precompile is turned off or does it mean that incremental compile is not working? That's fine. Precompilation is turned off intentionally as it can sometimes cause SDM to not detect just a single permutation. -- 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/9574bc95-abd7-4c08-bf6d-58f20c2fa6f3%40googlegroups.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/CAPVRV7dXFx1SYtYRLCJCe0V%3DBu%3Du3B6_VXe1jN5thhFOAE8OnA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.