h0ru5 / angulargwt Goto Github PK

This "issue" is a collection of thoughts, which should become own issues

So far, the workflow is forseen to contain only java-created or regular ng-modules wrapped in gwt.

There should be ways to better integrate gwt-created and regular angular modules.
Two ways of integration need to be reviewed:

AngularGWT modules in an AngularJS app (top-level-module is js)

• One issue is gwt's async loading,
  52eec1f migitates this by a callback for deffered bootstrapping , needs examples
• Another issue is method name mangeling when using GWT services in JS controllers

AngularJS modules in an AngularGWT app (top-level-module is GWT)

• JsInterOp might be handy here

introduce archetypes and distinguish Module-Projects and App-Projects

the jsInterface in GWT 3 might be helpful there, as manually providing the APIs in GWT is error-prone boilerplate.

Hi,
I have succesfully setup a Todo App with your angulargwt wrapper.

I have tryed to add a RCP communication for sending Todo's from the server side but that's always fail with an 404 error.

Is there something in angulargwt that prevent the standard RPC comunication to work ?

Thanks in avance for any help

Pierre

NB : I have setup my project adding manually 5 jars (angulargwt-1.1.4-SNAPSHOT.jar,com.google.common_1.0.0.201004262004.jar,gwt-elemental-2.6.0.jar,gwtquery-1.4.0.jar,json-20090211.jar)

This seems related to elemental running JSNI this[key]=Object(boolval) in GWT-2.6.0

Reproduce:
Add Todo - Watch scope with Batarang,
Todo gets added with correct title but with empty completed

for 1.1.3, the existing code for required-array was taken out.
This code is needed for inter-directive communication, as e.g. in form validation.

Instead of the javascript-esque way of parameter injection, I would go for a @required annotation, similiar to @injected

Should be easy to put back in, but needs an example and documentation then

As directives are the most complex part of Angular, there might be changes necessary to enable further features.

Refer to this talk for a good overview about features of directives in angular.

Roadmap:

• scope isolation
• attribute-binding
• restrictions
• templates
• transclusion
• compile function

For this to work, the structure of a Directive should be changed to one Directive per class IMHO.

Hi Johannes,

any idea how to use angular.js' $q (async calls) in angulargwt?

Gruß, Christian.

Injections in controllers are done by appending parameters to the onInit-Method, where the scope has to be the first parameter.

@NgInject(name = "MyCtrl")
public class MyController extends AngularController<MyScope> {
   private Location location;

  public void onInit(MyScope scope, Location location) {
      this.location=location;
   }

}

A cleaner way in my eyes would be to have the property injected by annotation an have to compiler write the onInit-Method:

@NgInject(name = "MyCtrl")
public class MyController extends AngularController<MyScope> {
  @NgInject("$location")  //the String arg could also be derived from the class
  public Location location; //injected by Framework

  @Override //this can be a regular (abstract) method now
  public void initialize(MyScope scope) {
      //use location
   }

}

Method names of services get minified. We need at least delegates with the original name.