Re: Troubles Getting Started with JsInterop

New insights: I manage to get the things working with @JsNamespace("$wnd.mylib") However, I ran in the following issues:

• I've to reboot super dev mode each time I change the namespace
  
• If I call @JsExport(<name>) (with a name) the symbol isn't exported to the namespace no more (it only worked with @JsExport without arguments)
• I also tested with @JsExport("$wnd.<name>") without success
• I couldn't mage to @JsExport to work with @JsType (not sure if I did and understand everything correctly)

On Saturday, February 14, 2015 at 8:12:46 PM UTC, Vasco Andrade Silva wrote:

Thank you Jens for your comment.

So my Issue #1 is closed until the JS.js method (or other alike) is out. By the way isn't there any library you know that has an implementation for a method like that?

However I was lazy regarding my copy for Issue #2 as I had the Foo class public - didn't work. Did you manage to get a simple @JsExport working?

On Saturday, February 14, 2015 at 7:56:57 PM UTC, Jens wrote:

I guess you have to make your Foo class public. While code examples in the doc uses default visibility I guess it is just because of laziness during writing the doc ;-)

Here is a recent commit that enforces public visibility: 

https://gwt-review.googlesource.com/#/c/11490/

Well and as already said the JS.js functionality is simply not yet implemented. So you have to use JSNI factory methods for now.

-- J.

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