Sebastian, on the subject of derivative work on public repos, you might want to contact the author of this [1] externs file. He has a long list of externs files [2] that were derived from around 3 years ago from DefinitelyTyped [3]. We would, of course, not be using this [1] in light of your constraints on derivative work.
[1] https://raw.githubusercontent.com/honzabrecka/ts-to-goog/master/externs/yfiles.extern.js [2] https://github.com/honzabrecka/ts-to-goog/tree/master/externs<https://github.com/honzabrecka/ts-to-goog> [3] https://github.com/DefinitelyTyped/DefinitelyTyped From: Yishay Weiss<mailto:[email protected]> Sent: Monday, February 3, 2020 2:57 PM To: [email protected]<mailto:[email protected]> Cc: [email protected]<mailto:[email protected]> Subject: RE: YFiles, EPL, Apache As promised, here is the summary of my correspondence with yFiles. > My questions to Sebastian from yWorks: > > a) Would yWorks allow us to create and publish typedefs (think of them > as Royale d.ts files) in our GitHub repository? I would also need to > check license issues on the Apache side. Our license does not allow publishing such files, which would be derivative works from files which are currently under our proprietary license. Although we could grant you permission to do that, we are currently very hesitant to do so. Here's why: Unless there is someone who actively maintains these typings, they would quickly become outdated because with every new release we add new features and APIs. The only way someone could reasonably maintain such a file (about 10k public API members, 7 MB TypeScript definition file) would be through a (semi-automatic?) conversion process. Thus both from a practical and legal perspective it would make a lot more sense to have a tool that reads our API definition files and creates the typedefs. Any licensed yFiles user could make use of this tool and would always get the typedefs matching her yFiles version. For you reference: This is what someone else did to get yFiles for HTML to work seemlessly with Kotlin/JS: https://github.com/turansky/yfiles-kotlin They got explicit permission from us for this (because they do not publish the original files). > > b) Would yWorks consider porting yFiles to Royale? Yes, if and once we get reasonable amount of feedback and customer interest. If you're interested in licensing yFiles for Apache Royale, please do state so and/or contact our support team: yworks.com/contact<http://yworks.com/contact> FWIW the vast majoriy of our previous yFiles FLEX customers has successfully migrated to "native web" technologies and is now happily using yFiles for HTML: With the current state of Apache Royale and the web, we don't see that Apache Royale has gained enough traction that would justify the efforts. We currently believe that creating the diagramming part using "classic" TypeScript/JavaScript and wrapping the resulting component up in a small Royale component with a tiny API surface is the superios and more efficient approach. From: Yishay Weiss<mailto:[email protected]> Sent: Sunday, January 12, 2020 11:37 PM To: [email protected]<mailto:[email protected]> Subject: RE: YFiles, EPL, Apache Ok, I contacted them. I’ll let you guys know. ________________________________ From: Carlos Rovira <[email protected]> Sent: Sunday, January 12, 2020 6:58:17 PM To: [email protected] <[email protected]> Subject: Re: YFiles, EPL, Apache Hi, I think you should contact yFiles directly and talk with them about it. That's better to try to figure if something could be wrong in the future. My understanding is that he should be able to give you permission since it implies make his commercial lib to clients that want to use in Royale. So that clientes will still need to pay for the commercial version, while if no typedefs are done, it will be more difficult to do. El dom., 12 ene. 2020 a las 16:30, Yishay Weiss (<[email protected]>) escribió: > > Hi, > > Before I start making inquiries in legal I wonder if anyone here can give > me some guidance. > > I want to create typedefs for yFiles [1], using an externs [2] file that’s > under an EPL [3]. Should that be a problem? > > This issue [4] makes me extra cautious. > > Thanks. > > [1] https://www.yworks.com/products/yfiles-for-html > [2] > https://raw.githubusercontent.com/honzabrecka/ts-to-goog/master/externs/yfiles.extern.js > [3] https://github.com/honzabrecka/ts-to-goog/blob/master/LICENSE > [4] https://github.com/DefinitelyTyped/DefinitelyTyped/issues/23310 > -- Carlos Rovira http://about.me/carlosrovira
