On Friday, December 18, 2015 at 10:37:59 AM UTC-5, Alberto Mancini wrote: > > Hello, > well, in my opinion "porting large existing java libraries" is one of the > strengths of GWT and in my experience it works really well in this. > > Were to find informations. > > Well, JSInterop is the way for the part "use the exposed, public classes > from Javascript." > > https://docs.google.com/document/d/10fmlEYIHcyead_4R1S5wKGs1t2I7Fnp_PaNaa7XTEk0/edit# > > and the talk of Julien Dramaix at GWTcon > https://drive.google.com/file/d/0BwVGJUurq6uVR1Y5anV5TC1SQkk/edit >
Thanks, this is very instructive, in particular the talk. I would have to do quite a bit of annotating, it looks like. Is there a WebIDL approach using an external file as well ? > For the part of transpiling the library you need more or less to > transform the library in a GWT module, i think you need > to follow > > http://www.gwtproject.org/doc/latest/DevGuideOrganizingProjects.html , > where you will find essentially what a module is and what <super-source> is > intended to (in case you need) and > http://www.gwtproject.org/doc/latest/RefJreEmulation.html that covers the > emulated jre. > Yes, I just discovered this. Hopefully, the emu would cover most what is used. > I'm biased about that but a few years ago we wrote a post on this subject > http://jooink.blogspot.it/2012/10/gwt-augmented-reality-howto-step-0.html > old but still not completely useless. > This looks similar, and talks a bit about (unused) java.io . Should be very helpful. 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
