jokade

I'm not sure about the project road-map and the project's relation to AngularJS 2.0. I've only started to consider Angular 2.0 three months ago, and there was not much information...

> I prefer for angulate to target angular 1.x and when angular 2.x becomes a real thing, create angulate2. You're right, it's probably best to start a separate project for...

Hi all, since Angular 2 really breaks with most of the Angular 1.x concepts (and API), I've decided to start a [seaparate project for the Scala.js / Angular 2 binding](https://github.com/jokade/angulate2)....

Angular 2 support will be provided by [angulate2](https://github.com/jokade/angulate2).

@florianhof there is some limited support for this provided by the experimental `@Data` annotation: ```scala @Data case class Foo(bar: String) val foo = Foo("bar") js.Dynamic.console.log(foo) // will print out {foo:...

~~`ControllerMacros.createController()` is not called during `compile` after a property was added to, or removed from a `Controller`. Maybe a cache problem -> check with Scala.js list~~ This is caused by...

I've opened a [thread on the scala-user list](https://groups.google.com/forum/#!topic/scala-user/M2QO1Ki3IyQ) for this issue.

This problem seems to be hard to solve with the current approach. We could use macro annotations on controller classes to generate the Angular.js code instead, which works quite well...

Requires https://github.com/scala-native/scala-native/issues/1652 to be fixed

see also https://github.com/scala-native/scala-native/issues/1940