-
Notifications
You must be signed in to change notification settings - Fork 177
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Eric X
committed
Aug 6, 2022
1 parent
8a5128a
commit 1e84ad4
Showing
4 changed files
with
28 additions
and
61 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,40 +1,28 @@ | ||
<!-- A component is a program that runs on Fuchsia in its own sandbox. | ||
A component is a program that runs on Fuchsia in its own sandbox. | ||
Each component is a composable module that interacts with other components | ||
through their capabilities. All software on Fuchsia is defined as a component | ||
except for the kernel image, bootstrapping processes, and the Component Manager. --> | ||
一个组件是一个运行在 Fuchsia 沙盒中的程序。每个组件都是一个可组合的模块,依据各自功能与其它组件交互。 | ||
Fuchsia 中的所有软件都被定义为一个个组件,除了内核、引导进程以及组件管理器。 | ||
except for the kernel image, bootstrapping processes, and the Component Manager. | ||
|
||
<!-- Fuchsia's component framework is responsible for running nearly all user space | ||
Fuchsia's component framework is responsible for running nearly all user space | ||
software in the system. The Component Manager is a system process that coordinates | ||
the execution and lifecycle of all component instances, maintains the component | ||
topology, provides components with their capabilities, and keeps them isolated | ||
from one another. --> | ||
Fuchsia 的组件框架致力于让系统可以运行几乎所有的用户空间软件。 | ||
组件管理器是一个系统进程,负责协调各个组件实例的执行和生命周期,维护组件拓扑,给组件提供相应功能,并使它们彼此隔离。 | ||
from one another. | ||
|
||
<!-- Components obtain privileges to access various parts of the wider system through | ||
Components obtain privileges to access various parts of the wider system through | ||
capabilities. Each component can declare new capabilities that they offer to the | ||
system and capabilities provided by other components (or the framework) that | ||
they require to function. Component Manager resolves and validates all capability | ||
requests between components to ensure they match capabilities that the component | ||
has been properly granted. --> | ||
组件通过功能获得访问更广泛系统的各个部分的特权。 | ||
每个组件都可以声明它们提供给系统的新功能以及需要其他组件(或框架)提供的功能。 | ||
组件管理器解析并验证组件之间的所有功能请求,以确保它们与组件已被正确授予的功能相匹配。 | ||
has been properly granted. | ||
|
||
<aside class="key-point"> | ||
<!-- <b>Legacy components</b> --> | ||
<b>旧版组件</b> | ||
<b>Legacy components</b> | ||
|
||
<!-- <p>This section focuses on modern components whose manifest declarations are | ||
<p>This section focuses on modern components whose manifest declarations are | ||
written in component manifest language (CML). The legacy framework based on | ||
<code>appmgr</code> and declared using CMX manifests is not covered here. --> | ||
<p>本节重点介绍使用组件清单语言 (CML) 编写清单声明的现代组件。 | ||
此处未介绍基于 <code>appmgr</code> 并使用 CMX 清单声明的旧框架。 | ||
<code>appmgr</code> and declared using CMX manifests is not covered here. | ||
|
||
<!-- <p>For more details on the legacy component framework, see | ||
<a href="/concepts/components/v1">legacy components</a>. --> | ||
<p>有关旧版组件的更多详细信息,请参看 | ||
<a href="/concepts/components/v1">旧版组件</a>. | ||
<p>For more details on the legacy component framework, see | ||
<a href="/concepts/components/v1">legacy components</a>. | ||
</aside> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,20 +1,13 @@ | ||
<!-- ## Driver framework --> | ||
## 驱动框架 | ||
## Driver framework | ||
|
||
<!-- Similar to session, the Fuchsia Driver Framework enables developers to | ||
Similar to session, the Fuchsia Driver Framework enables developers to | ||
implement product-specific device drivers as components. Some driver components | ||
represent hardware interface controllers, such as PCI or USB, while others | ||
interact with end devices, such as an ethernet controller or keyboard. --> | ||
与 session 类似,Fuchsia 驱动框架使开发人员能够将产品特定的设备驱动程序实现为组件。 | ||
一些驱动程序组件代表硬件接口控制器,例如 PCI 或 USB,而其他驱动程序组件则与终端设备交互, | ||
例如以太网控制器或键盘。 | ||
interact with end devices, such as an ethernet controller or keyboard. | ||
|
||
<!-- As devices are discovered or attached to the system, the `driver_manager` | ||
As devices are discovered or attached to the system, the `driver_manager` | ||
platform component starts the necessary driver components, binds them to the | ||
hardware interfaces, and manages their lifecycle. --> | ||
当设备被发现或连接到系统时,`driver_manager` 平台组件启动必要的驱动程序组件, | ||
将它们绑定到硬件接口,并管理它们的生命周期。 | ||
hardware interfaces, and manages their lifecycle. | ||
|
||
<!-- Note: For more details on the driver framework, see | ||
[Fuchsia Driver Framework](/development/drivers/concepts/fdf.md). --> | ||
注:有关驱动框架的细节,参考[Fuchsia 驱动框架](/development/drivers/concepts/fdf.md). | ||
Note: For more details on the driver framework, see | ||
[Fuchsia Driver Framework](/development/drivers/concepts/fdf.md). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,16 +1,10 @@ | ||
<!-- Components form the basis for the software that runs in Fuchsia user space. The | ||
Components form the basis for the software that runs in Fuchsia user space. The | ||
components you've explored so far are part of the core platform that is | ||
generally common to all products running Fuchsia. Fuchsia products are composed | ||
of platform components and product-specific elements to serve the unique needs | ||
of the device hardware and user experience. In this section, you'll explore how | ||
Fuchsia builds on components to enable product-level customization. --> | ||
组件构成了在 Fuchsia 用户空间中运行的软件的基础。 | ||
到目前为止,您探索的组件是运行 Fuchsia 的所有产品通用的核心平台的一部分。 | ||
Fuchsia 产品由平台组件和产品特定元素组成,以满足设备硬件和用户体验的独特需求。 | ||
在本节中,您将探索 Fuchsia 如何构建组件以实现产品级定制。 | ||
Fuchsia builds on components to enable product-level customization. | ||
|
||
<!-- ![Data table showing how Fuchsia enables product customization on top of the | ||
![Data table showing how Fuchsia enables product customization on top of the | ||
core platform through the Session Framework and Driver Framework.] | ||
(/get-started/images/components/product.png){: width="582"} --> | ||
![数据表展现了 Fuchsia 通过会话框架和驱动框架让产品在核心平台上的定制成为可能.] | ||
(/get-started/images/components/product.png){: width="582"} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,23 +1,15 @@ | ||
<!-- ## Session framework --> | ||
## Session 框架 | ||
## Session framework | ||
|
||
<!-- Sessions are components that encapsulate a product’s user experience. The | ||
Sessions are components that encapsulate a product’s user experience. The | ||
session framework serves as a boundary between the Fuchsia platform and the | ||
product-level user interaction. Each Fuchsia product defines a single session | ||
instance as the root of the product experience, which may or may not manage | ||
additional child components. --> | ||
会话是一系列封装了产品用户体验的组件。会话框架充当 Fuchsia 平台和产品级用户交互之间的边界。 | ||
每个 Fuchsia 产品都将单个会话实例定义为产品体验的根,并可能管理其他子组件。 | ||
additional child components. | ||
|
||
|
||
<!-- The `session_manager` platform component starts the session component on boot | ||
The `session_manager` platform component starts the session component on boot | ||
and offers it a fixed set of capabilities necessary to support the session | ||
framework APIs for elements such as window management, input event handling, or | ||
accessibility. --> | ||
`session_manager` 平台组件在启动时打开会话组件,并为其提供一组固定的功能,以支持诸如窗口管理、 | ||
输入事件处理或可访问元素的会话框架 API. | ||
accessibility. | ||
|
||
<!-- Note: For more details on the session framework, see | ||
[Introduction to the session framework](/concepts/session/introduction.md). --> | ||
注: 有关会话框架的更多细节,请参考 | ||
[会话框架介绍](/concepts/session/introduction.md). | ||
Note: For more details on the session framework, see | ||
[Introduction to the session framework](/concepts/session/introduction.md). |