First of all, as long d.ts works, end user should not care if the compiler directly understands it or there is a converter in between.
Even the starting point is d.ts or type annotations, in order to have good IDE support you still need a java representation so that your code will compile and auto complete. With java syntax, there are no special syntax coloring support required by IDE and you have the refactoring support. Also my expectation is; regular java interfaces should require minimal customization and special treatment in JDT and AST, compared to anything else. Interfaces also work well in jre only environment and jre unit tests. On top of all of these, GWT target user group is java developers who already familiar with java interfaces and they don't need to learn something new. However, given that corresponding js has type information (via jsdoc or d.ts), we can make the process seamless and not require manual interface creation. Generating elemental from Webkit IDL was difficult mostly because of the limitations of expressibility via JSOs; so I'm not worried much. There is already a d.ts to closure converter so if we support interface generation from closure than 'theoretically' d.ts support will be free. On Thu, Aug 8, 2013 at 9:18 AM, Xavier M. <xavier.meh...@gmail.com> wrote: > Yep, insuring a clear interface between different world is always valuable > and even mandatory in my opinion.. Typescript .d.ts files have already made > the job, so why not using this syntax. As a early adopter of gwt in 2006, i > could also say that I'm an early adopter of typescript on real projects > (not Dart I 'don't like), an Typescript convinced me... GWT has several > abilities Typescript have not yet and making a bridge between the two > approaches would be very nice. In my sense, the future if Ecmascript6 and > later... GWT with java8 could be a pragmatical competitor. > > regards > Xavier > > > 2013/8/8 Brian Slesinsky <skybr...@google.com> > >> It might be nice to be able to say that anything defined in a .d.ts can >> be imported into GWT. This will make it easier to work with JavaScript >> programmers since they don't have to write any Java code. So perhaps it's >> worth making sure that generating the Java interfaces from .d.ts files will >> work? I know that generating Elemental code from WebKit IDL files wasn't >> easy. >> >> However, our main use case is to import web components which are new. So >> my question is how likely people are to write .d.ts files for web >> components; I don't know if there is much overlap between those two >> communities yet. >> >> >> On Tue, Aug 6, 2013 at 3:02 PM, Goktug Gokdogan <gok...@google.com>wrote: >> >>> Jon (Stalcup) just warned me that it may not necessarily orthogonal so I >>> will make a clarification to what I said. >>> >>> There are number of reasons why it makes we sense to define the contract >>> with java syntax and interface files for GWT (easy IDE support and JDT >>> integration and developer familiarity etc.), but someone might have chosen >>> to start with a custom syntax like the d.ts files. >>> Assuming these interfaces exist and understood by the compiler, any >>> other support can be built on top of that by generating them and provide a >>> seamless integration. >>> >>> >>> On Tue, Aug 6, 2013 at 1:25 PM, Goktug Gokdogan <gok...@google.com>wrote: >>> >>>> We were planning to look into making integration seamless if closure >>>> type annotations exists but that's kind of orthogonal to this proposal. >>>> When we have that integration, it might not be hard to utilize >>>> typescript via typescript to closure conversion. >>>> Thanks for suggestion. >>>> >>>> >>>> On Tue, Aug 6, 2013 at 1:29 AM, Xavier Mehaut >>>> <xavier.meh...@gmail.com>wrote: >>>> >>>>> Hi goktuk >>>>> A nice way to interop with js is the way typescript does through the >>>>> .d.ts files where js api is declared in a typed way, ensuring then the >>>>> ability to interop with any preexisted js. Moreover, already existing >>>>> .d.ts >>>>> files for many js libraries exist on >>>>> https://github.com/borisyankov/DefinitelyTyped >>>>> No extra wirk to do then :) >>>>> >>>>> Best regards >>>>> Xavier >>>>> >>>>> >>>>> Envoyé de mon iPhone >>>>> >>>>> Le 6 août 2013 à 09:24, "Goktug Gokdogan (Google Drive)" < >>>>> gok...@google.com> a écrit : >>>>> >>>>> I've shared an item with you. >>>>> >>>>> This is a design doc that describes a proposal for improving >>>>> interoperability with GWT and javascript. The proposal provides some >>>>> essential pieces to provide better and easier interoperability with JS >>>>> while putting more complex scenarios (e.g. Web Components) and >>>>> testability into account. >>>>> >>>>> Please take a look and provide us some feedback. >>>>> >>>>> Cheers, >>>>> >>>>> - Goktug >>>>> >>>>> [image: Document] Nextgen GWT/JS Interop >>>>> (Public)<https://docs.google.com/document/d/1tir74SB-ZWrs-gQ8w-lOEV3oMY6u6lF2MmNivDEihZ4/edit?usp=sharing> >>>>> Google Drive: create, share, and keep all your stuff in one place. [image: >>>>> Logo for Google Drive] <https://drive.google.com> >>>>> >>>>> -- >>>>> http://groups.google.com/group/Google-Web-Toolkit-Contributors >>>>> --- >>>>> 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. >>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>> >>>>> >>>>> >>>>> -- >>>>> http://groups.google.com/group/Google-Web-Toolkit-Contributors >>>>> --- >>>>> 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. >>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>> >>>>> >>>>> >>>> >>>> >>> -- >>> http://groups.google.com/group/Google-Web-Toolkit-Contributors >>> --- >>> 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 >>> . >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >> -- >> http://groups.google.com/group/Google-Web-Toolkit-Contributors >> --- >> 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. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > > -- > *Bien cordialement, > Xavier* > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > --- > 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. > For more options, visit https://groups.google.com/groups/opt_out. > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
