Dart transpilation - Githubissues

jelbourn commented 8 years ago

[x] Re-use facades from angular/angular
[x] Dart output is generated from TS source
[x] Dart output passes DartAnalyzer
[x] Dart code is built and passes DartAnalyzer on Travis
[ ] Demo site runs in Dartium with Dart source (alpha.2)
[ ] Unit tests run in Dart (alpha.3)
[ ] Unit tests run in Dart on Travis (alpha.3)
[ ] E2E tests run against Dartium (alpha.4)

Where possible, extract as much as possible from angular/angular and use in both repos OR make improvements to ts2dart directly.

jelbourn commented 8 years ago

cc @yjbanov @vsavkin what else is missing here? I know this isn't a complete list.

yjbanov commented 8 years ago

That's a pretty good list already. Other things to consider:

Run dartanalyzer with strong mode enabled (--strong)
Dart code can be opened and edited in an IDE
Since material components are heavy on styling, I'd recommend running e2e tests in non-Chromium browsers too

Like angular/angular this repo is setting itself up to swim against the current. Why not adopt a package layout that works for all languages?

/             - repository root
/bin/         - command-line user tools
/lib/         - importable source code
/lib/src/     - non-importable (package-private) source code
/web/         - sample web apps, e2e test apps
/test/        - unit-tests, webdriver tests
/tools/       - command-line project tools (shell scripts, etc)
package.json  - NPM config file
pubspec.yaml  - pub config file

yjbanov commented 8 years ago

Forgot to mention. A better way to run Dart tests than Karma is using package:test. It is a well supported test API and a test runner that can run in all browsers, including PhantomJS. You'll need to use package:guinness2 instead of package:guinness.

zoechi commented 8 years ago

Is this the issue to follow the progress about the first (alpha) release for Dart?

jelbourn commented 8 years ago

@zoechi There's some news on this front. The team decided yesterday that we will be able to achieve the most impact from our efforts by no longer supporting a Dart version of Angular Material (Angular itself is unchanged). We know this is unfortunate for those hoping to use the Dart version, but we've concluded that the effort and time required get a quality Dart output working will be better spent making a totally solid TypeScript / JavaScript version.

For Material Design components with Angular 2 Dart, we'd recommend looking into interop with Polymer or Material Design Lite.

marcojakob commented 8 years ago

@jelbourn Very, very disappointed to hear that. I love Dart and I thought Dart could have a bright future. A good and complete UI library was the missing piece for me to finally start big projects. But I'm tired of waiting (a long time) and hearing promises that are never fulfilled and projects that are cancelled.

Yes, I'm looking at you, Dart VM in the browser, Chrome Dev Editor, DartEditor, Packages support for DartPad as replacement for DartEditor, and so on.

When will you announce that Angular 2 Dart will be discontinued as well, because, of course, it's too much work?

zoechi commented 8 years ago

unfortunate is quite some understatement

tomas234 commented 8 years ago

I'm in the exact same situation. What a disappointment :(

zoechi commented 8 years ago

@jelbourn thanks for the honest response anyway

wstrange commented 8 years ago

This is a really terrible decision. Please reconsider.

adaojunior commented 8 years ago

I'm also disappointed, just starting a big angular dart 2 project. Even though we knew it would not be possible to use ng material (it may not be finished in time) we planned to use parts of it in the future.

mswift42 commented 8 years ago

If even Google can't be bothered to support Angular2 Dart, what message does this send?

Interop with Polymer is not the answer, because according to this, it only works with Chrome. That leaves MDL, which might enable one to incorporate Material Design in an app, but is certainly not the ng2 componenty way of assembling an SPA.

Also, according to #199, you are going to make the Tour of Heroes use angular2-material. How will the Dart section of the tutorial then look?

marcojakob commented 8 years ago

@mswift42 Agree that interop with Polymer is not the answer. I was also waiting a long time to see if I could use Polymer in larger apps (and also did use it for a few things). But Google seems to have removed all resources from Polymer Dart (except for @jakemac53). The result was that Polymer JS 1.0 was released in May 2015 and now, almost a year later, we are still waiting for Polymer Dart 1.0 with updated official documentation (it's still a draft on a GitHub wiki). This doesn't make me very confident to bet on Polymer Dart.

In the Keynote of last years Dart Developer Summit Lars Bak and Kasper Lund announced that Angular 2.0 will be the preferred web application framework for Dart. I hope they will quickly come up with a clear strategy and communication about how they plan to do this (which would include a good set of UI components).

Sorry that my frustration is showing through in my statements. I apreciate the awesome work of the Dart team. But I'm very frustrated about communication and being misled so many times.

zoechi commented 8 years ago

@mswift42 I haven't tried it myself but I assume that Polymer works on other browsers than Chrome when full web_components polyfills are loaded.

I also still don't see Polymer as a viable replacement for Angular Material. I wouldn't expect this to work with WebWorkers for example.

adaojunior commented 8 years ago

I can't say for everyone else, but I certainly would prefer google to cancel polymer dart but keep angular projects in sync with the ts/js version.

andresaraujo commented 8 years ago

I'm also very disappointed with this decision, as zoechi said Polymer doesn't seem a viable replacement

filiph commented 8 years ago

To be clear: the Dart team is working on bringing you high quality, pure-Dart Material components for Angular 2. (As you may know, Google is building big things with Angular2, Dart, and Material Design.)

I said this on the dartlang slack yesterday but completely forgot to also say it here.

The fact that those components won't be coming from the angular/material2 team is, from the outside perspective, an implementation detail. It's just a way not to duplicate effort.

I'm sorry this implementation detail showed. In the ideal world, you'd just get the components immediately. Alas, this is not an ideal world. Please follow our blog, G+ or Twitter for updates on this.

mark1010 commented 8 years ago

@filiph Let’s hope the Dart version of Material reaches parity with, and tracks, the TypeScript version.

fallenreaper commented 8 years ago

wow.. Good to know.

ioancristea commented 8 years ago

We want a Dart version! The Dart programming is the best experience what I consumed for web programming. Material Design is a futuristic product and I want to be able in future to make the apps with this. Please consider that fact.

angular-automatic-lock-bot[bot] commented 5 years ago

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}

angular / components

Dart transpilation #37