com.asayama.gwt.angular.client

Interface Directive

All Known Implementing Classes:

AbstractDirective

public interface Directive

TODO This file needs some serious review and clean-up.

Author:

kyoken74

Nested Class Summary

Nested Classes

Modifier and Type	Interface and Description
static class	Directive.Restrict

Method Summary

Methods

Modifier and Type	Method and Description
void	compile(JQElement element, com.asayama.gwt.jsni.client.JSON attrs) In AngularJS, compile method returns linker function.
String	getName()
Directive.Restrict[]	getRestrict()
com.google.gwt.resources.client.TextResource	getTemplate()
String	getTemplateUrl()
boolean	getTransclude()
void	link(NGScope scope, JQElement element, com.asayama.gwt.jsni.client.JSON attrs)
NGScope	scope()
void	setName(String name)

Method Detail

getName

String getName()

getTransclude

boolean getTransclude()

setName

void setName(String name)

getRestrict

Directive.Restrict[] getRestrict()

getTemplate

com.google.gwt.resources.client.TextResource getTemplate()

getTemplateUrl

String getTemplateUrl()

scope

NGScope scope()

compile

void compile(JQElement element,
           com.asayama.gwt.jsni.client.JSON attrs)

In AngularJS, compile method returns linker function. In this implementation, however, we do not return any values. This is because DefaultDirectiveFactory wraps the call to link(NGScope, JQElement, JSON) into a JavaScript function, and returns that from the JavaScript wrapping of the compile function call.

This means that, unlike AngularJS, we currently do not support compile dependent linker option (i.e. the outcome of compile function cannot return different linker functions).

link

void link(NGScope scope,
        JQElement element,
        com.asayama.gwt.jsni.client.JSON attrs)