Re: Emulating CompletableFuture with Promise

[James Horsley]

This is brilliant. I would *love *to see this in GWT proper. Maybe even a
separate library temporarily since it won't make the 2.8.0 release train?

On Fri, Sep 9, 2016 at 2:41 PM Andrei Korzhevskii 
wrote:

> In this case I wanted 'new Promise', not 'Promise.resolve'. Thanks for
> spotting that out! I've updated my branch.
>
>
> On Tuesday, September 6, 2016 at 10:09:28 PM UTC+3, Ian Preston wrote:
>
>> For another hint, I think you don't want the "new" before
>> "Promise.resolve" on line 88 of impl/JsPromise :-)
>> What the best way for me to report bugs to you? A PR?
>>
> --
> 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.
>

-- 
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: Problem with 2.8.0 rc1 SDM

[James Horsley]

Updating gson to 2.6.x fixed it for me

On Thursday, August 11, 2016 at 10:04:44 PM UTC+1, Alberto Mancini wrote:
>
> Hello,
> in the attempt of porting an internal project from beta1 to rc1 we faced 
> an issue i do not understand how to debug. 
>
> The project uses errai but my feeling is that the problem is not related 
> to it because similar projects with errai work without problems. 
>
> Essentially SDM fails during the first compilation and the problem seems 
> in the generation of the source maps. 
>
> The relevant error log follows.
>
> [INFO] GET /recompile/it.e.u.Application
> [INFO]Job it.e.u.Application_1_0
> [INFO]   starting job: it.e.u.Application_1_0
> [INFO]   binding: user.agent=safari
> [INFO]   Compiling module it.e.u.Application
> ...
>
> [INFO]  Unification traversed 54946 fields and methods and 5256 
> types. 5210 are considered part of the current module and 5210 had all of 
> their fields and methods traversed.
> [INFO]  Compiling 1 permutation
> [INFO] Compiling permutation 0...
> [INFO] Linking per-type JS with 5190 new/changed types.
> [INFO] Source Maps Enabled
> [INFO]  Compile of permutations succeeded
> [INFO]  Compilation succeeded -- 35.850s
> [INFO]   Linking into 
> /var/folders/63/qxvnlkdn7yq2n689wbryx_vwrfzqfp/T/gwt-codeserver-2706361954965741673.tmp/it.e.u.Application/compile-2/war/it.e.u.Application;
>  Writing extras to 
> /var/folders/63/qxvnlkdn7yq2n689wbryx_vwrfzqfp/T/gwt-codeserver-2706361954965741673.tmp/it.e.u.Application/compile-2/extras/it.e.u.Application*[INFO]
>   [WARN] Can't write source map 
> CCA06A04193EDF5B35BDE836DF1FABBE_sourceMap0.json
> [INFO] java.lang.NullPointerException*
> [INFO]at 
> com.google.gwt.thirdparty.debugging.sourcemap.SourceMapConsumerV3.parse(SourceMapConsumerV3.java:101)
> [INFO]at 
> com.google.gwt.thirdparty.debugging.sourcemap.SourceMapConsumerV3.parse(SourceMapConsumerV3.java:88)
> [INFO]at 
> com.google.gwt.thirdparty.debugging.sourcemap.SourceMapConsumerV3.parse(SourceMapConsumerV3.java:78)
> [INFO]at 
> com.google.gwt.thirdparty.debugging.sourcemap.SourceMapGeneratorV3.mergeMapSection(SourceMapGeneratorV3.java:311)
> [INFO]at 
> com.google.gwt.core.linker.SymbolMapsLinker.link(SymbolMapsLinker.java:316)
> [INFO]at 
> com.google.gwt.core.ext.linker.impl.StandardLinkerContext.invokeLinkForOnePermutation(StandardLinkerContext.java:384)
> [INFO]at com.google.gwt.dev.Link.finishPermutation(Link.java:483)
> [INFO]at 
> com.google.gwt.dev.Link.doSimulatedShardingLink(Link.java:445)
> [INFO]at com.google.gwt.dev.Link.link(Link.java:178)
> [INFO]at com.google.gwt.dev.Compiler.compile(Compiler.java:244)
> [INFO]at 
> com.google.gwt.dev.codeserver.Recompiler.doCompile(Recompiler.java:362)
> [INFO]at 
> com.google.gwt.dev.codeserver.Recompiler.compile(Recompiler.java:175)
> [INFO]at 
> com.google.gwt.dev.codeserver.Recompiler.recompile(Recompiler.java:134)
> [INFO]at 
> com.google.gwt.dev.codeserver.Outbox.recompile(Outbox.java:135)
> [INFO]at 
> com.google.gwt.dev.codeserver.JobRunner.recompile(JobRunner.java:113)
> [INFO]at 
> com.google.gwt.dev.codeserver.JobRunner.access$000(JobRunner.java:37)
> [INFO]at 
> com.google.gwt.dev.codeserver.JobRunner$2.run(JobRunner.java:90)
> [INFO]at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [INFO]at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [INFO]at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [INFO]at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [INFO]at java.lang.Thread.run(Thread.java:745)
> [INFO]  Invoking Linker Export CompilationResult symbol maps
> [INFO] [ERROR] Failed to link
> [INFO] java.lang.NullPointerException
> [INFO]at java.util.TreeMap.put(TreeMap.java:563)
> [INFO]at java.util.TreeSet.add(TreeSet.java:255)
> [INFO]at 
> com.google.gwt.thirdparty.guava.common.collect.ForwardingCollection.add(ForwardingCollection.java:84)
> [INFO]at 
> com.google.gwt.core.ext.linker.TypeIndexedSet.add(TypeIndexedSet.java:101)
> [INFO]at 
> com.google.gwt.core.ext.linker.ArtifactSet.add(ArtifactSet.java:42)
> [INFO]at 
> com.google.gwt.core.linker.SymbolMapsLinker.link(SymbolMapsLinker.java:330)
> [INFO]at 
> com.google.gwt.core.ext.linker.impl.StandardLinkerContext.invokeLinkForOnePermutation(StandardLinkerContext.java:384)
> [INFO]at com.google.gwt.dev.Link.finishPermutation(Link.java:483)
> [INFO]at 
> com.google.gwt.dev.Link.doSimulatedShardingLink(Link.java:445)
> [INFO]at com.google.gwt.dev.Link.link(Link.java:178)
> [INFO]at com.google.gwt.dev.Compiler.compile(Compiler.java:244)
> [INFO] 

Re: Problem with 2.8.0 rc1 SDM

[James Horsley]

Ah, just realized this was discussed in more detail 
at https://groups.google.com/forum/#!topic/google-web-toolkit/-c4RR6oLr2o 
I'll check my gson dep and report back

On Thursday, August 25, 2016 at 11:28:58 PM UTC+1, James Horsley wrote:
>
> Meant to say that I'm seeing the same error after switching from beta-2 to 
> rc2
>
> On Thu, Aug 25, 2016 at 11:15 PM James Horsley  
> wrote:
>
>> Doesn't the CodeServer need the gwt-dev.jar though?
>>
>>
>> On Tuesday, August 23, 2016 at 3:45:03 PM UTC+1, viviana zimbone wrote:
>>>
>>> If you have a maven dependency for gwt-dev, removing it shoudl fix the 
>>> issue :)
>>>
>>> Il giorno martedì 16 agosto 2016 11:03:03 UTC+2, Alberto Mancini ha 
>>> scritto:
>>>>
>>>> Unfortunately removing the temporary files does not helps. 
>>>> Today we try to investigate further and eventually we will open an 
>>>> issue. 
>>>>
>>>> Thanks,
>>>>A. 
>>>>
>>>> On Sun, Aug 14, 2016 at 12:52 AM Andrei Korzhevskii <
>>>> a.korz...@gmail.com> wrote:
>>>>
>>>>> Reading the stacktrace, I think the problem is in 
>>>>> https://github.com/gwtproject/gwt/blob/master/dev/core/src/com/google/gwt/core/linker/SymbolMapsLinker.java#L282
>>>>> ,
>>>>> looks like disk cache returns null there.
>>>>>
>>>>> Did you try to remove folder /var/folders/63/qxvnlkdn7yq2n689wbryx_
>>>>> vwrfzqfp/T/gwt-codeserver-2706361954965741673.tmp
>>>>> and run compile again?
>>>>>
>>>>>
>>>>> On Friday, August 12, 2016 at 12:04:44 AM UTC+3, Alberto Mancini wrote:
>>>>>>
>>>>>> Hello,
>>>>>> in the attempt of porting an internal project from beta1 to rc1 we faced 
>>>>>> an issue i do not understand how to debug. 
>>>>>>
>>>>>> The project uses errai but my feeling is that the problem is not 
>>>>>> related to it because similar projects with errai work without problems. 
>>>>>>
>>>>>> Essentially SDM fails during the first compilation and the problem 
>>>>>> seems in the generation of the source maps. 
>>>>>>
>>>>>> The relevant error log follows.
>>>>>>
>>>>>> [INFO] GET /recompile/it.e.u.Application
>>>>>> [INFO]Job it.e.u.Application_1_0
>>>>>> [INFO]   starting job: it.e.u.Application_1_0
>>>>>> [INFO]   binding: user.agent=safari
>>>>>> [INFO]   Compiling module it.e.u.Application
>>>>>> ...
>>>>>>
>>>>>> [INFO]  Unification traversed 54946 fields and methods and 5256 
>>>>>> types. 5210 are considered part of the current module and 5210 had all 
>>>>>> of their fields and methods traversed.
>>>>>> [INFO]  Compiling 1 permutation
>>>>>> [INFO] Compiling permutation 0...
>>>>>> [INFO] Linking per-type JS with 5190 new/changed types.
>>>>>> [INFO] Source Maps Enabled
>>>>>> [INFO]  Compile of permutations succeeded
>>>>>> [INFO]  Compilation succeeded -- 35.850s
>>>>>> [INFO]   Linking into 
>>>>>> /var/folders/63/qxvnlkdn7yq2n689wbryx_vwrfzqfp/T/gwt-codeserver-2706361954965741673.tmp/it.e.u.Application/compile-2/war/it.e.u.Application;
>>>>>>  Writing extras to 
>>>>>> /var/folders/63/qxvnlkdn7yq2n689wbryx_vwrfzqfp/T/gwt-codeserver-2706361954965741673.tmp/it.e.u.Application/compile-2/extras/it.e.u.Application*[INFO]
>>>>>>   [WARN] Can't write source map 
>>>>>> CCA06A04193EDF5B35BDE836DF1FABBE_sourceMap0.json
>>>>>> [INFO] java.lang.NullPointerException*
>>>>>> [INFO]   at 
>>>>>> com.google.gwt.thirdparty.debugging.sourcemap.SourceMapConsumerV3.parse(SourceMapConsumerV3.java:101)
>>>>>> [INFO]   at 
>>>>>> com.google.gwt.thirdparty.debugging.sourcemap.SourceMapConsumerV3.parse(SourceMapConsumerV3.java:88)
>>>>>> [INFO]   at 
>>>>>> com.google.gwt.thirdparty.debugging.sourcemap.SourceMapConsumerV3.parse(SourceMapConsumerV3.java:78)
>>>>>> [INFO]   at 
>>>>>> com.google.gwt.thirdparty.debugging.sourcemap.Sou

Re: Problem with 2.8.0 rc1 SDM

[James Horsley]

Meant to say that I'm seeing the same error after switching from beta-2 to
rc2

On Thu, Aug 25, 2016 at 11:15 PM James Horsley 
wrote:

> Doesn't the CodeServer need the gwt-dev.jar though?
>
>
> On Tuesday, August 23, 2016 at 3:45:03 PM UTC+1, viviana zimbone wrote:
>>
>> If you have a maven dependency for gwt-dev, removing it shoudl fix the
>> issue :)
>>
>> Il giorno martedì 16 agosto 2016 11:03:03 UTC+2, Alberto Mancini ha
>> scritto:
>>>
>>> Unfortunately removing the temporary files does not helps.
>>> Today we try to investigate further and eventually we will open an
>>> issue.
>>>
>>> Thanks,
>>>A.
>>>
>>> On Sun, Aug 14, 2016 at 12:52 AM Andrei Korzhevskii 
>>> wrote:
>>>
>>>> Reading the stacktrace, I think the problem is in
>>>> https://github.com/gwtproject/gwt/blob/master/dev/core/src/com/google/gwt/core/linker/SymbolMapsLinker.java#L282
>>>> ,
>>>> looks like disk cache returns null there.
>>>>
>>>> Did you try to remove folder /var/folders/63/qxvnlkdn7yq2n689wbryx_
>>>> vwrfzqfp/T/gwt-codeserver-2706361954965741673.tmp
>>>> and run compile again?
>>>>
>>>>
>>>> On Friday, August 12, 2016 at 12:04:44 AM UTC+3, Alberto Mancini wrote:
>>>>>
>>>>> Hello,
>>>>> in the attempt of porting an internal project from beta1 to rc1 we faced
>>>>> an issue i do not understand how to debug.
>>>>>
>>>>> The project uses errai but my feeling is that the problem is not
>>>>> related to it because similar projects with errai work without problems.
>>>>>
>>>>> Essentially SDM fails during the first compilation and the problem
>>>>> seems in the generation of the source maps.
>>>>>
>>>>> The relevant error log follows.
>>>>>
>>>>> [INFO] GET /recompile/it.e.u.Application
>>>>> [INFO]Job it.e.u.Application_1_0
>>>>> [INFO]   starting job: it.e.u.Application_1_0
>>>>> [INFO]   binding: user.agent=safari
>>>>> [INFO]   Compiling module it.e.u.Application
>>>>> ...
>>>>>
>>>>> [INFO]  Unification traversed 54946 fields and methods and 5256 
>>>>> types. 5210 are considered part of the current module and 5210 had all of 
>>>>> their fields and methods traversed.
>>>>> [INFO]  Compiling 1 permutation
>>>>> [INFO] Compiling permutation 0...
>>>>> [INFO] Linking per-type JS with 5190 new/changed types.
>>>>> [INFO] Source Maps Enabled
>>>>> [INFO]  Compile of permutations succeeded
>>>>> [INFO]  Compilation succeeded -- 35.850s
>>>>> [INFO]   Linking into 
>>>>> /var/folders/63/qxvnlkdn7yq2n689wbryx_vwrfzqfp/T/gwt-codeserver-2706361954965741673.tmp/it.e.u.Application/compile-2/war/it.e.u.Application;
>>>>>  Writing extras to 
>>>>> /var/folders/63/qxvnlkdn7yq2n689wbryx_vwrfzqfp/T/gwt-codeserver-2706361954965741673.tmp/it.e.u.Application/compile-2/extras/it.e.u.Application*[INFO]
>>>>>   [WARN] Can't write source map 
>>>>> CCA06A04193EDF5B35BDE836DF1FABBE_sourceMap0.json
>>>>> [INFO] java.lang.NullPointerException*
>>>>> [INFO]at 
>>>>> com.google.gwt.thirdparty.debugging.sourcemap.SourceMapConsumerV3.parse(SourceMapConsumerV3.java:101)
>>>>> [INFO]at 
>>>>> com.google.gwt.thirdparty.debugging.sourcemap.SourceMapConsumerV3.parse(SourceMapConsumerV3.java:88)
>>>>> [INFO]at 
>>>>> com.google.gwt.thirdparty.debugging.sourcemap.SourceMapConsumerV3.parse(SourceMapConsumerV3.java:78)
>>>>> [INFO]at 
>>>>> com.google.gwt.thirdparty.debugging.sourcemap.SourceMapGeneratorV3.mergeMapSection(SourceMapGeneratorV3.java:311)
>>>>> [INFO]at 
>>>>> com.google.gwt.core.linker.SymbolMapsLinker.link(SymbolMapsLinker.java:316)
>>>>> [INFO]at 
>>>>> com.google.gwt.core.ext.linker.impl.StandardLinkerContext.invokeLinkForOnePermutation(StandardLinkerContext.java:384)
>>>>> [INFO]at com.google.gwt.dev.Link.finishPermutation(Link.java:483)
>>>>> [INFO]at 
>>>>> com.google.gwt.dev.Link.doSimulatedShardingLink(Link.java:445)
>>>>> [INFO]at com.goo

Re: Problem with 2.8.0 rc1 SDM

[James Horsley]

Doesn't the CodeServer need the gwt-dev.jar though?

On Tuesday, August 23, 2016 at 3:45:03 PM UTC+1, viviana zimbone wrote:
>
> If you have a maven dependency for gwt-dev, removing it shoudl fix the 
> issue :)
>
> Il giorno martedì 16 agosto 2016 11:03:03 UTC+2, Alberto Mancini ha 
> scritto:
>>
>> Unfortunately removing the temporary files does not helps. 
>> Today we try to investigate further and eventually we will open an issue. 
>>
>> Thanks,
>>A. 
>>
>> On Sun, Aug 14, 2016 at 12:52 AM Andrei Korzhevskii  
>> wrote:
>>
>>> Reading the stacktrace, I think the problem is in 
>>> https://github.com/gwtproject/gwt/blob/master/dev/core/src/com/google/gwt/core/linker/SymbolMapsLinker.java#L282
>>> ,
>>> looks like disk cache returns null there.
>>>
>>> Did you try to remove folder /var/folders/63/qxvnlkdn7yq2n689wbryx_
>>> vwrfzqfp/T/gwt-codeserver-2706361954965741673.tmp
>>> and run compile again?
>>>
>>>
>>> On Friday, August 12, 2016 at 12:04:44 AM UTC+3, Alberto Mancini wrote:

 Hello,
 in the attempt of porting an internal project from beta1 to rc1 we faced 
 an issue i do not understand how to debug. 

 The project uses errai but my feeling is that the problem is not 
 related to it because similar projects with errai work without problems. 

 Essentially SDM fails during the first compilation and the problem 
 seems in the generation of the source maps. 

 The relevant error log follows.

 [INFO] GET /recompile/it.e.u.Application
 [INFO]Job it.e.u.Application_1_0
 [INFO]   starting job: it.e.u.Application_1_0
 [INFO]   binding: user.agent=safari
 [INFO]   Compiling module it.e.u.Application
 ...

 [INFO]  Unification traversed 54946 fields and methods and 5256 
 types. 5210 are considered part of the current module and 5210 had all of 
 their fields and methods traversed.
 [INFO]  Compiling 1 permutation
 [INFO] Compiling permutation 0...
 [INFO] Linking per-type JS with 5190 new/changed types.
 [INFO] Source Maps Enabled
 [INFO]  Compile of permutations succeeded
 [INFO]  Compilation succeeded -- 35.850s
 [INFO]   Linking into 
 /var/folders/63/qxvnlkdn7yq2n689wbryx_vwrfzqfp/T/gwt-codeserver-2706361954965741673.tmp/it.e.u.Application/compile-2/war/it.e.u.Application;
  Writing extras to 
 /var/folders/63/qxvnlkdn7yq2n689wbryx_vwrfzqfp/T/gwt-codeserver-2706361954965741673.tmp/it.e.u.Application/compile-2/extras/it.e.u.Application*[INFO]
   [WARN] Can't write source map 
 CCA06A04193EDF5B35BDE836DF1FABBE_sourceMap0.json
 [INFO] java.lang.NullPointerException*
 [INFO] at 
 com.google.gwt.thirdparty.debugging.sourcemap.SourceMapConsumerV3.parse(SourceMapConsumerV3.java:101)
 [INFO] at 
 com.google.gwt.thirdparty.debugging.sourcemap.SourceMapConsumerV3.parse(SourceMapConsumerV3.java:88)
 [INFO] at 
 com.google.gwt.thirdparty.debugging.sourcemap.SourceMapConsumerV3.parse(SourceMapConsumerV3.java:78)
 [INFO] at 
 com.google.gwt.thirdparty.debugging.sourcemap.SourceMapGeneratorV3.mergeMapSection(SourceMapGeneratorV3.java:311)
 [INFO] at 
 com.google.gwt.core.linker.SymbolMapsLinker.link(SymbolMapsLinker.java:316)
 [INFO] at 
 com.google.gwt.core.ext.linker.impl.StandardLinkerContext.invokeLinkForOnePermutation(StandardLinkerContext.java:384)
 [INFO] at com.google.gwt.dev.Link.finishPermutation(Link.java:483)
 [INFO] at 
 com.google.gwt.dev.Link.doSimulatedShardingLink(Link.java:445)
 [INFO] at com.google.gwt.dev.Link.link(Link.java:178)
 [INFO] at com.google.gwt.dev.Compiler.compile(Compiler.java:244)
 [INFO] at 
 com.google.gwt.dev.codeserver.Recompiler.doCompile(Recompiler.java:362)
 [INFO] at 
 com.google.gwt.dev.codeserver.Recompiler.compile(Recompiler.java:175)
 [INFO] at 
 com.google.gwt.dev.codeserver.Recompiler.recompile(Recompiler.java:134)
 [INFO] at 
 com.google.gwt.dev.codeserver.Outbox.recompile(Outbox.java:135)
 [INFO] at 
 com.google.gwt.dev.codeserver.JobRunner.recompile(JobRunner.java:113)
 [INFO] at 
 com.google.gwt.dev.codeserver.JobRunner.access$000(JobRunner.java:37)
 [INFO] at 
 com.google.gwt.dev.codeserver.JobRunner$2.run(JobRunner.java:90)
 [INFO] at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 [INFO] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
 [INFO] at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
 [INFO] at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
 [INFO] at java.lang.Thread.run(Thread.java:745)
 [INFO]  Invoking Linker Export CompilationResult symbol maps
 [IN

Re: GWT 2.8.0 RC2 is here!

[James Horsley]

I saw there were some commits to master after RC2 was cut. Are there plans
to cut an RC3 or just roll those commits into the GA?

On Fri, Aug 19, 2016 at 5:31 PM Alexander Polunochev 
wrote:

> Hi Daniel,
>
> Link to download SDK on the official page still points to RC1.
> http://www.gwtproject.org/download.html
>
>
>
> On Thursday, August 11, 2016 at 6:25:18 PM UTC-7, Daniel Kurka wrote:
>>
>> Hi all,
>>
>> I just build the GWT 2.8.0 RC2 and pushed it to maven central. The
>> complete SDK is also available from here .
>>
>> Please start testing and let us know if you run into any trouble and file
>> bugs .
>>
>> We are planing to release this as GWT 2.8.0 if we do not here about any
>> serious issues within the next two weeks. The release notes for RC
>> 2
>>  will
>> be made available shortly after this notice, in the mean time you can take
>> a look at the github repository
>> 
>> .
>>
>> Daniel,
>> on behalf of the GWT team
>>
> --
> 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.
>

-- 
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: Ui Binder Alternatives

[James Horsley]

Something like Elemento + Elemental 2 seems like a great lightweight choice
in the future.

FWIW I agree with Paul that UiBinder plus some top layer of the widget API
(UIObject, Widget, etc.) will get ported over to work with GWT 3.0 by the
community. There's no reason it can't work with Java APT + JsInterop, just
needs the tech investment. I think this will be a huge help for many teams
doing a gradual upgrade.

On Tue, Jul 26, 2016 at 7:43 AM zakaria amine 
wrote:

> Elemento project sounds like an intersting alternative:
> https://github.com/hal/elemento
>
>
> Le dimanche 24 juillet 2016 03:40:02 UTC+2, N Troncoso a écrit :
>>
>> With GWT 3.0, Widgets and UI Binder is losing support. Even besides that,
>> I'm not a huge fan of UI Binder. I'd really just prefer to use vanilla
>> HTML. With that said, I've been searching for other options and I've only
>> found that alternatives are very limited. Even more so, examples of how to
>> integrate alternatives into GWT are basically non-existent. So, my question
>> is, what can I use instead of Widgets and UI Binder and where can I find
>> examples/tutorials/documentation on how to use them in GWT.
>>
>> I found Errai  as one option. But, this
>> seems to be an entire framework, rather than just a template system.
>>
>> Any insight would be greatly appreciated. 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.
>

-- 
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 React

[James Horsley]

Great work Paul. Thanks for sharing.

On Thu, Apr 14, 2016 at 1:57 PM Paul Stockley  wrote:

> I plan on doing this. I have a couple of things I need to prove out then I
> will start working on setting up the Github projects. I will post a preview
> to my google drive in a couple of weeks so you can take a look while I work
> on setting up the projects on Github.
>
>
> On Thursday, April 14, 2016 at 1:35:06 AM UTC-4, Debasish Padhy wrote:
>>
>> Hi Paul,
>>
>> Is there a possibility of you sharing the codebase over github and put a
>> license to it ? I have been working extensively with JsInterOp / TypeScript
>> cross usage and find your  POC interesting and would love to contribute if
>> its with an open license.
>>
>> thanks,
>> Debasish
>>
>> On Thursday, April 7, 2016 at 6:48:27 PM UTC+5:30, Paul Stockley wrote:
>>>
>>> Sorry,
>>>   I was just updating it to include samples for Redux that I just got
>>> working. The new link is
>>> https://drive.google.com/folderview?id=0Bxp8vLBG2ol3ZERCc3lHUEhKU2M&usp=sharing
>>>
>> --
> 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.
>

-- 
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: Is anybody of you guys using GWT with Lombok?

[James Horsley]

I haven't used Lombok due to similar reasons as Jens described but have had
really great success with annotation processing libraries like Immutables (
http://immutables.github.io/), AutoValue, etc. I've even started writing my
own annotation processors to help reduce boilerplate.

On Wed, Mar 16, 2016 at 12:37 PM Jens  wrote:

> If its just for value classes and factories you better use Google's
> AutoValue / AutoFactory projects which are based on annotation processing
> instead of hacking the Java compiler as Lombok does.
>
> Personally I would never use Lombok. As it adds code during compilation,
> that code is invisible to tools that work on Java source. IMHO Lombok is
> fragile and can break easily with any JDK update, you can also see this in
> the changelog as it contains quite some "Bugfix: X breaks starting with JDK
> Y". The reason is that Lombok relies on the com.sun.tools.javac package
> which is considered a private API.
>
> So I would generally advice using annotation processors instead.
>
> -- J.
>
> --
> 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.
>

-- 
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 release prioritization

[James Horsley]

Any chance someone from the steering committee could comment on this?

On 3 August 2015 at 09:37, maticpetek  wrote:

> 1+
>
>
> On Friday, July 31, 2015 at 11:39:00 AM UTC+2, James Horsley wrote:
>>
>> Firstly, I am very much looking forward to the next generation j2cl
>> compiler for GWT and think the new compiler vision is great. That said, I
>> think the community would benefit greatly with the steering committee
>> placing a higher priority on closing out on the 2.8 release. I know that
>> the current 2.8 is considered usable for production but 2.8 isn't feature
>> complete and organizations can be very hesitant to use non-GA versions of
>> libraries. In particular it would be a big win to have a "done" version of
>> JsInterop v1 and clear guidance on using the current version of elemental.
>>
>> I, and I'm sure the rest of the GWT community, would greatly appreciate a
>> clearer view on current release expectations and prioritization; is there
>> anything you guys can share on that front?
>>
>> Again, really appreciate the recent work and love the plans for GWT 3.0.
>>
>> Cheers,
>> James
>>
> --
> 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.
>

-- 
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.

GWT release prioritization

[James Horsley]

Firstly, I am very much looking forward to the next generation j2cl
compiler for GWT and think the new compiler vision is great. That said, I
think the community would benefit greatly with the steering committee
placing a higher priority on closing out on the 2.8 release. I know that
the current 2.8 is considered usable for production but 2.8 isn't feature
complete and organizations can be very hesitant to use non-GA versions of
libraries. In particular it would be a big win to have a "done" version of
JsInterop v1 and clear guidance on using the current version of elemental.

I, and I'm sure the rest of the GWT community, would greatly appreciate a
clearer view on current release expectations and prioritization; is there
anything you guys can share on that front?

Again, really appreciate the recent work and love the plans for GWT 3.0.

Cheers,
James

-- 
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: Research on Elemental

[James Horsley]

Is it recommended to use the current elemental API even though it's not
based on JsInterop yet? For example, if I use the current elemental API,
can I expect that Elemental 2.0 should be a fairly easy transition?

On Sun, Jun 21, 2015 at 5:14 PM Lukas Glowania 
wrote:

> Great resource! Thanks a lot.
>
> --
> 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.
>

-- 
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: Important videos from GWT Meet-up 2015

[James Horsley]

Thanks Thomas.

Good point on getting started experimenting before the compiler is made
available. I've been building a few of libraries using APT for code
generation recently, making use of the wonderful google & square libraries
like auto and javapoet. I think it'd be pretty straightforward to build an
annotation processor for a few existing libraries e.g. i18n. However, I'm
really hoping to make use of GWT compiler level solutions to overcome some
current APT challenges; in particular, invoking the processor when non-java
files are changed such as ui.xml files. Daniel mentioned in his talk that
there might be a general solution for this which would be pretty awesome to
use.

I was probably too specific in asking for early access to the compiler.
Early access to elemental 2.0 and jsinterop 2.0 would be really helpful to
try and figure out how to port JSNI/JSO code over to jsinterop.

In general my experience with GWT + APT for my own libraries has been
really good, so I'm quite positive about the plans for GWT 3.0. Hopefully,
with a clear migration story, the community will be able to smooth any
rough edges that the core GWT team can't take on.



On Sun, Jun 21, 2015 at 11:18 AM Thomas Broyer  wrote:

>
>
> On Sunday, June 21, 2015 at 11:17:50 AM UTC+2, James Horsley wrote:
>>
>> Also worth noting that, outside of GWT-RPC, I think that many of the
>> current major GWT features (widgets, uibinder, etc.) could be ported by the
>> community such that only minor code changes are necessary. I would even
>> hazard a guess that companies like Vaadin might be interested in supporting
>> or at least contributing to a 3.0 based port things like the widget library.
>>
>
> I'd rather bet on Sencha for widgets.
> (note: I have absolutely no information about whether this will happen and
> who would make it happen)
>
>
>> As I've said in other emails though, I think the migration/transition
>> story from 2.8 -> 3.0 needs work and open communication. Based on what's in
>> the videos from the meetup, I don't think it has to be as radical of a
>> change as is feared. To make it smoother, hopefully there will be early
>> access to the compiler API such that the community can start thinking about
>> building 3.0 versions of libraries we want available.
>>
>
> You don't need access to the new compiler for that, you can start
> experimenting right now: given that the idea is that the GWT.create() magic
> will be removed and things would have to be generated upfront using JavaC
> and annotation processors, that means the generated code has no GWT "magic"
> (besides possibly JSNI, which would have to eventually change to JsInterop
> or "JSNI 2.0") and can still be compiled using the current compiler (or
> 2.8.0-SNAPSHOT if you need System.getProperty("user.agent")).
> Disclaimer: I haven't yet tried it though.
> Note that if you'd like to start experimenting with annotation processors,
> I highly suggest you use auto-common's BasicAnnotationProcessor and other
> utilities: https://github.com/google/auto/tree/master/common
>
> --
> 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.
>

-- 
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: Important videos from GWT Meet-up 2015

[James Horsley]

Also worth noting that, outside of GWT-RPC, I think that many of the
current major GWT features (widgets, uibinder, etc.) could be ported by the
community such that only minor code changes are necessary. I would even
hazard a guess that companies like Vaadin might be interested in supporting
or at least contributing to a 3.0 based port things like the widget library.

As I've said in other emails though, I think the migration/transition story
from 2.8 -> 3.0 needs work and open communication. Based on what's in the
videos from the meetup, I don't think it has to be as radical of a change
as is feared. To make it smoother, hopefully there will be early access to
the compiler API such that the community can start thinking about building
3.0 versions of libraries we want available.

On Sun, Jun 21, 2015 at 3:19 AM David  wrote:

> When is GWT 3 available?
>
>
> On Sunday, June 21, 2015 at 6:38:50 AM UTC+8, Paul Robinson wrote:
>>
>> I suspect most people here just haven't quite realised the magnitude of
>> what's planned. The plans are quite reasonable for anybody that can start
>> from scratch (which doesn't include me). Anybody invested in GWT will have
>> a problem. That includes Google, although there are no obvious plans for a
>> migration path.
>>
>> It might mean GWT forks, although I can't see anybody new to GWT adopting
>> GWT 2.8 once 3.0 is out, and the current plans will put people off adopting
>> GWT now.
>>
>> Paul
>>
>  --
> 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.
>

-- 
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: Important videos from GWT Meet-up 2015

[James Horsley]

Someone in the video commented that there needs to be a very clear
messaging around how to best protect/"future proof" yourself. The
Modernizing GWT video was obviously a step in that direction but I'd love
to see something more concrete e.g. if UiBinder won't be supported, what
should we be using?

I had a specific question regarding the recommendation to use Elemental. My
understanding was that Elemental 2.0 was going to be released with GWT 3.0.
Is it safe to use Elemental in it's current state or will there be
significant enough changes that we should wait?

On 12 June 2015 at 15:29, jchimene  wrote:

> Thanks for the link .
>
> To those who've generously uploaded the videos: any possibility of also
> uploading the slides? The technical presentations are pretty much useless
> w/o the slides.
>
> TIA,
> jec
>
>
> On Friday, June 12, 2015 at 2:21:49 AM UTC-7, Phineas Gage wrote:
>>
>> I thought I'd share this link to a series of important videos from the
>> recent GWT Meet-up 2015, which was posted on G+ and in the GWT Contributors
>> group:
>>
>> https://www.youtube.com/playlist?list=PL1yReUCGwGvrqscLu1EAyYRPrr0ceEHLE
>>
>> *Summary:*
>>
>> For anyone who wasn't already aware, there are seismic changes coming for
>> GWT. Basically, gwt-user and everything in it will be gradually mothballed,
>> so widgets, GWT-RPC, UiBinder, CssResource, etc. While we're at it, the GWT
>> compiler will probably go too. If the plan stays as presented, everything
>> is going, sooner or later. It looks as though a much simpler and faster
>> Java to JS transpiler is proposed, maybe under a different project name,
>> with optimizations handled by Closure. I welcome corrections if I've got
>> something wrong here.
>>
>> *Editorial:*
>>
>> Having used GWT for a number of years, I think this is a massive but
>> needed change. It looks like a great direction, that maybe could have been
>> taken even sooner. But personally, I now can't see using GWT for new
>> projects until it appears in its new form. We're in a kind of purgatory now
>> where anything you write in GWT may not be easy to maintain, but the new
>> vision is currently just a hope for the future.
>>
>> As for myself, since I've got a project in its early stages, I'll
>> probably be porting everything I have to JavaScript, until I can count on a
>> stable Java to JS transpiler. At that point, I can decide to move some of
>> the code back to Java, if it's not too painful and the benefits to doing so
>> are clear. At the same time, even with years of Java experience, I have to
>> ask myself, why Java? If it's a better language that compiles to JavaScript
>> that we want, there are many: Dart is coming along, and there are more
>> options than there were before. It's speculation to say what an open source
>> Swift will mean, but the external forces affecting these options can play
>> themselves out while JavaScript will likely continue to be stable for years
>> to come.
>>
>> So rather than drag it out, I'd like to see these changes happen ASAP. As
>> it's sometimes said, "if you find yourself in a hole, stop digging." I
>> believe that if a stable and fast Java to JS transpiler were released, the
>> community would chip in to help complete JRE emulation or other needed
>> projects, and I'm glad to hear that much of the GWT team is being diverted
>> to compiler work.
>>
>> Thanks to the GWT team for sharing these plans with the community!
>>
>>  --
> 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.
>

-- 
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.

Default/Defender Method Support in JsInterop

[James Horsley]

Is support for defender/default methods planned to be support for JsInterop
in GWT 2.8? The change to add general GWT support (
https://gwt-review.googlesource.com/#/c/10330/) called out that JsInterop
support would follow in a subsequent patch but I wasn't sure if it's
targeted for 2.8 or not.

Cheers,
James

-- 
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: Issues with sourceLevel in latest 2.8.0-snapshot

[James Horsley]

Thanks. I had been trying various combinations of "value" and "line"
without success. Digging further it turned out that the snapshot jars were
working but the ones that weren't working were ones I'd built from source.
I eventually got the latest source working, but, unfortunately I didn't do
a good job isolating the changes so am not 100% which fixed it and have
spent enough time on it that I'm just going to roll forward :) Things I
changed included how I passed in sourceLevel using  and , also to switch from building GWT/master using buildonly to dist-dev.

If I go back to isolate the change that's making it work I'll report back
to this thread.

Thanks for your help.

Cheers,
James

On Tue, Apr 7, 2015 at 8:51 PM Jens  wrote:

>
> Thanks. I'm using ant with some custom build targets and passing in
>> sourceLevel using .
>>
>
> I think you must use 
>
> When using "line" it means you have two parameters "-sourceLevel" and
> "1.8".
>
> -- 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.
>

-- 
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: Issues with sourceLevel in latest 2.8.0-snapshot

[James Horsley]

Thanks. I'm using ant with some custom build targets and passing in
sourceLevel using .

I've looked into it a bit already but I'm still thinking the issue is most
likely something wonky in my build.xml but wanted to check here in case
others were having the same problem

I'll do some additional verification and report back.

Cheers,
James

On Tue, Apr 7, 2015 at 8:01 PM Jens  wrote:

> I have a custom build from 3rd April which only adds some Java 8 API
> emulation patches and it works without issues when using -sourceLevel 1.8 .
>
> Maybe you are not passing the parameter correctly? How do you launch
> DevMode/CodeServer/Compiler?
>
> -- 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.
>

-- 
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.

Issues with sourceLevel in latest 2.8.0-snapshot

[James Horsley]

I was using an older version of the 2.8.0-snapshot jars just fine, but
after pulling in the latest versions from sonatype I've started getting the
error "Lambda expressions are allowed only at source level 1.8 or above".
Adding "-sourceLevel 1.8" doesn't appear to fix this. I'm having the same
issue whether I'm running DevMode, CodeServer, or Compiler.

I only have JDK 8 installed on my laptop but confirmed that JDK 8 is being
used just in case there.

Anyone else seeing this?

-- 
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: master/3.0.0 js interop ready to play with?

[James Horsley]

I'm also interested in Cristian's second question about using callback 
functions. Is this supposed to "just work" with the current master or is 
Cristian's EventListenerFactory workaround the best bet for now?

Cheers,
James

On Monday, August 11, 2014 7:17:32 PM UTC+1, Cristian Rinaldi wrote:
>
> I was playing with JsInterop and perform several examples 
>DataTables Plugin of JQuery (import) 
>Polymer (Path Observer, Object Observer), etc...
>
> Here my exmaples:
>https://github.com/csrinaldi/samples-of-gwt/tree/master/gwt-playground
>
> But I 2 question about JsInterop:
>
> The first question with JsInterop is about the import methodology, when I 
> define a interface that maps with a JS core Element, by example: Object or 
> JSON, I not sure the best form for maps the static method of the Object, by 
> example Object.observe(...), or JSON.stringify().
>
> My understanding of JsInterop is that one defines an interface, which is 
> implemented by the compiler. 
> And the allocation for now is through a factory in JSNI, talking to 
> correlate Object for example, for Polymer ObjectObserver:
>
> public static native  ObjectObserver 
> createObjectObserver(T obj)/*-{
>  return new $wnd.ObjectObserver(obj);
> }-*/;
>
>
> But the asignations is a instance of Object, and the observe() method is a 
> static method.
>
> How to is the best form of map this case?
>
> The second question is about function callback passed to the Javascript 
> method
>
> button.addEventListener("click", function(event){
> console.log(event);
> });
>
> The way I found to the compiler to generate things correctly was:
>
> button.addEventListener("click", EventListenerFactory.createEventListener(
> new EventListener() {
>  @Override
>  public void onEvent(JsObject event) {
>//TODO
>  }
> }));
>
> where:
>
> public class EventListenerFactory {
> public static native gwt_sample.EventListener createEventListener(
> EventListener listener)/*-{
>  return function(evt){
>  listener.onEvent(evt);
>  }
>  }-*/;
> }
>
> and:
>
> @JsType
> public interface EventListener {
> void onEvent(E event);
> }
>
> Thanks!!
>
>
> El lunes, 11 de agosto de 2014 09:03:00 UTC-3, salk31 escribió:
>>
>> Thanks. I have great hopes for this stuff ;)
>>
>>>
>>>

-- 
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.7.0 Release Date

[James Horsley]

Is there any word as to whether Java 8 language/syntax support will be
included in 2.7?


On 28 May 2014 18:51, confile  wrote:

> Great thank you!
>
>
> Am Mittwoch, 28. Mai 2014 19:17:22 UTC+2 schrieb Jens:
>
>> Build GWT from source if you want to play around with it. You need to:
>>
>> 1.) mkdir gwt && cd gwt
>> 2.) git clone https://gwt.googlesource.com/gwt trunk
>> 3.) svn checkout http://google-web-toolkit.googlecode.com/svn/tools tools
>> 4.) cd trunk && ant dist-dev
>>
>> This builds GWT without samples and you can then find it in
>> trunk/build/dist/gwt-0.0.0.zip. Unzip it to a location of your choice
>> and then add the GWT SDK to Eclipse in the Eclipse settings.
>>
>> Release is targeted around Google IO 2014 which is at the end of June.
>> But personally I would expect it to be released mid/end July.
>>
>> -- 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.
>

-- 
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: March 12 minutes

[James Horsley]

(Replied to google-web-toolkit@googlegroups.com)

Thanks Colin. Out of interest, would it be likely for java 8 syntax to be
supported in a 2.7 release with the Google I/O target date? FWIW I'd
personally be delighted to have a 2.7 release for June with incremental
compilation as the big ticket item but I am of course looking forward to
using java 8 syntax ASAP :)


On 14 May 2014 17:36, Colin Alworth  wrote:

> Sorry for the delay in sending this out, it was approved by the members
> who were present, but I forgot to mail it out here:
>
>
> GWT Steering Committee call March 12, 2014
>
> Present
>
> Artur Signell
>
> Christian Goudreau
>
> Christian Sadilek
>
> Daniel Kurka
>
> Bhaskar Janakiraman
>
> Thomas Broyer
>
> Colin Alworth (taking notes)
>
> New Maintainers
>
> Manuel Carrasco Moñino nominated for RequestFactory, AutoBeans, I18n, and
> helping with Jenkins builds, approved
>
> John Tamplin nominated for I18n, approved
>
> GWT 2.6.1 release
>
> Thomas, Daniel, Bhaskar brought up various issues that have been fixed and
> should be shipped: e.g. super dev mode fixes for windows, jetty/classloader
> issues for dev mode, ie11 history encoding issues. Others that still need
> to be merged will go into a release checklist, which should also help us
> avoid release issues as in 2.6.0.
>
> Super Dev Mode Improvements
>
> Next GWT version will be 2.7, released around I/O, adding modular
> compilation (to improve Super Dev Mode performance). Other features may
> also be included, or may wait for a later GWT 3 release. Moving up this
> target date and making it a smaller release will get better Super Dev Mode
> out to users right away, rather than delaying until other new features are
> ready to go. IE6 and 7 support, disabled in GWT 2.6, will be removed in
> this release.
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Steering" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to gwt-steering+unsubscr...@googlegroups.com.
> 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: Chrome Canary 36 not showing sourcemaps

[James Horsley]

FWIW I have the same problem with Firefox hanging while using 100% CPU with
SDM


On 16 April 2014 05:41, Stefano Ciccarelli  wrote:

> Chrome 35 too. I ha dato switch back to chrome 34.
> On Firefox suorce maps are showing, but our project is so big that Firefox
> became unusable.
>
>
> Il mercoledì 16 aprile 2014, Thad Humphries  ha
> scritto:
>
> I'm trying to use the device emulator in Chrome Canary (v. 36.0.1941.0)
>> to test various mobile devices. I'd like to debug my mobile code with SDM's
>> sourcemaps, but they are not there, unlike on Chrome 34 where sourcemaps are
>> at localhost:9876/sourcemaps/mymodule. Is there a flag I need to add to get
>> sourcemaps, the way I must add --touch-events to test touch events?
>>
>> --
>> 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.
>>
>
>
> --
> Nel mondo esistono 10 categorie di persone, quelle che capiscono il
> binario e quelle che non lo capiscono.
>
>  --
> 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.
>

-- 
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: Thoughts on GWT 3.0 re: Java 8 and IE 8/9

[James Horsley]

Ray, sounds fantastic and can happily say that something along those lines
would tackle many of the issues with GWT I noted in the current GWT survey.
Will be eagerly awaiting the design docs and proposals.


On 26 October 2013 00:06, Ed  wrote:

> We're thinking about introducing a way of developing UI that is more like
>> traditional HTML design, you create HTML, CSS, and then attach behavior via
>> Java. UiBinder is sort of like this, but it is not
>
>
> Can't wait ... Would love seeing this...
> I feel the pain: a company abroad makes the html/css and then I put the
> logic behind it with gwt... But still find it far from optimal, used
> UIBinder a lot in the past, but not flex enough (not-change and test
> friendly).
> The develop process "gap" is simple too big which reduces productivity.
>
> I am sure that a higher and efficient/low cost productivity, realized with
> GWT, will surely attract more people using it (something I put this in the
> vaadin survey).
>
> --
> 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.
>

-- 
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: GWT 2.6 Release Note

[James Horsley]

GWT 2.6 Release Plan:
https://docs.google.com/document/d/1ZdMwcTjc4rkWg6nntCY1BDB1xI2PHPwaCnTYw-9uAKE/edit#



On 21 October 2013 10:31, Davide Cerbo  wrote:

> Hi all,
>
> somebody have news about GWT 2.6 release date, or information about new
> feature?
>
> Now we are in QA 2013 and the release date should be near.
>
> Should we have all feature specified in the slides below?
>
>
> https://docs.google.com/presentation/d/1PfXXegni0gcZQYpX09t0gs2Z9dqST5MmiHc_NoPSluo/edit#slide=id.p18
>
> Any news will be appreciated :)
>
> bye,
> Davide
>
> --
> --
> Davide Cerbo
> ---
> www.linkedin.com/in/davidecerbo
> + 39 329 70 81 927
> ---
>
> --
> 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.
>

-- 
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: RequestFactory module - queue, retry and non atomic batching..

[James Horsley]

I'm also quite interested but haven't had time to look.


On 18 July 2013 10:00, salk31  wrote:

> Ho k... I'll be very interested to hear your thoughts... If you think it
> is fixable maybe GAE demo with some UI may be next step for me?
>
>
> On Thursday, July 18, 2013 9:49:47 AM UTC+1, Thomas Broyer wrote:
>>
>> FYI, I still haven't found the time to look at it…
>>
>> On Thursday, July 18, 2013 9:26:35 AM UTC+2, salk31 wrote:
>>>
>>> H. Guess not a lot of demand then. Will hold off doing any more work
>>> on this.
>>>
>>> Cheers
>>>
>>> Sam
>>>
>>> On Wednesday, July 17, 2013 9:04:53 AM UTC+1, salk31 wrote:

 https://github.com/salk31/gwt-**rf-queue

 I've been allowed to open source this and given two hours a week to
 work on it...

 I thought it was worth sharing now that it compiles and there is a
 working demo. I've grafted it onto the dynatablerf sample and added some
 controls to fake auth and network failure.

 So, any thoughts on if this is worth pushing on with? A real generic
 need? I've missed an existing solution?

 Cheers

 Sam

>>>  --
> 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.
>
>
>

-- 
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: Code splittingmysteries

[James Horsley]

FYI I updated
http://code.google.com/p/google-web-toolkit/issues/detail?id=7874 with some
of my findings. I haven't found a workaround other than reverting to GWT
2.5.0 and am not sure I can dedicate any more time to this right now so
will just revert I guess :(


On 12 June 2013 19:34, Ed  wrote:

> Ed, out of interest, are you using Gin?
>
> No, but probably would use it if I would start "blank".
> When I started with GWT (about 7 years ago), there was no GIN, so I had to
> make my own "thinks" like factories, which I use nowadays .  This all
> resulted in having build my own rich gwt framework/lib, which I am happy
> about thought, works well..
> But in general I am careful using external gwt lib's there are many out
> there being not maintained anymore, which can result in gwt upgrade
> problems..
> I started out with mygwt, contributed some things... but then It became
> gxt and became half commercial :(
>
> --
> 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?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Code splittingmysteries

[James Horsley]

Ed, out of interest, are you using Gin?


On 12 June 2013 16:29, James Horsley  wrote:

> Yeah. the SOYC report in this case hasn't helped me much either because
> I'm not reading it right or it's just not surfacing the right info. The
> only 404 I get is regarding the "compiler metrics" link.
>
>
> On 12 June 2013 16:18, Ed Bras  wrote:
>
>> Yep, tried to go back to 2.5, but then I see some other bugs that are
>> solved in 2.5.1 ;)... So for me this was no option...
>>
>>
>> On Wed, Jun 12, 2013 at 5:17 PM, Ed Bras  wrote:
>>
>>> Yes, I understand what you mean, I experienced the same...
>>> It's hard to hand over a "test case" that fails, to the dev team, such
>>> that they can use that to work on :(
>>>
>>> Yes it would be nice to have better  facilities such that we can try to
>>> track done the cause our self. Currently the SOYC report isn't helping a
>>> lot.
>>> To my experience the SOYC report is buggy, as some pages result in a 404
>>> :(.. (I experienced that several times the last years with a correctly
>>> created soyc, it's also in some issue if I remember correctly).
>>>
>>>
>>>
>>> On Wed, Jun 12, 2013 at 4:45 PM, James Horsley 
>>> wrote:
>>>
>>>> Yeah. I've tried reproducing the issue with a sample app but thus far
>>>> haven't been able to; not sure that the sample webapp captures enough of
>>>> the complexity of the actual webapp we're having the problem with. As I
>>>> mentioned before can confirm that changing none of the webapp code but
>>>> switching between 2.5 and 2.5.1 causes everything to end up in the
>>>> leftover. From the compiler report it's not at all obvious why these
>>>> classes are in the leftover fragment as they look isolated from what I can
>>>> tell.
>>>>
>>>>
>>>> On 12 June 2013 13:13, Ed  wrote:
>>>>
>>>>>  Ed, did you ever get this sorted? As I commented on the linked issue
>>>>>> I'm running into what seems to be a similar problem.
>>>>>
>>>>> No. It's hard to track the exact cause. It tried, but had to give up
>>>>> (a lot of time, and not knowing exactly what happens.
>>>>> But it's good to see that more people are experiencing the same kind
>>>>> of problems such that I am not alone ;)
>>>>> Ray seem to be the code splitting guru. Let's hope he has has some
>>>>> time to look at this ;)
>>>>>
>>>>> If you can isolate the problem in a small program that reproduces this
>>>>> behavior, please do upload it in the issue. I tried, but failed :(
>>>>> This will help the gwt dev team a lot to solve the problem (and the
>>>>> issue will get a higher priority and solved sooner).
>>>>>
>>>>> --
>>>>> 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?hl=en.
>>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>>
>>>>>
>>>>>
>>>>
>>>>  --
>>>> You received this message because you are subscribed to a topic in the
>>>> Google Groups "Google Web Toolkit" group.
>>>> To unsubscribe from this topic, visit
>>>> https://groups.google.com/d/topic/google-web-toolkit/_8CdVbBb488/unsubscribe?hl=en
>>>> .
>>>> 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-web-toolkit@googlegroups.com.
>>>> Visit this group at
>>>> http://groups.google.com/group/google-web-toolkit?hl=en.
>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>
>>>>
>>>>
>>>
>>>
>>  --
>> 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?hl=en.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Code splittingmysteries

[James Horsley]

Yeah. the SOYC report in this case hasn't helped me much either because I'm
not reading it right or it's just not surfacing the right info. The only
404 I get is regarding the "compiler metrics" link.


On 12 June 2013 16:18, Ed Bras  wrote:

> Yep, tried to go back to 2.5, but then I see some other bugs that are
> solved in 2.5.1 ;)... So for me this was no option...
>
>
> On Wed, Jun 12, 2013 at 5:17 PM, Ed Bras  wrote:
>
>> Yes, I understand what you mean, I experienced the same...
>> It's hard to hand over a "test case" that fails, to the dev team, such
>> that they can use that to work on :(
>>
>> Yes it would be nice to have better  facilities such that we can try to
>> track done the cause our self. Currently the SOYC report isn't helping a
>> lot.
>> To my experience the SOYC report is buggy, as some pages result in a 404
>> :(.. (I experienced that several times the last years with a correctly
>> created soyc, it's also in some issue if I remember correctly).
>>
>>
>>
>> On Wed, Jun 12, 2013 at 4:45 PM, James Horsley 
>> wrote:
>>
>>> Yeah. I've tried reproducing the issue with a sample app but thus far
>>> haven't been able to; not sure that the sample webapp captures enough of
>>> the complexity of the actual webapp we're having the problem with. As I
>>> mentioned before can confirm that changing none of the webapp code but
>>> switching between 2.5 and 2.5.1 causes everything to end up in the
>>> leftover. From the compiler report it's not at all obvious why these
>>> classes are in the leftover fragment as they look isolated from what I can
>>> tell.
>>>
>>>
>>> On 12 June 2013 13:13, Ed  wrote:
>>>
>>>>  Ed, did you ever get this sorted? As I commented on the linked issue
>>>>> I'm running into what seems to be a similar problem.
>>>>
>>>> No. It's hard to track the exact cause. It tried, but had to give up (a
>>>> lot of time, and not knowing exactly what happens.
>>>> But it's good to see that more people are experiencing the same kind of
>>>> problems such that I am not alone ;)
>>>> Ray seem to be the code splitting guru. Let's hope he has has some time
>>>> to look at this ;)
>>>>
>>>> If you can isolate the problem in a small program that reproduces this
>>>> behavior, please do upload it in the issue. I tried, but failed :(
>>>> This will help the gwt dev team a lot to solve the problem (and the
>>>> issue will get a higher priority and solved sooner).
>>>>
>>>> --
>>>> 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?hl=en.
>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>
>>>>
>>>>
>>>
>>>  --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "Google Web Toolkit" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/google-web-toolkit/_8CdVbBb488/unsubscribe?hl=en
>>> .
>>> 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-web-toolkit@googlegroups.com
>>> .
>>> Visit this group at
>>> http://groups.google.com/group/google-web-toolkit?hl=en.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>>
>>>
>>
>>
>  --
> 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?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Code splittingmysteries

[James Horsley]

Quite frustrating as I don't feel like I'm making much progress and am just
going to have to go back to 2.5.0 but don't really want to lose out on the
bugfixes from 2.5.1 :(


On 12 June 2013 15:45, James Horsley  wrote:

> Yeah. I've tried reproducing the issue with a sample app but thus far
> haven't been able to; not sure that the sample webapp captures enough of
> the complexity of the actual webapp we're having the problem with. As I
> mentioned before can confirm that changing none of the webapp code but
> switching between 2.5 and 2.5.1 causes everything to end up in the
> leftover. From the compiler report it's not at all obvious why these
> classes are in the leftover fragment as they look isolated from what I can
> tell.
>
>
> On 12 June 2013 13:13, Ed  wrote:
>
>>  Ed, did you ever get this sorted? As I commented on the linked issue I'm
>>> running into what seems to be a similar problem.
>>
>> No. It's hard to track the exact cause. It tried, but had to give up (a
>> lot of time, and not knowing exactly what happens.
>> But it's good to see that more people are experiencing the same kind of
>> problems such that I am not alone ;)
>> Ray seem to be the code splitting guru. Let's hope he has has some time
>> to look at this ;)
>>
>> If you can isolate the problem in a small program that reproduces this
>> behavior, please do upload it in the issue. I tried, but failed :(
>> This will help the gwt dev team a lot to solve the problem (and the issue
>> will get a higher priority and solved sooner).
>>
>> --
>> 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?hl=en.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Code splittingmysteries

[James Horsley]

Yeah. I've tried reproducing the issue with a sample app but thus far
haven't been able to; not sure that the sample webapp captures enough of
the complexity of the actual webapp we're having the problem with. As I
mentioned before can confirm that changing none of the webapp code but
switching between 2.5 and 2.5.1 causes everything to end up in the
leftover. From the compiler report it's not at all obvious why these
classes are in the leftover fragment as they look isolated from what I can
tell.


On 12 June 2013 13:13, Ed  wrote:

>  Ed, did you ever get this sorted? As I commented on the linked issue I'm
>> running into what seems to be a similar problem.
>
> No. It's hard to track the exact cause. It tried, but had to give up (a
> lot of time, and not knowing exactly what happens.
> But it's good to see that more people are experiencing the same kind of
> problems such that I am not alone ;)
> Ray seem to be the code splitting guru. Let's hope he has has some time to
> look at this ;)
>
> If you can isolate the problem in a small program that reproduces this
> behavior, please do upload it in the issue. I tried, but failed :(
> This will help the gwt dev team a lot to solve the problem (and the issue
> will get a higher priority and solved sooner).
>
> --
> 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?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Code splittingmysteries

[James Horsley]

Ed, did you ever get this sorted? As I commented on the linked issue I'm 
running into what seems to be a similar problem.

On Wednesday, April 10, 2013 8:13:07 AM UTC+1, Ed wrote:
>
> I just downgraded to GWT 2.4 and my left over fragment disappeared :(... 
> (initial load was almost the same)
> Strange -> or 2.4. had a code splitting involved bug or 2.5. has one...
>
>
>
> On Mon, Mar 25, 2013 at 4:03 PM, Ed Bras 
> > wrote:
>
>> BTW: a corresponding issue in the issue tracker: 
>> https://code.google.com/p/google-web-toolkit/issues/detail?id=7874
>> Let's hope more people are experiencing the same problem (and vote the 
>> issue) such that the dev team put it on their priority list.
>>
>>
>> On Wed, Mar 20, 2013 at 3:22 PM, Ashton Thomas 
>> 
>> > wrote:
>>
>>> I would also be interested in any updates to this as I am currently 
>>> working on the async aspect or my app. (I wouldn't even know how to 
>>> identify anomalies due to a lack of experience here)
>>>
>>> I also remembrer having the same questions with soyc
>>>
>>> -at 
>>>
>>>
>>> On Wednesday, March 20, 2013 7:53:11 AM UTC-4, Ed wrote:

 After upgrading from 2.5.0 to 2.5.1 all of a sudden my code splitting 
 result is different:
 + Code fragments are bundles together which weren't before.
 + I have a left over fragment, which was 0 (see attachment).

 What changed concerning code splitting? Can't find any in the release 
 notes.

 A few observations:
 1) All my components have a singleton facade that contains a method to 
 create the package protected  controller implementation that is called 
 through split point (GWT.runAsync()).
 In this way I have a LoginControllerDefault that is present in the left 
 over, but this package protected controller ONLY appears in the 
 LoginFacade.
 In the same way I have SubscribeControllerControllerD**efault that 
 appears only in SubscribeControllerFacade...
 What suprised me is that they appear both in the same code split, 
 namely #30 (see screenshot attachment).

 No idea why.
 I moved the creation of  LoginControllerDefault  from the Facade 
 "directly" (see below for code snippets) in to the runAsync, but that had 
 no effect.
 I also removed the LoginControllerDefault completely which had little 
 effect on the left-over

 When I read the soyc report (automatically build during maven nightly 
 build), It doesn't really help me. This page is hard to understand, like 
 this page:
soycReport/compile-report/**leftoverStatus-0.html

 Even worse,  from this page you can go deeper  to see why a class is 
 in a certain split point but that results in a page not found (404).
 That is, the following page isn't present. BTW: the page also resulted 
 in a 404 in previous GWT releases.
  soycReport/compile-report/**
 methodDependencies-total-0.**html
 Why?

 I played with the nr of "fragmentCount", but that has little effect, 
 see the attached screenshots:
 + fragmentCount = 6: screenshot with 4 splits points.
 + fragmentCount = 8: screenshot with 6 splits points.
 + fragmentCount = 10: screenshot with 7 splits points.

 Below a code snippet that shows how I create the controllers in split 
 point #30 (see screenshot). It concerns the creation of the 
 LoginControllerDefault and SubscribeInfoControllerDefault**.
 Note: I don't find it the most elegant code solution, but before I 
 passed in a Creator interface that was used in GWT.runAsync(), but that 
 didn't work (big left over). I posted that in the forum and it was 
 mentioned that it could be that it is because the code removal is run 
 after 
 the split point code, and that is probably why it doesn't work and that 
 Ray 
 still have a look in to code split code that need to be optimized.

 How to solve/analyze these issues?
 What are your experiences?
 Any suggestions are more then welcome as I am out of ideas and find it 
 hard to solve this, but it frustrates me ;)


 Loading and creating the the Login and SubscribeInfo controller:
 -
 The code snippet that is called by the LoginControllerBuilder to load 
 the Login controller:
  public void create(final AsyncCallback callback) {
 getLazyLoader().**createInCodeSplitGeneral30(**LoginController.class, 
 callback);
  }


 The controller loading code (in other class):
 public  void createInCodeSplitGeneral30(**final Class type, 
 final AsyncCallback callback, final SimpleMediator mediator) {
  GWT.runAsync(new RunAsyncCallback() {
 public void onSuccess() {
 callback.onSuccess(**createCodeSplitGeneral30(type, mediator));
  }

 public void onFailure(final Throwable reason) {
 callback.onFailure(reason);
  }
 });
 }

>>>

Re: I/O 2013 - GWT Sessions?

[James Horsley]

+1 for a separate GWT convention


On 7 March 2013 06:06, Steve  wrote:

> Now that GWT is more community run, I think it would be better if we just
> had our own convention...
>
> I went to the second I/O, and GWT was all over the place. Then each year
> after there were fewer and fewer session, more free swag, and an android
> push. On top of that, there is such a media hype about the event nowadays
> that it's become less and less about developers and more and more about
> "Oh, look what we did! And here's some free stuff! Not a developer? No
> problem! See the show! Here's some more free stuff!".
>
> It's a shame. I don't even think all of the GWT session videos made it up
> on youtube. They had some great pointers...
>
>
>
> On Wednesday, March 6, 2013 5:56:52 PM UTC-5, James wrote:
>>
>> I know it's earlybut is anyone familiar with the planned Google Web
>> Toolkit sessions for Google I/O 2013?  It was a bit disappointing last year
>> when there was only one real GWT session...after there had been many in all
>> the previous years.  GWT Team...any comments?
>
>  --
> 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?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: RequestFactory issue with overloaded setters in domain type

[James Horsley]

 FYI writing my own ServiceLayerDecorator with the following worked like a
charm so extra thanks for the suggestion

private static Method getBeanMethod( BeanMethod methodType, Class
domainType, String property, Class propertyType ) {
for ( Method m : domainType.getMethods() ) {
if ( methodType.matches( m ) && property.equals(
methodType.inferName( m ) )
&& m.getParameterTypes()[0].isAssignableFrom(
propertyType ) ) {
m.setAccessible( true );
return m;
}
}
return null;
}

@Override
public Method getSetter( Class domainType, String property ) {
Class propertyType = getTop().getGetter( domainType, property
).getReturnType();
Method setter = getBeanMethod( BeanMethod.SET, domainType,
property, propertyType );
if ( setter == null ) {
setter = getBeanMethod( BeanMethod.SET_BUILDER, domainType,
property, propertyType );
}
return setter;
}


On 28 February 2013 13:44, James Horsley  wrote:

> Makes sense. Thanks!
>
>
> On 28 February 2013 13:27, Thomas Broyer  wrote:
>
>>
>>
>> On Thursday, February 28, 2013 1:50:03 PM UTC+1, James Horsley wrote:
>>>
>>> I'll take a stab at writing a ServiceLayerDecorator as that should get
>>> me unblocked without writing DTO's and if the correct setter is called the
>>> NPE's won't be an issue. Thanks to you both for the suggestions!
>>>
>>> Thomas, is this issue likely to end up as PatchesWelcome or WontFix? If
>>> the former then I'll look at getting a patch together.
>>>
>>
>> I you send a patch, I'll look at it; the outcome will depend on what
>> changes the patch has to make.
>>
>> --
>> 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?hl=en.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: RequestFactory issue with overloaded setters in domain type

[James Horsley]

Makes sense. Thanks!


On 28 February 2013 13:27, Thomas Broyer  wrote:

>
>
> On Thursday, February 28, 2013 1:50:03 PM UTC+1, James Horsley wrote:
>>
>> I'll take a stab at writing a ServiceLayerDecorator as that should get me
>> unblocked without writing DTO's and if the correct setter is called the
>> NPE's won't be an issue. Thanks to you both for the suggestions!
>>
>> Thomas, is this issue likely to end up as PatchesWelcome or WontFix? If
>> the former then I'll look at getting a patch together.
>>
>
> I you send a patch, I'll look at it; the outcome will depend on what
> changes the patch has to make.
>
> --
> 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?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: RequestFactory issue with overloaded setters in domain type

[James Horsley]

I'll take a stab at writing a ServiceLayerDecorator as that should get me
unblocked without writing DTO's and if the correct setter is called the
NPE's won't be an issue. Thanks to you both for the suggestions!

Thomas, is this issue likely to end up as PatchesWelcome or WontFix? If the
former then I'll look at getting a patch together.



On 28 February 2013 11:19, Thomas Broyer  wrote:

>
>
> On Thursday, February 28, 2013 11:18:22 AM UTC+1, Ignacio Baca
> Moreno-Torres wrote:
>>
>> If you don't want to have a delegator DTO, you may try AOP. For example,
>> with guice you can match the classes you have the NPE problem, and return
>> null before de NPE.
>>
>
> or in this specific case, use a ServiceLayerDecorator whose getSetter
> returns the appropriate setter for the given known class and property name
> (or possibly do the right thing in setProperty, without the need to go down
> to the java.lang.reflect level)
>
> --
> 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?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: RequestFactory issue with overloaded setters in domain type

[James Horsley]

Issue filed
https://code.google.com/p/google-web-toolkit/issues/detail?id=8039


On 27 February 2013 17:04, James Horsley  wrote:

> Thanks for the quick and detailed reply.
>
> Given a big win using RequestFactory is having it work well with existing
> server side data models it'd seem like something we'd want to fix, relative
> to other priorities of course. In this specifc case I don't own the domain
> class as it's from a 3rd party and it's been fantastic with RF to just use
> a proxy interface to pass the data across without another DTO. I can extend
> it in this specific case to override the behaviour of setUnit(SomeUnitEnum)
> but that's not always possible and I'm still at the mercy of the order the
> methods are iterated in as to what type I have to use in my Proxy
> interface, this throws it into the want to fix case for me (not surprising
> perhaps given I'm the one asking the question).
>
> I'll file an issue for it and am fully behind the fact that if I think
> it's important that I should get a patch out for it so will try to do that.
> The geTop().getGetter(domainClass, property) suggestion you made sounds
> like a quick and mildly dirty way through; although I may look at the first
> fallback based solution you mentioned.
>
> Cheers,
> James
>
>
>
>
> On 27 February 2013 16:05, Thomas Broyer  wrote:
>
>>
>>
>> On Wednesday, February 27, 2013 4:05:30 PM UTC+1, James Horsley wrote:
>>>
>>> I'm running into an issue where RequestFactory isn't calling the correct
>>> setter on the domain object in DevMode and I've not tried it compiled yet.
>>> Looking at the code it appears that ReflectiveServiceLayer.**getBeanMethod
>>> is just picking the first setter it finds based on SET/SET_BUILDER, are
>>> only verifying that the method is a setter, and the method name.
>>>
>>> I was going to submit an issue for it and see about getting a patch
>>> together but thought I'd ask here first to see if I'm missing something.
>>>
>>> A more concrete example that I'm running into is that the domain class
>>> has something like the following:
>>>
>>> DomainClass.java
>>> void setUnit(String unit) { this.unit = unit; }
>>> void setUnit(SomeUnitEnum unit) { this.unit = unit.toString(); }
>>>
>>> ProxyInterface.java
>>> void setUnit(String unit);
>>> String getUnit();
>>>
>>> when unit is null, the server side RF code is calling the enum version
>>> which is causing an NPE.
>>>
>>> Anything I'm missing or should just file the issue?
>>>
>>
>> Fixing this would require breaking changes in ServiceLayerDecorator
>> though (getSetter would need a new expectedType parameter, similar to
>> setProperty) so I wonder how best we could provide backwards compatibility
>> (ideally, getSetter(Class,String,Class) would fallback to
>> getSetter(Class,String) (to ensure backwards compatibility with custom
>> ServiceLayerDecorators) but we'd then like
>> ReflectiveServiceLayer#getSetter(Class,String) to answer based on the Class
>> originally passed to getSetter(Class,String,Class). Alternatively,
>> ReflectiveServiceLayer#getSetter could call getTop().getGetter(domainClass,
>> property) and then use the getter's return type to disambiguate overloaded
>> setters. That would then make it impossible to have proxies with
>> setter-only properties (see
>> https://code.google.com/p/google-web-toolkit/issues/detail?id=5760,
>> there's much to be done before this can be supported, so the server-side
>> implementation might be revisited at that point, i.e. not a showstopper)
>>
>> The question is: is this something we really *want* to fix? And honestly,
>> I don't have a problem rejecting overloaded setters (see also the comment
>> on https://code.google.com/p/google-web-toolkit/issues/detail?id=6587:
>> if it weren't for protobuf where the idiom is common, having "overloaded"
>> hasXxx and getXxx getters would have been declared illegal).
>>
>> Feel free to file an issue, but be warned that I'll categorize it as
>> PatchesWelcome.
>>
>> --
>> 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?hl=en.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: RequestFactory issue with overloaded setters in domain type

[James Horsley]

Thanks for the quick and detailed reply.

Given a big win using RequestFactory is having it work well with existing
server side data models it'd seem like something we'd want to fix, relative
to other priorities of course. In this specifc case I don't own the domain
class as it's from a 3rd party and it's been fantastic with RF to just use
a proxy interface to pass the data across without another DTO. I can extend
it in this specific case to override the behaviour of setUnit(SomeUnitEnum)
but that's not always possible and I'm still at the mercy of the order the
methods are iterated in as to what type I have to use in my Proxy
interface, this throws it into the want to fix case for me (not surprising
perhaps given I'm the one asking the question).

I'll file an issue for it and am fully behind the fact that if I think it's
important that I should get a patch out for it so will try to do that. The
geTop().getGetter(domainClass, property) suggestion you made sounds like a
quick and mildly dirty way through; although I may look at the first
fallback based solution you mentioned.

Cheers,
James




On 27 February 2013 16:05, Thomas Broyer  wrote:

>
>
> On Wednesday, February 27, 2013 4:05:30 PM UTC+1, James Horsley wrote:
>>
>> I'm running into an issue where RequestFactory isn't calling the correct
>> setter on the domain object in DevMode and I've not tried it compiled yet.
>> Looking at the code it appears that ReflectiveServiceLayer.**getBeanMethod
>> is just picking the first setter it finds based on SET/SET_BUILDER, are
>> only verifying that the method is a setter, and the method name.
>>
>> I was going to submit an issue for it and see about getting a patch
>> together but thought I'd ask here first to see if I'm missing something.
>>
>> A more concrete example that I'm running into is that the domain class
>> has something like the following:
>>
>> DomainClass.java
>> void setUnit(String unit) { this.unit = unit; }
>> void setUnit(SomeUnitEnum unit) { this.unit = unit.toString(); }
>>
>> ProxyInterface.java
>> void setUnit(String unit);
>> String getUnit();
>>
>> when unit is null, the server side RF code is calling the enum version
>> which is causing an NPE.
>>
>> Anything I'm missing or should just file the issue?
>>
>
> Fixing this would require breaking changes in ServiceLayerDecorator though
> (getSetter would need a new expectedType parameter, similar to setProperty)
> so I wonder how best we could provide backwards compatibility (ideally,
> getSetter(Class,String,Class) would fallback to getSetter(Class,String) (to
> ensure backwards compatibility with custom ServiceLayerDecorators) but we'd
> then like ReflectiveServiceLayer#getSetter(Class,String) to answer based on
> the Class originally passed to getSetter(Class,String,Class).
> Alternatively, ReflectiveServiceLayer#getSetter could call
> getTop().getGetter(domainClass, property) and then use the getter's return
> type to disambiguate overloaded setters. That would then make it impossible
> to have proxies with setter-only properties (see
> https://code.google.com/p/google-web-toolkit/issues/detail?id=5760,
> there's much to be done before this can be supported, so the server-side
> implementation might be revisited at that point, i.e. not a showstopper)
>
> The question is: is this something we really *want* to fix? And honestly,
> I don't have a problem rejecting overloaded setters (see also the comment
> on https://code.google.com/p/google-web-toolkit/issues/detail?id=6587: if
> it weren't for protobuf where the idiom is common, having "overloaded"
> hasXxx and getXxx getters would have been declared illegal).
>
> Feel free to file an issue, but be warned that I'll categorize it as
> PatchesWelcome.
>
> --
> 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?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

RequestFactory issue with overloaded setters in domain type

[James Horsley]

I'm running into an issue where RequestFactory isn't calling the correct
setter on the domain object in DevMode and I've not tried it compiled yet.
Looking at the code it appears that ReflectiveServiceLayer.getBeanMethod is
just picking the first setter it finds based on SET/SET_BUILDER, are only
verifying that the method is a setter, and the method name.

I was going to submit an issue for it and see about getting a patch
together but thought I'd ask here first to see if I'm missing something.

A more concrete example that I'm running into is that the domain class has
something like the following:

DomainClass.java
void setUnit(String unit) { this.unit = unit; }
void setUnit(SomeUnitEnum unit) { this.unit = unit.toString(); }

ProxyInterface.java
void setUnit(String unit);
String getUnit();

when unit is null, the server side RF code is calling the enum version
which is causing an NPE.

Anything I'm missing or should just file the issue?

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How to obfuscate RequestFactory type name, not only the operations ( GWT 2.4 )

[James Horsley]

I'll see if I can get some time to getting a patch together for this.

On 6 September 2012 17:32, Thomas Broyer  wrote:

>
> On Thursday, September 6, 2012 4:58:31 PM UTC+2, Chris Lercher wrote:
>>
>> On Thursday, September 6, 2012 3:58:34 PM UTC+2, Thomas Broyer wrote:
>>>
>>> Would you mind filing an issue in the tracker (if no one already did it)
>>> ?
>>>
>>
>> I did a few years ago: http://code.google.com/p/**
>> google-web-toolkit/issues/**detail?id=5729
>> It was closed as a duplicate of http://code.google.com/p/**
>> google-web-toolkit/issues/**detail?id=5394,
>> which is fixed and released in 2.4... but it doesn't really fix 5729.
>>
>
> Well, it obfuscates all type and method names, *but* the RequestFactory
> name (as it's needed to load the DeobfuscatorBuilder class)
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-web-toolkit/-/2yp-mCXMgfMJ.
>
> 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.
>

-- 
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.

Re: How to obfuscate RequestFactory type name, not only the operations ( GWT 2.4 )

[James Horsley]

I'm also very interested in this; I'd looked briefly going back but didn't
find anything either.

On 5 September 2012 11:01, zz  wrote:

> Hi,
>
> I've searched all over the web, but didn't quite get my question answered.
>
> How to obfuscate the type name of my request factory interface that
> extends RequestFactory? I can only see operations on service are obfuscated.
>
> For gwt-rpc, it's enabled by adding below to module file.
>  name='com.google.gwt.user.**RemoteServiceObfuscateTypeName**s'
> />
>
> Is there anything similar required to enable obfuscation for
> RequestFactory?
>
> Regards,
> zz
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-web-toolkit/-/ggMXO4wGPiEJ.
> 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.
>

-- 
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.

Re: GWT future

[James Horsley]

Google I/O 2012 - The History and Future of Google Web Toolkit (
http://www.youtube.com/watch?v=VOf27ez_Hvg )

On 23 July 2012 08:14, AG  wrote:

> I'm an Architect and we have been looking to port our legacy HTML w/ Java
> Script based web app  (with java backend) to a next generation web
> application. We are a java shop so GWT is very popular with our developers
> and I have been so called GWT fan-boy all along.
>
> However, lately I'm strongly considering moving away from GWT. Following
> are my observations that are scaring me to start looking for GWT
> alternatives:
>
> 1. Larry Page has been killing no-so-happening (or revenue generating)
> projects from google. I was reading that 30+ projects have already been
> killed/shelved ever since Larry became CEO.
>   -- I understand the need for this and I also understand that GWT
> currently enjoys a healthy developer community.
>
> 2. DART - Looks like its the next big thing within google to develop web
> applications. As a google outsider, at least this is what it seems like.
> Google IO 2012 has no sessions for GWT while DART had several and there is
> even a session to convert GWT apps to DART.
>
> 3. The latest update to Google Developer portal (
> http://developers.google.com) has no direct links to GWT. The web
> development section goes to chrome.
>
> I think the GWT team can address some of my concerns but it would be great
> if Google's management can stand behind GWT as a platform of choice for web
> development - similar to how Microsoft stands behind theirs development
> platforms.
>
> AG
>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-web-toolkit/-/PzISxYR26CIJ.
> 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.
>

-- 
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.

Re: Real time informations Draw in Gchart

[James Horsley]

I've been using  http://code.google.com/p/gflot/ and have been very happy
with it, in particular its latest 2.4 release. I think GFlot and GChart
(haven't looked at OFCGwt) have pretty extensive examples inc. source on
their sites?

On 7 June 2012 09:33, alaa aadil  wrote:

> Hello,
>
> i want to display some real time informations an a Gchart or
> OFCGwt  ,  please i need an exemple for that
>
>
> thanks
> best regards
>
> --
> 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.
>
>

-- 
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.

Re: GWT SDK 2.4 jars

[James Horsley]

Thomas, you've cleared up all the questions I had so many thanks for your
super informative answer! Seems like this should be in a wiki somewhere on
the main GWT site or perhaps worth a posterous entry from yourself?

Cheers,
James

On 12 September 2011 13:38, Thomas Broyer  wrote:

> I unfortunately don't think you'll find any "official statement" (or maybe
> in documentation for older versions, but I cannot find any in the current
> documentation).
>
>
>- gwt-dev contains the compiler and the DevMode; i.e. the dev tools.
>It's only needed at compile-time, and shouldn't be needed by your code,
>unless you're coding generators or linkers (that somehow "plug" into the
>compiler and devmode, so their APIs are defined in gwt-dev)
>- gwt-user contains the "user library", i.e. what you'll use in your
>code that will either be compiled to JS or run on the server. gwt-user has
>an implicit dependency on gwt-dev, as it contains generators and linkers.
>It also contains a few tools (webAppCreator, i18nCreator, etc.), most
>of which a deprecated (webAppCreator, i18nCreator, etc.), and the JUnit
>support (GWTTestCase et al.)
>This is what you'll add as to your project as a dependency
>(compile-time only though). gwt-user bundles a few dependencies
>(javax.servlet, “Flute” the CSS parser from the W3C) so it's not to be
>deployed.
>- gwt-servlet is a subset of gwt-user (well, there are also a few
>classes from gwt-dev) containing code to be run on the server
>(RemoteServiceServlet, etc.)
>
> The line between gwt-dev and gwt-user is a bit blurry though, and a few
> utility classes from gwt-dev are used in gwt-servlet too. This is all
> historical. If GWT were to be repackaged today, classes would probably be
> split differently among JARs.
>
> Finally, unless you intend to contribute to GWT (or go into deep debug
> sessions of GWT itself), all you have to know is that your project should
> have gwt-user.jar as a dependency; possibly gwt-dev.jar too; and you'll only
> ever deploy gwt-servlet.jar. gwt-dev is used for the devmode or to compile
> your code (or as a dependency if you have a generator or linker in your
> code).
>
> Now, in GWT 2.4, there are a few new JARs:
>
>- requestfactory-client: client-side code for RequestFactory (includes
>RequestFactorySource), to be used in a VM (unit tests, stress-tests, or an
>Android or desktop app)
>- requestfactory-server: server-side code for RequestFactory (includes
>RequestFactoryServlet). If you only use RF on the server (no GWT-RPC, no
>SafeHtml, etc.) then you can deploy this JAR instead of gwt-servlet.jar.
>- requestfactory-apt: annotation processor, used at compile-time only.
>See
>
> http://code.google.com/p/google-web-toolkit/wiki/RequestFactoryInterfaceValidation
>
> There's a large overlap between client and server, as "shared" code is in
> both JARs.
>
> Additionally, all three (client, server and apt) are bundled within
> gwt-user.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-web-toolkit/-/frzl_Ljvo6wJ.
> 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.
>

-- 
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.

GWT SDK 2.4 jars

[James Horsley]

Is there a good breakdown of what each of the jars are for and at what point
in the dev lifecycle they're intended to be used? There seems to be a large
set of overlap between the various jars content wise. While I can make
educated guesses it'd be great to have an official statement of their
intents.

Cheers,
James

-- 
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.

Re: HeaderLayoutPanel?

[James Horsley]

Setting the height of the SplitLayoutPanel to 100% works, but he
problem of it not resizing when the browser is resized by dragging the
bottom border of the window. Corner and left/right dragging trigger a
layout just fine.

On 31 August 2011 21:31, James Horsley  wrote:
> Thanks for the breakdown Thomas. At first I thought it was something
> particular to my application but I created a basic starter project and
> it doesn't show the SplitPanelLayout with the super basic example
> below. Oddly enough if you change the CSS position of the
> SplitLayoutPanel element to static then it shows just fine with the
> caveat that, although corner dragged resizes are handled okay, bottom
> edge draggged resizes don't update the HeaderPanel's layout.
>
> 
>
>    
>     header 
>
>    
>    
>        
>             Navbar 
>        
>
>        
>             Stuff 
>        
>    
>
>    
>     footer 
>
> 
>
> On 31 August 2011 15:57, Thomas Broyer  wrote:
>>
>> On Wednesday, August 31, 2011 9:18:22 AM UTC+2, James Horsley wrote:
>>>
>>> Would love to have the naturally resizing header and footer but to
>>> then add a SplitLayoutPanel as the center. Doing so causes nothing to
>>> show which I'm guess is due to HeaderPanel not being a LayoutPanel?
>>
>> HeaderPanel is a RequiresResize, and if you look at its source, you'll see
>> that it'll call onResize on its content widget if it's a RequiresResize too.
>> I guess the reason HeaderPanel doesn't implement ProvidesResize is because
>> it doesn't implement the behavior for the header and footer.
>> This does however make it a "layout panel".
>> In other words: it should work. (and I have no idea why it doesn't)
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Google Web Toolkit" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/google-web-toolkit/-/Kpd-yKfZSuIJ.
>> 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.
>>
>

-- 
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.

Re: HeaderLayoutPanel?

[James Horsley]

Thanks for the breakdown Thomas. At first I thought it was something
particular to my application but I created a basic starter project and
it doesn't show the SplitPanelLayout with the super basic example
below. Oddly enough if you change the CSS position of the
SplitLayoutPanel element to static then it shows just fine with the
caveat that, although corner dragged resizes are handled okay, bottom
edge draggged resizes don't update the HeaderPanel's layout.




 header 




 Navbar 



 Stuff 




 footer 



On 31 August 2011 15:57, Thomas Broyer  wrote:
>
> On Wednesday, August 31, 2011 9:18:22 AM UTC+2, James Horsley wrote:
>>
>> Would love to have the naturally resizing header and footer but to
>> then add a SplitLayoutPanel as the center. Doing so causes nothing to
>> show which I'm guess is due to HeaderPanel not being a LayoutPanel?
>
> HeaderPanel is a RequiresResize, and if you look at its source, you'll see
> that it'll call onResize on its content widget if it's a RequiresResize too.
> I guess the reason HeaderPanel doesn't implement ProvidesResize is because
> it doesn't implement the behavior for the header and footer.
> This does however make it a "layout panel".
> In other words: it should work. (and I have no idea why it doesn't)
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-web-toolkit/-/Kpd-yKfZSuIJ.
> 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.
>

-- 
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.

HeaderLayoutPanel?

[James Horsley]

Would love to have the naturally resizing header and footer but to
then add a SplitLayoutPanel as the center. Doing so causes nothing to
show which I'm guess is due to HeaderPanel not being a LayoutPanel?

Any plans for a HeaderLayoutPanel?

Cheers,
James

-- 
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.