angular-cn/aio/content/guide/user-input.md

431 lines
18 KiB
Markdown
Raw Normal View History

# User Input
2017-03-31 19:57:13 -04:00
Merge remote-tracking branch 'en/master' into aio # Conflicts: # aio/content/guide/ajs-quick-reference.md # aio/content/guide/animations.md # aio/content/guide/aot-compiler.md # aio/content/guide/architecture.md # aio/content/guide/attribute-directives.md # aio/content/guide/bootstrapping.md # aio/content/guide/browser-support.md # aio/content/guide/cb-index.md # aio/content/guide/change-log.md # aio/content/guide/cheatsheet.md # aio/content/guide/cli-quickstart.md # aio/content/guide/component-interaction.md # aio/content/guide/component-styles.md # aio/content/guide/dependency-injection-in-action.md # aio/content/guide/dependency-injection.md # aio/content/guide/deployment.md # aio/content/guide/displaying-data.md # aio/content/guide/dynamic-component-loader.md # aio/content/guide/dynamic-form.md # aio/content/guide/form-validation.md # aio/content/guide/forms.md # aio/content/guide/glossary.md # aio/content/guide/hierarchical-dependency-injection.md # aio/content/guide/i18n.md # aio/content/guide/index.md # aio/content/guide/learning-angular.md # aio/content/guide/lifecycle-hooks.md # aio/content/guide/ngmodule-faq.md # aio/content/guide/ngmodule.md # aio/content/guide/npm-packages.md # aio/content/guide/pipes.md # aio/content/guide/quickstart.md # aio/content/guide/reactive-forms.md # aio/content/guide/router.md # aio/content/guide/security.md # aio/content/guide/server-communication.md # aio/content/guide/set-document-title.md # aio/content/guide/setup-systemjs-anatomy.md # aio/content/guide/setup.md # aio/content/guide/structural-directives.md # aio/content/guide/styleguide.md # aio/content/guide/template-syntax.md # aio/content/guide/testing.md # aio/content/guide/ts-to-js.md # aio/content/guide/typescript-configuration.md # aio/content/guide/upgrade.md # aio/content/guide/user-input.md # aio/content/guide/visual-studio-2015.md # aio/content/guide/webpack.md # aio/content/navigation.json # aio/content/tutorial/index.md # aio/content/tutorial/toh-pt1.md # aio/content/tutorial/toh-pt2.md # aio/content/tutorial/toh-pt3.md # aio/content/tutorial/toh-pt4.md # aio/content/tutorial/toh-pt5.md # aio/content/tutorial/toh-pt6.md # aio/package.json # aio/src/styles/main.scss # aio/transforms/angular.io-package/index.js
2017-07-29 12:03:22 -04:00
# 用户输入
2017-03-31 19:57:13 -04:00
User actions such as clicking a link, pushing a button, and entering
text raise DOM events.
This page explains how to bind those events to component event handlers using the Angular
event binding syntax.
当用户点击链接、按下按钮或者输入文字时,这些用户动作都会产生 DOM 事件。
本章解释如何使用 Angular 事件绑定语法把这些事件绑定到事件处理器。
Run the <live-example></live-example>.
2017-03-31 19:57:13 -04:00
运行<live-example></live-example>
## Binding to user input events
## 绑定到用户输入事件
2017-03-31 19:57:13 -04:00
You can use [Angular event bindings](guide/template-syntax#event-binding)
to respond to any [DOM event](https://developer.mozilla.org/en-US/docs/Web/Events).
Many DOM events are triggered by user input. Binding to these events provides a way to
get input from the user.
你可以使用 [Angular 事件绑定](guide/template-syntax#event-binding)机制来响应任何 [DOM 事件](https://developer.mozilla.org/en-US/docs/Web/Events)。
许多 DOM 事件是由用户输入触发的。绑定这些事件可以获取用户输入。
To bind to a DOM event, surround the DOM event name in parentheses and assign a quoted
2017-03-31 19:57:13 -04:00
[template statement](guide/template-syntax#template-statements) to it.
要绑定 DOM 事件,只要把 DOM 事件的名字包裹在圆括号中,然后用放在引号中的[模板语句](guide/template-syntax#template-statements)对它赋值就可以了。
The following example shows an event binding that implements a click handler:
下例展示了一个事件绑定,它实现了一个点击事件处理器:
2017-03-31 19:57:13 -04:00
<code-example path="user-input/src/app/click-me.component.ts" region="click-me-button" title="src/app/click-me.component.ts" linenums="false">
</code-example>
2017-03-31 19:57:13 -04:00
{@a click}
The `(click)` to the left of the equals sign identifies the button's click event as the **target of the binding**.
The text in quotes to the right of the equals sign
2018-03-03 08:06:01 -05:00
is the **template statement**, which responds
to the click event by calling the component's `onClickMe` method.
等号左边的 `(click)` 表示把按钮的点击事件作为**绑定目标**。
等号右边引号中的文本是**模板语句**,通过调用组件的 `onClickMe` 方法来响应这个点击事件。
When writing a binding, be aware of a template statement's **execution context**.
The identifiers in a template statement belong to a specific context object,
usually the Angular component controlling the template.
The example above shows a single line of HTML, but that HTML belongs to a larger component:
写绑定时,需要知道模板语句的**执行上下文**。
出现在模板语句中的每个标识符都属于特定的上下文对象。
这个对象通常都是控制此模板的 Angular 组件。
上例中只显示了一行 HTML那段 HTML 片段属于下面这个组件:
2017-03-31 19:57:13 -04:00
<code-example path="user-input/src/app/click-me.component.ts" region="click-me-component" title="src/app/click-me.component.ts" linenums="false">
</code-example>
When the user clicks the button, Angular calls the `onClickMe` method from `ClickMeComponent`.
当用户点击按钮时Angular 调用 `ClickMeComponent``onClickMe` 方法。
2017-03-31 19:57:13 -04:00
## Get user input from the $event object
## 通过 $event 对象取得用户输入
DOM events carry a payload of information that may be useful to the component.
This section shows how to bind to the `keyup` event of an input box to get the user's input after each keystroke.
DOM 事件可以携带可能对组件有用的信息。
本节将展示如何绑定输入框的 `keyup` 事件,在每个敲击键盘时获取用户输入。
The following code listens to the `keyup` event and passes the entire event payload (`$event`) to the component event handler.
下面的代码监听 `keyup` 事件,并将整个事件载荷 (`$event`) 传递给组件的事件处理器。
2017-03-31 19:57:13 -04:00
<code-example path="user-input/src/app/keyup.components.ts" region="key-up-component-1-template" title="src/app/keyup.components.ts (template v.1)" linenums="false">
</code-example>
When a user presses and releases a key, the `keyup` event occurs, and Angular provides a corresponding
DOM event object in the `$event` variable which this code passes as a parameter to the component's `onKey()` method.
当用户按下并释放一个按键时,触发 `keyup` 事件Angular 在 `$event` 变量提供一个相应的 DOM
事件对象,上面的代码将它作为参数传递给 `onKey()` 方法。
<code-example path="user-input/src/app/keyup.components.ts" region="key-up-component-1-class-no-type" title="src/app/keyup.components.ts (class v.1)" linenums="false">
</code-example>
The properties of an `$event` object vary depending on the type of DOM event. For example,
a mouse event includes different information than an input box editing event.
`$event` 对象的属性取决于 DOM 事件的类型。例如,鼠标事件与输入框编辑事件包含了不同的信息。
All [standard DOM event objects](https://developer.mozilla.org/en-US/docs/Web/API/Event)
have a `target` property, a reference to the element that raised the event.
In this case, `target` refers to the [`<input>` element](https://developer.mozilla.org/en-US/docs/Web/API/HTMLInputElement) and
`event.target.value` returns the current contents of that element.
所有[标准 DOM 事件对象](https://developer.mozilla.org/en-US/docs/Web/API/Event)都有一个 `target` 属性,
引用触发该事件的元素。
在本例中,`target` 是[`<input>` 元素](https://developer.mozilla.org/en-US/docs/Web/API/HTMLInputElement)
`event.target.value` 返回该元素的当前内容。
After each call, the `onKey()` method appends the contents of the input box value to the list
in the component's `values` property, followed by a separator character (|).
2017-03-31 19:57:13 -04:00
The [interpolation](guide/template-syntax#interpolation)
displays the accumulating input box changes from the `values` property.
在组件的 `onKey()` 方法中,把输入框的值和分隔符 (|) 追加组件的 `values` 属性。
使用[插值表达式](guide/template-syntax#interpolation)来把存放累加结果的 `values` 属性回显到屏幕上。
Suppose the user enters the letters "abc", and then backspaces to remove them one by one.
Here's what the UI displays:
假设用户输入字母“abc”然后用退格键一个一个删除它们。
用户界面将显示:
<code-example>
2018-03-03 08:06:01 -05:00
a | ab | abc | ab | a | |
</code-example>
docs(aio): image sweep (#16609) * fix(aio): allow code blocks to clear floated images Previously the negative margin on the code headings were causing floated images to overlay the start of a code block. Now all code block successfully clear all floated elements. * feat(aio): add a `.clear` class for clearing floating images * fix(aio): tidy up image styles The css rules for `img.right` and `img.left` allow authors easy access to floating an image on the left or right, respectively. The `.image-display` rule which was always found on a figure has been simplified so that all figures have this styling. It is very unlikely that a figure will be used outside the content area; and at this time it seems like `figure` is as good an indicator that we want this kind of styling as anything. Now that images are all tagged with width and height values, we cannot assume to modify these dimensions via CSS as it can cause the image to lose its correct proportions. Until we find a better solition we must set `height` to `auto` when the screen width is below 1300px to ensure that these images maintain their proportions as they get shrunk to fit. * docs(aio): general tidy up of image HTML in guides Previously, the guides have a lot of inline image styling and unnecessary use of the `image-display` css class. Images over 700px are problematic for guide docs, so those have been given specific widths and associated heights. * docs(aio): use correct anchor for "back to the top" link The `#toc` anchor does not work when the page is wide enough that the TOC is floating to the side. * build(aio): add `#top-of-page` to path variants for link checking Since the `#top-of-page` is outside the rendered docs the `checkAnchorLinks` processor doesn't find them as valid targets for links. Adding them as a `pathVariant` solves this problem but will still catch links to docs that do not actually exist. * fix(aio): ensure that headings clear floated images * fix(aio): do not force live-example embedded image to 100% size This made them look too big, generally. Leaving them with no size means that they will look reasonable in large viewports and switch to 100% width in narrow viewports.
2017-05-09 18:53:32 -04:00
<figure>
2018-03-03 08:06:01 -05:00
<img src='generated/images/guide/user-input/keyup1-anim.gif' alt="key up 1">
</figure>
<div class="alert is-helpful">
Alternatively, you could accumulate the individual keys themselves by substituting `event.key`
for `event.target.value` in which case the same user input would produce:
或者,你可以用 `event.key` 替代 `event.target.value`,积累各个按键本身,这样同样的用户输入可以产生:
<code-example>
2017-03-31 19:57:13 -04:00
a | b | c | backspace | backspace | backspace |
</code-example>
2017-04-10 11:51:13 -04:00
</div>
{@a keyup1}
2017-03-31 19:57:13 -04:00
### Type the _$event_
### *$event*的类型
The example above casts the `$event` as an `any` type.
That simplifies the code at a cost.
There is no type information
that could reveal properties of the event object and prevent silly mistakes.
上例将 `$event` 转换为 `any` 类型。
这样简化了代码,但是有成本。
没有任何类型信息能够揭示事件对象的属性,防止简单的错误。
The following example rewrites the method with types:
下面的例子,使用了带类型方法:
2017-03-31 19:57:13 -04:00
<code-example path="user-input/src/app/keyup.components.ts" region="key-up-component-1-class" title="src/app/keyup.components.ts (class v.1 - typed )" linenums="false">
</code-example>
The `$event` is now a specific `KeyboardEvent`.
Not all elements have a `value` property so it casts `target` to an input element.
The `OnKey` method more clearly expresses what it expects from the template and how it interprets the event.
`$event` 的类型现在是 `KeyboardEvent`
不是所有的元素都有 `value` 属性,所以它将 `target` 转换为输入元素。
2018-08-05 00:03:58 -04:00
`OnKey` 方法更加清晰地表达了它期望从模板得到什么,以及它是如何解析事件的。
### Passing _$event_ is a dubious practice
### 传入 *$event* 是靠不住的做法
Typing the event object reveals a significant objection to passing the entire DOM event into the method:
the component has too much awareness of the template details.
It can't extract information without knowing more than it should about the HTML implementation.
That breaks the separation of concerns between the template (_what the user sees_)
and the component (_how the application processes user data_).
类型化事件对象揭露了重要的一点,即反对把整个 DOM 事件传到方法中,因为这样组件会知道太多模板的信息。
只有当它知道更多它本不应了解的 HTML 实现细节时,它才能提取信息。
这就违反了模板(*用户看到的*)和组件(*应用如何处理用户数据*)之间的分离关注原则。
The next section shows how to use template reference variables to address this problem.
下面将介绍如何用模板引用变量来解决这个问题。
## Get user input from a template reference variable
## 从一个模板引用变量中获得用户输入
There's another way to get the user data: use Angular
2017-03-31 19:57:13 -04:00
[**template reference variables**](guide/template-syntax#ref-vars).
These variables provide direct access to an element from within the template.
To declare a template reference variable, precede an identifier with a hash (or pound) character (#).
还有另一种获取用户数据的方式:使用 Angular 的[**模板引用变量**](guide/template-syntax#ref-vars)。
这些变量提供了从模块中直接访问元素的能力。
在标识符前加上井号 (#) 就能声明一个模板引用变量。
The following example uses a template reference variable
to implement a keystroke loopback in a simple template.
下面的例子使用了局部模板变量,在一个超简单的模板中实现按键反馈功能。
2017-03-31 19:57:13 -04:00
<code-example path="user-input/src/app/loop-back.component.ts" region="loop-back-component" title="src/app/loop-back.component.ts" linenums="false">
</code-example>
The template reference variable named `box`, declared on the `<input>` element,
refers to the `<input>` element itself.
The code uses the `box` variable to get the input element's `value` and display it
with interpolation between `<p>` tags.
这个模板引用变量名叫 `box`,在 `<input>` 元素声明,它引用 `<input>` 元素本身。
代码使用 `box` 获得输入元素的 `value` 值,并通过插值表达式把它显示在 `<p>` 标签中。
The template is completely self contained. It doesn't bind to the component,
and the component does nothing.
这个模板完全是完全自包含的。它没有绑定到组件,组件也没做任何事情。
Type something in the input box, and watch the display update with each keystroke.
在输入框中输入,就会看到每次按键时,显示也随之更新了。
docs(aio): image sweep (#16609) * fix(aio): allow code blocks to clear floated images Previously the negative margin on the code headings were causing floated images to overlay the start of a code block. Now all code block successfully clear all floated elements. * feat(aio): add a `.clear` class for clearing floating images * fix(aio): tidy up image styles The css rules for `img.right` and `img.left` allow authors easy access to floating an image on the left or right, respectively. The `.image-display` rule which was always found on a figure has been simplified so that all figures have this styling. It is very unlikely that a figure will be used outside the content area; and at this time it seems like `figure` is as good an indicator that we want this kind of styling as anything. Now that images are all tagged with width and height values, we cannot assume to modify these dimensions via CSS as it can cause the image to lose its correct proportions. Until we find a better solition we must set `height` to `auto` when the screen width is below 1300px to ensure that these images maintain their proportions as they get shrunk to fit. * docs(aio): general tidy up of image HTML in guides Previously, the guides have a lot of inline image styling and unnecessary use of the `image-display` css class. Images over 700px are problematic for guide docs, so those have been given specific widths and associated heights. * docs(aio): use correct anchor for "back to the top" link The `#toc` anchor does not work when the page is wide enough that the TOC is floating to the side. * build(aio): add `#top-of-page` to path variants for link checking Since the `#top-of-page` is outside the rendered docs the `checkAnchorLinks` processor doesn't find them as valid targets for links. Adding them as a `pathVariant` solves this problem but will still catch links to docs that do not actually exist. * fix(aio): ensure that headings clear floated images * fix(aio): do not force live-example embedded image to 100% size This made them look too big, generally. Leaving them with no size means that they will look reasonable in large viewports and switch to 100% width in narrow viewports.
2017-05-09 18:53:32 -04:00
<figure>
2018-03-03 08:06:01 -05:00
<img src='generated/images/guide/user-input/keyup-loop-back-anim.gif' alt="loop back">
</figure>
<div class="alert is-helpful">
**This won't work at all unless you bind to an event**.
**除非你绑定一个事件,否则这将完全无法工作。**
Angular updates the bindings (and therefore the screen)
only if the app does something in response to asynchronous events, such as keystrokes.
This example code binds the `keyup` event
to the number 0, the shortest template statement possible.
While the statement does nothing useful,
it satisfies Angular's requirement so that Angular will update the screen.
2018-03-03 08:06:01 -05:00
只有在应用做了些异步事件如击键Angular 才更新绑定(并最终影响到屏幕)。
本例代码将 `keyup` 事件绑定到了数字 0这可能是最短的模板语句了。
虽然这个语句不做什么,但它满足 Angular 的要求,所以 Angular 将更新屏幕。
2017-04-10 11:51:13 -04:00
</div>
It's easier to get to the input box with the template reference
variable than to go through the `$event` object. Here's a rewrite of the previous
`keyup` example that uses a template reference variable to get the user's input.
从模板变量获得输入框比通过 `$event` 对象更加简单。
下面的代码重写了之前 `keyup` 示例,它使用变量来获得用户输入。
2017-03-31 19:57:13 -04:00
<code-example path="user-input/src/app/keyup.components.ts" region="key-up-component-2" title="src/app/keyup.components.ts (v2)" linenums="false">
</code-example>
A nice aspect of this approach is that the component gets clean data values from the view.
It no longer requires knowledge of the `$event` and its structure.
这个方法最漂亮的一点是:组件代码从视图中获得了干净的数据值。再也不用了解 `$event` 变量及其结构了。
2017-03-31 19:57:13 -04:00
2018-03-03 08:06:01 -05:00
{@a key-event}
2017-03-31 19:57:13 -04:00
## Key event filtering (with `key.enter`)
## 按键事件过滤(通过 `key.enter`
The `(keyup)` event handler hears *every keystroke*.
Sometimes only the _Enter_ key matters, because it signals that the user has finished typing.
One way to reduce the noise would be to examine every `$event.keyCode` and take action only when the key is _Enter_.
`(keyup)` 事件处理器监听*每一次按键*。
有时只在意*回车*键,因为它标志着用户结束输入。
解决这个问题的一种方法是检查每个 `$event.keyCode`,只有键值是*回车*键时才采取行动。
There's an easier way: bind to Angular's `keyup.enter` pseudo-event.
Then Angular calls the event handler only when the user presses _Enter_.
更简单的方法是:绑定到 Angular 的 `keyup.enter` 模拟事件。
然后,只有当用户敲*回车*键时Angular 才会调用事件处理器。
2017-03-31 19:57:13 -04:00
<code-example path="user-input/src/app/keyup.components.ts" region="key-up-component-3" title="src/app/keyup.components.ts (v3)" linenums="false">
</code-example>
Here's how it works.
下面展示了它是如何工作的。
docs(aio): image sweep (#16609) * fix(aio): allow code blocks to clear floated images Previously the negative margin on the code headings were causing floated images to overlay the start of a code block. Now all code block successfully clear all floated elements. * feat(aio): add a `.clear` class for clearing floating images * fix(aio): tidy up image styles The css rules for `img.right` and `img.left` allow authors easy access to floating an image on the left or right, respectively. The `.image-display` rule which was always found on a figure has been simplified so that all figures have this styling. It is very unlikely that a figure will be used outside the content area; and at this time it seems like `figure` is as good an indicator that we want this kind of styling as anything. Now that images are all tagged with width and height values, we cannot assume to modify these dimensions via CSS as it can cause the image to lose its correct proportions. Until we find a better solition we must set `height` to `auto` when the screen width is below 1300px to ensure that these images maintain their proportions as they get shrunk to fit. * docs(aio): general tidy up of image HTML in guides Previously, the guides have a lot of inline image styling and unnecessary use of the `image-display` css class. Images over 700px are problematic for guide docs, so those have been given specific widths and associated heights. * docs(aio): use correct anchor for "back to the top" link The `#toc` anchor does not work when the page is wide enough that the TOC is floating to the side. * build(aio): add `#top-of-page` to path variants for link checking Since the `#top-of-page` is outside the rendered docs the `checkAnchorLinks` processor doesn't find them as valid targets for links. Adding them as a `pathVariant` solves this problem but will still catch links to docs that do not actually exist. * fix(aio): ensure that headings clear floated images * fix(aio): do not force live-example embedded image to 100% size This made them look too big, generally. Leaving them with no size means that they will look reasonable in large viewports and switch to 100% width in narrow viewports.
2017-05-09 18:53:32 -04:00
<figure>
2018-03-03 08:06:01 -05:00
<img src='generated/images/guide/user-input/keyup3-anim.gif' alt="key up 3">
</figure>
2017-03-31 19:57:13 -04:00
## On blur
## 失去焦点事件 (blur)
In the previous example, the current state of the input box
is lost if the user mouses away and clicks elsewhere on the page
without first pressing _Enter_.
The component's `value` property is updated only when the user presses _Enter_.
前上例中,如果用户没有先按回车键,而是移开了鼠标,点击了页面中其它地方,输入框的当前值就会丢失。
只有当用户按下了回车键候,组件的 `values` 属性才能更新。
To fix this issue, listen to both the _Enter_ key and the _blur_ event.
下面通过同时监听输入框的回车键和失去焦点事件来修正这个问题。
2017-03-31 19:57:13 -04:00
<code-example path="user-input/src/app/keyup.components.ts" region="key-up-component-4" title="src/app/keyup.components.ts (v4)" linenums="false">
</code-example>
## Put it all together
## 把它们放在一起
The previous page showed how to [display data](guide/displaying-data).
This page demonstrated event binding techniques.
上一章介绍了如何[显示数据](guide/displaying-data)。
本章展示了事件绑定技术。
Now, put it all together in a micro-app
that can display a list of heroes and add new heroes to the list.
The user can add a hero by typing the hero's name in the input box and
clicking **Add**.
现在,在一个微型应用中一起使用它们,应用能显示一个英雄列表,并把新的英雄加到列表中。
用户可以通过输入英雄名和点击“添加”按钮来添加英雄。
docs(aio): image sweep (#16609) * fix(aio): allow code blocks to clear floated images Previously the negative margin on the code headings were causing floated images to overlay the start of a code block. Now all code block successfully clear all floated elements. * feat(aio): add a `.clear` class for clearing floating images * fix(aio): tidy up image styles The css rules for `img.right` and `img.left` allow authors easy access to floating an image on the left or right, respectively. The `.image-display` rule which was always found on a figure has been simplified so that all figures have this styling. It is very unlikely that a figure will be used outside the content area; and at this time it seems like `figure` is as good an indicator that we want this kind of styling as anything. Now that images are all tagged with width and height values, we cannot assume to modify these dimensions via CSS as it can cause the image to lose its correct proportions. Until we find a better solition we must set `height` to `auto` when the screen width is below 1300px to ensure that these images maintain their proportions as they get shrunk to fit. * docs(aio): general tidy up of image HTML in guides Previously, the guides have a lot of inline image styling and unnecessary use of the `image-display` css class. Images over 700px are problematic for guide docs, so those have been given specific widths and associated heights. * docs(aio): use correct anchor for "back to the top" link The `#toc` anchor does not work when the page is wide enough that the TOC is floating to the side. * build(aio): add `#top-of-page` to path variants for link checking Since the `#top-of-page` is outside the rendered docs the `checkAnchorLinks` processor doesn't find them as valid targets for links. Adding them as a `pathVariant` solves this problem but will still catch links to docs that do not actually exist. * fix(aio): ensure that headings clear floated images * fix(aio): do not force live-example embedded image to 100% size This made them look too big, generally. Leaving them with no size means that they will look reasonable in large viewports and switch to 100% width in narrow viewports.
2017-05-09 18:53:32 -04:00
<figure>
2018-03-03 08:06:01 -05:00
<img src='generated/images/guide/user-input/little-tour-anim.gif' alt="Little Tour of Heroes">
</figure>
2017-03-31 19:57:13 -04:00
Below is the "Little Tour of Heroes" component.
下面就是“简版英雄指南”组件。
2017-03-31 19:57:13 -04:00
<code-example path="user-input/src/app/little-tour.component.ts" region="little-tour" title="src/app/little-tour.component.ts" linenums="false">
</code-example>
### Observations
### 小结
* **Use template variables to refer to elements** &mdash;
The `newHero` template variable refers to the `<input>` element.
You can reference `newHero` from any sibling or child of the `<input>` element.
**使用模板变量来引用元素** &mdash; `newHero` 模板变量引用了 `<input>` 元素。
你可以在 `<input>` 的任何兄弟或子级元素中引用 `newHero`
* **Pass values, not elements** &mdash;
Instead of passing the `newHero` into the component's `addHero` method,
get the input box value and pass *that* to `addHero`.
2018-03-03 08:06:01 -05:00
**传递数值,而非元素** &mdash;
获取输入框的值并将*它*传递给组件的 `addHero`,而不要传递 `newHero`
* **Keep template statements simple** &mdash;
The `(blur)` event is bound to two JavaScript statements.
The first statement calls `addHero`. The second statement, `newHero.value=''`,
clears the input box after a new hero is added to the list.
2018-03-03 08:06:01 -05:00
**保持模板语句简单** &mdash;
`(blur)` 事件被绑定到两个 JavaScript 语句。
第一句调用 `addHero`。第二句 `newHero.value=''` 在添加新英雄到列表中后清除输入框。
## Source code
## 源代码
Following is all the code discussed in this page.
下面是本章讨论过的所有源码。
<code-tabs>
<code-pane title="click-me.component.ts" path="user-input/src/app/click-me.component.ts">
</code-pane>
<code-pane title="keyup.components.ts" path="user-input/src/app/keyup.components.ts">
</code-pane>
<code-pane title="loop-back.component.ts" path="user-input/src/app/loop-back.component.ts">
</code-pane>
<code-pane title="little-tour.component.ts" path="user-input/src/app/little-tour.component.ts">
</code-pane>
</code-tabs>
## Summary
## 小结
You have mastered the basic primitives for responding to user input and gestures.
你已经掌握了响应用户输入和操作的基础技术。
These techniques are useful for small-scale demonstrations, but they
quickly become verbose and clumsy when handling large amounts of user input.
Two-way data binding is a more elegant and compact way to move
values between data entry fields and model properties.
The next page, `Forms`, explains how to write
two-way bindings with `NgModel`.
这些技术对小规模演示很实用,但是在处理大量用户输入时,很容易变得累赘和笨拙。
要在数据录入字段和模型属性之间传递数据,双向数据绑定是更加优雅和简洁的方式。
下一章 ` 表单 ` 解释了如何用 `NgModel` 来进行双向绑定。