Google Web Toolkit: August 2015

Monday, August 31, 2015

Re: GWT Plugin Problem

use Mozilla current 24 portable

Jonathan Franchesco Torres Baca

CIO - Kiongo Inc.

Av. Manuel Seoane 761 2do Piso- La Victoria

Teléfono 074 - 613534

Cel. 958429349

La información contenida en este e-mail es confidencial, privilegiada y está dirigida exclusivamente a su destinatario. Su revisión, difusión, distribución o copiado está prohibido. Si ha recibido este e-mail por error por favor bórrelo y envíe un mensaje al remitente.

The information contained in this e-mail is privileged and confidential and is intended only for its addressee. Any review, dissemination, distribution or copying of this is prohibited. If you have received this mail in error please delete the original message and e-mail us.

2015-08-26 9:40 GMT-05:00 Magnus <alpineblaster@gmail.com>:

Ok, and how do you debug the server side code?

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Recommended GWT Map Library?

Thanks for the reply Greg. I was seriously considering OpenLayers as well.

I think I've decided to just stick with standard Google Maps (the 3.8 api I linked above). The reason I went with this is the JavaScript documentation for the Google Maps API is very good, and I can just use native JavaScript functions to use it on top of my GWT application. Instead of searching for an up-to-date GWT option, I've decided to cut GWT out and stick with native JavaScript (called from the GWT Java code) as much as possible.

That is perhaps not optimal, but it's going to be hard for a GWT team to stay more up to date than me simply using the JavaScript API directly.

On Friday, August 28, 2015 at 3:58:40 AM UTC-4, Greg wrote:

In my projects I used mostly OpenLayers 2 with custom bindings for GWT (At the beginning I used GWT-OpenLayers but then I switched to own impl.).

OpenLayers 3 looks very nice and it's built with performance and new technologies in mind so you could check that.
Other alternative is Leaflet - very simple but maybe it will be enough for your purposes.

BTW I'm not sure but I think that gwt-google-apis were not created / are maintained by GWT Team.

On Tuesday, August 25, 2015 at 8:16:34 PM UTC+2, Kevin Workman wrote:
I've been using gwt-google-apis as a GWT wrapper of the Google Maps JavaScript API. I've been using the jar from here.

It works okay, but I'm starting a new GWT project that requires a map display, and I noticed that the jar hasn't been updated since 2012.

I'm starting a new project from scratch, so I'm in a position to start over with a new wrapper, if that's the correct way to go. I've come across GWT-OpenLayers, which looks promising, but I'm not sure how much of a change it will be from using the Google API wrapper. I've also come across branflake2267's wrapper, but that hasn't been updated in over a year.

So, my question is: what would you consider the "best" approach to displaying a map in a GWT application? Should I stick with the "official" google product? All I really need to do is display some polygons and circles on the map, but adding stuff like weather would be a really nice feature as well. Are there any libraries that I missed that are worth checking out?

Re: heap memory consumption by CrossSiteIframeLinker

I think GWT could make a conservative guess on the StringBuilder initial size so there is no need for a compile parameter. As you see from the message the compiler already knows the total size of the script.

Alternatively just give the compiler a bit more heap space. 100 MB might already be enough.

-- J

Tammin Sursok tweeted: Get your personalized Instagram post!!! ❤️❤️❤️lets make this happen!!

Followed by Emily Stoll.

Tammin Sursok

@tamminsursok1

Get your personalized Instagram post!!! ❤️❤️❤️lets make this happen!! instagram.com/p/7C_m_Gyzaz/

View on Twitter

Kelly Clarkson

@kelly_clarkson

....one day I will make a record and this song and this woman will be its muse #daughteroftheblues

YouTube

View on Twitter

Jonell @jonell_lennon

Mistress America via @YouTube

YouTube

View on Twitter

Nick Jonas

@nickjonas

It's here. Watch the official #Levels video on Vevo now!

@WeForSheArg You guys are incredible! The fact that you all became friends makes me SO happy!😃 ❤️❤️❤️ Thank You!Xx

YouTube

View on Twitter

Followed by Emily Stoll, Nick Cannon and AshleyTisdaleFrench.

Perez Hilton

@PerezHilton

.@Pharrell and his wife keep it casual in denim at the #VMAs! goo.gl/ArJgoF

View on Twitter

heap memory consumption by CrossSiteIframeLinker

Hello,

I'm meeting a problem during gwt compilation. My application is quite big.

[INFO]   
Permutation 8 (strong name BA14D66EEC73FB44262423A88ADFC40E) has an initial download size of 19984060 and total script size of 37457074
[INFO]   Invoking Linker RPC policy file manifest
[INFO]    Invoking Linker Cross-Site-Iframe
[INFO]       [ERROR] Failed to link
[INFO] java.lang.OutOfMemoryError: Java heap space
[INFO]  at java.util.Arrays.copyOf(Arrays.java:2367)
[INFO]  at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:130)
[INFO]  at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:114)
[INFO]  at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:415)
[INFO]  at java.lang.StringBuilder.append(StringBuilder.java:132)
[INFO]  at com.google.gwt.core.linker.CrossSiteIframeLinker.wrapPrimaryFragment(CrossSiteIframeLinker.java:700)
[INFO]  at com.google.gwt.core.ext.linker.impl.SelectionScriptLinker.generatePrimaryFragmentString(SelectionScriptLinker.java:406)
[INFO]  at com.google.gwt.core.ext.linker.impl.SelectionScriptLinker.generatePrimaryFragment(SelectionScriptLinker.java:377)
[INFO]  at com.google.gwt.core.ext.linker.impl.SelectionScriptLinker.doEmitCompilation(SelectionScriptLinker.java:254)
[INFO]  at com.google.gwt.core.ext.linker.impl.SelectionScriptLinker.link(SelectionScriptLinker.java:196)
[INFO]  at com.google.gwt.core.ext.linker.impl.StandardLinkerContext.invokeLinkForOnePermutation(StandardLinkerContext.java:381)
[INFO]  at com.google.gwt.dev.Link.finishPermutation(Link.java:489)
[INFO]  at com.google.gwt.dev.Link.doSimulatedShardingLink(Link.java:450)
[INFO]  at com.google.gwt.dev.Link.link(Link.java:182)
[INFO]  at com.google.gwt.dev.Compiler.run(Compiler.java:246)
[INFO]  at com.google.gwt.dev.Compiler.run(Compiler.java:158)
[INFO]  at com.google.gwt.dev.Compiler$1.run(Compiler.java:120)
[INFO]  at com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:55)
[INFO]  at com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:50)
[INFO]  at com.google.gwt.dev.Compiler.main(Compiler.java:127)
[INFO]  [ERROR] Out of memory; to increase the amount of memory, use the -Xmx flag at startup (java -Xmx128M ...)
[INFO] Shutting down PersistentUnitCache thread

The problem appears while appending String using a StringBuilder which size is not initialized. As permutations size is huge, I guess it would work better (needing less heap) if the initial StringBuilder size was initialized with a big value (in code or through a parameter).

AbstractStringBuilder : 

void expandCapacity(int minimumCapacity) {
111
         int newCapacity = (value.length + 1) * 2;
112
         if (newCapacity < 0) {
113
             newCapacity = Integer.MAX_VALUE;
114
         } else if (minimumCapacity > newCapacity) {
115
             newCapacity = minimumCapacity;
116
         }
117
         value = Arrays.copyOf(value, newCapacity); <-- value exists twice here, doubling memory consumption.
118
     }

If permutation size is known before entering in CrossSiteIframeLinker, I think StringBuilder should be initialized correctly. I don't even mention the number of array copies needed to allocate several Mb by starting from 16 bytes to final size.

What do you think of it ?

Thank you.

dominique