Re: Recent touch issues on mobiles?

[Bruno Salmon]

Please ignore my post, the problem was my underlying framework that was 
wrongly consuming touch events in some cases, sorry...

On Friday, 1 September 2023 at 14:59:21 UTC+1 Bruno Salmon wrote:

> hi,
>
> I noticed that some of my GWT demos are not reacting to some touch events 
> anymore on mobiles (I haven't tried on desktops as I don't have a touch 
> screen).
>
> For example, this demo reacts correctly to the first tap, but then the 
> sliders are not reacting to touch events anymore: 
> https://moderngauge.webfx.dev
>
> In this one, the game is working fine with touch events but not the links 
> on the info page: https://fx2048.webfx.dev
>
> In this one, the "Choose files" button has also stopped reacting to touch 
> events: https://files.webfx.dev
>
> I'm sure these issues didn't exist a few of month ago, and I haven't made 
> any change...
>
> Are you aware of recent changes to the mobile browser sandbox that may 
> affect touch events on GWT apps?
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/2ede0d20-1362-40d2-9f77-1d6e1e7a942an%40googlegroups.com.

Recent touch issues on mobiles?

[Bruno Salmon]

hi,

I noticed that some of my GWT demos are not reacting to some touch events 
anymore on mobiles (I haven't tried on desktops as I don't have a touch 
screen).

For example, this demo reacts correctly to the first tap, but then the 
sliders are not reacting to touch events 
anymore: https://moderngauge.webfx.dev

In this one, the game is working fine with touch events but not the links 
on the info page: https://fx2048.webfx.dev

In this one, the "Choose files" button has also stopped reacting to touch 
events: https://files.webfx.dev

I'm sure these issues didn't exist a few of month ago, and I haven't made 
any change...

Are you aware of recent changes to the mobile browser sandbox that may 
affect touch events on GWT apps?

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/8a26d03c-289b-4ec2-93ce-a7a2eaa21923n%40googlegroups.com.

Re: Partial super source? Possible?

[Bruno Salmon]

Thanks Thomas. By "shadow" I was actually quoting you when you said: 

you cannot "augment" it, but you can "shadow" it by providing your own 
super-source version of java.lang.String


In my previous reply, I was saying that I'm happy with this solution for my 
GWT app (whatever you call this method "shadow" or something else).

But my concern is now with J2CL (as I plan to move my GWT app to J2CL in 
the future).
I would like to know if this solution will also work with J2CL.
i.e. will I be able to provide my own implementation of String.format() if 
not emulated by J2CL?

On Tuesday, 25 July 2023 at 15:20:19 UTC+1 Thomas Broyer wrote:

On Tuesday, July 25, 2023 at 2:26:14 PM UTC+2 Bruno Salmon wrote:

The shadow super-source should work in my case, thank you.

 If later I want to move from GWT to J2CL, will I have a similar feature 
(ex: providing my own implementation of String.format() if not emulated) ?


IIRC, no: each source file must only appear once, so you cannot use 
shadowing.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/cd1e2396-afe8-47b6-8b37-5a5ca4459eb6n%40googlegroups.com.

Re: Partial super source? Possible?

[Bruno Salmon]

The shadow super-source should work in my case, thank you.

 If later I want to move from GWT to J2CL, will I have a similar feature 
(ex: providing my own implementation of String.format() if not emulated) ?

On Friday, 21 July 2023 at 16:34:23 UTC+1 Colin Alworth wrote:

> I don't use String.format() a lot, even in the normal JVM, but based on 
> the Javadoc it looks like we could add the format method, and delegate to a 
> java.util.Formatter, but then leave that unimplemented by default. Then, 
> downstream applications could more easily add that, without having to worry 
> about keeping the rest of String.java up to date? 
>
> Note also when trying to do anything beyond simple %s replacement, the 
> java.util.Locale type exists in GWT emulation, but offers no instance 
> methods outside of toString.
>
>
> https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object..
> .)
>
> https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/util/Formatter.html
>
> https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/util/Locale.html
>
>
> On Friday, July 21, 2023 at 4:38:24 AM UTC-5 Thomas Broyer wrote:
>
>> GWT standard emulation is "just" super-source itself. You cannot 
>> "augment" it, but you can "shadow" it by providing your own super-source 
>> version of java.lang.String (copy from GWT and patch; and make sure it 
>> appears before GWT's emulation in the source path – i.e. IIRC make sure the 
>>  comes before any  that would bring 
>> com.google.gwt.emul.Emulation). This means you'll have to update your 
>> version whenever GWT updates its own.
>> But only ever do this for an application, never for a library!
>>
>> On Thursday, July 20, 2023 at 1:46:15 PM UTC+2 Bruno Salmon wrote:
>>
>>> hi,
>>>
>>> If GWT emulates a Java class but not all methods, is it possible to 
>>> provide a complement as a super source?
>>>
>>> For example, can I provide a super source for String.format() while 
>>> keeping other String methods emulated by GWT?
>>>
>>> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/e9c73b85-e300-4b69-ac27-abaa66fbe865n%40googlegroups.com.

Partial super source? Possible?

[Bruno Salmon]

hi,

If GWT emulates a Java class but not all methods, is it possible to provide 
a complement as a super source?

For example, can I provide a super source for String.format() while keeping 
other String methods emulated by GWT?

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/7c05e220-edc7-4d5e-b95a-a6f3d36246d8n%40googlegroups.com.

Re: JavaFX for GWT

[Bruno Salmon]

Yes, we will provide server communications features soon, because the 
project is actually not "just" about the JavaFX API, but also about a whole 
ecosystem around it, so people can do Enterprise-level development.

To start with, we are working on the Web Fetch API emulation (that works 
cross-platform), which will allow you to request web services. More info 
about that can be found in this GitHub discussion 
<https://github.com/webfx-project/webfx/discussions/15>.

We are also working on a cross-platform WebSocket API, which will be 
published in a second step after the Fetch API.

And finally on top of WebSocket, we will publish a cross-platform EventBus 
API, with a server-side implementation for Vert.x (we will probably do a 
SpringBoot implementation as well, but later).
Vert.x is prioritised because Modality (the Enterprise app we are talking 
about in our README) is using Vert.x.


On Wednesday, 9 November 2022 at 19:02:18 UTC eliasbala...@gmail.com wrote:

> This is quite an interesting approach, I am intrigued.
>
> Some remoting capabilities could be useful though.
> I know a few standalone apps (Swing, SWT, JavaFX etc.) that rely on server 
> communications.
>
> Perhaps custom communication layers for various protocols and transports 
> could be added by contributors.
>
> On Wednesday, 9 November 2022 at 14:58:42 UTC Bruno Salmon wrote:
>
>> hi Jonathan,
>>
>> Unfortunately for your project, I have no plan to support Swing as 
>> covering JavaFX is already a big job.
>>
>> If you are looking for a solution to run your app without a server like 
>> WebFX does, I don't think that exists for Swing.
>>
>> But if you don't mind having a server, there are solutions like WebSwing 
>> that can run your app on a server, and then you can have a kind of remote 
>> desktop of it in the browser. 
>>
>> On Wednesday, 9 November 2022 at 12:39:48 UTC Jonathan Franchesco Torres 
>> Bca wrote:
>>
>>> Hi,
>>>
>>> And what about JFC Swing which is interoperable with JavaFX.
>>> I have a desktop application that mixes both and we use substance to 
>>> improve the display of the controls
>>> I leave an example
>>> [image: image.png]
>>>
>>>  
>>>
>>>  * <https://www.facebook.com/KiongoCompany>  
>>> <https://www.linkedin.com/company/kiongo-inc>   
>>> <https://www.youtube.com/channel/UC1HKa8IPofVRmeAFZ22m3HQ> *
>>>
>>> Jonathan Franchesco Torres Baca(@jofrantoba)
>>>
>>> CIO - Kiongo Technology
>>>
>>> *Jr Juan Voto Bernales 344 - La Victoria, Lima - Perú*
>>>
>>> Teléfono   *+5116357857 <+51%201%206357857>*
>>>
>>> Cel.+51929913524 <+51%20929%20913%20524>
>>>
>>>
>>> El mar, 8 nov 2022 a las 9:38, Bruno Salmon () 
>>> escribió:
>>>
>>>> Hi,
>>>>
>>>> I'm working on a JavaFX transpiler powered by GWT.
>>>> It lets you use JavaFX as a UI toolkit in your GWT apps.
>>>> The JavaFX API is far from completely covered, but you can already see 
>>>> some interesting results.
>>>>
>>>> The project is on GitHub for those who are interested.
>>>> https://github.com/webfx-project/webfx
>>>>
>>>> If you have any questions, please let me know.
>>>>
>>>> -- 
>>>>
>>> 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-tool...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/google-web-toolkit/8210a6a2-ad1a-4b2d-ba68-19dcc5fbeef3n%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/google-web-toolkit/8210a6a2-ad1a-4b2d-ba68-19dcc5fbeef3n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/628df0ef-c57b-49a5-98ce-fc1820ede45dn%40googlegroups.com.

Re: JavaFX for GWT

[Bruno Salmon]

hi Jonathan,

Unfortunately for your project, I have no plan to support Swing as covering 
JavaFX is already a big job.

If you are looking for a solution to run your app without a server like 
WebFX does, I don't think that exists for Swing.

But if you don't mind having a server, there are solutions like WebSwing 
that can run your app on a server, and then you can have a kind of remote 
desktop of it in the browser. 

On Wednesday, 9 November 2022 at 12:39:48 UTC Jonathan Franchesco Torres 
Bca wrote:

> Hi,
>
> And what about JFC Swing which is interoperable with JavaFX.
> I have a desktop application that mixes both and we use substance to 
> improve the display of the controls
> I leave an example
> [image: image.png]
>
>  
>
>  * <https://www.facebook.com/KiongoCompany>  
> <https://www.linkedin.com/company/kiongo-inc>   
> <https://www.youtube.com/channel/UC1HKa8IPofVRmeAFZ22m3HQ> *
>
> Jonathan Franchesco Torres Baca(@jofrantoba)
>
> CIO - Kiongo Technology
>
> *Jr Juan Voto Bernales 344 - La Victoria, Lima - Perú*
>
> Teléfono   *+5116357857 <+51%201%206357857>*
>
> Cel.+51929913524 <+51%20929%20913%20524>
>
>
> El mar, 8 nov 2022 a las 9:38, Bruno Salmon () 
> escribió:
>
>> Hi,
>>
>> I'm working on a JavaFX transpiler powered by GWT.
>> It lets you use JavaFX as a UI toolkit in your GWT apps.
>> The JavaFX API is far from completely covered, but you can already see 
>> some interesting results.
>>
>> The project is on GitHub for those who are interested.
>> https://github.com/webfx-project/webfx
>>
>> If you have any questions, please let me know.
>>
>> -- 
>>
> 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-tool...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit/8210a6a2-ad1a-4b2d-ba68-19dcc5fbeef3n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/google-web-toolkit/8210a6a2-ad1a-4b2d-ba68-19dcc5fbeef3n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/4a35b72f-a665-4107-848b-a331eafd17a6n%40googlegroups.com.

JavaFX for GWT

[Bruno Salmon]

Hi,

I'm working on a JavaFX transpiler powered by GWT.
It lets you use JavaFX as a UI toolkit in your GWT apps.
The JavaFX API is far from completely covered, but you can already see some 
interesting results.

The project is on GitHub for those who are interested.
https://github.com/webfx-project/webfx

If you have any questions, please let me know.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/8210a6a2-ad1a-4b2d-ba68-19dcc5fbeef3n%40googlegroups.com.

Re: Is it possible to implement a web worker with GWT?

[Bruno Salmon]

Thank you both for your inputs.

Yes the gwt-worker is the linker I was looking for :)

However the produced JS file breaks because it still contains some 
references to the window object which doesn't exist in the context of a web 
worker.

Is there an option in the GWT compiler to tell that the context is a web 
worker and that it should not use such objects but "self" instead?

Otherwise I noticed the linker already produces some patch code before 
calling GWT, the first JS line looks like this:
$stats=function(){};$self=self;$wnd=self;$doc=self;$sessionId=null; etc...

Manually adding window=self; in that line actually solves the JS break 
issue.

In the probable case GWT has not been designed for web workers and we can't 
prevent it producing code without refering to window, I will open an issue 
in the gwt-worker linker repository to ask adding window=self; in the patch 
line. 


On Friday, 2 October 2020 at 17:14:03 UTC+1 lofid...@gmail.com wrote:

> I'm not sure, will this project helps you: 
> https://gitlab.com/ManfredTremmel/gwt-webworker?
>
> t.br...@gmail.com schrieb am Freitag, 2. Oktober 2020 um 17:04:55 UTC+2:
>
>> It is, through a linker: 
>> http://www.gwtproject.org/doc/latest/DevGuideLinkers.html
>> It might work with the D8ScriptLinker shipped in GWT (
>> https://github.com/gwtproject/gwt/blob/2.9.0/dev/core/src/com/google/gwt/core/linker/D8ScriptLinker.java);
>>  
>> you'll have to declare it in a *.gwt.xml though (define-linker then 
>> add-linker).
>> Or there might be (IIRC, there are) libraries with such a linker 
>> specifically for workers.
>>
>>
>> On Thursday, October 1, 2020 at 10:43:37 PM UTC+2, Bruno Salmon wrote:
>>>
>>> hi,
>>>
>>> I have a GWT web app that I would like to make more reactive by moving 
>>> some heavy computation code into web workers. This code doesn't need the 
>>> context of the application to run, I just need to pass it a few input 
>>> parameters so it should be a good fit for a web worker.
>>>
>>> I see how the web app can instantiate web workers 
>>> using elemental2.dom.Worker.
>>>
>>> But as my worker code is in Java, I would like to know if I can use the 
>>> GWT compiler to generate the worker itself. I expect a js file with a 
>>> onmessage function as output that I can load from the web app.
>>>
>>> Is it possible to do this?
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/26a5afff-b155-4c03-9825-451a0c92d463n%40googlegroups.com.

Is it possible to implement a web worker with GWT?

[Bruno Salmon]

hi,

I have a GWT web app that I would like to make more reactive by moving some 
heavy computation code into web workers. This code doesn't need the context 
of the application to run, I just need to pass it a few input parameters so 
it should be a good fit for a web worker.

I see how the web app can instantiate web workers 
using elemental2.dom.Worker.

But as my worker code is in Java, I would like to know if I can use the GWT 
compiler to generate the worker itself. I expect a js file with a onmessage 
function as output that I can load from the web app.

Is it possible to do this?

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/4202749b-6b5d-4938-8dd0-798bb6fccfedn%40googlegroups.com.

Re: [ANN] JRS gwt-time 1.4.10 release

[Bruno Salmon]

Hi Stas,

Thanks for providing this java.time GWT emulation module.

I'm gettiing GWT compilation errors in this last version.

So I opened an issue for this: https://github.com/foal/gwt-time/issues/2

Thank you!

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/fee3f090-6afa-48fe-b46e-2a787bd7a7a1%40googlegroups.com.

Re: How to pass a build number to a gwt app?

[Bruno Salmon]

Thanks Thomas, I'm using GWT 2.8.2 so I tried your first suggestion and it 
works :-)

I just declared the property in my gwt.xml module file:




 and set its value (with the maven property which is set by Jenkins) when 
calling your plugin in the configuation section: 



-setProperty
build.number=${build.number}




Then System.getProperty("build.number") returns the expected value :-)

Thank you

On Monday, 12 March 2018 23:27:17 UTC+1, Thomas Broyer wrote:
>
> Easiest with recent GWT version would be to declare a 
> , get it using System.getProperty(), and set it 
> with --property.
>
> With older versions, use Maven filtering on a properties file you use with 
> a com.google.gwt.i18n.client.Constants; or have a look at Mojo's Java 
> template plugin.
>

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

How to pass a build number to a gwt app?

[Bruno Salmon]

hi,

I would like my gwt app to be able to identify its version itself, by 
providing a method that returns the build number.

I'm using Jenkins, maven and the maven plugin for gwt 
 to build my app. Jenkins 
generates the build number and I know how to pass that build number to 
maven (using a build.number maven property), but I don't know how I can 
pass that build.number to the GWT compiler and how to code that method in 
my java source so it returns that build number.

Any idea how I can do that?

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

Re: How to debug a crash that occurs only when draftCompile=false?

[Bruno Salmon]

Thank you Vassilis, I didn't know about that option and this definitely 
helped me to identify and fix the problem.

I think the crash came from a GWT compiler bug but I found a workaround as 
explained below (I'm sharing in case this can help others).

That -style DETAILED compiler option is not as comfortable as the super dev 
mode but I could indeed at least recognize my java code within the 
javascript call stack, except for the very last call (the one causing the 
crash) which had actually nothing to do with the java caller code! GWT 
strangely jumped without explanation into a lambda expression that comes 
from another method of the same java class (perhaps with 
draftCompile=false, GWT tries to make some piece of code factorization 
including lambda expressions?). Anyway this lambda expression was 
translated into a javascript function that was called from 2 different 
places in the JS code whereas it is actually used only once in my java 
code, and that second place was in the caller code which was a complete 
compilation mistake. Hopefully when I rewrote my lamda expression using the 
old java 7 style in my java source code, GWT stopped doing that compilation 
mistake, so my app crash is now fixed :-)

Thanks for you help


Le lundi 5 mars 2018 22:03:36 UTC+1, Vassilis Virvilis a écrit :
>
> I would try to compile with -style DETAILED
>
> The generated js maps pretty well to the java code.
>
> Vassilis
>
> On Mon, Mar 5, 2018 at 5:52 PM, Bruno Salmon  > wrote:
>
>> hi,
>>
>> I have a GWT application that runs ok when draftCompile=false but crashes 
>> when turning draftCompile to true (which is the case in production).
>>
>> How can I fix that? Can it be related to something wrong in my java code 
>> source?
>>
>> The browser reports an exception (a classical property access problem on 
>> an undefined object) and I have the exact JS line where this happens, but 
>> it's not helpful if I can't match this line with my java code.
>> The problem is that when I run the app in super dev mode to get the 
>> source maps, the crash doesn't occur anymore... Is it because the code 
>> server automatically make a draft compile ? Can we avoid that to get the 
>> same result as the production environment?
>>
>> 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-we...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/google-web-toolkit.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Vassilis Virvilis
>

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

How to debug a crash that occurs only when draftCompile=false?

[Bruno Salmon]

hi,

I have a GWT application that runs ok when draftCompile=false but crashes 
when turning draftCompile to true (which is the case in production).

How can I fix that? Can it be related to something wrong in my java code 
source?

The browser reports an exception (a classical property access problem on an 
undefined object) and I have the exact JS line where this happens, but it's 
not helpful if I can't match this line with my java code.
The problem is that when I run the app in super dev mode to get the source 
maps, the crash doesn't occur anymore... Is it because the code server 
automatically make a draft compile ? Can we avoid that to get the same 
result as the production environment?

Thanks

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

Re: Elemental2 RC1: RegExp disappeared?

[Bruno Salmon]

I had'nt noticed indeed, thanks for this clarification

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

Elemental2 RC1: RegExp disappeared?

[Bruno Salmon]

hi,

I would like to upgrade to the latest Elemental2 version (RC1) but I can't 
find RegExp anymore in the core library.

Any idea where it has gone?

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.

Problem writing module-info.java for gwt modules using jsinterop

[Bruno Salmon]

hi,

I'm moving a maven java/gwt multi-modules project to java 9 and would like 
to write module-info.java files also for gwt modules (why not?).

I'm using GWT 2.8.2. Since it doesn't provide java 9 modules info, I need 
to rely on automatic module names. I wrote my module-info.java as follow:

module my.gwt.module {
...
requires gwt.user; // works
requires jsinterop.annotations; // doesn't work
...
}

The java 9 compiler accepts this file without complaining (no "module not 
found" error so I guess it finds the modules). And it successfully compiles 
java files that only uses gwt.user. But compiling java files also using 
jsinterop fails with the following error:

package jsinterop.annotations is not visible
(package jsinterop.annotations is declared in the unnamed module, but module 
jsinterop.annotations does not read it)

Any idea why?

I found a workaround by adding a dependency to the jsinterop head snapshot 
in my pom (also declared the google snapshot repository):


 com.google.jsinterop
 jsinterop-annotations
 HEAD-SNAPSHOT


and changing my module info to:


module my.gwt.module {
...
requires gwt.user; // works
requires jsinterop.annotations.HEAD.SNAPSHOT; // works
...
}

Then the java 9 compiler successfully compiles java files using jsinterop. But 
I would prefer not doing this.


Any better solution?

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

[Bruno Salmon]

>
> Additionally, this supports the recent beta release of jsinterop.base and 
> elemental2, available from Maven Central.
>
>
>
Where can we find that elemental2  beta release (I can see only the June 
2016 version on that page 

)?

Thanks for all your amazing work.

-- 
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: Strippable check system in GWT 2.8?

[Bruno Salmon]

Thank you Thomas,  in my gwt.xml file works :-)

On Friday, 3 February 2017 13:47:57 UTC+1, Thomas Broyer wrote:
>
> This is 
> https://github.com/gwtproject/gwt/blob/2.8.0/user/super/com/google/gwt/emul/javaemul/internal/InternalPreconditions.java
> The javadoc and first few lines of the class tells it all (note that 
> System.getProperty is the emulated one here, so the properties are from 
> your gwt.xml files, not the JVM System properties when calling the GWT 
> compiler)
> FWIW, the properties (and their default value) are defined in 
> https://github.com/gwtproject/gwt/blob/2.8.0/user/super/com/google/gwt/emul/Preconditions.gwt.xml
>
> On Friday, February 3, 2017 at 12:47:00 PM UTC+1, Bruno Salmon wrote:
>>
>> hi,
>>
>> I heard that the GWT 2.8 check system is strippable (source: 
>> https://www.youtube.com/watch?v=P4VhPck5s_g&t=1337s).
>>
>> By defaut the check level would be normal, which means that the generated 
>> js code will do all checks (such as collections bounds checks, API usage 
>> checks, java type checks, ...). But if we are confident that the 
>> application successfully passes all checks, it seems possible to reduce 
>> that check level from normal to optimized or minimal and get a smaller and 
>> faster compiled production code.
>>
>> I haven't found any documentation about this feature, not sure it is 
>> actually documented.
>>
>> Does anybody know how to tell the GWT compiler to change that check level?
>>
>

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

Strippable check system in GWT 2.8?

[Bruno Salmon]

hi,

I heard that the GWT 2.8 check system is strippable 
(source: https://www.youtube.com/watch?v=P4VhPck5s_g&t=1337s).

By defaut the check level would be normal, which means that the generated 
js code will do all checks (such as collections bounds checks, API usage 
checks, java type checks, ...). But if we are confident that the 
application successfully passes all checks, it seems possible to reduce 
that check level from normal to optimized or minimal and get a smaller and 
faster compiled production code.

I haven't found any documentation about this feature, not sure it is 
actually documented.

Does anybody know how to tell the GWT compiler to change that check level?

-- 
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: My GWT 2.8 app stopped working with Chrome 54 (timers not working anymore)

[Bruno Salmon]

No I just remove all elements under  except the 

Re: My GWT 2.8 app stopped working with Chrome 54 (timers not working anymore)

[Bruno Salmon]

I found the problem, so I'm sharing the result of my investigation as this 
may help other people facing a similar issue with Chrome 54+ or other 
webkit based browsers:

My app replaces the document  (which initially contains a splash 
screen) with the application root element once loaded and initialized. This 
replacement removed all previous elements under the  tag which were 
actually not only the splash screen but also the  tags (this was 
considered a best practice to put them here - not sure if this is still the 
case with http2).

Anyway removing the scripts tags once the application was loaded in memory 
didn't cause any problem up to Chrome 54 and the application could continue 
working as the scripts were already resident in memory.

But from Chrome 54 this is not the case anymore: it seems removing the 
script elements now immediately removes the resident application from the 
memory as well.

This is what caused my app stop working and even my timers programmed in 
the initialization step were finally not called after the scripts tags have 
been removed...


On Thursday, 27 October 2016 13:17:35 UTC+2, Bruno Salmon wrote:
>
> hi,
>
> My Chrome updated yesterday from version 53 to 54 and this made my GWT 2.8 
> app stop working.
>
> There is no error message in the console but after some investigation, I 
> noticed that the problem come from the timers which are not called anymore 
> (whatever the method: GWT Timer / Elemental2 / JSNI). It's like 
> setTimeout() doesn't work anymore in the browser (and this is what freezes 
> my app).
>
> However if I write a simple GWT 2.8 app whose code is just a timer 
> invocation, it works in Chrome 54...
>
> The timers stop working only when I invoke my application logic (a quite 
> big app). So it looks like something breaks the timers in the compiled 
> javascript code, but I don't know how to investigate further (as the whole 
> application logic run without error).
>
> My app works fine in FireFox.
>
> Any idea what's happening?
>
>

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

My GWT 2.8 app stopped working with Chrome 54 (timers not working anymore)

[Bruno Salmon]

hi,

My Chrome updated yesterday from version 53 to 54 and this made my GWT 2.8 
app stop working.

There is no error message in the console but after some investigation, I 
noticed that the problem come from the timers which are not called anymore 
(whatever the method: GWT Timer / Elemental2 / JSNI). It's like 
setTimeout() doesn't work anymore in the browser (and this is what freezes 
my app).

However if I write a simple GWT 2.8 app whose code is just a timer 
invocation, it works in Chrome 54...

The timers stop working only when I invoke my application logic (a quite 
big app). So it looks like something breaks the timers in the compiled 
javascript code, but I don't know how to investigate further (as the whole 
application logic run without error).

My app works fine in FireFox.

Any idea what's happening?

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

Latest version of Elemental2?

[Bruno Salmon]

hi,

I would like to know if the last version of Elemental2 is still 16-06-30 or 
if there is a more recent release.

I'm asking because I'm getting the following compilation error with 
16-06-30 while trying to use the SVG API:

[INFO]Errors in elemental2/SVGSVGElement.java
[INFO]   [ERROR] Line 222: JsProperty setter 'void 
SVGSVGElement.setStyle(Object)' and getter 'String[] 
SVGSVGElement.getStyleAsStringArray()' cannot have inconsistent types.
[INFO]   [ERROR] Line 225: JsProperty setter 'void 
SVGSVGElement.setStyle(Object)' and getter 'CSSStyleDeclaration 
SVGSVGElement.getStyleAsCSSStyleDeclaration()' cannot have inconsistent 
types.
[INFO]Errors in elemental2/SVGStylable.java
[INFO]   [ERROR] Line 46: JsProperty setter 'void 
SVGStylable.setStyle(Object)' and getter 'String[] 
SVGStylable.getStyleAsStringArray()' cannot have inconsistent types.
[INFO]   [ERROR] Line 49: JsProperty setter 'void 
SVGStylable.setStyle(Object)' and getter 'CSSStyleDeclaration 
SVGStylable.getStyleAsCSSStyleDeclaration()' cannot have inconsistent types.

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.

Public and war folders in the maven project layout (tbroyer plugin)?

[Bruno Salmon]

Hi,

The GWT documentation 

 
describes the project layout using Eclipse, but I have a couple of 
questions when transposing it into the maven project layout (using the 
tbroyer plugin):

- where is the public folder located in the maven project layout? I tried 
different places (such as src/public, src/main/public, 
src/main/resources/public) but it was never found by the compiler

- where can I put my host page and other html/css sources files? The 
documentation talks about the war folder, but this directory seems to be 
the webappDirectory in the tbroyer plugn, so it's a an output directory 
under the target folder which is not a good place for sources files (they 
are erased with maven clean).

Thanks

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

Re: How to declare standard java libraries dependencies to the GWT compiler with the tbroyer maven plugin?

[Bruno Salmon]

Thanks Ignacio, I understood your plugin won't disappear but as I'm 
upgrading a project to the future GWT way (removing widgets, using 
elemental, etc...), it's the opportunity to include this migration as well.

Thanks Thomas, I was focusing on the plugin goals pages and didn't notice 
the answer was in the introduction page! Sorry...

Now the GWT compilation works :-)

Just a couple of questions:

- my GWT app is part of a mutli maven modules project (and some are GWT 
modules) but although the plugin seems to analyse the GWT app dependencies, 
I need to declare all these sources in the app pom. It doesn't work if I 
declare them in the dependent modules. So it's a long flat list of all 
sources directly or indirectly used by the dependent modules. It's a bit 
hard to maintain that long list here. I would have preferred to be able to 
declare these sources dependencies just besides the binary dependencies 
(binary / sources pair) in the different modules poms. Or perhaps it should 
work but I'm doing something wrong? 

- I haven't found where to put the html host page and other static web 
resources in the project layout (I suspect somewhere under 
src/main/resources/) so the gwt-app packaging include them in the final war 
artifact.


Le samedi 27 août 2016 09:53:07 UTC+2, Ignacio Baca Moreno-Torres a écrit :
>
> I updated the 'deprecation notice', deprecation is a strong word and 
> people get scared that the plugin is going to disappear. But the idea is 
> the same, you should migrate if you can, so thanks Bruno Salmon to try it 
> out!
>
> On Friday, August 26, 2016 at 4:51:21 PM UTC+2, Thomas Broyer wrote:
>>
>>
>>
>> On Friday, August 26, 2016 at 3:36:52 PM UTC+2, Bruno Salmon wrote:
>>>
>>> hi,
>>>
>>> Having read the deprecation notice 
>>> <https://github.com/gwt-maven-plugin/gwt-maven-plugin/issues/137>, I'm 
>>> trying to move from the mojo plugin to the new recommended plugin, the one 
>>> written by Thomas.
>>>
>>> But I'm facing this problem: my GWT application uses some java libraries 
>>> (standard jar packaging but with GWT compatible sources), however the GWT 
>>> compiler can't find these sources although I have listed these libraries in 
>>> the application pom:
>>>
>>> 
>>> lib1-groupId
>>> lib1-artifactId
>>> lib1-version
>>> 
>>> 
>>> lib2-groupId
>>> lib2-artifactId
>>> lib2-version
>>> 
>>> ...
>>>
>>> With the mojo plugin already it was not enough to just declare their 
>>> dependencies in the pom, I had to declare them a second time in the 
>>> compileSourceArtifacts section of the plugin configuration, like this:
>>>
>>> 
>>> ...
>>> 
>>> lib1-groupId:lib1-artifactId
>>> 
>>> lib2-groupId:lib2-artifactId
>>> 
>>> ...
>>> 
>>> 
>>>
>>> and then the GWT compiler could find the sources of these libraries and 
>>> include them for the application compilation.
>>>
>>> I haven't seen the equivalent with the tbroyer plugin.
>>> Anybody knows how to do it?
>>>
>>
>> Add dependencies to the source artifacts in addition to the "binary" ones:
>>
>> 
>> lib1-groupId
>> lib1-artifactId
>> lib1-version
>> sources
>> 
>> 
>> lib2-groupId
>> lib2-artifactId
>> lib2-version
>> sources
>> 
>> ...
>>
>> See the description of the different kind of dependencies in the home 
>> page: https://tbroyer.github.io/gwt-maven-plugin/
>>
>

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

How to declare standard java libraries dependencies to the GWT compiler with the tbroyer maven plugin?

[Bruno Salmon]

hi,

Having read the deprecation notice 
, I'm 
trying to move from the mojo plugin to the new recommended plugin, the one 
written by Thomas.

But I'm facing this problem: my GWT application uses some java libraries 
(standard jar packaging but with GWT compatible sources), however the GWT 
compiler can't find these sources although I have listed these libraries in 
the application pom:


lib1-groupId
lib1-artifactId
lib1-version


lib2-groupId
lib2-artifactId
lib2-version

...

With the mojo plugin already it was not enough to just declare their 
dependencies in the pom, I had to declare them a second time in the 
compileSourceArtifacts section of the plugin configuration, like this:


...

lib1-groupId:lib1-artifactId

lib2-groupId:lib2-artifactId

...



and then the GWT compiler could find the sources of these libraries and 
include them for the application compilation.

I haven't seen the equivalent with the tbroyer plugin.
Anybody knows how to do it?

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To 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: Are there already some JSInterop repositories available somewhere?

[Bruno Salmon]

There is still a big difference between JSweet and GWT because although 
JSweet supports Java 8 syntax, it doesn't do any JRE emulation. So JSweet 
is much simpler and it can be a good choice if you just want to write your 
JS code from Java (with all the advantage provided by your Java IDE like 
auto completion, refactoring, etc...) and if you don't need to refer to any 
JRE class (List, Map, etc...) in your code. With JSweet your code is only a 
Java (better) view of your JS code. But if you want to use the JRE 
emulation or share some Java code between your frontend and your backend 
(client and/or server), JSweet can't do it whereas GWT can.

The candies are a big advantage of JSweet but yes GWT will soon fill the 
gap and offer exactly the same so, as you said, it's really cool.

My understanding is that JsInterop.xyz is not hand crafted and has a 
generator. But it is an individual initiative (and not sure it is still 
active) whereas Elemental2 and its generator are more official (and active) 
parts of the GWT project.

It seems we don't know yet exactly when the Elemental2 generator will be 
out. Very exciting stuff but let's be patient first...


On Wednesday, 24 August 2016 13:37:03 UTC+2, Vassilis Virvilis wrote:
>
> Bruno thanks for the links. I didn't know about jsweet and jsinterop.xyz.
>
> It would be really cool if GWT could tap on all of these js libraries 
> (candies) offered by jsweet. Then of course the differences between GWT and 
> jsweet become hard to see.
>
> jsinterop.xyz is of also interesting. Isn't this the same thing as 
> elemental2 - DOM and window APis are exposed via jsinterop - what's the 
> difference?
> The only difference I can spot is the fact that jsinterop.xyz looks like 
> hand crafted as opposed to the automated elementa2.
>
> Vassilis
>
> On Tue, Aug 23, 2016 at 10:26 PM, Bruno Salmon  > wrote:
>
>> I didn't know there was a DefinitelyTyped to JSInterop generator project 
>> in the pipeline, glad to hear about it, it's exactly what I was looking for 
>> :-)
>>
>> Thank you. 
>>
>>
>> On Tuesday, 23 August 2016 19:16:19 UTC+2, Jens wrote:
>>>
>>> A post from the thread I linked before:
>>>
>>>
>>> https://groups.google.com/d/msg/google-web-toolkit-contributors/6ycG2nm0OSM/mUP-GnJ0EAAJ
>>>
>>> So once the elemental2 generator is open source and supports typescript 
>>> definition files, you should be able to use everything that 
>>> https://github.com/DefinitelyTyped/DefinitelyTyped 
>>> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2FDefinitelyTyped%2FDefinitelyTyped&sa=D&sntz=1&usg=AFQjCNG8L2YKJ-TMsAeDcXyfftPT7GgQBw>
>>>  
>>> provides (which is what JSweet also uses)
>>>
>>> For the time being there is no such generator, you would need to write 
>>> the bindings yourself. Also the author of jsinterop.xyz has not 
>>> published its generator (at least not at the time I looked at it).
>>>
>>> -- 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-we...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/google-web-toolkit.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Vassilis Virvilis
>

-- 
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: Are there already some JSInterop repositories available somewhere?

[Bruno Salmon]

I didn't know there was a DefinitelyTyped to JSInterop generator project in 
the pipeline, glad to hear about it, it's exactly what I was looking for :-)

Thank you. 


On Tuesday, 23 August 2016 19:16:19 UTC+2, Jens wrote:
>
> A post from the thread I linked before:
>
>
> https://groups.google.com/d/msg/google-web-toolkit-contributors/6ycG2nm0OSM/mUP-GnJ0EAAJ
>
> So once the elemental2 generator is open source and supports typescript 
> definition files, you should be able to use everything that 
> https://github.com/DefinitelyTyped/DefinitelyTyped 
> 
>  
> provides (which is what JSweet also uses)
>
> For the time being there is no such generator, you would need to write the 
> bindings yourself. Also the author of jsinterop.xyz has not published its 
> generator (at least not at the time I looked at it).
>
> -- 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.

Re: Are there already some JSInterop repositories available somewhere?

[Bruno Salmon]

Thanks but Elemental only gives the basics (such as the DOM API and some 
HTML5 features). I'm more asking about a project that would expose many JS 
libraries.

A kind of set like this one  
offered by JSweet.

I would like for example use the pixi.js graphical library in a GWT project 
without having to rewrite myself the whole pixi API in JSInterop.


On Tuesday, 23 August 2016 17:55:16 UTC+2, Jens wrote:
>
> Take a look at Elemental 2: 
> https://groups.google.com/d/msg/google-web-toolkit-contributors/6ycG2nm0OSM/RW3psRrqAAAJ
>
> Its experimental but covers all browser APIs (auto generated from closure 
> externs: https://github.com/google/closure-compiler/tree/master/externs). 
> Its the JsInterop version of Elemental 1.0 that is part of GWT SDK.
>
> -- 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.

Are there already some JSInterop repositories available somewhere?

[Bruno Salmon]

hi,

I haven't used JSInterop yet but in all examples I watched, people are 
writing all their interfaces themselves including the DOM API...

I guess this is a temporary situation because JSInterop is new and that 
some JSInterop repositories will appear in the future so we will have most 
of JS libraries API automatically ported into JSInterop. This step will 
really open GWT to the whole JS ecosystem. It would be great to have 
something similar to what JSweet 
 did with more than 1000 
well-typed JavaScript libraries available.

Does anybody know if this is part of the GWT project itself or if the idea 
is to delegete this job to some other third-party projects?

Do some such projects already exist? I found a project called JsInterop.xyz 
 that started in that direction but 
it doesn't seem to be active.

Any info about this?
Thanks

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

Re: Runtime error when switching a GWT Polymer Elements project from 2.8.0-beta1 to 2.8.0-rc1/rc2

[Bruno Salmon]

I mainly wanted to check if it was a GWT issue and it seems from what you 
say it's rather a gwt-polymer-elements issue.

I'm happy to stay with beta1 until this gwt-polymer-elements issue is 
resolved (I will open the issue once GWT 2.8.0 will be out).

Thanks

On Friday, 12 August 2016 17:26:57 UTC+2, Kristofer Blom wrote:
>
> We had this problem too. I built a new version of the library from current 
> source (instructions here ), 
> and that resolved at least that particular issue. The generated jar file 
> has 1.2.3.1 as version number, and our application seems to work well with 
> 2.8.0-rc1 now. 
>
> Kristofer 
>

-- 
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: Runtime error when switching a GWT Polymer Elements project from 2.8.0-beta1 to 2.8.0-rc1/rc2

[Bruno Salmon]

You're right, I use Polymer.importHref() too, but I don't want to move this 
directly in the html as our project supports different UI toolkits, not 
only polymer, so it depends on the configuration and imports need to be 
done at runtime.

So I think I will open an issue and stay with beta1 until the issue is 
resolved.

Thanks.

On Friday, 12 August 2016 17:12:55 UTC+2, zakaria amine wrote:
>
> You must be using Polymer.importHref() right ? and then you call  
> Polymer.ready() I had the same issue before, and I ended up 
> removing Polymer.importHref() and Polymer.ready(), and adding the imports 
> manually in the head, now it works fine. You can check out this commit in 
> my project here: 
> https://github.com/gwidgets/gwt-polymer-starter-kit/commit/7ce3c9523e3e7955f87659f9fcc4d03ac8928a5e
>   
> <https://github.com/gwidgets/gwt-polymer-starter-kit/commit/7ce3c9523e3e7955f87659f9fcc4d03ac8928a5e>
>
> If it does not work then you can open an issue, but you should now that 
> the project's contributors are very slow to respond...
>
> Le vendredi 12 août 2016 16:37:31 UTC+2, Bruno Salmon a écrit :
>>
>> Yes I'm using the latest gwt-polymer-elements version, so 1.2.3.0, and 
>> it works for me with beta1.
>>
>> The runtime error occurs also in production mode, not only in Dev mode.
>>
>> I don't call whenPolymerLoaded() directly in my code, I only use 
>> Polymer.ready(Element 
>> e, Function f) but I guess whenPolymerLoaded() is then called within the 
>> Vaadin implementation. 
>>
>> Actually I just would like to know if it's a gwt-polymer-elements 1.2.3.0 
>> issue (in this case I will wait Vaadin to deliver the next release that 
>> will work GWT 2.8.0) or if it's a GWT issue that needs to be fixed before 
>> 2.8.0 is out.
>>
>> Should I rather open an issue on the gwt-polymer-elements github project?
>>
>>
>> On Friday, 12 August 2016 14:49:04 UTC+2, zakaria amine wrote:
>>>
>>> Normally, the latest version gwt-polymer-elements 1.2.3.0 is not 
>>> supposed to work with beta1 but with SNAPSHOT or rc1, which version are you 
>>> using? 
>>>
>>> Another advise is try not use whenPolymerLoaded() in Dev mode, comment 
>>> it out and take out the statements inside it, use it only when deploying to 
>>> a server. 
>>>
>>>
>>> Le vendredi 12 août 2016 11:39:41 UTC+2, Bruno Salmon a écrit :
>>>>
>>>> Hi,
>>>>
>>>> I have a GWT Polymer Elements project that compiles and run ok with GWT 
>>>> 2.8.0-beta1.
>>>>
>>>> When switching to 2.8.0-rc1 or 2.8.0-rc2, it compiles ok but doesn't 
>>>> run due to the follow runtime error:
>>>>
>>>> Uncaught TypeError: ok_0_g$.call_1_g$ is not a function
>>>> Polymer.java:159
>>>>
>>>> The Polymer.java:159 line is underlined in the code below:
>>>>
>>>> private static native void whenPolymerLoaded(Function ok)
>>>> /*-{
>>>> function done() {
>>>>   // Set our static reference to Base
>>>>   @com.vaadin.polymer.Polymer::Polymer = $wnd.Polymer;
>>>>   @com.vaadin.polymer.Polymer::Base = $wnd.Polymer.Base;
>>>>   // Polymer dynamic loaded does not remove unresolved
>>>>   $doc.body.removeAttribute('unresolved');
>>>>   //
>>>>   *ok.@com.vaadin.polymer.elemental.Function::call(*)()*;
>>>> }
>>>> if (!$wnd.Polymer) {
>>>> var l = $doc.createElement('link');
>>>> l.rel = 'import';
>>>> l.href = 
>>>> @com.vaadin.polymer.Polymer::absoluteHref(*)('polymer');
>>>> l.onload = done;
>>>> $doc.head.appendChild(l);
>>>> } else {
>>>>done();
>>>> }
>>>> }-*/;
>>>>
>>>> I don't know if this is a GWT issue or a GWT Polymer Elements issue.
>>>> Any idea?
>>>>
>>>> Thanks.
>>>>
>>>

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

Re: Runtime error when switching a GWT Polymer Elements project from 2.8.0-beta1 to 2.8.0-rc1/rc2

[Bruno Salmon]

Yes I'm using the latest gwt-polymer-elements version, so 1.2.3.0, and it 
works for me with beta1.

The runtime error occurs also in production mode, not only in Dev mode.

I don't call whenPolymerLoaded() directly in my code, I only use 
Polymer.ready(Element 
e, Function f) but I guess whenPolymerLoaded() is then called within the 
Vaadin implementation. 

Actually I just would like to know if it's a gwt-polymer-elements 1.2.3.0 
issue (in this case I will wait Vaadin to deliver the next release that 
will work GWT 2.8.0) or if it's a GWT issue that needs to be fixed before 
2.8.0 is out.

Should I rather open an issue on the gwt-polymer-elements github project?


On Friday, 12 August 2016 14:49:04 UTC+2, zakaria amine wrote:
>
> Normally, the latest version gwt-polymer-elements 1.2.3.0 is not supposed 
> to work with beta1 but with SNAPSHOT or rc1, which version are you using? 
>
> Another advise is try not use whenPolymerLoaded() in Dev mode, comment it 
> out and take out the statements inside it, use it only when deploying to a 
> server. 
>
>
> Le vendredi 12 août 2016 11:39:41 UTC+2, Bruno Salmon a écrit :
>>
>> Hi,
>>
>> I have a GWT Polymer Elements project that compiles and run ok with GWT 
>> 2.8.0-beta1.
>>
>> When switching to 2.8.0-rc1 or 2.8.0-rc2, it compiles ok but doesn't run 
>> due to the follow runtime error:
>>
>> Uncaught TypeError: ok_0_g$.call_1_g$ is not a function
>> Polymer.java:159
>>
>> The Polymer.java:159 line is underlined in the code below:
>>
>> private static native void whenPolymerLoaded(Function ok)
>> /*-{
>> function done() {
>>   // Set our static reference to Base
>>   @com.vaadin.polymer.Polymer::Polymer = $wnd.Polymer;
>>   @com.vaadin.polymer.Polymer::Base = $wnd.Polymer.Base;
>>   // Polymer dynamic loaded does not remove unresolved
>>   $doc.body.removeAttribute('unresolved');
>>   //
>>   *ok.@com.vaadin.polymer.elemental.Function::call(*)()*;
>> }
>> if (!$wnd.Polymer) {
>> var l = $doc.createElement('link');
>> l.rel = 'import';
>> l.href = 
>> @com.vaadin.polymer.Polymer::absoluteHref(*)('polymer');
>> l.onload = done;
>> $doc.head.appendChild(l);
>> } else {
>>done();
>> }
>> }-*/;
>>
>> I don't know if this is a GWT issue or a GWT Polymer Elements issue.
>> Any idea?
>>
>> 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.

Runtime error when switching a GWT Polymer Elements project from 2.8.0-beta1 to 2.8.0-rc1/rc2

[Bruno Salmon]

Hi,

I have a GWT Polymer Elements project that compiles and run ok with GWT 
2.8.0-beta1.

When switching to 2.8.0-rc1 or 2.8.0-rc2, it compiles ok but doesn't run 
due to the follow runtime error:

Uncaught TypeError: ok_0_g$.call_1_g$ is not a functionPolymer.java:159

The Polymer.java:159 line is underlined in the code below:

private static native void whenPolymerLoaded(Function ok)
/*-{
function done() {
  // Set our static reference to Base
  @com.vaadin.polymer.Polymer::Polymer = $wnd.Polymer;
  @com.vaadin.polymer.Polymer::Base = $wnd.Polymer.Base;
  // Polymer dynamic loaded does not remove unresolved
  $doc.body.removeAttribute('unresolved');
  //
  *ok.@com.vaadin.polymer.elemental.Function::call(*)()*;
}
if (!$wnd.Polymer) {
var l = $doc.createElement('link');
l.rel = 'import';
l.href = 
@com.vaadin.polymer.Polymer::absoluteHref(*)('polymer');
l.onload = done;
$doc.head.appendChild(l);
} else {
   done();
}
}-*/;

I don't know if this is a GWT issue or a GWT Polymer Elements issue.
Any idea?

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.

Is 2.8.0-rc2 GWT Maven Plugin available?

[Bruno Salmon]

Hi,

Just reporting: Maven can find the 2.8.0-rc1 GWT Plugin but not the 
2.8.0-rc2 one.

Thanks.

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

Re: Compiling only what is needed to run?

[Bruno Salmon]

>
>
> It would be great if we had an option to tell GWT to not fail on 
>> compilation errors but automatically mark non compiling code as 
>> @GwtIncompatible.
>> Is it a possible enhancement I can submit?
>>
>
> But then you would hide real compilation issues.
>

Perhaps not if in this mode there is a final standard compilation after all 
the GWT incompatible code has been removed. If the application really 
doesn't use this incompatible code, it should finally compile. If not, an 
error will be reported. That's basically the behaviour that the other 
transpiler had and I was very happy with it.
 

>
>  
>
>> So for now, the only way to use thrid-party libraries that don't compile 
>> as is with GWT (even if the problem is in a part that I don't use) is to 
>> copy the sources and then patch them with @GwtIncompatible annotations?
>>
>
> Yes either use @GwtIncompatible or provide a super-source implementation. 
> In the best case you would fork the third-party library in question, make 
> it GWT compatible by adding @GwtIncompatible annotation and contribute it 
> back.
>
> But keep in mind when using @GwtIncompatible its acts like you have 
> deleted that annotated method in source code. The source code must still be 
> valid even with the now "deleted" method and as the JavaDoc states it can 
> have surprising effects with method overloading or inheritance if you do 
> not take care.
>
> -- J.
>

Sure, it's all about removing code that is really not used by the final GWT 
application.

Forking the library and adding the annotations is an additional work, but 
ok, I will do it if there is no other possibility.
But what is annoying is that this process will need to be repeated each 
time there is a new release of the library.

Perhaps I'm not the only one facing this problem when using third-party 
java libraries with GWT.
Would that make sense to add this new compilation option (eventually with 
scope = only the library source artifact)?

Or, if this enhancement is not possible, would it be possible to declare 
the incompatible code in a separate declarative file instead of using 
annotations (this would reduce the amount of work when moving to another 
library release)? What do you think?

-- 
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: Compiling only what is needed to run?

[Bruno Salmon]

Annoting the second method with @GwtIncompatible fixed the problem indeed, 
good to know, thank you. And I noticed it could work at different levels 
(class, method and field).

But this was a trivial example, my initial question was about third-party 
java libraries and I can't modify the code in this case...

The java (bytecode) to javascript transpiler I used could remove dead code 
even on code it couldn't compile, this allowed me to use some third-party 
libraries even if some parts (that I didn't use) couldn't compile.

But I get better performance with GWT (on both javascript code size and 
execution speed) so I would like to continue with GWT.

It would be great if we had an option to tell GWT to not fail on 
compilation errors but automatically mark non compiling code as 
@GwtIncompatible.
Is it a possible enhancement I can submit?

So for now, the only way to use thrid-party libraries that don't compile as 
is with GWT (even if the problem is in a part that I don't use) is to copy 
the sources and then patch them with @GwtIncompatible annotations?

-- 
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: Compiling only what is needed to run?

[Bruno Salmon]

Ok, great that GWT automatically removes dead code.

I invoke the compiler using the maven plugin so I assume it is a production 
compile (right?).

But this simple code fails on compilation:

public class MyEntryPoint implements EntryPoint {

@Override
public void onModuleLoad() {
methodCompileOk();
}

public void methodCompileOk() {
Logger.getLogger("").info("This compiles with GWT");
}

public void methodCompileNotOk() {
// Logger.getAnonymousLogger() is not emulated by GWT so this code 
doesn't compile with GWT
Logger.getAnonymousLogger().warning("This doesn't compile with GWT");
}

}


I'm getting this error: The method getAnonymousLogger() is undefined for 
the type Logger
even if my code actually doesn't call the second method.

Shouldn't the second method be considered as dead code and automatically 
removed by GWT?

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

Compiling only what is needed to run?

[Bruno Salmon]

Hello,

I would like to know if it's possible to tell the compiler to not compile 
all sources provided but only the classes and methods that are actually 
used.

I already used another java to javascript transpiler that has a per-method 
dependency analyser from the initial entry point, that determines the set 
of methods that are really needed to run the application.
It worked and could drastically reduce the translated code size especially 
when using third-party java libraries (it's not rare we actually use just 
some parts of them). 

It seems GWT doesn't have this feature. Is it right or did I miss a 
compiler option?

-- 
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: Maven can't load gwt-maven-plugin:2.8.0-SNAPSHOT

[Bruno Salmon]

Yes but I thought it was not coming from our Jenkin server because it has 
no other connectivity problem than this one.

However I finally noticed that repo.maven.apache.org is not correctly 
resolved (the IP is wrong for any strange reason) so the problem is finally 
from our server side.

Sorry to have vainly bothered you...

On Monday, 11 January 2016 23:40:22 UTC+1, Thomas Broyer wrote:
>
> "Connection timed out": it's a net connectivity issue.

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

Maven can't load gwt-maven-plugin:2.8.0-SNAPSHOT

[Bruno Salmon]

hi,


I have a maven project using GWT 2.8.0-beta1 and 
gwt-maven-plugin:2.8.0-SNAPSHOT which was working a mounth ago (last run was 
2015/12/09) but is now reporting this error:


[ERROR] Plugin org.codehaus.mojo:gwt-maven-plugin:2.8.0-SNAPSHOT or one of its 
dependencies could not be resolved: Failed to read artifact descriptor for 
org.codehaus.mojo:gwt-maven-plugin:jar:2.8.0-SNAPSHOT: Could not transfer 
artifact org.codehaus.mojo:mojo-parent:pom:38 from/to central 
(http://repo.maven.apache.org/maven2): Connect to repo.maven.apache.org:80 
[repo.maven.apache.org/67.227.162.254] failed: Connection timed out -> [Help 1]


Any idea what's happening?


Bruno

-- 
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: JsInterop Maven fail

[Bruno Salmon]

I tried with versions 2.8.0-20151119.055507-99 and 2.8.0-20151118.055323-98 
but got the same problem about JSInterop.
Earlier versions have no pom file (only pom.asc file) so maven can't load 
them.

So I tried the other way you suggested and successfully built GWT locally. 
I finally got jsInterop 1.0.0-SNAPSHOT installed locally using 
maven/push-gwt.sh (curiously the gwt version was also 1.0.0-SNAPSHOT in the 
local maven repository instead of 2.8.0-SNAPHOT). However maven was then 
able to download the gwt-user 2.8.0-SNAPSHOT dependency without complaining 
this time about JSInterop (thanks to the local install). But finally the 
gwt maven plugin ended with an error:

[INFO] --- gwt-maven-plugin:2.8.0-SNAPSHOT:compile (default) @ naga-gwt ---
Downloading: 
https://oss.sonatype.org/content/repositories/google-snapshots/com/google/gwt/gwt-dev/2.8.0-SNAPSHOT/maven-metadata.xml
Downloading: 
http://nexus.codehaus.org/snapshots/com/google/gwt/gwt-dev/2.8.0-SNAPSHOT/maven-metadata.xml
Downloading: 
https://oss.sonatype.org/content/repositories/snapshots/com/google/gwt/gwt-dev/2.8.0-SNAPSHOT/maven-metadata.xml
Downloaded: 
https://oss.sonatype.org/content/repositories/google-snapshots/com/google/gwt/gwt-dev/2.8.0-SNAPSHOT/maven-metadata.xml
 
(359 B at 0.2 KB/sec)
[WARNING] Could not transfer metadata 
com.google.gwt:gwt-dev:2.8.0-SNAPSHOT/maven-metadata.xml from/to 
codehaus-snapshots (http://nexus.codehaus.org/snapshots/): 
nexus.codehaus.org
Downloading: 
https://oss.sonatype.org/content/repositories/snapshots/com/google/gwt/gwt-dev/2.8.0-SNAPSHOT/gwt-dev-2.8.0-20151123.054735-102.pom
Downloading: 
https://oss.sonatype.org/content/repositories/google-snapshots/com/google/gwt/gwt-dev/2.8.0-SNAPSHOT/gwt-dev-2.8.0-20151123.054735-102.pom
Downloaded: 
https://oss.sonatype.org/content/repositories/google-snapshots/com/google/gwt/gwt-dev/2.8.0-SNAPSHOT/gwt-dev-2.8.0-20151123.054735-102.pom
 
(2 KB at 1.9 KB/sec)
Downloading: 
http://nexus.codehaus.org/snapshots/com/google/gwt/gwt-user/2.8.0-SNAPSHOT/maven-metadata.xml
Downloading: 
https://oss.sonatype.org/content/repositories/snapshots/com/google/gwt/gwt-user/2.8.0-SNAPSHOT/maven-metadata.xml
[WARNING] Could not transfer metadata 
com.google.gwt:gwt-user:2.8.0-SNAPSHOT/maven-metadata.xml from/to 
codehaus-snapshots (http://nexus.codehaus.org/snapshots/): 
nexus.codehaus.org
Downloading: 
https://oss.sonatype.org/content/repositories/google-snapshots/com/google/gwt/gwt-dev/2.8.0-SNAPSHOT/gwt-dev-2.8.0-20151123.054735-102.jar
Downloaded: 
https://oss.sonatype.org/content/repositories/google-snapshots/com/google/gwt/gwt-dev/2.8.0-SNAPSHOT/gwt-dev-2.8.0-20151123.054735-102.jar
 
(40815 KB at 1344.7 KB/sec)
Downloading: 
https://oss.sonatype.org/content/repositories/snapshots/com/google/gwt/gwt/2.8.0-SNAPSHOT/maven-metadata.xml
Downloading: 
https://oss.sonatype.org/content/repositories/snapshots/com/google/gwt/gwt/2.8.0-SNAPSHOT/gwt-2.8.0-SNAPSHOT.pom
[INFO] 

[INFO] BUILD FAILURE
[INFO] 

[INFO] Total time: 37.506s
[INFO] Finished at: Mon Nov 23 13:59:05 CET 2015
[INFO] Final Memory: 10M/27M
[INFO] 

[ERROR] Failed to execute goal 
org.codehaus.mojo:gwt-maven-plugin:2.8.0-SNAPSHOT:compile (default) on 
project naga-gwt: Failed to resolve artifact: 1 problem was encountered 
while building the effective model for 
com.google.gwt:gwt-user:2.8.0-SNAPSHOT
[ERROR] [FATAL] Non-resolvable parent POM: Could not find artifact 
com.google.gwt:gwt:pom:2.8.0-SNAPSHOT in snapshots 
(https://oss.sonatype.org/content/repositories/snapshots/) @ line 6, column 
13
[ERROR] for project com.google.gwt:gwt-user:2.8.0-SNAPSHOT for project 
com.google.gwt:gwt-user:2.8.0-SNAPSHOT
[ERROR] -> [Help 1]

Any idea?


Le lundi 23 novembre 2015 10:35:29 UTC+1, josef...@gmail.com a écrit :
>
> Thank you Thomas, as you probably figured, I thought I had to pin 
> jsinterop :)
>
> On Monday, November 23, 2015 at 10:12:28 AM UTC+1, Thomas Broyer wrote:
>>
>>
>> On Monday, November 23, 2015 at 9:51:28 AM UTC+1, josef...@gmail.com 
>> wrote:
>>>
>>> I am using GWT snapshots from 
>>> https://oss.sonatype.org/content/repositories/google-snapshots/
>>>
>>> Where can I find a working jsinterop?
>>>
>>
>> Pin an earlier snapshot that works; e.g. 
>> 2.8.0-20151119.055507-99 for gwt-user (this is where the 
>> issue is, it should work with the latest snapshot of gwt-dev, but if you 
>> want to use the gwt-dev from the same build, then use 
>> 2.8.0-20151123.054735-102 for gwt-dev).
>>  
>>
>>> On Saturday, November 21, 2015 at 2:55:27 PM UTC+1, Thomas Broyer wrote:

 We're having an error deploying the new com.google.jsinterop artifacts: 
 http://build.gwtproject.org/job/gwt/306

 Try pinning the previous snapshot (using its time-stamped version) or 
 build GWT locally 

Re: Mojo's maven-gwt-plugin or Thomas's maven-gwt-plugin?

[Bruno Salmon]

Thanks Thomas, I will continue on that tread

Le lundi 23 novembre 2015 10:44:15 UTC+1, Thomas Broyer a écrit :
>
>
>
> On Monday, November 23, 2015 at 10:29:20 AM UTC+1, Bruno Salmon wrote:
>>
>> Thanks Thomas, maven can now download the plugin with the correct 
>> repository url you gave me, a step forward to 2.8 :-)
>>
>> However, this is now the gwt-user actifact itself that fails to download 
>> (this time in the google-snapshots repository) due to this unresolved 
>> dependency: 
>> Failure to find com.google.jsinterop:jsinterop:pom:1.0.0-SNAPSHOT in 
>> https://oss.sonatype.org/content/repositories/google-snapshots/
>> And indeed, there is no "jsinterop" repository under 
>> https://oss.sonatype.org/content/repositories/google-snapshots/com/google/
>>
>> Any idea what's wrong?
>>
>
> See https://groups.google.com/forum/#!topic/google-web-toolkit/Ty78TNg58iA
>
>

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

Re: Mojo's maven-gwt-plugin or Thomas's maven-gwt-plugin?

[Bruno Salmon]

Thanks Thomas, maven can now download the plugin with the correct 
repository url you gave me, a step forward to 2.8 :-)

However, this is now the gwt-user actifact itself that fails to download 
(this time in the google-snapshots repository) due to this unresolved 
dependency: 
Failure to find com.google.jsinterop:jsinterop:pom:1.0.0-SNAPSHOT in 
https://oss.sonatype.org/content/repositories/google-snapshots/
And indeed, there is no "jsinterop" repository under 
https://oss.sonatype.org/content/repositories/google-snapshots/com/google/

Any idea what's wrong?


Le vendredi 20 novembre 2015 23:27:58 UTC+1, Thomas Broyer a écrit :
>
>
>
> On Friday, November 20, 2015 at 10:58:40 PM UTC+1, Bruno Salmon wrote:
>>
>> Hello,
>>
>> I'm trying to use the gwt-maven-plugin version 2.8.0-SNAPSHOT but it 
>> seems Maven can't load it:
>>
>> Downloading: 
>> https://oss.sonatype.org/content/repositories/google-snapshots/org/codehaus/mojo/gwt-maven-plugin/2.8.0-SNAPSHOT/gwt-maven-plugin-2.8.0-SNAPSHOT.pom
>> [WARNING] The POM for 
>> org.codehaus.mojo:gwt-maven-plugin:jar:2.8.0-SNAPSHOT is missing, no 
>> dependency information available
>> [ERROR] Plugin org.codehaus.mojo:gwt-maven-plugin:2.8.0-SNAPSHOT or one 
>> of its dependencies could not be resolved: Failed to read artifact 
>> descriptor for org.codehaus.mojo:gwt-maven-plugin:jar:2.8.0-SNAPSHOT: Could 
>> not find artifact org.codehaus.mojo:gwt-maven-plugin:pom:2.8.0-SNAPSHOT in 
>> google-snapshots (
>> https://oss.sonatype.org/content/repositories/google-snapshots/) -> 
>> [Help 1]
>>
>> Any idea what am I doing wrong?
>>
>
> gwt-maven-plugin snapshots are in the 
> https://oss.sonatype.org/content/repositories/snapshots/ repository, not 
> the https://oss.sonatype.org/content/repositories/google-snapshots/ one 
> (this one contains snapshots of GWT proper)
>  
>

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

Re: Mojo's maven-gwt-plugin or Thomas's maven-gwt-plugin?

[Bruno Salmon]

Hello,

I'm trying to use the gwt-maven-plugin version 2.8.0-SNAPSHOT but it seems 
Maven can't load it:

Downloading: 
https://oss.sonatype.org/content/repositories/google-snapshots/org/codehaus/mojo/gwt-maven-plugin/2.8.0-SNAPSHOT/gwt-maven-plugin-2.8.0-SNAPSHOT.pom
[WARNING] The POM for org.codehaus.mojo:gwt-maven-plugin:jar:2.8.0-SNAPSHOT 
is missing, no dependency information available
[ERROR] Plugin org.codehaus.mojo:gwt-maven-plugin:2.8.0-SNAPSHOT or one of 
its dependencies could not be resolved: Failed to read artifact descriptor 
for org.codehaus.mojo:gwt-maven-plugin:jar:2.8.0-SNAPSHOT: Could not find 
artifact org.codehaus.mojo:gwt-maven-plugin:pom:2.8.0-SNAPSHOT in 
google-snapshots 
(https://oss.sonatype.org/content/repositories/google-snapshots/) -> [Help 
1]

Any idea what am I doing wrong?


Le vendredi 20 novembre 2015 13:35:33 UTC+1, Thomas Broyer a écrit :
>
>
>
> On Friday, November 20, 2015 at 11:46:22 AM UTC+1, Martin Trummer wrote:
>>
>> @Thomas: I am surprised, that you make a maven plugin.
>> I can remember one of your blog posts was like "Maven is broken by design"
>> Then, why do you write a maven plugin?
>>
>
> Ha, because a) I happen to still use Maven in some projects† and b) Maven 
> users deserve a better plugin than Mojo's one, and an overall better 
> Maven+GWT integration.
> This is also one reason I created and continue to maintain my Maven 
> archetypes for GWT: https://github.com/tbroyer/gwt-maven-archetypes
>
> † I even tend to use Maven by default for libraries; but I avoid it all 
> all costs for applications.
>
> Did Maven improve with version 3.x,
>>
>
> I don't think I ever used anything else than 3.x (or only briefly, and not 
> really knowing Maven at the time). But yes there's been some progress in 
> 3.2 and 3.3.
> But my main issues with Maven (it's linear lifecycle, and how it's applied 
> to a reactor build) are by-design and I really doubt they'll ever change 
> that.
>  
>
>> or is there just no other alternative for some reason?
>>
>
> There are, and I'd written about it too: 
> http://blog.ltgt.net/in-quest-of-the-ultimate-build-tool/
> I'm a (rather) happy Gradle user, lurking at Bazel.
>  
>
>> What build system would you recommend for a new gwt project?
>>
>
> Gradle without an hesitation, either with the gwt-gradle-plugin (I must 
> say I never used it though; haven't created a new GWT project since I 
> settled on Gradle, or created projects for customers who asked for Maven) 
> or rolling your own tasks;
> but if you're familiar with Maven and don't have major issues with it, 
> then go ahead and then just pick one of the gwt-maven-plugin.
>
>

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