-
Notifications
You must be signed in to change notification settings - Fork 514
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any thoughts on possibly moving to Dart lang instead of using TypeScript? #45
Comments
TypeScript suits our needs quite well at the moment. In particular it gives us a very high degree of control over the generated JavaScript, and makes it trivial to mix JavaScript and TypeScript. It's difficult to imagine being able to justify the cost of switching our actual engine code. However, I'm sure it would not be too difficult to create Dart declarations for the Turbulenz engine and develop your code against those. Potentially these declarations could be automatically generated from our Again, I'm not familiar enough with Dart to know if this is really practical. If you have any experience or insight into this kind of thing I'd be interested to hear. |
I'm currently evaluating 2d physics engines for a Dart project. And I like the one that comes with this turbulenz, but since there's no Dart API ready I'll probably end up using either box2d or p2 Dart ports for now. But it would be entirely possible to interoperate with the js files of turbulenz, by declaring the API in a Dart file. There's a full example with the chart.js lib, and info. |
Thanks for the comments. We don't currently have any plans to provide the Dart declarations. (It also appears that there is now at least one project to generate Dart declarations from .d.ts files. I have no idea how stable it would be, but it could be interesting to try and may provide the bulk of what you need.) |
Seems like Dart is making good head way to building strong programming practices.
The text was updated successfully, but these errors were encountered: