Yeah regarding this licensing issues aside, I looked all over and didn't see any type of lexer/parser/tokenizer for this "grammar".
Obviously this means it will be a huge amount of work to get something up and running. I don't have enough time to do this and work on the compiler at the same time, so I am just letting people know. I did have an idea that the TS compiler has to be able to parse these things into some type of AST or scanner, if that part of the compiler could be found, it could be forked and used as a structure to emit the .as interfaces/classes. I don't know though, if I had time or was getting paid to do this, I would just write my own in Java, then I could extend it however I wanted. Maybe I am over thinking this and there is an easier solution. Mike On Fri, May 29, 2015 at 9:25 PM, Josh Tynjala <joshtynj...@gmail.com> wrote: > Mike and Alex, in case you missed it, Microsoft includes a lib.d.ts file > with the TypeScript compiler that defines the core JS types, including DOM > APIs. It is very clearly licensed Apache 2.0 (with a license header in the > file too) in their official repository on Github: > > https://github.com/Microsoft/TypeScript/blob/master/bin/lib.d.ts > > That ought to be useful. :) > > - Josh > > On Fri, May 29, 2015 at 5:52 PM, Josh Tynjala <joshtynj...@gmail.com> > wrote: > > > If there are any concerns about copyright that cannot be overcome, I > think > > it makes perfect sense to simply create at tool to parse and convert d.ts > > files and so there on the Apache side. > > > > Let the individual developers figure copyright status on their own when > > using the tool. I'm sure something like DefinitelyTyped will emerge > quickly > > outside of Apache, and those that feel safe using this resource will have > > it just as easy as TypeScript developers. No big deal. > > > > - Josh > > On May 29, 2015 4:11 PM, "Michael Schmalle" <teotigraphix...@gmail.com> > > wrote: > > > >> So what is stopping me from making my own parser and offering libraries > on > >> my won github account that is not tied to Apache? > >> > >> With IDL parser, if I made my own parser could that be used at Apache? > >> > >> Mike > >> > >> On Fri, May 29, 2015 at 6:51 PM, Justin Mclean < > jus...@classsoftware.com> > >> wrote: > >> > >> > HI, > >> > > >> > > Good. All of these pieces seem to be Apache compatible. > >> > > >> > Sorry but that may not actually be the case. > >> > 1) The file has no licence header [1] and from the header seems it may > >> be > >> > part of the CanvasJS project [2] which is a paid for product [3] and > >> also > >> > has an EULA [4] which doesn’t look apache comparable to me. > >> > 2) If you look at the file history you'll see that it was contributed > by > >> > mover5 [5] who looks like from the email address on his gthub to be a > >> > Microsoft employee. Depending on his employment contact Microsoft may > or > >> > may not own the code. > >> > > >> > This is the issue with code found on github in that the provenance in > a > >> > lot of cases can be unclear. > >> > > >> > Thanks, > >> > Justin > >> > > >> > 1. > >> > > >> > https://github.com/borisyankov/DefinitelyTyped/blob/master/canvasjs/canvasjs.d.ts > >> > 2. http://canvasjs.com/ > >> > 3. http://canvasjs.com/license-canvasjs/ > >> > 4. http://canvasjs.com/eula/chart/ > >> > 5. https://github.com/mover5 > >> > > >
