subject:"Re\: \[gwt\-contrib\] Experience with JsInterop status"

Re: [gwt-contrib] Experience with JsInterop status

2015-05-05 Thread Marcin Okraszewski

It worked! But I had to also restart the SDM. When I just cleaned the cache
and reloaded the page it claims no files were changed - see below. Only
when I cleaned and then restarted SDM it started to work.

GET /clean/interop_problems
*   Cleaning disk caches.*
  Cleaned in 2ms.
GET /recompile/interop_problems
   Job com.cloudorado.jsinterop.InteropProblems_1_2
  starting job: com.cloudorado.jsinterop.InteropProblems_1_2
  binding: user.agent=safari
*  skipped compile because no input files have changed*
  0,043s total -- Compile completed


Marcin

On Tue, May 5, 2015 at 7:05 PM, 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> If you clear the cache, does it help? (You can clear it by visiting the
> SuperDevMode URL where there is a button for it)
>
> On Tue, May 5, 2015 at 12:20 AM, Marcin Okraszewski 
> wrote:
>
>> I wasn't able to make it run in SuperDevMode. Worked only in the normal
>> compilation. The idea to try it with normal compilation was from this
>> thread:
>> https://groups.google.com/forum/#!msg/google-web-toolkit-contributors/u1BKRUsjjgI
>>
>> The launch config is part of the project attached to my yesterday
>> message:
>> https://groups.google.com/d/msg/google-web-toolkit-contributors/QrkNflMKe9E/-3XhHdOXfDsJ
>> The arguments passed to dev mode are as follows: "-superDevMode -remoteUI
>> "${gwt_remote_ui_server_port}:${unique_id}" -startupUrl index.html
>> -logLevel INFO -codeServerPort 9997 -port  -XjsInteropMode JS -war
>> C:\workspaces\gwt-demo\interop-problems\war
>> com.cloudorado.jsinterop.InteropProblems"
>> I'm testing with build from trunk done morning Apr 29.
>>
>> Regards,
>> Marcin
>>
>>
>> On Monday, 4 May 2015 23:54:15 UTC+2, Goktug Gokdogan wrote:
>>>
>>> No worries.
>>>
>>> One thing I didn't fully understand is; is this still broken for
>>> SuperDevMode or not?
>>>
>>> On Mon, May 4, 2015 at 2:46 PM, Marcin Okraszewski 
>>> wrote:
>>>
 Are you passing the flag to enable JsInterop for your project?
>

  I was adding  "-XjsInteropMode JS" only in SuperDevMode. This question
 made me realize I didn't for the compilation, when I was testing in
 external web server. So it works like charm with normal compilation running
 on external web server, when I add " -XjsInteropMode JS" to compilation
 parameters. I now feel like in those support quotes - "Did you plug your
 computer?" ... Sorry I did take you so much time for finding yet another
 user error.

 Regards,
 Marcin

 --
 You received this message because you are subscribed to the Google
 Groups "GWT Contributors" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to
 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/e6bd7cb2-2742-4192-bada-eb3eac9bc30e%40googlegroups.com
 
 .

 For more options, visit https://groups.google.com/d/optout.

>>>
>>>  --
>> You received this message because you are subscribed to the Google Groups
>> "GWT Contributors" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/bffa2a4f-8b2e-4f5c-aed6-46f1529167e6%40googlegroups.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "GWT Contributors" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit-contributors/QrkNflMKe9E/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA0WZFPQ%2B2YzG5xXTPjd6waN8ZQkGJs%3D3SLoKMF09SMXrA%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+un

Re: [gwt-contrib] Experience with JsInterop status

2015-05-05 Thread 'Goktug Gokdogan' via GWT Contributors

If you clear the cache, does it help? (You can clear it by visiting the
SuperDevMode URL where there is a button for it)

On Tue, May 5, 2015 at 12:20 AM, Marcin Okraszewski 
wrote:

> I wasn't able to make it run in SuperDevMode. Worked only in the normal
> compilation. The idea to try it with normal compilation was from this
> thread:
> https://groups.google.com/forum/#!msg/google-web-toolkit-contributors/u1BKRUsjjgI
>
> The launch config is part of the project attached to my yesterday message:
> https://groups.google.com/d/msg/google-web-toolkit-contributors/QrkNflMKe9E/-3XhHdOXfDsJ
> The arguments passed to dev mode are as follows: "-superDevMode -remoteUI
> "${gwt_remote_ui_server_port}:${unique_id}" -startupUrl index.html
> -logLevel INFO -codeServerPort 9997 -port  -XjsInteropMode JS -war
> C:\workspaces\gwt-demo\interop-problems\war
> com.cloudorado.jsinterop.InteropProblems"
> I'm testing with build from trunk done morning Apr 29.
>
> Regards,
> Marcin
>
>
> On Monday, 4 May 2015 23:54:15 UTC+2, Goktug Gokdogan wrote:
>>
>> No worries.
>>
>> One thing I didn't fully understand is; is this still broken for
>> SuperDevMode or not?
>>
>> On Mon, May 4, 2015 at 2:46 PM, Marcin Okraszewski 
>> wrote:
>>
>>> Are you passing the flag to enable JsInterop for your project?

>>>
>>>  I was adding  "-XjsInteropMode JS" only in SuperDevMode. This question
>>> made me realize I didn't for the compilation, when I was testing in
>>> external web server. So it works like charm with normal compilation running
>>> on external web server, when I add " -XjsInteropMode JS" to compilation
>>> parameters. I now feel like in those support quotes - "Did you plug your
>>> computer?" ... Sorry I did take you so much time for finding yet another
>>> user error.
>>>
>>> Regards,
>>> Marcin
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "GWT Contributors" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com
>>> .
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/e6bd7cb2-2742-4192-bada-eb3eac9bc30e%40googlegroups.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/bffa2a4f-8b2e-4f5c-aed6-46f1529167e6%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA0WZFPQ%2B2YzG5xXTPjd6waN8ZQkGJs%3D3SLoKMF09SMXrA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Experience with JsInterop status

2015-05-05 Thread Marcin Okraszewski

I wasn't able to make it run in SuperDevMode. Worked only in the normal 
compilation. The idea to try it with normal compilation was from this 
thread: 
https://groups.google.com/forum/#!msg/google-web-toolkit-contributors/u1BKRUsjjgI

The launch config is part of the project attached to my yesterday 
message: 
https://groups.google.com/d/msg/google-web-toolkit-contributors/QrkNflMKe9E/-3XhHdOXfDsJ
The arguments passed to dev mode are as follows: "-superDevMode -remoteUI 
"${gwt_remote_ui_server_port}:${unique_id}" -startupUrl index.html 
-logLevel INFO -codeServerPort 9997 -port  -XjsInteropMode JS -war 
C:\workspaces\gwt-demo\interop-problems\war 
com.cloudorado.jsinterop.InteropProblems"
I'm testing with build from trunk done morning Apr 29. 

Regards,
Marcin


On Monday, 4 May 2015 23:54:15 UTC+2, Goktug Gokdogan wrote:
>
> No worries.
>
> One thing I didn't fully understand is; is this still broken for 
> SuperDevMode or not?
>
> On Mon, May 4, 2015 at 2:46 PM, Marcin Okraszewski  > wrote:
>
>> Are you passing the flag to enable JsInterop for your project?
>>>
>>
>>  I was adding  "-XjsInteropMode JS" only in SuperDevMode. This question 
>> made me realize I didn't for the compilation, when I was testing in 
>> external web server. So it works like charm with normal compilation running 
>> on external web server, when I add " -XjsInteropMode JS" to compilation 
>> parameters. I now feel like in those support quotes - "Did you plug your 
>> computer?" ... Sorry I did take you so much time for finding yet another 
>> user error. 
>>
>> Regards,
>> Marcin
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "GWT Contributors" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com 
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/e6bd7cb2-2742-4192-bada-eb3eac9bc30e%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/bffa2a4f-8b2e-4f5c-aed6-46f1529167e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Experience with JsInterop status

2015-05-04 Thread 'Goktug Gokdogan' via GWT Contributors

No worries.

One thing I didn't fully understand is; is this still broken for
SuperDevMode or not?

On Mon, May 4, 2015 at 2:46 PM, Marcin Okraszewski  wrote:

> Are you passing the flag to enable JsInterop for your project?
>>
>
>  I was adding  "-XjsInteropMode JS" only in SuperDevMode. This question
> made me realize I didn't for the compilation, when I was testing in
> external web server. So it works like charm with normal compilation running
> on external web server, when I add " -XjsInteropMode JS" to compilation
> parameters. I now feel like in those support quotes - "Did you plug your
> computer?" ... Sorry I did take you so much time for finding yet another
> user error.
>
> Regards,
> Marcin
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/e6bd7cb2-2742-4192-bada-eb3eac9bc30e%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA21HUSL0d_wXBfydhZn4hmaVS%2BLHBCs%2B8__jLPsq2UGQA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Experience with JsInterop status

2015-05-04 Thread Marcin Okraszewski


>
> Are you passing the flag to enable JsInterop for your project?
>

 I was adding  "-XjsInteropMode JS" only in SuperDevMode. This question 
made me realize I didn't for the compilation, when I was testing in 
external web server. So it works like charm with normal compilation running 
on external web server, when I add " -XjsInteropMode JS" to compilation 
parameters. I now feel like in those support quotes - "Did you plug your 
computer?" ... Sorry I did take you so much time for finding yet another 
user error. 

Regards,
Marcin

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/e6bd7cb2-2742-4192-bada-eb3eac9bc30e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Experience with JsInterop status

2015-05-04 Thread 'Goktug Gokdogan' via GWT Contributors

On Mon, May 4, 2015 at 4:07 AM, Marcin Okraszewski  wrote:

> Hi,
> Sorry for the delay. I still wasn't able to make @JsExport work for me.
> One thing I was for sure missing is I've never used the class in my GWT
> project. It was referenced only from JS.
>

We already have a test covering that and it is passing (see
MyClassExportsMethodWithoutReference)


> Once I instantiated the class from the module load, it started to complain
> about @JsExport on non-static method
>


Are you passing the flag to enable JsInterop for your project?


> , which I interpret that it wasn't processed earlier. I also tried with
> compiled version served from a webserver, not from Super Dev Mode. In case
> it was happening in dev mode only.
>
> The method now looks as below and I'm still having errors that "interop"
> is undefined. I attach the project in question.
>
> A word of comment on @JsType - that was completely not intuitive that I
> still need to add @JsType if I use @JsExport.
>
> @JsNamespace("interop")
> @JsExport
> @JsType
> public class Hello {
> @JsExport
> public Hello() {
> }
>  public String sayHello() {
> return "Hello World!";
> }
>
> @JsExport
> public static String sayHelloStatic() {
> return "Hello World!";
> }
> }
>
>
> Regards,
> Marcin Okraszewski
>
>
> JsExport is no longer fully qualified, you need to supply JsNamespace. Try
>> following:
>>
>> @JsNameSpace("interop") @JsExport
>> class Hello {
>>public Hello() {}
>>public String sayHello() { .. }
>> }
>>
>> Also you need to put @JsType if you want to call sayHello from javascript.
>>
>>
>>
>>> public Hello() {
>>> }
>>>  @JsExport
>>> public String sayHello() {
>>> return "Hello World!";
>>> }
>>> }
>>>
>>> JavaScript:
>>>
>>>   var hello = new interop.Hello();
>>>   alert(hello.sayHello());
>>>
>>> Result:
>>>
>>> Uncaught ReferenceError: interop is not defined
>>>
>>> Marcin
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "GWT Contributors" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com
>>> .
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/7a6094ef-da19-42ff-bf93-3e90a202fe5a%40googlegroups.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/da3a45aa-08ef-419a-8cfa-0007a1fc9487%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA010v22PA8TVzzFe7gDWrLCKeOqrbW7eQi6wfnL%3DqyqcA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Experience with JsInterop status

2015-05-04 Thread Jens



> A word of comment on @JsType - that was completely not intuitive that I 
> still need to add @JsType if I use @JsExport.
>

Yeah thats why there is a discussion in [1] to make it more intuitive. Feel 
free to provide some additional input. 

[1] 
https://groups.google.com/d/msg/google-web-toolkit-contributors/Dwdk-aEHs8Y/OvSNe6egUekJ

-- J.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/78d67cce-aa33-4236-9a4e-9014e01df03d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Experience with JsInterop status

2015-04-29 Thread 'Goktug Gokdogan' via GWT Contributors

On Wed, Apr 29, 2015 at 7:53 AM, Marcin Okraszewski 
wrote:

> Hi Goktung,
> I've compiled the latest version from trunk and rechecked those items you
> wanted the snippets for.
>
>
>>>1. I wasn't able to call methods on jQuery object returned from JSNI
>>>when using just @JsType annotation. It only worked when I used
>>>@JsType(prototype="jQuery")
>>>
>>>
> It didn't happen this time. So either
>
>
>>
>>>1. Couldn't access class with @JsExport annotation from JS.
>>>
>>>
> I had multiple tries of using @JsExport as well as @JsNamespace. This is
> one of them:
>
> public class Hello {
> @JsExport("interop.Hello")
>

JsExport is no longer fully qualified, you need to supply JsNamespace. Try
following:

@JsNameSpace("interop") @JsExport
class Hello {
   public Hello() {}
   public String sayHello() { .. }
}

Also you need to put @JsType if you want to call sayHello from javascript.



> public Hello() {
> }
>  @JsExport
> public String sayHello() {
> return "Hello World!";
> }
> }
>
> JavaScript:
>
>   var hello = new interop.Hello();
>   alert(hello.sayHello());
>
> Result:
>
> Uncaught ReferenceError: interop is not defined
>
> Marcin
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/7a6094ef-da19-42ff-bf93-3e90a202fe5a%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA0O_XfOhWcnnt3dUs%2Bend%2BoqCs0_Z1n_3N-S2aw6mGYhw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Experience with JsInterop status

2015-04-29 Thread Marcin Okraszewski

Maybe to supplement a bit - the JavaScript code is run in onclick handler, 
so GWT is already loaded. A wider scope would be:


  function sayHello() {
  var hello = new interop.Hello();
  alert(hello.sayHello());
  }


...

Say hello

Marcin


On Wednesday, 29 April 2015 16:53:37 UTC+2, Marcin Okraszewski wrote:
>
> Hi Goktung,
> I've compiled the latest version from trunk and rechecked those items you 
> wanted the snippets for. 
>
>
>>>1. I wasn't able to call methods on jQuery object returned from JSNI 
>>>when using just @JsType annotation. It only worked when I used 
>>>@JsType(prototype="jQuery")
>>>
>>>
> It didn't happen this time. So either 
>  
>
>>
>>>1. Couldn't access class with @JsExport annotation from JS.
>>>
>>>
> I had multiple tries of using @JsExport as well as @JsNamespace. This is 
> one of them:
>
> public class Hello {
> @JsExport("interop.Hello")
> public Hello() {
> }
>  @JsExport
> public String sayHello() {
> return "Hello World!";
> }
> }
>
> JavaScript:
>
>   var hello = new interop.Hello();
>   alert(hello.sayHello());
>
> Result:
>
> Uncaught ReferenceError: interop is not defined
>
> Marcin
>  
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/c819123d-2967-4f12-ba29-326bc4caf837%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Experience with JsInterop status

2015-04-29 Thread Marcin Okraszewski

Hi Goktung,
I've compiled the latest version from trunk and rechecked those items you 
wanted the snippets for. 


>>1. I wasn't able to call methods on jQuery object returned from JSNI 
>>when using just @JsType annotation. It only worked when I used 
>>@JsType(prototype="jQuery")
>>
>>
It didn't happen this time. So either 
 

>
>>1. Couldn't access class with @JsExport annotation from JS.
>>
>>
I had multiple tries of using @JsExport as well as @JsNamespace. This is 
one of them:

public class Hello {
@JsExport("interop.Hello")
public Hello() {
}
 @JsExport
public String sayHello() {
return "Hello World!";
}
}

JavaScript:

  var hello = new interop.Hello();
  alert(hello.sayHello());

Result:

Uncaught ReferenceError: interop is not defined

Marcin
 

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/7a6094ef-da19-42ff-bf93-3e90a202fe5a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Experience with JsInterop status

2015-04-28 Thread 'Goktug Gokdogan' via GWT Contributors

Thanks for the feedback.

On Tue, Apr 28, 2015 at 6:40 AM, Marcin Okraszewski 
wrote:

> Hi,
> I was playing a bit with the new JsInterop on trunk build. After some
> conversation with Goktug, I was to write some of issues I've found. It was
> April 3 build, sorry didn't check if anything changed since then. So, here
> it goes:
>
>1. @JsFunction exported to JS doesn't have apply() and call()
> operations. Apply() is used by JQuery (2.1.3) to call callbacks, so
>basically it wasn't possible to add handlers using JQuery. See other thread
>on this:
>https://groups.google.com/forum/#!topic/google-web-toolkit/PHtfLTSAJDM
>
> We are going to fix this before the release; it's in the queue.


>
>1. js() function is not yet available.
>
> There are some disagreements in the team, so this may not make to v1.0.


>
>1. I wasn't able to call methods on jQuery object returned from JSNI
>when using just @JsType annotation. It only worked when I used
>@JsType(prototype="jQuery")
>
>
Can you elaborate more? Can you send a small code snippet that reproduces
the problem?


>
>1. @JsProperty set on methods were not available in JS.
>
>
JsProperty on methods doesn't work yet if you implement the interface in
java (though you can call it if the interface is implemented by
javascript). You can use @JsType on concrete classes with public fields
instead for now.


>
>1. Couldn't access class with @JsExport annotation from JS.
>
>
This needs some code snippet as well so we can reproduce it.



> I've workarounded the @JsFunction issue by adding .apply() in JS, so I've
> made it work. And I must tell, the new JsInterop is really GREAT!
>
> I also used @JsType with @JsProperty to access a JSON returned from
> server. I just used JSON.safeEval() and casted to @JsType interface. It
> worked great! I hope it could be a replacement for me of AutoBeans, if only
> the JS arrays and Java collections were unified.
>
> Regards,
> Marcin Okraszewski
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/af52b996-9bec-41d0-9768-934e0371270a%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA1WsHGGgLRww%3DQHwO3uC-6eb9xZHD5wwmyYX7NO_TDZ4Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Experience with JsInterop status

Re: [gwt-contrib] Experience with JsInterop status

Re: [gwt-contrib] Experience with JsInterop status

Re: [gwt-contrib] Experience with JsInterop status

Re: [gwt-contrib] Experience with JsInterop status

Re: [gwt-contrib] Experience with JsInterop status

Re: [gwt-contrib] Experience with JsInterop status

Re: [gwt-contrib] Experience with JsInterop status

Re: [gwt-contrib] Experience with JsInterop status

Re: [gwt-contrib] Experience with JsInterop status

Re: [gwt-contrib] Experience with JsInterop status

11 matches

Site Navigation

Mail list logo

Footer information