thanks. Sounds exciting.
On Mon, Feb 2, 2015 at 8:42 PM, 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:
> We are going to introduce configuration file based exports in the future
> however for now your best bet is to super-source the files and ad
We are going to introduce configuration file based exports in the future
however for now your best bet is to super-source the files and add
annotations that you need.
On Mon, Feb 2, 2015 at 5:21 PM, Joseph Gardi wrote:
> that makes sense. How would I apply the @JsExport and @JsType to a third
>
that makes sense. How would I apply the @JsExport and @JsType to a third
party library without forking it though?
On Mon, Feb 2, 2015 at 8:11 PM, 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:
> @JsExport exports constructors and static members a
@JsExport exports constructors and static members and pins them so they act
as entry points and not get pruned.
On the other hand, @JsType enforces generation of javascript compatible
prototype for the class so if there is a method named "someMethod" in the
Java object, same method with same name e
I have a few questions about exporting:
It said: "@JsExport can only be applied to constructors, static fields and
static methods, and whole concrete classes.
". Does this mean that we'll just continue to use GWT-exporter for this or
will there be another way. Also, what will be the easiest way
