Re: [gwt-contrib] Asking for decision on DevMode embedded Jetty support

[JonL]

As a developer of various GWT apps large and small, I personally would like 
to see the Jetty support separated and modularized but maintained. The 
embedded Jetty support allows for a simple start to new projects where you 
can focus on getting started on development vs getting setup.  This 
reduction of friction was a big selling point in our initial usage of GWT.  
The problem with dropping the embedded Jetty support isn't just removing 
it, most of the documentation on the gwtproject.org revolves around using 
it.  There is little or no documentation about setting up to not use it, so 
I think that would need to be one of the first things that would have to be 
done is provide examples for various IDEs, build tools and run scenarios 
before it were dropped.

Ultimately though, modularizing and separating it into it's own project 
would hopefully incentivize the community and especially IDE plugin authors 
to expand it and keep it up to date.

On Wednesday, April 14, 2021 at 3:44:34 AM UTC-4 eliasbala...@gmail.com 
wrote:

> >> As a user and non-contributor, I would vote for bumping up versions 
> (Java 7 to 8, Jetty to 9.4). The move to Java 8 is something I would have 
> to do if I had any Java 7 projects left. And Jetty has lots of used 
> features that I'm not hearing proposals for replacement for.
>
> I couldn't agree more.
> Losing support for Java 7 is both tolerable and desirable.
> Losing support for embedded Jetty is not acceptable, not without a 
> replacement which wasn't proposed.
>
> On Tuesday, 13 April 2021 at 19:01:04 UTC+1 ric...@gmail.com wrote:
>
>> As a user and non-contributor, I would vote for bumping up versions (Java 
>> 7 to 8, Jetty to 9.4). The move to Java 8 is something I would have to do 
>> if I had any Java 7 projects left. And Jetty has lots of used features that 
>> I'm not hearing proposals for replacement for.
>> On 2021-04-11 9:15 a.m., Jens wrote:
>>
>> Hi, 
>>
>> we all know the issue: DevMode bundles Jetty and people are using it even 
>> though we do not recommend it. Consequently people are complaining that 
>> bundled Jetty is too old. So every once in a while we upgrade it.
>>
>> Currently with GWT 2.9.0 the situation is:
>> - GWT SDK is compiled to Java 7 byte code
>> - GWT Compiler requires ASM 7.x to support Java 11
>> - DevMode bundles Jetty 9.2 which uses ASM 5.x
>> - gwt-dev.jar can only bundle a single Jetty, since we do not relocate 
>> it. However there is already a question asking for Jakarta Servlet support, 
>> e.g. Jetty 11 / Tomcat 10.
>>
>> Currently the ASM version misalignment between Jetty 9.2 and GWT compiler 
>> causes classpath issues. This could be fixed by upgrading to Jetty 9.4 and 
>> consequently compiling GWT SDK to Java 8 byte code as that is a requirement 
>> for Jetty 9.4.
>>
>> However given the new Jakarta namespace and first questions about 
>> supporting it, I am wondering if it wouldn't be wiser to remove embedded 
>> Jetty from DevMode now, invest some work to make GWT-RPC and RequestFactory 
>> useable with old javax.servlet and new jakarta.servlet namespaces and 
>> finally cut a 2.10 or 3.0 release given the removal of embedded Jetty.
>>
>> Personally I would strongly vote for removal because GWT nowadays is in 
>> maintenance mode with only very few changes here and there to support J2CL 
>> better. Even reviews from contributors are rare these days I guess. Every 
>> action we take nowadays should take maintenance effort into account and a 
>> low maintenance effort is obviously preferred. If we upgrade Jetty to 9.4 
>> we still have that Jakarta issue coming up more often in the future for 
>> sure.
>>
>> Generally this would be a decision made by GWT steering group but I have 
>> no idea if this group still exists. So I am asking here for a decision how 
>> to move on.
>>
>> -- 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-co...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/622544a8-85d5-41c5-b8da-7a733667eb89n%40googlegroups.com
>>  
>> 
>> .
>>
>>

-- 
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/d11e3ff4-aad1-4f7e-ab46-55cba6f5978an%40googlegroups.com.

Re: java.sql.Date - java.util.Date serialization issue

[JonL]

You could write a custom field serializer for java.sql.Date.  Serialize the 
information you need to recreate with the fidelity required for your use 
case.

On Thursday, July 23, 2020 at 10:17:25 AM UTC-4 ralph.f...@gmail.com wrote:

> I know it is quite some time ago since you posted this, but I just now 
> (2020!) ran into the very same issue (using the very same workaraound). Is 
> there any real solution for this by now?
>
>
> On Tuesday, August 22, 2006 at 2:32:24 AM UTC+2, StudyBlue wrote:
>>
>> Casting 'non-serializable' objects to 'serializable' objects alone is
>> not enough!
>>
>> 1.  According to the serialization documentation for the GWT,
>> java.util.Date is serializable.
>> (
>>
>> http://code.google.com/webtoolkit/documentation/com.google.gwt.doc.DeveloperGuide.RemoteProcedureCalls.SerializableTypes.html
>> )
>> 2.  According to the java docs, java.sql.Date is a subclass of
>> java.util.Date.
>> ( http://java.sun.com/j2se/1.5.0/docs/api/java/sql/Date.html )
>> 3.  According to you-can-look-it-up-yourself you can validly cast a
>> subclass to the type of the superclass.
>>
>> Intuitively, you should be able to send java.sql.Dates across the RPC
>> boundary simply by casting them.  Unfortunately, the reflection calls
>> appear to look for the most specific type possible, not necessarily
>> whatever it was cast to last.  (Maybe that's intended.  Maybe I'm
>> totally off on my blind guess for what's causing this.)  No matter how
>> I cast I java.sql.Date to java.util.Date, the call would always throw
>> an exception claiming I was trying to send a java.sql.Date.  Eventually
>> I got fed up with that and created a new java.util.Date from the
>> java.sql.Date's getTime() method.  Creating an entirely new object
>> solved the problem, but I'm assuming that's taking more time and
>> processing than a simple cast.  If there's any way to make a sufficient
>> cast, I'd love to hear it.
>>
>>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/1d2098c9-4380-48b9-9202-86da9ccb54b4n%40googlegroups.com.

Re: GWT-RPC-AsyncCallback

[JonL]

Depending on your architecture, the server generating the file might not 
have any control over the timeout.  You could have proxies, firewalls, etc 
that can affect the timeout.  It is best to remove the timeout from the 
equation.  

If you can not fix the fetch, I would split it into a call that spawns a 
separate thread to do the generation, returns to the client saying "your 
request was successful and is pending", then use a secondary async call to 
poll periodically to check if the file creation is finished, then when 
available, the user can click a button to download and you can immediately 
write the file to the browser.  The secondary request could possibly 
include progress to display to the user if you can provide feedback on the 
number of records being processed, etc.

On Wednesday, July 22, 2020 at 9:32:10 AM UTC-4 vie...@gmail.com wrote:

> Hi Paddy,
>
> maybe you can split the request. ATM you trigger the export and fetch the 
> data. I suggest to write a request for trigger the export (and you receive 
> a unique export id) and then check the download service from time to time 
> with the export id. If the export is not finished yet the callback is 
> rescheduled, otherwise you fetch the data. 
> I think you can build better solutions with webhooks and stuff, but the 
> main idea is split the two actions ;)
>
> Hope this helps.
>
> Norbert
> Paddy schrieb am Mittwoch, 22. Juli 2020 um 03:01:14 UTC+2:
>
>> Hi All,
>> We have a UI application, where user searches for records and exports the 
>> data to an excel. Once the export is completed at the server side, it 
>> notifies the client by async call back and then there is code at client 
>> side to give a popup to the customer saying, the file is ready for download 
>> and give an option to download the file from server.
>> However, when server side fetch takes more than 3 minutes, the client is 
>> closing the socket(I think). Though the report is getting generated at the 
>> server, the user is not getting the pop up to download the report. Is there 
>> anyway to stop the client from closing the socket? This issue happens only 
>> when there are more than 400 records to be fetched. One way to fix this, is 
>> to fix the fetch (which at this point cannot be done as there are some 
>> encryption calls happening during this). But wanted to know if there is any 
>> timeout parameters that can be configured, so that we can somehow stop 
>> client from closing the socket?
>> I am seeing socket timeout exceptions in the GWT logs.
>>
>>
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/14b9d0b7-d36c-470a-a31a-07ff2dc8d1d8n%40googlegroups.com.

Re: Advice needed - compile error while moving back to GWT 2.7 from 2.8.2

[JonL]

We have seen similar issues with this when we were experimenting with some 
projects and upgrading to 2.8.2.  The things to double check are:

1. That there are no duplicate jars from different versions of GWT, as 
mentions by Thomas Broyer.
2. Delete any GWT generated folder such as the gwt-unitCache, and the 
script outputs in the war folder and also any GWT generated files in the 
temp folder.
3. If still running into problems, delete the Eclipse workspace .metadata 
folder, re-setup the workspace and import the existing projects into the 
cleaned workspace.

Due to GWT compilation caching, and Eclipse deployment caching, if files do 
not change during the modification process, they can still reference the 
the incorrect version of GWT, or the jars that are actually deployed to the 
location where the Jetty server is run from by eclipse may not be updated.

On Monday, May 14, 2018 at 6:06:09 AM UTC-7, Rachel wrote:
>
> We have to move our project back to GWT 2.7 due to some java 1.8 issues. 
> I've checked all my jar files to make sure they are 2.7 and no duplicate 
> jars in the build path but am getting errors when I try to compile with Ant.
> Any suggestions would be greatly appreciated. Thank you.
>
> *prepareGWT*:
>
> [*delete*] Deleting directory 
> C:\Users\s235985\workspace\wkflw_test\Approval\gwt-unitCache
>
> [*java*] Compiling module com.aep.mro.approval.approvalsystem
>
> [*java*] Computing all possible rebind results for 
> 'gwtupload.client.bundle.UploadCss'
>
> [*java*] Rebinding gwtupload.client.bundle.UploadCss
>
> [*java*] Invoking generator 
> com.google.gwt.resources.rebind.context.InlineClientBundleGenerator
>
> [*java*] Initializing ResourceGenerator
>
> [*java*] [ERROR] Unable to determine default for GSS in UiBinder
>
> [*java*] [ERROR] An internal compiler exception occurred
>
> [*java*] *com.google.gwt.dev.jjs.InternalCompilerException*: Unexpected 
> error during visit.
>
> [*java*] at com.google.gwt.dev.jjs.ast.JVisitor.translateException(
> *JVisitor.java:121*)
>
> [*java*] at com.google.gwt.dev.jjs.ast.JModVisitor.accept(
> *JModVisitor.java:296*)
>
> [*java*] at com.google.gwt.dev.jjs.ast.JModVisitor.accept(
> *JModVisitor.java:285*)
>
> [*java*] at com.google.gwt.dev.jjs.ast.JVisitor.accept(*JVisitor.java:128*
> )
>
> [*java*] at com.google.gwt.dev.jjs.ast.JCastOperation.traverse(
> *JCastOperation.java:67*)
>
> [*java*] at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(
> *JModVisitor.java:381*)
>
> [*java*] at com.google.gwt.dev.jjs.ast.JModVisitor.accept(
> *JModVisitor.java:293*)
>
> [*java*] at com.google.gwt.dev.jjs.ast.JModVisitor.accept(
> *JModVisitor.java:285*)
>
> [*java*] at com.google.gwt.dev.jjs.ast.JVisitor.accept(*JVisitor.java:128*
> )
>
> [*java*] at com.google.gwt.dev.jjs.ast.JDeclarationStatement.traverse(
> *JDeclarationStatement.java:49*)
>
> [*java*] at com.google.gwt.dev.jjs.ast.JModVisitor$ListContext.traverse(
> *JModVisitor.java:95*)
>
> [*java*] at com.google.gwt.dev.jjs.ast.JModVisitor.acceptWithInsertRemove(
> *JModVisitor.java:351*)
>
> [*java*] at com.google.gwt.dev.jjs.ast.JBlock.traverse(*JBlock.java:92*)
>
> [*java*] at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(
> *JModVisitor.java:381*)
>
> [*java*] at com.google.gwt.dev.jjs.ast.JModVisitor.accept(
> *JModVisitor.java:293*)
>
> [*java*] at com.google.gwt.dev.jjs.ast.JVisitor.accept(*JVisitor.java:149*
> )
>
> [*java*] at com.google.gwt.dev.jjs.ast.JVisitor.accept(*JVisitor.java:145*
> )
>
> [*java*] at com.google.gwt.dev.jjs.ast.JMethodBody.traverse(
> *JMethodBody.java:83*)
>
> [*java*] at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(
> *JModVisitor.java:381*)
>
> [*java*] at com.google.gwt.dev.jjs.ast.JModVisitor.accept(
> *JModVisitor.java:293*)
>
> [*java*] at com.google.gwt.dev.jjs.ast.JModVisitor.accept(
> *JModVisitor.java:285*)
>
> [*java*] at com.google.gwt.dev.jjs.ast.JMethod.visitChildren(
> *JMethod.java:600*)
>
> [*java*] at com.google.gwt.dev.jjs.ast.JMethod.traverse(*JMethod.java:569*
> )
>
> [*java*] at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(
> *JModVisitor.java:381*)
>
> [*java*] at com.google.gwt.dev.jjs.ast.JModVisitor.accept(
> *JModVisitor.java:293*)
>
> [*java*] at com.google.gwt.dev.jjs.ast.JModVisitor.accept(
> *JModVisitor.java:285*)
>
> [*java*] at com.google.gwt.dev.jjs.impl.UnifyAst.mainLoop(
> *UnifyAst.java:1505*)
>
> [*java*] at com.google.gwt.dev.jjs.impl.UnifyAst.exec(*UnifyAst.java:870*)
>
> [*java*] at 
> com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$Precompiler.unifyJavaAst(
> *JavaToJavaScriptCompiler.java:1305*)
>
> [*java*] at 
> com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$Precompiler.constructJavaAst(
> *JavaToJavaScriptCompiler.java:1038*)
>
> [*java*] at 
> com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$Precompiler.precompile(
> *JavaToJavaScriptCompiler.java:954*)
>
> [*java*] at 
> com.google.gwt.dev.jjs.MonolithicJavaToJavaScriptCompiler.precompile(
> *MonolithicJavaToJavaScriptCompiler.java:303*)
>
> [*java*] at 

Re: Internet Explorer Google Web Toolkit Plugin Installing but not Working.

[JonL]

The GWT browser plugins are no longer supported, though they can get 
installed into old versions of browsers.  As of 2.7.x Super Dev mode is the 
supported method of development and the support for the plugin is 
deprecated.

On Thursday, November 10, 2016 at 7:03:05 AM UTC-7, Hendré Louw wrote:
>
> 2.8.0. Super Dev mode works.
>
> On Thursday, 10 November 2016 15:19:59 UTC+2, Velusamy Velu wrote:
>>
>> Which version of GWT you are trying with? Have you tried the Super Dev 
>> mode?
>>
>> On Thursday, November 10, 2016 at 5:22:13 AM UTC-5, Hendré Louw wrote:
>>>
>>> I created a new project in Eclipse with the sample code option. IE 
>>> prompts me to install the developer plugin, however the link does not work. 
>>> After coping the plugin link I managed to install the plugin. The download 
>>> page keep reappearing every time I run the application. Please assist.
>>>
>>

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

Re: Update conversation by displaying new messages when they are sent

[JonL]

Others have suggested websockets, but there are several other options as 
well.  There is google cloud messaging and many other libraries to solve 
this problem as well as ServerSent Events.

http://www.html5rocks.com/en/tutorials/eventsource/basics/

If none of those are options, try to avoid using a regular timer.  More 
timers, more problems.  If you must use a timer like object, I would 
suggest using gwt Scheduler instead.

On Tuesday, September 20, 2016 at 2:38:11 AM UTC-7, Olar Andrei wrote:
>
> Hello,
>
> In my GWT application I have a messaging system integrated within. When a 
> specific conversation gets opened, a query runs and selects all messages 
> available for this conversation. From the same view you can reply to that 
> conversation. When replying, the other user has to click a small refresh 
> button (located on top, which agian gets all mesages from the DB running 
> the same query from above) in order for the last message to appear.
>
> My question: How can I make that refresh automatically, so you don't have 
> to click on the button in order to refresh the conversation. Like in FB, 
> Messenger, etc, where you don't refresh the conversation and the messages 
> keep coming without you having to do anything.
>
> Thanks in advance.
>

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

Re: [gwt-contrib] Re: CodeServer with Bookmarklets not working in GWT 2.7 (2nd request)

[JonL]

I've had to do this when working on a sdm compiled application in a web 
wrapper on ios, instead of a proxy, I wrote a custom nocache.js that 
replaces the one generated by sdm and adds a url parameter to tell it the 
remote server to connect to where the codeserver is running, allowing me to 
debug the application running directly on the ipad correctly.

Here is a gist of a sligtly modified version of the nocache.js replacing 
the module name with "module_name":
https://gist.github.com/jonl-percsolutions-com/403ec9ba1bf50a6abcb0db852b171d0c

So I just run my gwt-compile, replace the nocache.js and then create the 
war for deployment.   The when accessing the url, provide the url paramter "
remote_server=http://ip:port;.

Not sure if this will be what you need 100% but should work instead of 
setting up a proxy or clobbering the codeserver api.

On Monday, September 12, 2016 at 12:24:54 PM UTC-7, Brandon Donnelson wrote:
>
> Proxying wasn't an option for developers because of the I.T. security 
> protocols. Besides it feels a bit overcomplicated to have to set up a 
> channel back to the code server. I think it would be easier to clobber the 
> codeserver api with a workaround and setting the hosteName and hand that to 
> the developers. I'm contemplating on forking the code server for GWT 2.7 
> users to provide a workaround for the hostName through the program 
> arguments.   
>
> On Sat, Sep 10, 2016 at 1:43 AM Thomas Broyer <t.br...@gmail.com 
> > wrote:
>
>> How about proxying through a local server that would intercept the 
>> nocache.js and route everything else to your external server? This is 
>> basically how webpack devserver and browserSync work in the JS land.
>>
>> --
>> 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/13bfb1ba-f2fb-40cf-afda-c9902d016cb3%40googlegroups.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> *Brandon Donnelson*
> GXT Support Engineer
> <http://www.facebook.com/senchainc> <http://twitter.com/sencha> 
> <https://www.linkedin.com/company/sencha-inc> 
> <http://www.youtube.com/SenchaInc> 
> <https://plus.google.com/117303203295549187007?prsrc=3>
> [image: SenchaCon 2016 Aria Resort, Las Vegas, November 7-9] 
> <https://www.senchacon.com/>
> *Join me at SenchaCon 2016!*
>

-- 
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/274f1c7b-8267-4164-8d11-ab3e64dd9721%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Please help: GWT generates .class files to src folder

[JonL]

If you are running in Eclipse, this is an eclipse setting in the Project 
Properties -> Java Build Path, make sure "Allow output folders for source 
folders" is unchecked or make sure that each source folder is pointing its 
output folder to a desired location.

On Wednesday, August 31, 2016 at 1:45:08 AM UTC-7, Florian Heymel wrote:
>
> Hello all,
>
> i got a strange issue recently. If i launch gwt superdev mode gwt somehow 
> compiles classes on demand, as soon as they are used (servlets or daos 
> etc). What i dont understand is, why they occure in my src folder?
>
> Can anyone hep with that issue? That is really annoying because it totaly 
> confuses my svn.
>
> Eclipse mars/GWT 2.7
>
> Best regards 
> Florian
>

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

Re: remove annotation in gwt compiler process ?

[JonL]

If you need to specify specific annotation processors, or mess with the 
annotation processors that are on the path, these two javac options might 
help you:

*-processor* *class1[,class2,class3...]*Names of the annotation processors 
to run. This bypasses the default discovery process.*-processorpath* 
*path*Specify 
where to find annotation processors; if this option is not used, the class 
path will be searched for processors.
https://docs.oracle.com/javase/7/docs/technotes/tools/solaris/javac.html

On Sunday, August 28, 2016 at 3:45:22 PM UTC-7, Marian S wrote:
>
> Hi, 
>
> Im write a annotation processor for  shared package and need remove this 
> in gwt compilation process ?
> Im try with "super source"  but I take only error  ..  ( have maybe 
> someone example project for "super source " ?) 
> e.g. expected package not the same like .
> Im using gwt 2.8 from eclipse !
> For moment I comment this for compilation but this is not really solution 
> ! I miss preprocessor like in C or C++ 
>
> Have someone a ideea ? or solution better as my ?
>
> Greeting
> Marian
>
>
>

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

Re: [gwt-contrib] Re: Eclipse Code Server Launcher Icon

[JonL]

I guess I didn't word it correctly.  I think I am talking more of the 
experience of running the CodeServer and the embedded Jetty Server serving 
the app, in one shot utilizing the eclipse plugin has become synonymous in 
my head with SDM.  Where as running the web app on an external server and 
manually starting the CodeServer, I don't so much attribute to being 
"super", but more "cumbersome" dev mode.  So I guess what I am trying to 
say is that from the eclipse development perspective, utilizing the plugin, 
there should always be a one shot command that starts up the CodeServer and 
deploys the app for you and then maybe you start a browser using SDBG 
Plugin, should remain the most cumbersome experience for utilizing the 
plugin, by default.  

I don't use the maven plugin, but I would guess by discussion that there is 
a similar experience where the maven plugin starts up the codeserver and 
uses DevMode plugin for deployment.  

So ultimately, I think, unless there is a better way, across all these 
plugins to provide a similar getting started experience where you run one 
command to start the CodeServer and a deployment server, my vote, if it 
counts for anything, would be to keep c.g.g.dev.DevMode with only SDM and 
refactor it possibly so that its clear to what it is and separate it, 
cognitively, from the old classic DevMode utilizing the browser plugin.

On Friday, August 26, 2016 at 7:58:24 AM UTC-7, Thomas Broyer wrote:
>
>
>
> On Friday, August 26, 2016 at 4:30:48 PM UTC+2, JonL wrote:
>>
>> I have always considered the deprecation of "DevMode" to mean the 
>> deprecation of the "HostedMode"/GWT Dev Mode plugin combo and that SDM was 
>> the non-deprecated version. It sounds like some are considering losing SDM 
>> as the default run mode.  I think that would be a mistake and would make it 
>> appear that GWT is more cumbersome to use than it is.  Hosted Mode w./ Dev 
>> Mode Plugin was broken due to the deprecation of the NPAPI plugin, other 
>> than possibly refactoring out SDM from the DevMode class, I would 
>> personally consider removing SDM as breaking something that isn't broken 
>> for no particular reason.
>>
>
> I don't understand what you mean.
>
> DevMode can mean either "dev mode using the browser plugin", or "the 
> c.g.g.dev.DevMode entrypoint class".
> SDM, to me, can only mean "dev mode using compiled-on-the-fly JS", so it'd 
> be the opposite of "dev mode using the browser plugin", without saying 
> "how" you run it.
> The opposite of "the c.g.g.dev.DevMode class" is CodeServer (i.e. "the 
> c.g.g.dev.codeserver.CodeServer class").
> And SDM could be used either through c.g.g.dev.DevMode or CodeServer.
> So for SDM, there's no terminology problem, and yet I don't understand 
> what you mean by "removing SDM".
>
> CodeServer will stay, that's a given. The question (to the Steering 
> Committee) is whether c.g.g.dev.DevMode will stay with only its SDM mode, 
> or whether it'll be removed (and SDM can only run through CodeServer, which 
> would remain the only "development mode" of GWT).
>

-- 
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/34c1cf6d-2c9a-457a-8cd4-e0cbe2d26890%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Eclipse Code Server Launcher Icon

[JonL]

I have always considered the deprecation of "DevMode" to mean the 
deprecation of the "HostedMode"/GWT Dev Mode plugin combo and that SDM was 
the non-deprecated version. It sounds like some are considering losing SDM 
as the default run mode.  I think that would be a mistake and would make it 
appear that GWT is more cumbersome to use than it is.  Hosted Mode w./ Dev 
Mode Plugin was broken due to the deprecation of the NPAPI plugin, other 
than possibly refactoring out SDM from the DevMode class, I would 
personally consider removing SDM as breaking something that isn't broken 
for no particular reason.

Also, we use ivy for dependency resolution and due to a bug in the IvyDE 
classpath container, it does not load things it considers to be a source 
jar onto the classpath, we already deploy all our libs to WEB-INF/lib.

On Friday, August 26, 2016 at 1:41:33 AM UTC-7, Thomas Broyer wrote:
>
>
>
> On Friday, August 26, 2016 at 3:16:25 AM UTC+2, Brandon Donnelson wrote:
>>
>> Hm, I hadn't thought about making the CodeServer the default yet. I've 
>> been helping folks convert to super dev mode every chance I get so my 
>> feeling is that keeping the legacy the default method that starts up with 
>> SDM probably is the way to go on for a bit longer.
>>
>
> FWIW, when the release notes say "DevMode is deprecated", people can 
> understand it in 2 different ways; and I had the impression that Daniel 
> Kurka at least interpreted it as com.google.gwt.dev.DevMode is deprecated.
> I'm not sure we were all on the same line in the Steering Committee when 
> saying "DevMode is deprecated"; I think most thought that "legacy dev mode" 
> was deprecated, but c.g.g.dev.DevMode would stay (just losing its 
> -nosuperDevMode).
> I, for one, would have preferred that we didn't even integrate SDM within 
> c.g.g.dev.DevMode in 2.7; or explicitly describe it as a transitional 
> feature, encouraging everyone to switch to CodeServer even before 2.8.
> In any case, if we do keep c.g.g.dev.DevMode in the future, I'll campaign 
> (again) for removing its custom WebAppClassLoader and force users to put 
> all their deps and compiled server classes into WEB-INF/lib and 
> WEB-INF/classes.
>
> So, I'm with Jens here wrt icons.
>

-- 
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/bb004c58-9c3b-4bb8-bd0c-f81f8936de3c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problems connecting to Super Dev Mode server with 2.8 / multi-module project

[JonL]

I don't use maven, so not 100% familiar with it.  It appears that there is 
a dependency report that should tell you where it is coming from:

https://maven.apache.org/plugins/maven-project-info-reports-plugin/

Then you should just exclude it:

https://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html

On Thursday, August 18, 2016 at 10:20:28 AM UTC-7, Drew Spencer wrote:
>
> Thanks for the help. I'm not sure why, but I still have servlet-api:2.5 in 
> my dependencies, as well as javax.servlet-api:3.1.0. I read somewhere that 
> javax.servlet-api replaced servlet-api... I removed it manually but it's 
> being brough in from somewhere and I can't work out where. For the first 
> time in a year I wish I was back in eclipse instead of IntelliJ IDEA :( Any 
> chance you can look at my pom.xml files and help me work it out? 
> https://gist.github.com/slugmandrew/1d9acf86be2c7db89031dc60de9df6e2
>
> On 18 August 2016 at 17:08, JonL <jo...@percsolutions.com > 
> wrote:
>
>> Besides possibly switching to the gwt-maven-archetypes as Frank 
>> suggested, I just added a comment to my answer.  The problem is that you 
>> don't need servlet-api jars on your classpath at all. GWT provides the 
>> appropriate classes for compile time in gwt-user and gwt-dev.
>>
>>
>> On Thursday, August 18, 2016 at 5:54:12 AM UTC-7, Drew Spencer wrote:
>>>
>>> Hey all, I have recently changed the structure of my project to separate 
>>> client, server and shared code into their own maven projects (modules).
>>>
>>> I am getting a HTTP Error 500 related to the Servlet API: 
>>> *java.lang.NoSuchMethodError: 
>>> javax.servlet.http.HttpServletResponse.getHeader(Ljava/lang/String;)Ljava/lang/String;*
>>>
>>> If anyone can help me it would be massively appreciated, as I can't 
>>> really do much without Super Dev Mode
>>>
>>> Full info here: 
>>> http://stackoverflow.com/questions/38979519/why-cant-gwt-connect-to-superdevmode-server-in-multi-module-maven-project
>>>
>>> Thanks to all for your great work on GWT 2.8. It really is appreciated :)
>>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "GWT Users" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/google-web-toolkit/dF8KhbxnlBY/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> google-web-toolkit+unsubscr...@googlegroups.com .
>> To post to this group, send email to google-we...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/google-web-toolkit.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Drew Spencer
>

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

Re: Problems connecting to Super Dev Mode server with 2.8 / multi-module project

[JonL]

Besides possibly switching to the gwt-maven-archetypes as Frank suggested, 
I just added a comment to my answer.  The problem is that you don't need 
servlet-api jars on your classpath at all. GWT provides the appropriate 
classes for compile time in gwt-user and gwt-dev.

On Thursday, August 18, 2016 at 5:54:12 AM UTC-7, Drew Spencer wrote:
>
> Hey all, I have recently changed the structure of my project to separate 
> client, server and shared code into their own maven projects (modules).
>
> I am getting a HTTP Error 500 related to the Servlet API: 
> *java.lang.NoSuchMethodError: 
> javax.servlet.http.HttpServletResponse.getHeader(Ljava/lang/String;)Ljava/lang/String;*
>
> If anyone can help me it would be massively appreciated, as I can't really 
> do much without Super Dev Mode
>
> Full info here: 
> http://stackoverflow.com/questions/38979519/why-cant-gwt-connect-to-superdevmode-server-in-multi-module-maven-project
>
> Thanks to all for your great work on GWT 2.8. It really is appreciated :)
>

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

Re: Return a HorizontalPanel to a DisclosurePanel when I perform an AsyncCallback

[JonL]

Your order of operations appears incorrect.  From your original code I 
don't see where GetAddressHandler.addressHorizontalPanel is ever actually 
added to the addressDisclosurePanel.


On Tuesday, August 9, 2016 at 3:15:42 PM UTC-7, Glyndwr Bartlett wrote:
>
> Hi Jens,
>
> I have spent over three weeks trying to get this to work. I have tried to 
> include your suggestion; however, I just can not get it to work. Any 
> assistance you, or anyone else, can provide would be greatly appreciated.
>
> Kind regards,
>
> Glyn
>
> On 8 August 2016 at 19:16, Glyndwr Bartlett  > wrote:
>
>> Hi Jens,
>>
>> When I do this (in onSuccess) I get the error: addressDisclosurePanel 
>> cannot be resolved
>>
>> Are you ale to provide me with code examples please as I am not a real 
>> programmer I am doing this for Scouts.
>>
>> Kind regards,
>>
>> Glyn
>>
>>
>> On 8 August 2016 at 18:31, Jens  
>> wrote:
>>
>>> Move
>>>
>>> //addressDisclosurePanel.add(addressHorizontalPanel);
>>>
>>> into your GetAddressHandler and pass in the newly created 
>>> addressDisclosurePanel? Alternatively use an anonymous class as callback.
>>>
>>> -- J.
>>>
>>> -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "GWT Users" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/google-web-toolkit/taQlLOMZ3zw/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to 
>>> google-web-toolkit+unsubscr...@googlegroups.com .
>>> To post to this group, send email to google-we...@googlegroups.com 
>>> .
>>> Visit this group at https://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 "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] gwtproject.org site

[JonL]

If everything is static pages, what about firebase?

-- 
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/2c6674a4-3ffa-4198-a999-5b2de29146f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GWT RPC in GWT 3.0+

[JonL]

Agreed, it's all a matter of perspective.  I use GWT-RPC alot, I actually 
don't see anything wrong with the underlying mechanisms, except for the 
SerializationPolicy and its generator.  It's the SerializationPolicy 
generation that is the main culprit for the deficiencies perceived in 
GWT-RPC.  However, I think that they don't have to be part and parcel and 
in GWT 3.0, I would personally like to see them separated and the 
SerializationPolicy made pluggable, instead of ripping out GWT-RPC.  IMO, 
if the Serialization policy generation were made pluggable, then we could 
have different solutions that provide different tradeoffs and GWT devs 
could choose the solution that best suits them.

On Tuesday, July 19, 2016 at 1:34:28 PM UTC-7, clou...@gmail.com wrote:
>
> I was contrasting the blog post to the presentations Ray/Daniel have given 
> in the past, hence the Singular example preceding what you are quoting.  
> These are on youtube and I've also attended their presentations in person.
>
> I'm not trying to argue the compilation efficiency of GWT-RPC or get an 
> explanation of why it is so slow or say there aren't alternatives.  If I am 
> giving off those impressions, I apologize.
>
> I am attempting to point out (poorly I suppose) that the value of the 
> feature largely stems from one's perspective or point of view.  When one 
> uses GWT-RPC, one trades the compile-hit for the functionality.  Similarly 
> with SOYC reports or massive numbers of permutations, you can generate 
> them, however they incur a time/space cost.  These are choices, they have 
> costs, and my point has largely been to let the users decide if the 
> trade-offs fit their needs or not. (Please don't explain how SOYC/Perms 
> don't impact incremental compile!)
>
> Most of the GWT-RPC criticism here (and in the blog post) are purely 
> technical detail about some of its shortcomings and its impact on 
> incremental compile.  From the detailed technical point of view, 
> Daniel/Thomas make accurate observations and there is not much to discuss.  
> However, at the feature level of GWT-RPC, given its flaws/quirks, many 
> folks would still opt to use it in at least some situations with the cost 
> it incurs.
>

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

Re: Eclipse Neon - Can't load plugin

[JonL]

Looks like it is being worked on now.

On Thursday, July 14, 2016 at 6:59:35 AM UTC-7, Michael Joyner wrote:
>
> Heads up!
>
> The latest GWT plugin from github does not work with NEON.
>
> There is a pending pull request from Jun 8 2016 which has a fix, but it 
> has not been rebuilt with the patch yet.
>
> "axls" has posted a link to a an alternative build with the patch applied:
>
>
> * axls  * commented 20 days ago 
> 
>  
>
> Experimental build with this fix can be installed from 
> 
> https://dl.bintray.com/axls/gwt-eclipse-plugin.
> GWT part works for me, but I'm not sure about AppEngine (never used this 
> one).
>
>
> -Mike
>

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

Re: GWT RPC in GWT 3.0+

[JonL]

While I agree that it could theoretically work with annotations, 
annotations require access to code, so for things you have no control over, 
you either would need to implement custom serialization anyways, or use the 
GWT serialization.

I personally think there are optimizations to be had in the serialization 
policy generator that would prevent that whole classpath rescan issue, but 
I haven't had a chance to look into the code.

If we were to use annotations, I think it would be better to use 
annotations on the RPC mechanism.

On Wednesday, July 13, 2016 at 9:23:19 AM UTC-7, Thomas Broyer wrote:
>
>
>
> On Wednesday, July 13, 2016 at 5:53:20 PM UTC+2, Paul Robinson wrote:
>>
>>
>> On 13 Jul 2016 9:17 a.m., "Kay Pac"  
>> wrote:
>> >
>> > Will the gwt serialization mechanism used in GWT-RPC remain? GWT object 
>> serialization has been plugged into the atmosphere (realtime 
>> communication/websockets) GWT extension. It would be useful to know if we 
>> should migrate away from the GWT serialization and towards JSON.
>>
>> It's the serialisation that's the problem, so it will be gone in 3.0. 
>> JSON is a good choice. (I'm moving that way)
>>
>
> The actual problem is not serialization per se, it is that the RPC 
> generator scans the whole classpath for subclasses of transferred classes 
> to generate their specific ser/deser code (taking into account their 
> CustomFieldSerializer if one exists).
> RPC (thus probably Atmosphere) could be made to work (as annotation 
> processors) if they use another mechanism to determine what can be 
> transferred (e.g. annotations similar to RequestFactory's @ExtraTypes).
> I believe Daniel Kurka said something along those lines a year ago when 
> first talking about those changes. The logical next question is: is there 
> anyone willing to make those changes and continue to maintain GWT-RPC? The 
> answer seemed to be (have been?) "at least that won't be Google", and this 
> is why people start to "panic". That does not mean RPC will be gone (that 
> doesn't mean it'll still be there either).
> But let's concentrate on 2.8 for now.
>

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

Re: java script file linking with gwt java file

[JonL]

You need to provide more info for a definitive answer, but it is likely a 
race condition,either in the semantics of your html or just because of the 
manner in which GWT loads.  You will likely want to add some sort of check 
that the function exists and do a deferred scheduling until the point where 
the function exists. You will also need to make sure that you are 
referencing the function correctly via JSNI using the $wnd., IE 
$wnd.MakeTextBoxUrduEnabled(). 
You could also provide a Interface wrapper for the class.

Options for checking loaded:

1. manual checks
2. Instead of adding the js via html, you can use scriptInjector which 
provides a callback interface.

On Thursday, June 23, 2016 at 4:43:02 AM UTC-7, Syed Shahkar Raza wrote:
>
> Hey there,
> i m working on GWT Urdu Editor application. i have managed to write 
> javascript file to convert data in unicode. but in my entrypoint class i m 
> unable to call the function which is being used in .js file i m attaching 
> files . please kindly help me out.
>

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

Re: window.showModelDialog replacement

[JonL]

There is a new html5 dialog element that is being implemented in various 
browsers and a pollyfill that will give you what you need, cross posted 
from my reply on the GWT google+ community:

 
This is the new html5 way:

http://www.w3schools.com/jsref/dom_obj_dialog.asp
http://www.w3schools.com/tags/tag_dialog.asp

Pollyfill:

https://github.com/GoogleChrome/dialog-polyfill

On Tuesday, May 24, 2016 at 2:02:52 AM UTC-7, David wrote:
>
> I am using GWT to improve an existing web site written in ASP. This site 
> has a lot of window.showModalDialog. It needs to run in Android phones too. 
> The window.showModalDialog has been disabled by Chrome it is giving me 
> error as "undefined is not a function". I can use window.open to replace 
> it. But I can not get a return value from window.open. 
> Can anyone please tell me what is the alternative for the 
> window.showModelDialog or how to get a return value from window.open?
>
> Thanks,
>
> David
>

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

Re: GWT, Firefox, and focusout

[JonL]

This is not a GWT issue really, so let me GTFY:

https://gist.github.com/nuxodin/9250e56a3ce6c0446efa

On Thursday, April 21, 2016 at 1:16:00 PM UTC-7, N Troncoso wrote:
>
> I have an issue where an event isn't firing in Firefox, and it turns out 
> this is because Firefox doesn't currently support the focusin and focusout 
> events.
>
> This is a problem in a custom cell where I'm overriding onBrowserEvent. On 
> the blur event, the ValueUpdater parameter is null, but it's not null on 
> the focusout event. How can I work around this issue?
>

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

Re: What needs to be done after a successful login

[JonL]

There are multiple options you could take.  One would be to use something 
like spring and redirect to a separate url.  Another might be to use code 
splitting and at the time of login, download the rest of the page. 
 Finally, you could just download all the code in one module, whether the 
user is logged in or not.

On Monday, April 11, 2016 at 7:10:53 AM UTC-7, Olar Andrei wrote:
>
> Hello,
>
> I'm new to GWT and a I have a problem, which I don't understand quite 
> well. I'm making a GWT application where a user is required to log in. So I 
> do my stuff, by checking the username and password if they match and so on.
> But, on the onSuccess() method, what needs to be done in order to open the 
> actual application ? I mean the current application is just the login 
> screen with the DB connection. What needs to be done if they match, how do 
> I open a new page, or a new application... ?
>
> I understood that GWT basically is just a one-page application. Then how 
> should I do this ? 
>
> Thanks in advance.
>
> DBConnectionAsync rpcService = (DBConnectionAsync) 
> GWT.create(DBConnection.class);
> ServiceDefTarget target = (ServiceDefTarget) rpcService;
> String moduleRelativeURL = GWT.getModuleBaseURL() + "DBConnectionImpl";
> target.setServiceEntryPoint(moduleRelativeURL);
> rpcService.authenticateUser("admin", "admin", new AsyncCallback() {
>@Override
>public void onSuccess(User result) {
>  // What to do here ?
>}
>@Override
>public void onFailure(Throwable caught) {
>   // Failure
>}
> });
>
>
>

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

Re: Can anyone help me to copy the text to clipboard in a simple way and which works on all browsers

[JonL]

This might be helpful:

https://www.lucidchart.com/techblog/2014/12/02/definitive-guide-copying-pasting-javascript/

On Monday, March 28, 2016 at 12:06:42 PM UTC-7, Dhinakar Reddy Pothireddi 
wrote:
>
> Sorry Ed, I didn't work and even this is not what I need. I want to access 
> the clipboard in the Chrome with some appropriate JSNI. The code I posted 
> previously works for IE but fails on Chrome. Thanks.
>
> On Monday, March 21, 2016 at 7:48:50 PM UTC+5:30, Ed wrote:
>>
>> Hi,
>>
>> Try this:
>>   
>>  final HTML CopyIcon = new HTML("Copy");
>> 
>> CopyIcon.setStyleName("gwt-HTMLGreen");
>> CopyIcon.setTitle("Drag and Drop");
>> 
>> CopyIcon.getElement().setDraggable(Element.DRAGGABLE_TRUE);
>>
>> CopyIcon.addDomHandler(new 
>> DragStartHandler() {
>>
>> @Override
>> public void 
>> onDragStart(DragStartEvent event) {
>>
>> event.setData("text/plain", 
>> YOURDATATOCOPY);
>>
>> 
>> event.getDataTransfer().setDragImage(CopyIcon.getElement(), 10, 10);
>>
>> }
>>
>> }, DragStartEvent.getType());
>>
>> Hope this helps
>>
>> Ed
>>
>>
>> On Mon, Mar 21, 2016 at 8:10 AM, Dhinakar Reddy Pothireddi <
>> dhinaka...@gmail.com> wrote:
>>
>>> Can anyone help me to copy the text to clipboard in a simple way and 
>>> which works on all browsers especially on Safari, Chrome and IE and with 
>>> out the need of flash or any other apps. Thanks in advance
>>>
>>> public static native void 
>>> copyFrom(com.google.gwt.user.client.Element element) /*-{
>>>   $wnd.window.clipboardData.setData('text', element.innerText);
>>> }-*/;
>>> public static native void pasteTo(com.google.gwt.user.client.Element 
>>> element) /*-{
>>>   $wnd.window.clipboardData.getData(element);
>>> }-*/; 
>>> This code only works on IE and returns an exception on Chrome.
>>>
>>> I need to process this event on a button click.
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "GWT Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to google-web-toolkit+unsubscr...@googlegroups.com.
>>> To post to this group, send email to google-we...@googlegroups.com.
>>> Visit this group at https://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 "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GXT 2.3.1 Cannot read property 'style' of null on google chrome version 49

[JonL]

Looks to me, based on the stacktrace, that you have a race condition. 
 Based on the trace, it appears that you are updating an object after 
receiving data from the server.  There are many things that can affect and 
effect this timing.  Many GXT elements, especially older GXT versions, have 
properties that can not be modified until the element is attached the first 
time.  So if the data comes back before the elements are attached and you 
attempt to update the widgets, this kind of thing can happen.  That is the 
best I can say without looking at the code in question.


On Tuesday, March 29, 2016 at 2:42:16 AM UTC-7, akshatha shetty wrote:
>
> We keep getting this issue in chrome 49 when we access pages with grid and 
> hidden columns.And the same issue is not reproducible in Firefox.
> Please let me know if any one else face this issue
> stack trace for reference 
>
>
> SEVERE: Uncaught exceptioncom.google.gwt.core.client.JavaScriptException: 
> (TypeError) : Cannot read property 'booleanValue_2_g$' of undefined
> at Unknown.wrap_4_g$(Exceptions.java:36)
> at Unknown.onSuccess_1651_g$(SharesPage.java:211)
> at Unknown.onSuccess_1650_g$(SharesPage.java:205)
> at Unknown.onSuccess_1546_g$(CifsConfigCModeOperations.java:686)
> at Unknown.onSuccess_1547_g$(CifsConfigCModeOperations.java:674)
> at Unknown.onOriginServerRequestSuccess_1_g$(NaZapiServer.java:272)
> at Unknown.onSuccess_181_g$(NaHttpServer.java:49)
> at Unknown.onSuccess_4_g$(OriginServerRequest.java:354)
> at Unknown.passResponse_2_g$(AbstractAuthenticator.java:277)
> at Unknown.handleResponse_0_g$(AbstractAuthenticator.java:367)
> at Unknown.intercept_2_g$(AbstractAuthenticator.java:262)
> at Unknown.onResponseReceived_2_g$(OriginServerRequest.java:264)
> at Unknown.fireOnResponseReceived_0_g$(Request.java:250)
> at Unknown.onReadyStateChange_0_g$(RequestBuilder.java:412)
> at Unknown.anonymous(XMLHttpRequest.java:329)
> at Unknown.apply_0_g$(Impl.java:247)
> at Unknown.entry0_0_g$(Impl.java:300)
> at Unknown.anonymous(Impl.java:72)
> error_2_g$ @ ConsoleLogHandler.java:69
> ConsoleLogHandler.java:77 Mon Mar 28 11:09:41 GMT+530 2016 
> INFO: Shares Page - Hidden
> ConsoleLogHandler.java:77 Mon Mar 28 11:09:41 GMT+530 2016 
> INFO: API request start : qtree-list-iter
> XMLHttpRequest.java:343 Refused to set unsafe header 
> "Content-Length"$setRequestHeader_0_g$ @ XMLHttpRequest.java:343
> ConsoleLogHandler.java:77 Mon Mar 28 11:09:41 GMT+530 2016 
> INFO: API response received : qtree-list-iter
> SuperDevModeLogger.java:71 Error in loading page : 
> SuperDevModeLogger.java:75 
> com.google.web.bindery.event.shared.UmbrellaException: Exception caught: 
> Exception caught: (TypeError) : Cannot read property 'getHeight_33_g$' of 
> null
>   at fillInStackTrace_0_g$
>   at Throwable_3_g$
>   at Exception_4_g$
>   at RuntimeException_3_g$
>   at UmbrellaException_3_g$
>   at doFire_0_g$
>   at fireEvent_12_g$
>   at fireEvent_17_g$
>   at goTo_0_g$
>   at processPlace_2_g$
>   at processPlace_1_g$
>   at navigateToPlace_0_g$
>   at onSelect_6_g$
>   at dispatch_322_g$
>   at dispatch_321_g$
>   at dispatch_0_g$
>   at dispatchEvent_2_g$
>   at doFire_0_g$
>   at fireEvent_12_g$
>   at fireEvent_11_g$
>   at fireEvent_28_g$
>   at onClick_187_g$
>   at onBrowserEvent_34_g$
>   at onBrowserEvent_26_g$
>   at onBrowserEvent_27_g$
>   at onBrowserEvent_28_g$
>   at dispatchEventImpl_0_g$
>   at dispatchEvent_4_g$
>   at dispatchEvent_6_g$
>   at apply_0_g$
>   at entry0_0_g$
>   at anonymous
> Caused by: com.google.gwt.event.shared.UmbrellaException: Exception 
> caught: (TypeError) : Cannot read property 'getHeight_33_g$' of null
>   at fillInStackTrace_0_g$
>   at Throwable_3_g$
>   at Exception_4_g$
>   at RuntimeException_3_g$
>   at UmbrellaException_3_g$
>   at UmbrellaException_5_g$
>   at onPlaceChange_0_g$
>   at dispatch_80_g$
>   at dispatch_79_g$
>   at dispatch_0_g$
>   at dispatchEvent_2_g$
>   at doFire_0_g$
>   at fireEvent_12_g$
>   at fireEvent_17_g$
>   at goTo_0_g$
>   at processPlace_2_g$
>   at processPlace_1_g$
>   at navigateToPlace_0_g$
>   at onSelect_6_g$
>   at dispatch_322_g$
>   at dispatch_321_g$
>   at dispatch_0_g$
>   at dispatchEvent_2_g$
>   at doFire_0_g$
>   at fireEvent_12_g$
>   at fireEvent_11_g$
>   at fireEvent_28_g$
>   at onClick_187_g$
>   at onBrowserEvent_34_g$
>   at onBrowserEvent_26_g$
>   at onBrowserEvent_27_g$
>   at onBrowserEvent_28_g$
>   at dispatchEventImpl_0_g$
>   at dispatchEvent_4_g$
>   at dispatchEvent_6_g$
>   at apply_0_g$
>   at entry0_0_g$
>   at anonymous
> Caused by: com.google.gwt.core.client.JavaScriptException: (TypeError) : 
> Cannot read property 'getHeight_33_g$' of null
>   at wrap_4_g$
>   at adjustHeights_0_g$
>   at onAttach_16_g$
>   at onAttach_28_g$
>   at doAttachNative_0_g$
>   at doAttach_1_g$
>   at doAttach_2_g$
>   at doAttachChildren_24_g$
>   at onAttach_0_g$
>   at onAttach_1_g$
>   at doAttachNative_0_g$
>   at doAttach_1_g$
>   at attachChildren_0_g$
>   

Re: GWT 2.8-SNAPSHOT has broken JSP support in SDM & DM

[JonL]

Since the upgrade to Jetty 9.2 was just completed recently, I would submit 
a bug.

On Monday, February 29, 2016 at 11:23:41 AM UTC-7, Bauna wrote:
>
> Hi Guys,
> After updating to Jetty 9.2 in GWT 2.8 the JSP support is not working any 
> more during debug (it doesn't matter if you use SDM o DM).
> It seems that since Jetty 9.2[1] jsp support is not enabled by default and 
> need to enabled when embedding. As a workaround you can add this snippet[2] 
> to web.xml.
> I don't know if I this expected or I should fill a bug.
>
> [1] 
> http://www.eclipse.org/jetty/documentation/current/configuring-jsp.html 
>
> [2] Code Snippet
>  
> jsp
> org.apache.jasper.servlet.JspServlet
> 
> logVerbosityLevel
> DEBUG
> 
> 
> fork
> >false
> 
> 
> keepgenerated
> >true
> 
> 0
>   
>  
>   
> jsp
> *.jsp
> *.jspf
> *.jspx
> *.xsp
> *.JSP
> *.JSPF
> *.JSPX
> *.XSP
>   
>

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

Re: Unable to install GWT Developer Plugin (ver 1.0.11357) on Chrome 48

[JonL]

If you are running in eclipse and want to debug your server and client code 
both in eclipse, you can use the SDBG Plugin.  https://sdbg.github.io/

I believe IntelliJ has similar support built in or through the gwt IntelliJ 
plugin.

On Monday, February 1, 2016 at 5:48:11 AM UTC-7, va...@ant.ee wrote:
>
> You can't see server-side code at the browser. I believe every class that 
> is marked in gwt.xml file as translatable generates source maps, but this 
> is not server-side code. 
> I will try shortly what you have suggested. Thanks!
>

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

Re: Ready made Ui component set for GWT

[JonL]

Another option is to use a framework that you know is going to stick around 
through each iteration, such as GXT or Vaadin, which are both part of the 
steering committee and would be the likely candidates for continuing a 
widget hierarchy.

I am personally hoping we will see the base Widget classes remain in GWT 
proper and the rest of the actual widgets broken into several parts, 
UIBinder, CellWidgets, and possibly LayoutWidgets as separate libraries, 
then you only import what you need and someone can pick up the maintenance 
of each or add additional libraries like GWT-Polymer or something that are 
still compatible between them.  

That would be the biggest loss to remove Widget from GWT proper, possible 
loss of compatibility between different widget sets without jumping through 
a bunch of hoops.

On Friday, December 11, 2015 at 10:36:39 AM UTC-7, gau...@ainosoft.com 
wrote:
>
> As I understand the new advise for using GWT is when we need ready 
> components such as lists, grids etc. we are encouraged to use ui components 
> from polymer or other such framework. 
>
> Is this understanding correct ?
>
> If yes, why so ?
>
> If not, is it a good idea to create a new pure GWT Ui component library on 
> the lines of smart GWT / ext-gwt ?
>
> TIA,
> Gautam
>

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

Re: How to Load GWT theme Dynamically

[JonL]

There are a myriad set of approaches that you can use

The easiest way to do this with GWT, is to inherit them both and have a 
primary stylename which differentiates them where different, then apply 
that primary style name to the body.

Another ploy is to not use inherits for particular pieces, but use 
resources.  Then programmatically load the resources.

Finally, you could also create multiple modules for each theme, then use a 
servlet/jsp or some other logic in an entry point to switch/import the 
appropriate modules.

On Thursday, November 12, 2015 at 3:18:37 AM UTC-7, abdul wrote:
>
> I have an application built on GWT with internationaliation. I want to 
> load the GWT theme dynamically.For example:If 
> (`localhost:8080/GWTApps/app.html`) then load this ` name='com.google.gwt.user.theme.clean.Clean'/>` theme or else 
> (`localhost:8080/GWTApps/app.html=ar`) load this ` name='com.google.gwt.user.theme.clean.CleanRTL'/>`.How to achieve this 
> dynamically any idea or thoughts on this?
>

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

Re: GWT as a "thin" layer over JavaScript?

[JonL]

There are multiple ways to do this.  

See these pages:

http://www.gwtproject.org/doc/latest/DevGuideCodingBasicsJSNI.html
http://www.gwtproject.org/doc/latest/DevGuideCodingBasicsOverlay.html

GWT 2.8, if I remember correctly, will also introduce a new Elemental 
generator, so the Elemental jar will always be up to date.

Vaadin also has an api generator for GWT.

https://github.com/vaadin/gwt-api-generator

On Monday, October 26, 2015 at 2:51:18 AM UTC-7, negora wrote:
>
> Hello:
>
> I code in both JavaScript and Java. I make my back-ends with Java whereas 
> I use JavaScript for the front-ends. Nothing new. However, for the last 
> years I aimed my career so much to Java, that I missed out many important 
> JavaScript libraries and projects. Instead, I always used my old custom 
> JavaScript libraries. Now I want to change that, but I got a little tired 
> of the dynamic typing, among other ugly things of JavaScript. That's why 
> I'm considering to move either to TypeScript or to GWT.
>
> In the case of GWT, I know that I'm "arriving" very late. There are some 
> people that even told me to stay away from it. However, I also want to hear 
> directly from people who still use GWT.
>
> I don't want too much abstraction of the DOM. Indeed, I want to have 
> absolute control over it if necessary. Could be GWT used that way, as a 
> "thin" layer over JavaScript? I read about Elemental, but it seems to be 
> very tied to WebKit and experimental. I also have read about GwtQuery. 
> Would it be what I need to manipulate the DOM, instead of Elemental? Is it 
> still maintained? Does it still receive new features?
>
> With this I don't mean that I'm not interested in using the GWT widgets. 
> It's the opposite really. But I want to be sure that, if I need it, I still 
> can do things at a lower level.
>
> Thank you.
>
>

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

Re: GWT as a "thin" layer over JavaScript?

[JonL]

I think the key to remember is that when working on the client side code 
for GWT is that, even though you are writing in Java, your are ultimately 
writing Javascript.  It's a key mindset, there is nothing that you can't do 
in Javascript that you can't do in GWT with the right mindset.  Typescript 
is even just javascript once its boiled down and sent to the browser.

The GWT compiler can even offer you some optimizations and performance 
gains over regular Javascript.

If you find that you don't need some of the things at runtime that GWT 
enables, like type casting, class checking, etc, you can turn them off via 
a compiler flag.  Maybe you only use those flags during development and 
testing, but turn them off in production to reduce code size and speed 
things up.

GWT client side code isn't a wrapper around Javascript, it IS javascript, 
highly optimized and transpiled from Java.  "Wrappers" of common Javascript 
projects are simply thin facades over the javascript, if they are written 
correctly, according to my standards.

GWT doesn't preclude the usage of other Javascript libraries either and 
there are very few instances where you would find GWT incompatible with any 
particular Javascript project.

On Monday, October 26, 2015 at 8:29:35 AM UTC-7, negora wrote:
>
> That information is interesting. I had read about JSNI, but not about 
> JavaScript overlays. The tool from Vaadin also looks like useful. Thank you.
>
> I guess I'll have to read the entire tutorials and documentation from the 
> GWT website to know if I'm going to feel comfortable in this new scenario. 
> I'm so used to do all these things with JavaScript, that I'm a little 
> afraid :S .
>
>
> On 26/10/15 14:57, JonL wrote:
>
> There are multiple ways to do this.  
>
> See these pages:
>
> http://www.gwtproject.org/doc/latest/DevGuideCodingBasicsJSNI.html
> http://www.gwtproject.org/doc/latest/DevGuideCodingBasicsOverlay.html
>
> GWT 2.8, if I remember correctly, will also introduce a new Elemental 
> generator, so the Elemental jar will always be up to date.
>
> Vaadin also has an api generator for GWT.
>
> https://github.com/vaadin/gwt-api-generator
>
> On Monday, October 26, 2015 at 2:51:18 AM UTC-7, negora wrote: 
>>
>> Hello:
>>
>> I code in both JavaScript and Java. I make my back-ends with Java whereas 
>> I use JavaScript for the front-ends. Nothing new. However, for the last 
>> years I aimed my career so much to Java, that I missed out many important 
>> JavaScript libraries and projects. Instead, I always used my old custom 
>> JavaScript libraries. Now I want to change that, but I got a little tired 
>> of the dynamic typing, among other ugly things of JavaScript. That's why 
>> I'm considering to move either to TypeScript or to GWT.
>>
>> In the case of GWT, I know that I'm "arriving" very late. There are some 
>> people that even told me to stay away from it. However, I also want to hear 
>> directly from people who still use GWT.
>>
>> I don't want too much abstraction of the DOM. Indeed, I want to have 
>> absolute control over it if necessary. Could be GWT used that way, as a 
>> "thin" layer over JavaScript? I read about Elemental, but it seems to be 
>> very tied to WebKit and experimental. I also have read about GwtQuery. 
>> Would it be what I need to manipulate the DOM, instead of Elemental? Is it 
>> still maintained? Does it still receive new features?
>>
>> With this I don't mean that I'm not interested in using the GWT widgets. 
>> It's the opposite really. But I want to be sure that, if I need it, I still 
>> can do things at a lower level.
>>
>> Thank you.
>>
>> -- 
> You received this message because you are subscribed to the Google Groups 
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to google-web-toolkit+unsubscr...@googlegroups.com .
> To post to this group, send email to google-we...@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 "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: SuperDevMode and same origin policy

[JonL]

Greg,

You can create a filter that will set the appropriate headers for things 
served from the CodeServer with a filter like the one below (from 
https://spring.io/guides/gs/rest-service-cors/) .


public class SimpleCORSFilter implements Filter {

public void doFilter(ServletRequest req, ServletResponse res, 
FilterChain chain) throws IOException, ServletException {
HttpServletResponse response = (HttpServletResponse) res;
response.setHeader("Access-Control-Allow-Origin", "*");
response.setHeader("Access-Control-Allow-Methods", "POST, GET, 
PUT, OPTIONS, DELETE");
response.setHeader("Access-Control-Max-Age", "3600");
response.setHeader("Access-Control-Allow-Headers", "Origin, 
X-Requested-With, Content-Type, Accept");
chain.doFilter(req, res);
}

public void init(FilterConfig filterConfig) {}

public void destroy() {}
}



Only use this filter in dev mode though, remove it from the web.xml for 
production.

On Wednesday, October 21, 2015 at 8:02:56 AM UTC-7, Greg wrote:
>
> Hi
>
> This is an old thread but I have similar SOP issue:
>
> I have a host page in the root of the webapp: /index.html
> I also have a web worker on public path which ends up in 
> /worker/Name.worker.js
>
> I'm starting the worker using 'new Worker(); 
> which is based on GWT.getModuleBaseUrlForStaticFiles();
>
> The problem is when running in SDM public path is hosted from CodeServer 
> and not from DevMode server where host page is located:
> http://localhost:/index.html
> http://localhost:9876//worker/Name.worker.js
>
> Is there any workaround for this except moving worker file from public 
> path to webapp directory?
>
> Greg
>
> On Monday, March 4, 2013 at 11:22:45 AM UTC+1, Thomas Broyer wrote:
>>
>>
>>
>> On Monday, March 4, 2013 10:45:35 AM UTC+1, Harold wrote:
>>>
>>> Hi Thomas,
>>>
>>> Thanks for you answer.
>>>
>>> Following your suggestion ( new Image(myImageResource) ), there is no 
>>> more security error :)
>>>
>>> All my textures are loaded but are almost empties. According to 
>>> WebGLInspector all textures have size 1x1 with a transparent pixel.
>>> It looks like that the HTMLImageElement obtained via image.getElement() 
>>> is not properly filled now.
>>>
>>> An idea about that ?
>>>
>>
>> The image then is probably a "clipped image" using a sprited image: the 
>> image itself is a 1×1px transparent gif (clear.cache.gif, served from the 
>> same origin as the app) and the image is set as its background, with 
>> background-position and clip to only show the portion of the sprited image 
>> that corresponds to the original image. That makes me think we should add a 
>> isComplete() or isSprited() to ImageResource to "optimize" the way we 
>> create Image widgets out of ImageResources (which I happen to have already 
>> proposed in issue 7403 
>> ).
>>
>> Anyway, that explains why the security error has vanished.
>> So in the mean time, revert to "new Image(myImageResource.getSafeUri())" 
>> (no need to use asString(), there's an overload taking a SafeUri argument), 
>> but then I bet you'll have the security error back…
>>
>>>

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

Re: [gwt-contrib] Re: Voice of the GWT Committee???

[JonL]

Alberto,

I will also say that I think you did a great job of promoting GWTCon and my 
comments should only be taken in terms of visibility of people who might 
not be entrenched in the community so steeply as we all are.  Someone new 
coming into GWT, what does the message, brand and presence say to them, if 
their first landing page is gwtproject.org.

I am probably also slightly frustrated because I can not attend GWTCon and 
there appear no plans for GWT.create yet and I can not make plans yet to 
attend.

On Friday, October 16, 2015 at 4:07:49 AM UTC-7, Alberto Mancini wrote:
>
>  
>>
>>> There is no promotion on the main GWT site of the only currently 
>>> scheduled GWT conference and the normally already scheduled GWT.create 
>>> conference, there is no chatter about.
>>>
>>
>> Conference organizers are probably the ones who should promote their 
>> conference; GWT core contributors don't have time for that. But anyone can 
>> promote the conferences, anywhere.
>> The web site is open to contributions <
>> http://www.gwtproject.org/makinggwtbetter.html#webpage> and it just 
>> happens that nobody (organizers, or anyone in the community) proposed (pull 
>> request or even just an issue) to promote the conference on the site.
>>
>
> This point is my fault probably, or at least something that matter me 
> firsthand being one of the organizers of GWTcon2015. 
>
> I Never minded to ask for a note in the site, actually there's not a 
> section for news on gwtproject and asking for a note on the front page was 
> too much promotional. 
> GWTcon has been promoted at our best actually trough all the channels we 
> can reach but any help is definitely appreciated. 
>
> Last but not least, any info on GWTcon is available at: www.gwtcon.org 
> and there's a Q organized by Arcbees scheduled for
> October 28th https://plus.google.com/+ChristianGoudreau/posts/SNMUJbF2jha
>
> and, well, just ask me if you want informations. 
>
> Cheers,
> Alberto
>
>
>

-- 
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/f3e21d16-7a4b-4bab-9d42-a311efb9ea27%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Voice of the GWT Committee???

[JonL]

Thanks for the link Thomas!  I knew something along this line must exist. 
 However, it appears that the GWT Steering google group is not listed on 
the GWT Resources page, so it is kind of hidden from view and I was unaware 
it existed.

I made a suggested edit and pull request to have it added to the GWT 
Resources page.

On Friday, October 16, 2015 at 2:35:58 AM UTC-7, Thomas Broyer wrote:
>
>
>
> On Friday, October 16, 2015 at 2:15:22 AM UTC+2, JonL wrote:
>>
>> There is no clear status of the next release or when it can be expected 
>> or what are the blockers on the Contributor forum here.
>>
>
> This is not exact: 
> https://groups.google.com/d/topic/gwt-steering/uv_WsmNkti0/discussion
> (*not* saying it's plain wrong either !)
>  
>
>> GWT 2.8 milestone on GitHub is only 14%, there are only 3 closed issues 
>> and the last release of GWT is almost a year now and only 1 person appears 
>> to be working on the next release planned features if those issues are the 
>> plan because there is no other apparent plan that has been laid out that I 
>> can find accessible.
>>
>
> The migration of issues from Google Code to GitHub earlier this summer 
> didn't keep the detailed "status" field, only a boolean open/close. At 
> Google Code, we used to keep issues opened with a FixedNotReleased status 
> until the next release (because, I believe, most people don't search for 
> closed issues). Knowing that, if you look closer, you can see that 13 open 
> issues assigned to Milestone 2.8 are actually "FixedNotReleased": 
> https://github.com/gwtproject/gwt/issues?q=is%3Aissue+milestone%3A2.8+FixedNotReleased
> But yes, the issue tracker needs some love, and I proposed a process (and 
> have some open questions) to the Steering Committee.
>  
>
>> There is no promotion on the main GWT site of the only currently 
>> scheduled GWT conference and the normally already scheduled GWT.create 
>> conference, there is no chatter about.
>>
>
> Conference organizers are probably the ones who should promote their 
> conference; GWT core contributors don't have time for that. But anyone can 
> promote the conferences, anywhere.
> The web site is open to contributions <
> http://www.gwtproject.org/makinggwtbetter.html#webpage> and it just 
> happens that nobody (organizers, or anyone in the community) proposed (pull 
> request or even just an issue) to promote the conference on the site.
>

-- 
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/8d0edec2-83b0-42c4-bc12-c806af89f7e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Voice of the GWT Committee???

[JonL]

So I agree with you 99%.  What we disagree is on this point:

On the other hand, I also think that exists some level of 
> confusion/misinformation, *but it's not a critical situation* and if you 
> spent some time in google groups, gerrit or github you end up knowing 
> exactly what's happening (doubts to google+ and ##irc).



I believe it is a critical situation for people who might want to come into 
the community or for those attempting to justify not moving to something 
new.

There is no clear roadmap on the main GWT site..  Search for GWT Roadmap, 
the first result is a link stating GWT 2.8 will be out in 3 months, back in 
January.
There is no clear status of the next release on the main GWT site.  There 
is no clear status of the next release or when it can be expected or what 
are the blockers on the Contributor forum here.  GWT 2.8 milestone on 
GitHub is only 14%, there are only 3 closed issues and the last release of 
GWT is almost a year now and only 1 person appears to be working on the 
next release planned features if those issues are the plan because there is 
no other apparent plan that has been laid out that I can find accessible.
There is no promotion on the main GWT site of the only currently scheduled 
GWT conference and the normally already scheduled GWT.create conference, 
there is no chatter about.

On Thursday, October 15, 2015 at 11:02:21 AM UTC-7, Ignacio Baca 
Moreno-Torres wrote:
>
> IMHO current organization is pretty good, docs in the official page, news 
> in google+, question and issues in Google groups and you can always chat 
> with the community in ##gwt. All this 4 places are easy to contribute, so 
> if you see less info and news is just because the community is not very 
> news friendly ;). And! I don't think this is bad at all. Maybe is only 
> motivated by the evolution of GWT, which start as a web framework but now a 
> days is more a java2js transpiler (at least is the more important and 
> evolving part, and I think than most of the work by the committee is in the 
> compiler side of GWT), and I think that front-end communities are just more 
> likely to share lot of cool things than compiler communities. 
>
> You probably find a lot of more cool things in the gxt, vaadin or errai 
> blogs, which are front end frameworks.
>
> If you want to see 'not so cool' but much more technical interenting news 
> you just subscribe to this feed 
> *https://github.com/gwtproject/gwt/commits/master.atom 
> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fgwtproject%2Fgwt%2Fcommits%2Fmaster.atom=D=1=AFQjCNEm7ZlM_c_pcDsHEmxNRkUygbthGQ>*
>
> At least, that's how I see it... ;)
>
> On the other hand, I also think that exists some level of 
> confusion/misinformation, but it's not a critical situation and if you 
> spent some time in google groups, gerrit or github you end up knowing 
> exactly what's happening (doubts to google+ and ##irc).
>
> El jue., 15 de octubre de 2015 8:35, Brian Pedersen <brian.p...@gmail.com 
> > escribió:
>
>> +1 all the way.
>>
>> I use every chance I have to spread the word about the changes JS Interop 
>> will bring to the web, but the apparent lack of engagement in the community 
>> from the people driving GWT, is giving me second thoughts.
>>
>> The official blog used to be OK, but that changed when google open 
>> sourced it, and now the closest you get to official information is 6 months 
>> old videos on youtube.
>>
>> I believe this is already driving people away from GWT, at a time where 
>> we should be getting people back, drawn by the awesomeness of GWT 3.0.
>>
>>
>> Den onsdag den 14. oktober 2015 kl. 21.51.57 UTC+2 skrev JonL:
>>>
>>> We've been using GWT for a long time.  There was some trepidation when 
>>> Google moved GWT into the open source realm and the steering committee was 
>>> announced.  A lot of good things are happening.  I see a lot of movement 
>>> here and there, but some of it appears as if it is un-directed and 
>>> un-coordinated.  Without joining like 15 different groups, it seems 
>>> impossible to get a full understanding of what is happening in GWT.  As a 
>>> project that is currently utilized by projects of many levels, I think the 
>>> only thing that keeps GWT at the forefront of anyones mind at this time has 
>>> more to do with inertia than anything else.  The closest thing that I can 
>>> come by, which appears to pull the disparate parts of GWT community 
>>> together is gwtdaily.com blog, but there is no indication how that is 
>>> run, it is not linked between any of the other gwt sites
>>>
>>> So here's my questions:
>>>
>>> Are there

[gwt-contrib] Voice of the GWT Committee???

[JonL]

We've been using GWT for a long time.  There was some trepidation when 
Google moved GWT into the open source realm and the steering committee was 
announced.  A lot of good things are happening.  I see a lot of movement 
here and there, but some of it appears as if it is un-directed and 
un-coordinated.  Without joining like 15 different groups, it seems 
impossible to get a full understanding of what is happening in GWT.  As a 
project that is currently utilized by projects of many levels, I think the 
only thing that keeps GWT at the forefront of anyones mind at this time has 
more to do with inertia than anything else.  The closest thing that I can 
come by, which appears to pull the disparate parts of GWT community 
together is gwtdaily.com blog, but there is no indication how that is run, 
it is not linked between any of the other gwt sites

So here's my questions:

Are there any plans to create a "Voice of GWT" presence anywhere which 
could act as a goto location to view progress, like the old GWT blog?

Besides each steering committee member advocating GWT as used in their 
paradigm, is there anyone who is considered the advocate for just GWT 
itself.  IE Vaadin promotes Vaadin, ArcBees promotes GWT-P and their 
various GWT projects, Sencha promotes GXT, who is going out and saying, 
lets just use GWT?

I think if there was one person who was acting as part of the GWT steering 
committee as that advocate that had a blog and was able to take the time to 
bring all the disparate threads together to present a overall view of the 
current development plan and future of GWT and status of the major efforts 
under the various tents, I think that would go a long way to assuaging many 
peoples fears that GWT is dying out and becoming irrelevant.

Or even just a central blog where members of the committee would commit to 
posting regularly.  The Google+ community is good, but I see as more of a 
discussion board and not just the platform where the community can announce 
things.

The format of gwtdaily.com is good and I see that people can submit posts 
to it so that might be a good location, I believe it is run by a 
contributor/committee member, but it doesn't appear official and has no 
links from the official GWT sites.

-- 
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/f8028d0e-d84b-467c-aeac-4a2bdc5f9784%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Could not find com.google.gwt.dom.client.MRODOMImplMozilla in types compiled from source. Is the source glob too strict?

[JonL]

If you are extending it, you should give it its own package name within 
your own package structure so that it is caught up by the compiler 
correctly.  There is no need to keep it in the same package.  IF you need 
to access private or protected variables, then you can use jsni to access 
them.

On Tuesday, October 6, 2015 at 2:25:28 AM UTC-7, narasimhu...@jda.com wrote:
>
> Hi,
>
> I extended DOMImplMozilla and wrote new MRODOMImplMozilla.java file. I 
> added below snippet in my .gwt.xml file.
>
>   
> 
> 
>   
>
> While compiling i encountered with below issue. Can any one please let me 
> know how to rectify this. My GWT version is 2.7.0.
>
>
> [INFO][ERROR] Could not find 
> com.google.gwt.dom.client.MRODOMImplMozilla in types compiled from source. 
> Is the source glob too strict?
> [INFO][ERROR] Errors in 'com/google/gwt/dom/client/DOMImpl.java'
> [INFO]   [ERROR] Line 23: Rebind result 
> 'com.google.gwt.dom.client.MRODOMImplMozilla' could not be found
>
> Thanks in Advance,
>
> Narasimhulu BB
>

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

IntelliJ IDEA/GWT/IvyIDEA

[JonL]

We are taking a look at IntelliJ IDEA.  Our current setup uses ivy for 
dependency resolution.  I found the IvyIDEA plugin, which, for the most 
part appears to work well.  There are some quirks with that that we will 
need to work through apparently, but the major problem that I am seeing is 
that super dev mode is not picking up the source files for projects on the 
class path or in the lib folder or the modules in the classpath.

The source files are in a jar of the lib folder in the www directory, but 
not being picked up.

The source files are in a module on the classpath, but not being picked up.

I see one of two possibilities:

1. IDEA is not picking up any of the sources from the other modules or from 
the ivy classpaths.
2. There is a classpath conflict because Ivy does not remove the jars for 
the open modules in the workspace.

So, has anyone else had experience with this kind of setup and have any 
pointers of where I can look to correct the issue?  Right now, IntelliJ 
IDEA is a non-starter if I can't fix this and I would like to give it as 
good a college try as I gave to eclipse when we worked out all its quirks 
with our development style.




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

Re: GWT vs js performance: Collections and Strings

[JonL]

Hmm.. in the Javascript version of the compress, you don't have a loop to 
initialize the dict like you do the map.  It appears you are updating the 
dict during the same loop.  While in the Java version, you have two 
loops.  Why the slight difference in logic?

On Wednesday, May 6, 2015 at 7:35:14 AM UTC-7, Vassilis Virvilis wrote:

 Anyway I profiled a bit. Here is the results

 compress total time:  721
 compress self: 203  ? What is it doing? The main loop probably
containsKey 180 (Map operation with jonL suggestion)
put 164 (Map)
append self 91 / total 119 (StringBuilder)
toString() 16 (StringBuilder)
valueOf 16 (convert dict_size++ to something in order to put it in the 
 map)

 The difference with the js version is around 200-250 msec. I can't imagine 
 where the next low hanging fruit would  be.

 JonL after implementing __correctly__ your suggestion I was able to trim 
 40-45 msec from the profile run (SDM). Unfortunately I cannot see that 
 improvement in the fully compiled version.


Vassilis

 On Wed, May 6, 2015 at 4:12 PM, Vassilis Virvilis vas...@gmail.com 
 javascript: wrote:

 Hi Eric,

 I haven't use the JsArray because the compression algorithm requires map 
 access and not list access.


Vassilis


 On Wed, May 6, 2015 at 12:35 PM, Eric Ponthiaux ponth...@sfeir.com 
 javascript: wrote:

 Have you done any testing with JsArray or JsArrayOf ? 


 Le mardi 5 mai 2015 14:34:46 UTC+2, Vassilis Virvilis a écrit :

 Hi,

 At some point in time I needed to handle lzw compressing/uncompressing 
 in the client so I found https://gist.github.com/revolunet/843889

 Later on I rewrite the LZW in java.

 So I did. I benchmarked the difference and the new implementation was 
 way slower when compressing. GWT/java is actually better when 
 uncompressing.

 I changed the java collections to javascript collections JsMap, and 
 JsList and the difference was greatly reduced but not enough to be able to 
 scrap the js implementation.

 My guess any remaining gains are hidden in the StringBuilder but I may 
 by wrong.

 Chrome  
 Firefox   IE
 Js  544/61   
 626/78   795/171
 Java  750/48   
 1702/48  2401/468
 JavaJsCollections  785/38   
 1398/38 1877/351

 The numbers are compressing/uncompressing
 1000 iterations with a random string multiplied 10 times

 I am using a single permutation with collapse-all. Can this be the 
 culprit?

 Any idea what to change in order to increase the performance in the 
 java code?

 Here is the code


 package com.biovista.lib.gwt.client;

 import com.google.gwt.core.client.JavaScriptObject;

 public class Util {
 private static final char DICT_SIZE = 256;

 public static class JsMapT extends JavaScriptObject {
 protected JsMap() {
 }

 public final native void put(String key, T value) /*-{
 this[key] = value;
 }-*/;

 public final native boolean containsKey(String key) /*-{
 return (key in this);
 }-*/;

 public final native T get(String key) /*-{
 return this[key];
 }-*/;

 public static JsMap createInstance() {
 return (JsMap) createObject();
 }
 }

 public static class JsListT extends JavaScriptObject {
 protected JsList() {
 }

 public final native void add(T value) /*-{
 this.push(value);
 }-*/;

 public final native int size() /*-{
 return this.length;
 }-*/;

 public final native T get(char index) /*-{
 return this[index];
 }-*/;

 public static JsList createInstance() {
 return (JsList) createArray();
 }
 }

 public static String compressLZW(String text) {
 // Build the dictionary.
 // final MapString, Character map = new HashMapString, 
 Character(
 // DICT_SIZE);
 final JsMapCharacter map = JsMap.createInstance();
 for (char i = 0; i  DICT_SIZE; i++) {
 map.put( + i, i);
 }

 char dict_size = DICT_SIZE;

 String w = ;
 final StringBuilder result = new StringBuilder();
 for (char c : text.toCharArray()) {
 final String wc = w + c;
 if (map.containsKey(wc))
 w = wc;
 else {
 result.append(map.get(w));
 // Add wc to the dictionary.
 map.put(wc, dict_size++);
 w =  + c;
 }
 }

 // Output the code for w.
 if (!w.equals())
 result.append(map.get(w));

 return result.toString();
 }

 /** uncompress a string. */
 public static String uncompressLZW(String

Re: GWT vs js performance: Collections and Strings

[JonL]

Why all the final variables in the Java version?  You aren't passing the 
variables to anonymous inner classes or anything, so there should be no 
need to mark anything final.  I'm not 100% sure what effect that will have 
on the output from the GWT compiler though as far as speed.

As far as I can tell, the biggest difference is in the way you are checking 
if a value is already in  your map.

In java code you are calling :

if (map.containsKey(wc))
w = wc;

map.containsKey converts to: return (key in this)

In javascript you are calling:

if (dict[phrase + currChar] != null) {
phrase += currChar;


According to the below speed test, key in this is the slowest of the 
options for comparing if an object contains a key and would almost double 
the runtime.

https://jsperf.com/checking-if-a-key-exists-in-a-javascript-array



On Tuesday, May 5, 2015 at 5:34:46 AM UTC-7, Vassilis Virvilis wrote:

 Hi,

 At some point in time I needed to handle lzw compressing/uncompressing in 
 the client so I found https://gist.github.com/revolunet/843889

 Later on I rewrite the LZW in java.

 So I did. I benchmarked the difference and the new implementation was way 
 slower when compressing. GWT/java is actually better when uncompressing.

 I changed the java collections to javascript collections JsMap, and JsList 
 and the difference was greatly reduced but not enough to be able to scrap 
 the js implementation.

 My guess any remaining gains are hidden in the StringBuilder but I may by 
 wrong.

 Chrome  
 Firefox   IE
 Js  544/61   
 626/78   795/171
 Java  750/48   
 1702/48  2401/468
 JavaJsCollections  785/38   
 1398/38 1877/351

 The numbers are compressing/uncompressing
 1000 iterations with a random string multiplied 10 times

 I am using a single permutation with collapse-all. Can this be the culprit?

 Any idea what to change in order to increase the performance in the java 
 code?

 Here is the code


 package com.biovista.lib.gwt.client;

 import com.google.gwt.core.client.JavaScriptObject;

 public class Util {
 private static final char DICT_SIZE = 256;

 public static class JsMapT extends JavaScriptObject {
 protected JsMap() {
 }

 public final native void put(String key, T value) /*-{
 this[key] = value;
 }-*/;

 public final native boolean containsKey(String key) /*-{
 return (key in this);
 }-*/;

 public final native T get(String key) /*-{
 return this[key];
 }-*/;

 public static JsMap createInstance() {
 return (JsMap) createObject();
 }
 }

 public static class JsListT extends JavaScriptObject {
 protected JsList() {
 }

 public final native void add(T value) /*-{
 this.push(value);
 }-*/;

 public final native int size() /*-{
 return this.length;
 }-*/;

 public final native T get(char index) /*-{
 return this[index];
 }-*/;

 public static JsList createInstance() {
 return (JsList) createArray();
 }
 }

 public static String compressLZW(String text) {
 // Build the dictionary.
 // final MapString, Character map = new HashMapString, 
 Character(
 // DICT_SIZE);
 final JsMapCharacter map = JsMap.createInstance();
 for (char i = 0; i  DICT_SIZE; i++) {
 map.put( + i, i);
 }

 char dict_size = DICT_SIZE;

 String w = ;
 final StringBuilder result = new StringBuilder();
 for (char c : text.toCharArray()) {
 final String wc = w + c;
 if (map.containsKey(wc))
 w = wc;
 else {
 result.append(map.get(w));
 // Add wc to the dictionary.
 map.put(wc, dict_size++);
 w =  + c;
 }
 }

 // Output the code for w.
 if (!w.equals())
 result.append(map.get(w));

 return result.toString();
 }

 /** uncompress a string. */
 public static String uncompressLZW(String compressed_text) {
 // Build the dictionary.
 // final ListString rmap = new ArrayListString(DICT_SIZE);
 final JsListString rmap = JsList.createInstance();
 for (char i = 0; i  DICT_SIZE; i++) {
 rmap.add( + i);
 }
 final char[] compressed = compressed_text.toCharArray();

 String w =  + compressed[0];
 final StringBuilder result = new StringBuilder(w);
 for (int i = 1; i  compressed.length; i++) {
 final char k = 

Re: GWT Material Design

[jonl]

There are ways to overcome this.

The blunt way, custom field serializers for all of the data models. 

The other solution, replace the usage of the serialization policy by 
overriding the remote servlet base implementation and using some other 
serialization, but still utilizing the RPC mechanisms.

On Sunday, March 29, 2015 at 6:47:53 AM UTC-7, Andrei wrote:

 RPC is not a good idea for mobile apps. Every change in your code may 
 result in an incompatible serialization policy. This is not a problem for 
 regular web apps - a user can load a new version by simply refreshing a 
 page. It's more of an issue if an app is installed on a mobile device - not 
 all users will update their apps at the same time, so you will have to run 
 multiple versions in parallel to keep serialization policies in sync. A 
 better option is to use a REST API which can often be extended without a 
 need for a mandatory update of all clients.

 On Saturday, March 28, 2015 at 4:29:33 PM UTC-4, mark kevin ringor wrote:

 GWT Phonegap also is added in the repository. You can check it out and 
 play with as Im studying the RPC mechanism of GWT inside phonegap.



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

Re: Development Mode will not be supported in Firefox 27+

[jonl]

https://sdbg.github.io

Allows you to debug javascript in Eclipse when running your application in 
Chrome.  Has its limitations and is a work in progress, but it works.

On Tuesday, March 3, 2015 at 1:49:47 AM UTC-7, Liam Stewart wrote:

 Debugging javascript is a king size pain in the arse if you live and 
 breath Java, super dev mode is still nowhere near good enough to *really* use 
 when you have a lot going on and you need to step through and evaluate line 
 by line the state of the application at runtime, this becomes particularly 
 important if you are delving deeply into hibernate and hazelcast 
 environment like we do.

 I was tasked with evaluating IntelliJ as a viable alternative after we 
 went to GWT.create this year, I used it for a morning and wasn't impressed 
 with what I saw... it is painfully obvious you are debugging javascript as 
 the values you want are hidden down inside elements and the debugger simply 
 won't play ball at times, having to put in a debugger API call if you 
 actually do really want it to stop is ridiculous...

 I've attached an image of how I feel google has responded to the issue of 
 dev mode - if they really cared about the developers they would have just 
 released a dev version of chrome or something for us, not dropped us in it 
 with a super dev mode that 'will definitely be good, honest, promise... at 
 some time in the infinite future'.

 Grumble.


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

Re: call a java class from GWT

[jonl]

While written in both Java on the server and client side, GWT is 
javascript, once deployed, on the client side.  So the answer to your 
question is the same for any project written for Javascript. 

Based on your description of Pinpad device, I'm guessing that your target 
user has this pinpad device installed on their machine and you want to 
communicate it.  We have a similar issue with a hardware sensor.  Our 
solution, on desktop, was to write a system tray application for each OS. 
 On mobile we wrap the web application in a UIWebView.  On all platforms we 
communicate with the web application and sensor helper via a websocket. 
 This is the only solution that we saw that limited the platform support 
requirements the most.

On Thursday, December 18, 2014 1:22:04 PM UTC-7, david esteban rodriguez 
wrote:

 Hello, I have a java class that calls a dll from a Pinpad device and what 
 I want to do is to run my java class from my GWT application. So how can I 
 do that?.

 I'll look forward your prompt reply.

 thanks   


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

Re: GWT: Decoupling Client code dependency in Server Code

[jonl]

I do something similar, but I decided that three jars were pointless.  I 
have a -user jar, which contains everything and a -server jar that I use 
for deployment which contains everything, except source, in shared/server.

So your hotfix, then would be for the -server.jar instead of the -user.jar. 
 The -user jar is only needed during client side and GWT compile.

To enforce the separation and reduce the possibility of unneeded 
serializers, I also have a common extensive rpc.blacklist that blacklists 
everything in a .client. package.  There are a few exceptions to this list 
though, because GWT does not enforce its own client/shared/server 
convention in some of the older code for RPC And Servlets so there is some 
serializable RPC things and exceptions in the client packages that are 
needed if you want to do remote logging or RPC.

On Friday, December 12, 2014 3:23:24 AM UTC-7, Sachin Gupta wrote:

 --

 *My requirement is to modularize existing GWT application so that whenever 
 required Client code can be updated and just hot fix for Client jar can be 
 done rather than complete application war deployment. *

 To achieve above requirement I modularize my existing Smart GWT code into 
 Parent-Child modules where Child modules will be Server, Client and Shared 
 Modules. Client, Server, Shared package of application will be present in 
 Client, Server, Shared modules respectively.

 I am packaging:-
 Server Module in war.
 Client Module in Jar,
 Shared Module in jar as well as jar containing Source code.

 I put dependencies relative to Shared package in Client and Server Module 
 code as both will be accessing Shared Module codebase.

 But when i am introducing Server Module's dependency in Client Module I am 
 getting compilation errors in Server Module as this is *against GWT 
 convention* wherein Client interface is extended in Server 
 implementation. 

 Can you please help me out how can i introduce server dependency in client 
 module to achieve my requirement.

 Do let me know if you need my POC code for reference.


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

Re: Current state of one .js file per module

[jonl]

If Eclipse is your IDE you can also use the SDBG plugin to debug in 
Eclipse.  https://sdbg.github.io/

If IntelliJ is your IDE, there is support there as well, but not sure how 
it works.

On Saturday, December 6, 2014 11:39:59 AM UTC-7, Luis Fernando Planella 
Gonzalez wrote:

 Ok, I'll try to use separated servers for code server and server side.

 Regarding the monolithic .js, in GWT 1.6 it was impossible to debug in 
 both Chrome and Firefox - they both crashed, and I always suspected that 
 the js / sourcemap file were too big.
 Now with GWT 2.7 I can debug normally in Chrome (didn't try in Firefox 
 yet). 
 Still I guess it could be faster to debug using separated .js files. 
 However, as this is no longer GWT's goal, ok.
 At least now debugging in Chrome is usable, and I no longer need that old 
 version of Firefox 26 which still runs the classic dev mode.

 Em sexta-feira, 5 de dezembro de 2014 12h31min41s UTC-2, Jens escreveu:

 Separate compilation mentioned in your linked issue has been reworked 
 into incremental per file compilation what you have now with GWT 2.7. The 
 benefit is that people do not have to refactor their applications into 
 multiple modules to get the benefit of faster recompiles in SDM. 


 Regarding CodeServer restarts:

 With current GWT master branch, a restart of the CodeServer reuses the 
 caches from the last compile which reduces the startup time of CodeServer 
 significantly.

 Keep in mind that you do not have to use the DevMode class to start the 
 embedded Jetty + Code Server process. You can also split these processes so 
 you do not have to restart SDM CodeServer if you do a server side change.

 DevMode -noserver or launching CodeServer directly only starts the SDM 
 code server. Then you can provide your own application server or actually 
 start DevMode -nosuperdevmode which does start classic DevMode but also 
 the embedded Jetty for your server side code.

 I rarely restart CodeServer during the work day.


 -- J.



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

Re: GWT dev plugin stopped working on Chrome 39

[jonl]

Search Portable Chrome, make sure it's the 32 bit version.

Since its another year away, I wonder what the possibility of getting one 
more build of the browser DevMode plugin?  Maybe plug some memory leaks and 
recompile it so it will work with 64 bit Chrome, where possible?

On Tuesday, November 25, 2014 3:21:28 AM UTC-7, Igor Zubchenok wrote:

 Thank you Jens, this make a sense!

 SuperDevMode has ugly debugging. Unforutnately...
 Do you know where Chrome 38 OSX can be downloaded?

 Chrome is now 64 bit on OS X and the plugin is only 32 bit.

 So you have to use a different/older browser or use SuperDevMode.



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

Re: Copying SDM's output to Phonegap's www directory for easier phone development?

[jonl]

Look at the flags of the CodeServer.  You can use flag -workDir to 
specify the directory specifically where output is compiled to.

http://www.gwtproject.org/articles/superdevmode.html

If you do not use this flag, it outputs to a temporary directory.  The 
directory is output when the CodeServer is started up.

https://gwt.googlesource.com/gwt/+/release/2.7/dev/codeserver/java/com/google/gwt/dev/codeserver/CodeServer.java

Since the CodeServer serves the code, you could also just talk to it 
directly, via its api, to download files.  IE instead of pushing the 
updated code to the phonegap app, if SDM is enabled in the compiled app, it 
will automatically redirect to the codeserver. You could look at how GWT 
turns on SuperDevMode with the old bookmarklets and do something similar by 
injecting javascript into the webpage. 

On Wednesday, November 12, 2014 11:31:20 PM UTC-7, Ali Akhtar wrote:

 There is a way to have a very fast compile - refresh cycle for phone app 
 development, i.e hitting 'Compile' for SDM, and having the app refresh on 
 your phone.

 This can be done through Phonegap's app ( http://app.phonegap.com/ ) 
 which monitors your www folder. Each time you make any changes, they are 
 sent over wifi to your phone, and your app auto refreshes on the phone. 

 A similar utility can be written, which monitors SDM's output folder. Each 
 time you do an SDM compile, it syncs the SDM output folder with phonegap's 
 www, which would then trigger a refresh on your phone.

 I think this can be very productive, and I'm happy to write this utility. 
 However, I need to know how it would determine where SDM's output directory 
 is located. I.e, can the user find out where the output is being stored, 
 and pass the path as an argument to the directory? If not, the user can 
 just input the codeserver url, and the files can be monitored via an http 
 request, although that would be less efficient.

 Please let me know of your thoughts and how to determine SDM's output 
 directory path, or if there's a better way to do what I'm trying to 
 accomplish.

 Thanks.


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

Re: GWT with Restful Web Services and Hibernate.

[jonl]

There are multiple ways to arrange your three tiers.  How are they arranged?

IE is it:
DB - DAO - REST - Client?

If that is the case, and you only want to rewrite the client portion in 
GWT, take a look at https://github.com/resty-gwt/resty-gwt.

On Tuesday, November 11, 2014 1:16:27 AM UTC-7, Ugo Giordano wrote:

 Hi all,

 I have already implemented a web application that server side has a 
 three-tier architecture with restful web service - DAO - hibernate that 
 connects to the DB.
 So, I want know how to bring this web app in GWT. Must I make special 
 integrations? There is an example of a web app with this architecture for 
 GWT?

 Thanks to all :)


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

Re: Modify the property of an object via Deferred Binding

[jonl]

I was hoping for something other than a generator.  I only need to change 
one property after instantiation, and only sometimes, at this point and it 
seems like a lot of work to write a generator to do that.  I'd likely just 
create an override of the class at this point and update the rebind that 
already exists.

It would be awesome if the gwt compiler would support something along these 
lines:

replace-with class=com.my.FavoriteImplementation
when-type-is class=com.SomeInterface/
set-object-property type=boolean value=false 
name=turnFeatureOn/
set-object-property type=string value=MyPrimaryStyle 
name=defaultStyle/
set-object-property name=complexProperty 
provider=com.my.ComplexPropertyProvider/
/replace-with

This might actually reduce the need for custom generators and make 
customization via GWT.create a bit more powerful.

On Sunday, October 26, 2014 3:06:15 PM UTC-7, Jens wrote:

 Ignacio is right. Use a Generator that generates an implementation of your 
 interface and implements the interface methods based on some property value 
 (generators have access to properties). If your implementation is generally 
 the same except some small changes then you can also create an abstract 
 class that implements your interface and then generate a sub class which 
 only implements the property specific changes.

 Since properties only exist at compile time you need to generate property 
 specific code. You can not do that at runtime.

 -- J.


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

Modify the property of an object via Deferred Binding

[jonl]

I am using DeferredBinding to create the instance of an interface.  Now 
there is a property on the instance that is instantiated that I would like 
to change for every object created of that type via the GWT.create() call. 
 Is there a way in the replace-with settings to do this, without 
overriding the class?  Or is there a way to read a property defined in the 
.gwt.xml using the set-property tag at runtime?

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

Re: GPE Preview Build Testing

[jonl]

I would be interested.  Will it also work in Kepler or Luna only?

On Monday, October 13, 2014 10:31:01 AM UTC-7, Brandon Donnelson wrote:

 Would anybody be interested in testing a GPE preview build with the SDM 
 enhancement? 

 (This will only work in a clean Luna install, and should not be handed 
 out, or it could create issues.)

 Thanks,
 Brandon


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

Re: Understanding GWT serialzation

[jonl]

I had a similar issue.  The problem ended up being that the custom field 
serializer was not being included on the GWT source path during compilation in 
some instances causing the server and client side to use different serializers. 
 One the custom and one the auto generated.  Since the classnames of the 
serializers are used as part of the hashcode you will end up with different 
hashcodes. I personally think this may cause people issues when adding and 
removing serializers when necessary.   I don't see why the name of the class 
and maybe the serial version uid are not the sole factors in determining the 
hash.  I haven't had much time to look into it.  If it were it might be 
possible to generate more stable serialization policies.  I still hate that the 
policy file is a hashcode of the contents and not something that is more 
lenient.

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

Re: recognizing errors in embedded JS code

[jonl]

This might be something that the sdbg plugin can handle or should be able 
to handle in the long run..

https://github.com/sdbg/sdbg

On Saturday, September 13, 2014 4:26:16 PM UTC-7, Magnus wrote:

 Hi,

 when using embedded JS code, I found that I sometimes do not recognize 
 simple errors like this:


  private native JavaScriptObject makeAnnotation (int x,int y,int as,char c)
  /*-{

   var pi = i * cs + cs / 2;

  ...

   return (i);
  }-*/;


 In this case, variable i is not defined. But there is no compiler or 
 runtime error reported. It simply doesn't work and you get the (chrome) 
 browser message paused in debugger. When you continue debugging, you find 
 yourself somewhere in exception handling code in Impl.java. Then, after 
 setting additional breakpoints, you fnally see, what's wrong.

 This process is time-consuming. How can you detect such simple errors 
 sooner?

 Thanks
 Magnus




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

Re: GWT 2.2.0 does not serialize/deserialize basic Java types if not referenced explicitly

[jonl]

One thing that I do to prevent rpc serlizer generation explosion as well is 
to use the following in my base gwt.xml module:

extend-configuration-property name=rpc.blacklist value=-.*\.client\..*
/
extend-configuration-property name=rpc.blacklist value=
-.*\.shared\..*Service/
extend-configuration-property name=rpc.blacklist value=
+.*\.client\..*Exception/
extend-configuration-property name=rpc.blacklist value=
+.*\.client\.rpc\..*/

This basically prevents anything in the client package that is not an 
exception or used in the RPC process from being added to the GWT generated 
serialization policy.  In the shared package, it prevents Service 
interfaces from being added to the serialization policy as well, as long as 
the class name ends in service.

On Tuesday, September 16, 2014 6:51:56 PM UTC-7, Justin Zhang wrote:

 I'm so excited to see so many quality replies. This is really the place to 
 get in-depth knowlege of GWT.

 Regarding my own issue, the service interface was designed a couple of 
 years by someone who is no longer with the company. I just want to explore 
 the possibility to upgrade GWT to have better tooling with minimal changes 
 to the legacy code.

   I understand the current service interface design does not work the 
 pricinple of GWT-RPC serialzation/deserialization. But it avoids a great 
 number of similar looking service methods or the need of value object. I'm 
 just wondering if we can enhance the RPC policy file generation code to 
 consider additional hints for generic types like Object. The hints indicate 
 what specific types like java.lang.Integer, java.util.Date will the generic 
 type be at runtime. The specification of specific types can be an 
 annotation in the service interface or deferred binding config in module 
 xml.

   Thank you very much!
 On Monday, September 15, 2014 1:37:35 AM UTC-7, Thomas Broyer wrote:



 On Monday, September 15, 2014 6:57:24 AM UTC+2, Justin Zhang wrote:

 Hi GWT experts,
   I had a problem with the GWT-RPC on 2.2.0 and above.

   I have a generic service interface which serves as multiple RPC
 requests depending on the value of event parameter:

 @RemoteServiceRelativePath(Service)
 public interface Service extends RemoteService {
 EventResult execute(String event, MapString, Object eventData)
 throws ServiceException;
 }

 The details of request are passed as Map with String key and the value 
 (the eventData)
 can be String, Integer, Double and Date (java.util.Date precisely).
 This works well on GWT 1.6.4. But when I try to upgrade to 2.2.0 (for
 better dev mode tool),



 You couldn't have chosen a worse moment to finally move from Hosted Mode 
 to Dev Mode!
 Just when Dev Mode is only still supported by Internet Explorer and 
 everyone's switching to Super Dev Mode (which the GWT Team is working on 
 all rage to get you a better dev experience in the upcoming GWT 2.7)

  

 it complains that:

 Type 'java.util.Date' was not included in the set of types which can
 be deserialized by this SerializationPolicy or its Class object could
 not be loadded. For security purposes, this will not be deserialized.

 I came across an SO post on a workaround to add the problematic type
 explicitly to a dummy method. For instance to get past the java.util.Date
 issue, you modify the above interface like:

 @RemoteServiceRelativePath(Service)
 public interface Service extends RemoteService {
 EventResult execute(String event, MapString, Object eventData)
 throws ServiceException;


 This was a really bad idea. You should use the most specific types as 
 possible in your RPC interfaces and transfer-objects (it's not news, it has 
 always been that way, it's just become stricter over time).
 So HashMap (or LinkedHashMap or TreeMap) rather than Map, and NOT Object.
 In that specific case, create a value object that can transport any of 
 your supported value types; either use one object with as many properties 
 as the types you support (stringValue, intValue, doubleValue, dateValue) 
 and use the one field that's not null, or create a base class and as many 
 subclasses each wrapping a single value (e.g. new StringValue(foo), new 
 IntValue(42), etc.) and use instanceof on that wrapper class.
 That way, by static analysis of your code and class hierarchy, GWT can 
 know exactly which types you'll send over the wire, and it will generate 
 the code to handle all of those types, and only those types (not too few 
 –causing errors like you're seeing–, not too many –generating bloated 
 code–).
 …or better yet, create specific event objects (whether they all inherit 
 from a base class so that you can use a single, polymorphic execute() 
 service method is up to you; I, for one, would rather use specific methods, 
 possibly using multiple arguments rather than event objects then).
  

 void dummy(Date date);
 }

 Since the GWT 1.6.4 serialize/deserialize the basic 

Main Advantages of using GWT against other technology like [jsp,spring,javascript...]

[jonl]

The thing is, its not an either or proposition.  GWT is java AND javascript.  
You can uses jsps to create the page that your gwt module resides in.  You can 
use spring to manage your beans and secure the client and server side of the 
application.  I would say that struts might mot offer much in integrating with 
a GWT project but it would be possible to integrate them.  As far as js 
libraries go, there is nothing to prevent you from integrating any particular 
js library that you wish.

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

Re: JSNI function and DevMode

[jonl]

After reading the other replies and looking at this, I would suspect it to 
be a race condition in DevMode.  Where the problem lies in when the 
exportMenuClickedMethod() is called.  

This is where the method being static or not comes into play.  By it not 
being static, it can't be called until an instance of the class is created, 
which in DevMode may different than in compiled mode because you have the 
back and forth of the browser and Eclipse here.

So, I would make the method static, and call it in a static initialize 
block for the class in which it is declared.  That way it will be exported 
more consistently in DevMode and compiled mode.


On Wednesday, July 2, 2014 10:33:33 AM UTC-7, gktcs wrote:

 I was trying to anonymize what was actually being done when pasting in 
 here and somehow ended up with an extra single quote.  I've verified that 
 the application is correct and just using 'PAGE'.

 As for the export function not being static...probably just an oversight. 
  I wouldn't think it matters either, but I'll make the change and see if 
 that makes any difference.

 On Wednesday, July 2, 2014 11:59:47 AM UTC-4, Patrick Tucker wrote:

 You have 2 single quotes after PAGE??

 Also, not that it should matter here, but why isn't your export function 
 static?



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

Re: Google Chrome 35 GWT plugin incompatibility

[jonl]

Try Chrome Portables:

http://sourceforge.net/projects/portableapps/files/Google%20Chrome%20Portable/Google%20Chrome%20Portable%2034/

On Thursday, May 22, 2014 9:12:12 AM UTC-7, Blake wrote:

 I have spent the last hour looking for Chrome 34 (the last version to 
 support dev mode on Linux - I believe).  Apparently, Google has gone far 
 out of their way to make sure nobody can find old version of Chrome.  Even 
 the sites that specialize in saving old versions of software just link to 
 Google download.  They don't store old versions either. (Since they don't 
 have old versions of Chrome, and that is their business, I feel confident 
 that Google made sure they don't!)

 Not only do they make finding old versions nearly impossible, but they 
 also make it as difficult as they can to stop auto-updates.

 I think it is real pompous of Google to drop support of GWT debugging 
 without making it possible for developers to stick with an old version. 
  This would have given us time more time to improve SuperDevMode.  I know 
 they have been warning us, and that is fine.  They can do as they please. 
  The problem is them making it nearly impossible to get or use an older 
 version.

 I understand and appreciate Google's problems with Oracle, and their 
 subsequent pseudo abandonment of GWT, but they shouldn't punish all the 
 people who have committed to Google's GWT when it was Google's.

 Anyway, I downloaded and saved a copy of Chrome 33 for all platforms. 
  Does anyone have version 34?

 Thanks.

 Blake




 On Thu, May 22, 2014 at 4:48 AM, Алексей Волков sof...@gmail.comjavascript:
  wrote:

 Chrome just updated to 35.0.1916.114 and thats broke the GWT development 
 plugin stating: Sorry, the GWT Developer Plugin no longer works with Chrome 
 on Linuxccseferf 

 I am running Linux Mint 16 with default depositories and autimatic 
 updates, is it possible to get GWT plugin back to work?

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




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

Re: GWTBridgeImpl throws com.google.gwt.core.ext.UnableToCompleteException exception

[jonl]

This could be as simple as the gwtUnitCache or the symbolMaps getting 
corrupted.  Happens every now and then and a clean of the gwt-build 
environment is the only way to fix it.  I delete my gwtUnitCache and the 
built war directories every time I build from scropt to prevent this kind 
of thing.  If running a script build and running hosted mode from the same 
base, it also best to make sure that your script builds to a directory that 
your IDE does not.  Otherwise their could be cross contamination of 
compilations creating incompatibilities in the compiled version.

On Thursday, January 9, 2014 9:03:40 AM UTC-7, dhoffer wrote:

 I was finally able to get this working in hosted mode again but I'm not 
 exactly sure why.  All the evidence points to a bug in IntelliJ as the fix 
 involved deleting the IntelliJ project files and rebuilding from the Maven 
 pom files and messing with the JDK version both specified in the Maven pom 
 files and in IntelliJ.

 I've seen cases before where IntelliJ gets confused by the Maven project 
 and just looses dependencies, but that did not seem to be occurring in this 
 case.  Also IntelliJ does not handle well cases where, in a multi-module 
 build, modules use more than one JDK version.  And that is my case due to 
 GWT not supporting JDK7 yet.

 That being said...it's possible that I don't have the JDK version 
 specified properly in my Maven pom files.  I'd like to know how best to 
 configure the JDK in the Maven build when using GWT.  Here is my use case:

 I have a multi-module build where my runtime JDK has to be 7.0.  In 
 addition I have lots of dependencies that were built with JDK7 so I have to 
 use that as my main compiler for my build.  In my maven project I have one 
 child folder that handles all the GWT parts of the build.  That GWT parent 
 folder has the following 3 modules:

 myapp-gwt-api
 - Module that contains shared code between myapp-gwt-dev  both the client 
 and server portion of myapp-gwt-war
 - This module is of type pom but it generates a jar.  I presume this was 
 made a pom type to give full control over what goes in the jar, the build 
 is configured to compile and then include both the classes and the java 
 source in the jar.  However in this build the JDK version is not specified 
 in the maven-compiler-plugin configuration...so I guess it uses some 
 default?  In retrospect it seems the classes could use JDK7 as that is what 
 all the server side code uses but the java source has to be JDK6 compatible 
 else the GWT compiler won't be able to use the source.

 myapp-gwt-dev
 - Module that contains GWT rebind code.  Our project makes heavy use of 
 GWT's rebind code generation feature so all the code that is needed to 
 rebind/generate code is in this module.
 - This module has a dependency on myapp-gwt-api
 - This module is of type pom but generates a jar.  This module appears to 
 be just like the previous one...it generates a jar with both classes and 
 source files.  
 - Also this module gets the GWT compiler classes from the gwt-dev jar and 
 puts them in this module.  I presume this is so that in the next module GWT 
 has all that it needs to perform the GWT rebind operation without having to 
 add a dependency on gwt-dev in the war module.  Also it would serve as a 
 way to keep the rebind code out of the war...as that is not needed at 
 runtime.

 myapp-gwt-war
 - This is the main GWT module and is of type war.
 - It has a dependency on myapp-gwt-api and on myapp-gwt-dev however in the 
 later case it has provided scope to stop it from going into the wars 
 runtime dependencies.
 - This module uses gwt-maven-plugin to compile the GWT application, 
 however the JDK version is not specified so I assume that uses a GWT 
 default?
 - In this module, in the maven-compiler-plugin, we do specify the JDK 
 version, it's set to 1.6 for both source  target.  I'm not clear what this 
 should be.  Ideally we would want the source  target to be 1.7 for the 
 server side code.  However the client side source has to be 1.6 for GWT. 
  And does this setting affect what compiler is used by the 
 gwt-maven-plugin, or is that completely separate?

 Now that I get to the end of analysis of the Maven build I see that that 
 the maven-compiler-plugin is configured in the pluginManagement section to 
 use JDK 1.7 for both source  target.  So I assume that where I said above 
 the compiler version was not specified...it would use 1.7 as the defaults.

 In retrospect it seems that for both myapp-gwt-api  myapp-gwt-dev we 
 should use 1.6 for the source and 1.7 for the target in the 
 maven-compiler-plugin config?  I'm not sure about in myapp-gwt-war...maybe 
 the same.

 I'd really appreciate feedback on how best to configure this.

 -Dave

 On Wednesday, January 8, 2014 1:39:41 PM UTC-7, dhoffer wrote:

 I have a large GWT application using 2.5.1 and all of a sudden I am 
 getting the following error when run/debug in GWT hosted mode:

 

Re: Custom MessageInterpolator for Validation ?

[jonl]

Several ways to skin this cat

1. You can implement both the ValidationProvider  and ValidatorFactory 
interfaces  directly and use defferred binding to replace them.  

2. You could just create versions of the ConstraintValidatorFactory, 
TraversableResolver and MessageInterpolator that delegate in a manner that 
you like.

3. If you must absolutely positively extend AbstractGwtValidatorFactory,  
you could use jsni to bypass the final java methods and access the 
variables of the class via jsni, creating your own init method, overriding 
the buildValidatorFactory method to call your custom jsni init method. 

All of this requires deferred binding and deferred binding can be used to 
replace any of these classes ,so that is your cleanest solution.


On Sunday, January 5, 2014 7:30:57 AM UTC-7, kibu Kuhn wrote:

 hi,

 thanks. This works as long as you only have 1 resolver in your module. But 
 what if you want to have more than 1? Imagine a module with dozens of 
 places/views. Then all validation messages are in 1 bundle. This is what 
 I'm trying to avoid.

 kibu


 Am Sonntag, 5. Januar 2014 14:59:40 UTC+1 schrieb Nicolas Weeger:

 Hello. 



  As you provide different i18n message bundles for each place / view I'm 
  trying to provide different ValidationMessagesResolvers. But this seems 
 to 
  be quite difficult. 
  You define a custom ValidatorFactory derived from 
  AbstractGwtValidatorFactory and a ValidationMessagesResolver in the 
 module 
  xml. But GWT always creates a UserValidationMessagesResolver in 
  GwtMessageInterpolator, which gets created in turn in 
   AbstractGwtValidatorFactory#init(). But this init method is final... 

 Would this help? 

 http://stackoverflow.com/questions/14031803/gwt-validation-framework-how-to- 

 specify-location-of-internationalization-bundlehttp://stackoverflow.com/questions/14031803/gwt-validation-framework-how-to-specify-location-of-internationalization-bundle
  


 Or if you understand french (or just glance at the code, or use Google 
 Translate :)), http://blog.developpez.com/karbos/p11535/recettes-de-code/la- 

 validation-des-donnees-avec-gwt-2-5-cote-clienthttp://blog.developpez.com/karbos/p11535/recettes-de-code/la-validation-des-donnees-avec-gwt-2-5-cote-clientexplains
  how to customize 
 constraints messages too. 



 Best regards 


 Nicolas 



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

Re: NPAPI

[jonl]

The NPAPI is being deprecated by the Chrome team this year. You might look 
into super-dev mode instead, since you are having trouble anyways.

http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html

http://www.gwtproject.org/articles/superdevmode.html



On Saturday, November 9, 2013 3:48:53 PM UTC-7, Millie Smith wrote:

 When I try to install the Chrome plugin for GWT, I get the following text 
 in a popup: NPAPI plugin is required by this app. All of the NPAPI 
 installs look complicated. Is there an easy way to get this installed?
 Also, when I installed the Firefox plugin, Firefox refused to start again 
 without a complete factory reset. 

 The Internet Explorer plugin works, so I'm developing in IE. 
 I don't like IE.
 Please stop the torture.

 Any suggestions? :)



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

Re: Unable to read from byte cache

[jonl]

I see this issue when something modifies the gwt-unitCache while run time.

This could include:

Manually running GWT compile while running in hosted mode.
Modifying a file during debug that is compiled to JS while runtime is 
paused using a break point.

Juno and GWT really sucked. Indigo and Kepler are both better options, imo

On Monday, April 29, 2013 9:11:11 AM UTC-7, Kris wrote:

 Hi, I get this in dev mode en eclipse Juno, get 2.5.1

 java.util.concurrent.ExecutionException: java.lang.RuntimeException: 
 Unable to read from byte cache
 at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:252)
 at java.util.concurrent.FutureTask.get(FutureTask.java:111)
 at 
 com.google.gwt.dev.javac.PersistentUnitCache.awaitUnitCacheMapLoad(PersistentUnitCache.java:466)
 at 
 com.google.gwt.dev.javac.PersistentUnitCache.find(PersistentUnitCache.java:391)
 at 
 com.google.gwt.dev.javac.CompilationStateBuilder.addArchive(CompilationStateBuilder.java:365)
 at 
 com.google.gwt.dev.ArchivePreloader.preloadArchives(ArchivePreloader.java:65)
 at 
 com.google.gwt.dev.DevModeBase$UiBrowserWidgetHostImpl.createModuleSpaceHost(DevModeBase.java:106)
 at 
 com.google.gwt.dev.shell.OophmSessionHandler.loadModule(OophmSessionHandler.java:197)
 at 
 com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:526)
 at 
 com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:364)
 at java.lang.Thread.run(Thread.java:722)
 Caused by: java.lang.RuntimeException: Unable to read from byte cache
 at com.google.gwt.dev.util.DiskCache.transferFromStream(DiskCache.java:171)
 at 
 com.google.gwt.dev.util.DiskCacheToken.readObject(DiskCacheToken.java:87)
 at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:601)
 at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1004)
 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1872)
 at 
 java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1777)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1347)
 at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1970)
 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1894)
 at 
 java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1777)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1347)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)
 at java.util.ArrayList.readObject(ArrayList.java:733)
 at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:601)
 at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1004)
 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1872)
 at 
 java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1777)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1347)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)
 at 
 com.google.gwt.dev.javac.CachedCompilationUnit.readObject(CachedCompilationUnit.java:205)
 at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:601)
 at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1004)
 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1872)
 at 
 java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1777)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1347)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)
 at 
 com.google.gwt.dev.javac.PersistentUnitCache.loadUnitMap(PersistentUnitCache.java:517)
 at 
 com.google.gwt.dev.javac.PersistentUnitCache.access$800(PersistentUnitCache.java:96)
 at 
 com.google.gwt.dev.javac.PersistentUnitCache$4.run(PersistentUnitCache.java:222)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 ... 1 more
 Caused by: java.io.StreamCorruptedException: unexpected EOF in middle of 
 data block
 at 
 java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2518)
 at 
 java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2681)
 at java.io.ObjectInputStream.read(ObjectInputStream.java:862)
 at java.io.InputStream.read(InputStream.java:101)
 at 

Firefox 5 beta

[jonl]

Is there a way to force GWT to work in firefox 5 beta?  Or how soon will an 
update of the plugin be available now that firefox is going to a more rapid 
release schedule?

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.