update Dart API index, plus Dart guide chapters 3 & 4
This commit is contained in:
parent
58e607e873
commit
b3c6189fc6
|
@ -2,9 +2,12 @@
|
||||||
h2 Developer Preview
|
h2 Developer Preview
|
||||||
|
|
||||||
p.
|
p.
|
||||||
The Angular 2.0 API is currently in active development and not production ready.
|
The proposed Angular 2 API does not yet have Dart-specific documentation.
|
||||||
This page will showcase a preview of proposed methods to help further the discussion
|
However, because the Dart and JavaScript APIs are generated from the same source,
|
||||||
in the development community.
|
you might find the JavaScript API docs helpful:
|
||||||
|
|
||||||
|
p.text-center
|
||||||
|
<b><a href="/docs/js/latest/api/">Angular 2 API Preview (JavaScript)</a></b>
|
||||||
|
|
||||||
.l-sub-section
|
.l-sub-section
|
||||||
h3 Angular 1.X for Production
|
h3 Angular 1.X for Production
|
||||||
|
|
|
@ -1,10 +1,13 @@
|
||||||
.l-main-section
|
.l-main-section
|
||||||
p.
|
p.
|
||||||
As mentioned earlier, you build Angular applications as a tree of nested components. You've seen how to create
|
As mentioned earlier, you build Angular applications as a tree of nested components.
|
||||||
a top-level component. You add child components to a parent component by using them in the parent component's
|
You've seen how to create a top-level component.
|
||||||
template.
|
You add child components to a parent component by using them in
|
||||||
|
the parent component's template,
|
||||||
|
and by specifying the child component classes in the parent's list of directives.
|
||||||
p.
|
p.
|
||||||
Given a bootstrapping template with a <code><parent></code> tag in the body, you can create a parent
|
Given a bootstrapping template with a <code><parent></code> tag in the body,
|
||||||
|
you can create a parent
|
||||||
component that uses a <code><child></code> component like so:
|
component that uses a <code><child></code> component like so:
|
||||||
|
|
||||||
pre.prettyprint.linenums.lang-dart
|
pre.prettyprint.linenums.lang-dart
|
||||||
|
@ -17,9 +20,9 @@
|
||||||
@View(
|
@View(
|
||||||
template: '''
|
template: '''
|
||||||
<h1>{{ message }}</h1>
|
<h1>{{ message }}</h1>
|
||||||
<child></child>
|
<span class="pnk"><child></child></span>
|
||||||
''',
|
''',
|
||||||
directives: const[ChildComponent]
|
directives: const[<span class="pnk">ChildComponent</span>]
|
||||||
)
|
)
|
||||||
class ParentComponent {
|
class ParentComponent {
|
||||||
String message = "I'm the parent";
|
String message = "I'm the parent";
|
||||||
|
@ -43,8 +46,5 @@
|
||||||
String message = "I'm the child";
|
String message = "I'm the child";
|
||||||
}
|
}
|
||||||
|
|
||||||
p.
|
|
||||||
Notice that in addition to using the <code><child></code> element in the parent template, you also need to
|
|
||||||
add <code>ChildComponent</code> in <code>ParentComponent</code>'s list of directives
|
|
||||||
//p.
|
//p.
|
||||||
[TODO: Motivate communication between components with iterator example that passes index to the child]
|
[TODO: Motivate communication between components with iterator example that passes index to the child]
|
||||||
|
|
Binary file not shown.
Before Width: | Height: | Size: 21 KiB After Width: | Height: | Size: 19 KiB |
|
@ -1,40 +1,52 @@
|
||||||
.l-main-section
|
.l-main-section
|
||||||
p.
|
p.
|
||||||
You can make your application respond to user input by associating events with functions in your controller
|
Use the event syntax <strong>(<em>eventName</em>)</strong> to
|
||||||
using the event syntax using <strong>()</strong> to surround the name of an event.
|
make your application respond to user input.
|
||||||
p.
|
p.
|
||||||
For a particular control like an input you can have it call methods on your controller on keyup event like so:
|
You can specify the event handler—a method in the component controller—like this:
|
||||||
|
|
||||||
pre.prettyprint.lang-html
|
pre.prettyprint.lang-html
|
||||||
code.
|
code.
|
||||||
<input (keyup)="myControllerMethod()">
|
<input (keyup)="myControllerMethod()">
|
||||||
p.
|
p.
|
||||||
As in previous examples, you can make element references available to other parts of the template as a local
|
As in previous examples, you can make element references available to
|
||||||
variable using the # syntax. With this and events, we can do the old "update text as you type" example:
|
other parts of the template as a local
|
||||||
|
variable using the <b>#</b> syntax.
|
||||||
|
Using <code>#</code> and events,
|
||||||
|
you can write the old "update text as you type" example:
|
||||||
|
<!-- PENDING: make sure we use recommended word separation scheme.
|
||||||
|
my-name doesn't work, but my_name does. Would myName work? -->
|
||||||
|
|
||||||
pre.prettyprint.lang-html
|
pre.prettyprint.lang-html
|
||||||
code.
|
code.
|
||||||
<input #my-name (keyup)>
|
<input #myname (keyup)>
|
||||||
<p>{{my-name.value}}</p>
|
<p>{{myname.value}}</p>
|
||||||
|
|
||||||
p.text-body(ng-non-bindable).
|
p.text-body(ng-non-bindable).
|
||||||
The <code>#my-name</code> creates a local variable in the template that we'll refer to below in the
|
In that example, <code>#myname</code> creates a local variable in the template that
|
||||||
<code><p></code> element. The <code>(keyup)</code> tells Angular to trigger updates when it gets a keyup
|
the <code><p></code> element can refer to.
|
||||||
event. And the <code>{{my-name.value}}</code> binds the text node of the <code><p></code> element to the
|
The <code>(keyup)</code> tells Angular to trigger updates when it gets a keyup
|
||||||
|
event. And <code>{{myname.value}}</code> binds the text node of the
|
||||||
|
<code><p></code> element to the
|
||||||
input's value property.
|
input's value property.
|
||||||
p Let's do something a little more complex where users enter items and add them to a list like this:
|
|
||||||
|
p.
|
||||||
|
Let's do something a little more complex, where the user enters items
|
||||||
|
that the app adds to a list:
|
||||||
figure.image-display
|
figure.image-display
|
||||||
img(src='user-input-example1.png')
|
img(src='user-input-example1.png')
|
||||||
|
|
||||||
|
|
||||||
.l-main-section
|
.l-main-section
|
||||||
h2#section-create-an-array-property Create an array property
|
h2#section-create-an-array-property Create a list property
|
||||||
p.
|
p.
|
||||||
With the default bootstrapping in place, create a TodoController class that will manage interactions with the
|
With the default files in place,
|
||||||
list. Inside TodoController, add an array with an initial list of items. Then add a method that pushes new items
|
create a TodoController class to manage interactions with the
|
||||||
on the array when called.
|
list. Inside TodoController, add a list with some initial items.
|
||||||
|
Then add a method that adds new items
|
||||||
|
to the list.
|
||||||
|
|
||||||
pre.prettyprint.linenums.lang-dart
|
pre.prettyprint.lang-dart
|
||||||
code.
|
code.
|
||||||
class TodoList {
|
class TodoList {
|
||||||
List<String> todos =
|
List<String> todos =
|
||||||
|
@ -43,20 +55,25 @@
|
||||||
addTodo(String todo) {
|
addTodo(String todo) {
|
||||||
todos.add(todo);
|
todos.add(todo);
|
||||||
}
|
}
|
||||||
|
}
|
||||||
|
|
||||||
.callout.is-helpful
|
.callout.is-helpful
|
||||||
header Production Best Practice
|
header Production Best Practice
|
||||||
p.
|
p.
|
||||||
As with the previous example, in a production application you will separate your model out into another class
|
As shown in the previous example, a production application you would
|
||||||
and inject it into <code>TodoController</code>. We've omitted it here for brevity.
|
separate the model out into another class
|
||||||
|
and inject it into <code>TodoController</code>.
|
||||||
|
We've omitted that here for brevity.
|
||||||
|
|
||||||
|
<br><br><!-- PENDING: fix formatting of main sections after callouts -->
|
||||||
|
|
||||||
.l-main-section
|
.l-main-section
|
||||||
h2#section-display-the-list-of-todos Display the list of todos
|
h2#section-display-the-list-of-todos Display the list of todos
|
||||||
p.
|
p.
|
||||||
Using the <code>*for</code> iterator, create an <code><li></code> for each item in the todos array and set
|
Using the <code>*for</code> iterator, create an <code><li></code> for each item in the todos list and set
|
||||||
its text to the value.
|
its text to the value.
|
||||||
|
|
||||||
pre.prettyprint.linenums.lang-html
|
pre.prettyprint.lang-html
|
||||||
code.
|
code.
|
||||||
<ul>
|
<ul>
|
||||||
<li *for="#todo of todos">
|
<li *for="#todo of todos">
|
||||||
|
@ -74,40 +91,60 @@
|
||||||
code.
|
code.
|
||||||
<input #todotext>
|
<input #todotext>
|
||||||
p.
|
p.
|
||||||
Lastly, specify the target of the click event binding as your controller's <code>addTodo()</code> method and pass
|
Specify the target of the click event binding as your controller's
|
||||||
it the value. Since you created a reference called <code>todotext</code>, you can get the value with
|
<code>addTodo()</code> method and pass
|
||||||
<code>todotext.value.</code>
|
it the value. Since you created a reference called <code>todotext</code>,
|
||||||
|
you can get the value with <code>todotext.value.</code>
|
||||||
|
|
||||||
pre.prettyprint.lang-html
|
pre.prettyprint.lang-html
|
||||||
code.
|
code.
|
||||||
<button (click)="addTodo(todotext.value)">Add Todo</button>
|
<button (click)="addTodo(todotext.value)">Add Todo</button>
|
||||||
|
|
||||||
p And then create the doneTyping() method on TodoList and handle adding the todo text.
|
p.
|
||||||
|
To make pressing Enter do something useful,
|
||||||
|
you can add a keyup event handler to the input field.
|
||||||
|
This event handler uses APIs defined in
|
||||||
|
<a href="https://api.dartlang.org/apidocs/channels/stable/dartdoc-viewer/dart:html">dart:html</a>,
|
||||||
|
so be sure to import that library.
|
||||||
|
|
||||||
pre.prettyprint.lang-dart
|
.code-box
|
||||||
|
pre.prettyprint.lang-dart(data-name="todo_list.dart")
|
||||||
code.
|
code.
|
||||||
|
// In the template:
|
||||||
|
<input #todotext (keyup)="doneTyping(\$event)">
|
||||||
|
|
||||||
|
// In the component controller class:
|
||||||
doneTyping(KeyboardEvent event) {
|
doneTyping(KeyboardEvent event) {
|
||||||
if (event.which == 13) {
|
if (event.keyCode == KeyCode.ENTER) {
|
||||||
InputElement e = event.target;
|
InputElement e = event.target;
|
||||||
addTodo(e.value);
|
addTodo(e.value);
|
||||||
e.value = null;
|
e.value = null;
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
pre.prettyprint.lang-dart(data-name="main.dart")
|
||||||
|
code.
|
||||||
|
library user_input;
|
||||||
|
|
||||||
|
import 'dart:html';
|
||||||
|
...
|
||||||
|
|
||||||
|
|
||||||
.l-main-section
|
.l-main-section
|
||||||
h2#section-final-code Final Code
|
h2#section-final-code Final code
|
||||||
p Here's the final <code>todo_list.dart</code>
|
|
||||||
pre.prettyprint.lang-dart
|
.code-box
|
||||||
|
pre.prettyprint.lang-dart(data-name="todo_list.dart")
|
||||||
code.
|
code.
|
||||||
|
// web/todo_list.dart
|
||||||
part of user_input;
|
part of user_input;
|
||||||
|
|
||||||
@Component(
|
@Component(
|
||||||
selector: 'todo-list'
|
selector: 'todo-list'
|
||||||
)
|
)
|
||||||
@View(
|
@View(
|
||||||
// Without r before ''' (a raw string), $event breaks Angular!
|
// Without r before ''' (a raw string), $event breaks Angular.
|
||||||
// An alternative is to use \$event instead.
|
// An alternative to a raw string is to use \$event instead.
|
||||||
template: '''
|
template: r'''
|
||||||
<ul>
|
<ul>
|
||||||
<li *for="#todo of todos">
|
<li *for="#todo of todos">
|
||||||
{{ todo }}
|
{{ todo }}
|
||||||
|
@ -128,10 +165,52 @@
|
||||||
}
|
}
|
||||||
|
|
||||||
doneTyping(KeyboardEvent event) {
|
doneTyping(KeyboardEvent event) {
|
||||||
if (event.which == 13) {
|
if (event.keyCode == KeyCode.ENTER) {
|
||||||
InputElement e = event.target;
|
InputElement e = event.target;
|
||||||
addTodo(e.value);
|
addTodo(e.value);
|
||||||
e.value = null;
|
e.value = null;
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
pre.prettyprint.lang-dart(data-name="main.dart")
|
||||||
|
code.
|
||||||
|
// web/main.dart
|
||||||
|
library user_input;
|
||||||
|
|
||||||
|
import 'dart:html';
|
||||||
|
|
||||||
|
import 'package:angular2/angular2.dart';
|
||||||
|
import 'package:angular2/src/reflection/reflection.dart' show reflector;
|
||||||
|
import 'package:angular2/src/reflection/reflection_capabilities.dart' show ReflectionCapabilities;
|
||||||
|
|
||||||
|
part 'todo_list.dart';
|
||||||
|
|
||||||
|
main() {
|
||||||
|
reflector.reflectionCapabilities = new ReflectionCapabilities();
|
||||||
|
bootstrap(TodoList);
|
||||||
|
}
|
||||||
|
pre.prettyprint.lang-html(data-name="html")
|
||||||
|
code.
|
||||||
|
<!-- web/index.html -->
|
||||||
|
<!DOCTYPE html>
|
||||||
|
<html>
|
||||||
|
<head>
|
||||||
|
<link rel="stylesheet" href="style.css">
|
||||||
|
</head>
|
||||||
|
<body>
|
||||||
|
|
||||||
|
<todo-list></todo-list>
|
||||||
|
|
||||||
|
<script type="application/dart" src="main.dart"></script>
|
||||||
|
<script src="packages/browser/dart.js"></script>
|
||||||
|
</body>
|
||||||
|
</html>
|
||||||
|
pre.prettyprint.lang-yaml(data-name="yaml")
|
||||||
|
code.
|
||||||
|
# pubspec.yaml
|
||||||
|
name: user_input
|
||||||
|
description: Dart version of Angular 2 example, Responding to User Input
|
||||||
|
version: 0.0.1
|
||||||
|
dependencies:
|
||||||
|
angular2: 2.0.0-alpha.20
|
||||||
|
browser: any
|
||||||
|
|
|
@ -4,7 +4,7 @@
|
||||||
header Developer Preview
|
header Developer Preview
|
||||||
p.
|
p.
|
||||||
The Angular 2.0 API is currently in active development and not production ready.
|
The Angular 2.0 API is currently in active development and not production ready.
|
||||||
This page will showcase a preview of proposed methods to help further the discussion
|
This page showcases a preview of proposed methods to help further the discussion
|
||||||
in the development community. If you're building a production app today, please
|
in the development community. If you're building a production app today, please
|
||||||
<a href="https://docs.angularjs.org/api">use Angular 1.X</a>.
|
<a href="https://docs.angularjs.org/api">use Angular 1.X</a>.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue