I desagree with this assertion ; the goal is not to interop with ts, haxe, coffee, ..., but only with js. Moreover the future of js is ecmascript 6, so ts is a good candidate to express properly an interface; this is not the case IMO of a jsdoc like solution which is verbose and not so precise and concise as a true language.
To finish, i recall in mind https://github.com/borisyankov/DefinitelyTyped as a reminder of the power of the d.ts technics Best regards Xavier Envoyé de mon iPhone Le 8 août 2013 à 22:39, Ray Cromwell <[email protected]> a écrit : > As cool as I think TS is, there are far more lines of code out there in Js, > some even with JsDoc type assertions, so I think the latter would be more > useful as a first pass. JsDoc is comments so it works with existing JS. We > could explore importing libraries defined in TS, Dart, haXe, et al via some > kind of standard plugin extension. > > > > On Thu, Aug 8, 2013 at 9:08 AM, Brian Slesinsky <[email protected]> wrote: >> 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 <[email protected]> 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 <[email protected]> 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 <[email protected]> >>>> 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)" >>>>> <[email protected]> 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 >>>>>> Nextgen GWT/JS Interop (Public) >>>>>> Google Drive: create, share, and keep all your stuff in one place. >>>>>> -- >>>>>> 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 [email protected]. >>>>>> 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 [email protected]. >>>>> 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 [email protected]. >>> 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 [email protected]. >> 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 [email protected]. > 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
