diff --git a/en/application-dev/reference/arkui-js/js-components-svg-animatetransform.md b/en/application-dev/reference/arkui-js/js-components-svg-animatetransform.md index 4b4cf63bcb25cd7e8a7abc010ae91af3bb308ad6..1cb9c1f4eb4520ab4e85193353fd0798d23158ca 100644 --- a/en/application-dev/reference/arkui-js/js-components-svg-animatetransform.md +++ b/en/application-dev/reference/arkui-js/js-components-svg-animatetransform.md @@ -1,21 +1,22 @@ -# animateTransform +# animateTransform The **** component is used to apply a transform animation and supports the following components: , , , , , , , ->![](../../public_sys-resources/icon-note.gif) **NOTE:** +>**NOTE** +> >This component is supported since API version 7. Updates will be marked with a superscript to indicate their earliest API version. -## Required Permissions +## Required Permissions None -## Child Components +## Child Components Not supported -## Attributes +## Attributes The **animate** attributes and the attributes in the following table are supported. @@ -46,7 +47,7 @@ The **animate** attributes and the attributes in the following table are suppo -## Example +## Example ``` diff --git a/en/application-dev/ui/ui-ts-components.md b/en/application-dev/ui/ui-ts-components.md index 93c7604eaa72dc5a34848c518a91c0d1d0ba7454..deec9ebda22e4d0c68e05dc994fb0382a262b296 100644 --- a/en/application-dev/ui/ui-ts-components.md +++ b/en/application-dev/ui/ui-ts-components.md @@ -6,7 +6,7 @@ Before customizing a component, get to know what the [component and decorator](# ## Components and Decorators -In a declarative UI, all pages are composed of components. The data structure of the component is struct, and the decorator [@Component](ts-component-based-component.md) is the component-based flag. The struct decorated by @Component indicates that the struct has the component capability. +In a declarative UI, all pages are composed of components. The data structure of the component is struct, and the decorator @Component is the component-based flag. The struct decorated by @Component indicates that the struct has the component capability. The method for declaring a custom component is as follows: @@ -23,7 +23,7 @@ interface Builder { } ``` -The component decorated by [@Entry](../ui/ts-component-based-entry.md) is the main entry, or in other words, the root node, of the page. Note that a page must have one and only one @Entry. Only the @Entry decorated component and its child components are displayed on the page. +The component decorated by @Entry is the main entry, or in other words, the root node, of the page. Note that a page must have one and only one @Entry. Only the @Entry decorated component and its child components are displayed on the page. @Component and @Entry are basic and important decorators. To put it simply, a decorator assigns a capability to an object to be decorated. For example, @Entry assigns the capability of the page entry, and @Component assigns the component capability. diff --git a/en/contribute/template/js-template.md b/en/contribute/template/js-template.md index 3b165dfeb546f502ee80c91c0d034549d2c5006d..57910d025c4214fec8cc1f3a7a09b03c10f5f3ea 100644 --- a/en/contribute/template/js-template.md +++ b/en/contribute/template/js-template.md @@ -141,10 +141,10 @@ Describe the method. For details, see the fourth and fifth points in "Writing In **Return value** (This part is optional. Delete it if there is no return value.) -| Type | Description | -| ------------------------------------------ | ----------------------------------------------- | -| string | Describe the return value, for example, what can be done after the return value is obtained. | -| Promise\> | Describe the return value. For details about how to write promise methods, see item 14 in "General Writing Instructions."| +| Type | Description | +| ------------------------------------------ | ------------------------------------------------------------ | +| string | Describe the return value, for example, what can be done after the return value is obtained. | +| Promise\> | Describe the return value. For details about how to write promise methods, see item 14 in "General Writing Instructions." | **Example** @@ -193,7 +193,7 @@ Describe the method. For details, see the fourth and fifth points in "Writing In | Name | Type | Mandatory| Description | | -------- | ------------------------------------ | ---- | ------------------------------------------------------------ | | type | string | Yes | Describe the event and when or how it will be triggered. If a method involves multiple events, describe them separately.
**Example 1 (single event):**
Type of the event. The `'play'` event is triggered when the `play()` API is called and audio playback starts.
**Example 2 (multiple events)**:
Type of the event. The following events are supported:
- 'play': triggered when the play() API is called and audio playback starts.
- 'dataLoad': triggered when the audio data is loaded, that is, when the `src` attribute is configured.
- 'finish': triggered when the audio playback is finished. | -| callback | Callback\<[CustomType](#CustomType)> | No | Describe the parameter. The instructions are the same as those provided under [Methods](#methods). | +| callback | Callback\<[CustomType](#customtype)> | No | Describe the parameter. The instructions are the same as those provided under [Methods](#methods). | **Return value** (This part is optional. Delete it if there is no return value.) diff --git a/en/device-dev/device-dev-guide.md b/en/device-dev/device-dev-guide.md index f0ececf4cb84370794b75de3a734e745664b7d48..1dc53366e9d55c468b1a70c8d565b4100fe63ff4 100644 --- a/en/device-dev/device-dev-guide.md +++ b/en/device-dev/device-dev-guide.md @@ -35,7 +35,7 @@ In addition, OpenHarmony provides a wide array of system components that can be | Development resources | Preparing for your development | - [Obtaining Source Code](get-code/sourcecode-acquire.md)
- [Obtaining Tools](get-code/gettools-acquire.md) | | Getting started | Getting started with setup, build, burning, debugging, and running of OpenHarmony | - [Mini and Small System Overview](quick-start/quickstart-ide-lite-overview.md)| | Basic capabilities | Using basic capabilities of OpenHarmony | - [Kernel for Mini System](kernel/kernel-mini-overview.md)
- [Kernel for Small System](kernel/kernel-small-overview.md)
- [HDF](driver/driver-hdf-overview.md)
- [Subsystems](subsystems/subsys-build-all.md)
- [Security Guidelines](security/security-guidelines-overall.md)
- [Privacy Protection](security/security-privacy-protection.md) | -| Advanced development | Developing smart devices based on system capabilities | - [WLAN-connected Products](guide/device-wlan-led-control.md)
- [Cameras Without a Screen](guide/device-iotcamera-control-overview.md)
- [Cameras with a Screen](guide/device-camera-control-overview.md) | +| Advanced development | Developing smart devices based on system capabilities | - [WLAN-connected Products](guide/device-wlan-led-control.md)
- [Cameras with a Screen](guide/device-camera-control-overview.md) | | Porting and adaptation | - Porting and adapting OpenHarmony to an SoC
- Porting and adapting OpenHarmony to a third-party library
- Third-party vendor porting cases
| - [Mini System SoC Porting Guide](porting/porting-minichip.md)
- [Small System SoC Porting Guide](porting/porting-smallchip-prepare-needs.md)
- [Third-Party Library Porting Guide for Mini and Small Systems](porting/porting-thirdparty-overview.md)
- [Mini-System Devices with Screens — Bestechnic SoC Porting Case](porting/porting-bes2600w-on-minisystem-display-demo.md)
- [Combo Solution – ASR Chip Porting Case](porting/porting-asr582x-combo-demo.md)
| | Contributing components | Contributing components to OpenHarmony | - [HPM Part Overview](hpm-part/hpm-part-about.md)
- [HPM Part Development](hpm-part/hpm-part-development.md)
- [HPM Part Reference](hpm-part/hpm-part-reference.md) | | Reference | Referring to development specifications | [FAQs](faqs/faqs-overview.md) | diff --git a/en/device-dev/guide/Readme-EN.md b/en/device-dev/guide/Readme-EN.md index 4da6d3441ea153312b7a0f283be891052c430515..cb8a1d1ac921569f267574c6afb9ef17c817ff61 100644 --- a/en/device-dev/guide/Readme-EN.md +++ b/en/device-dev/guide/Readme-EN.md @@ -4,13 +4,6 @@ - WLAN-connected Products - [LED Peripheral Control](device-wlan-led-control.md) - [Third-Party SDK Integration](device-wlan-sdk.md) - - Cameras Without a Screen - - Camera Control - - [Overview](device-iotcamera-control-overview.md) - - Development Guidelines - - [Photographing](device-iotcamera-control-demo-photodevguide.md) - - [Video Recording](device-iotcamera-control-demo-videodevguide.md) - - [Use Case](device-iotcamera-control-example.md) - Cameras with a Screen - Screen and Camera Control - [Overview](device-camera-control-overview.md) diff --git a/en/readme/telephony.md b/en/readme/telephony.md index c20e7ad87e5067218f72f68b82f30b61c8b1b4bc..78b7169591cad3eec673cb1e4cf1d70135931ba5 100755 --- a/en/readme/telephony.md +++ b/en/readme/telephony.md @@ -1,15 +1,6 @@ -# Telephony +# Telephony -- [Introduction](#section104mcpsimp) -- [Directory Structure](#section119mcpsimp) -- [Constraints](#section123mcpsimp) -- [Usage](#section128mcpsimp) - - [Obtaining the Current Cellular Network Signal Information](#section1458213210369) - - [Observing Changes to the Cellular Network Status](#section750135512369) - -- [Repositories Involved](#section152mcpsimp) - -## Introduction +## Introduction The Telephony subsystem provides APIs for obtaining information about the wireless cellular network and SIM card. Applications can call these APIs to obtain information such as the name of the currently registered network, network service status, signal strength, and SIM card information. @@ -28,7 +19,7 @@ The Telephony subsystem consists of the following modules: ![](figures/en-us_architecture-of-telephony-subsystem.png) -## Directory Structure +## Directory Structure ``` base/telephony/ @@ -42,16 +33,16 @@ base/telephony/ └── ril_adapter # RIL Adapter module ``` -## Constraints +## Constraints 1. The open-source version currently provides the cellular call (CS call only), SMS & MMS, and cellular data services and supports the dual-SIM framework. -2. The Hardware Device Interface (HDI) support is subject to the chip vendors' adaptation capability. For details, see [Telephony Service Development](https://gitee.com/openharmony/docs/blob/master/en/device-dev/subsystems/subsys-tel.md). +2. The Hardware Device Interface (HDI) support is subject to the chip vendors' adaptation capability. For details, see [Telephony Development](../device-dev/subsystems/subsys-tel-guide). -## Usage Guidelines +## Usage Guidelines To learn more about the usage of each subsystem module, refer to the respective README. The following illustrates API usage by exemplifying how to obtain the current cellular network signal information and observe the cellular network status changes. -### Obtaining the Current Cellular Network Signal Information +### Obtaining the Current Cellular Network Signal Information 1. Import the **radio** namespace from **@ohos.telephony.radio.d.ts**. 2. Call the **getSignalInformation\(slotId: number\)** function via callback or promise. This function works in asynchronous mode. @@ -92,7 +83,7 @@ To learn more about the usage of each subsystem module, refer to the respective ``` -### Observing Cellular Network Status Changes +### Observing Cellular Network Status Changes Adding an Observer @@ -125,7 +116,7 @@ Removing the Observer ``` -## Repositories Involved +## Repositories Involved **Telephony Subsystem** diff --git a/en/release-notes/OpenHarmony-v3.1-release.md b/en/release-notes/OpenHarmony-v3.1-release.md index e2f37c76e6c3fd32e868fd0ad3a3d60152407dda..21ab0449d8b55b0cda5cc901d9999d85699a08d7 100644 --- a/en/release-notes/OpenHarmony-v3.1-release.md +++ b/en/release-notes/OpenHarmony-v3.1-release.md @@ -189,8 +189,7 @@ This version has the following updates to OpenHarmony 3.1 Beta. For details, see the following: - -*[API Differences](api-change/v3.1-Release/readme.md)* +*[API Differences](api-change/v3.1-Release/Readme-EN.md)* ### Chip and Development Board Adaptation diff --git a/en/release-notes/OpenHarmony-v3.2-beta1.md b/en/release-notes/OpenHarmony-v3.2-beta1.md index 3c61d876db1cf1caa1906375fe8b0f484c3ed0f5..af1d74702410ed1a557c02a2ab67bc289b74ae3c 100644 --- a/en/release-notes/OpenHarmony-v3.2-beta1.md +++ b/en/release-notes/OpenHarmony-v3.2-beta1.md @@ -172,8 +172,7 @@ This version has the following updates to OpenHarmony 3.1 Release. ### API Updates - -*[API Differences](api-change/v3.2-beta1/readme.md)* +*[API Differences](api-change/v3.2-beta1/Readme-EN.md)* ### Chip and Development Board Adaptation diff --git a/zh-cn/release-notes/OpenHarmony-v3.1-release.md b/zh-cn/release-notes/OpenHarmony-v3.1-release.md index 046c3317e6a37dd20492f8b4f5e81284c49ab3ba..bc1018830bfcb168b3f56b7767cebd4ecc851213 100755 --- a/zh-cn/release-notes/OpenHarmony-v3.1-release.md +++ b/zh-cn/release-notes/OpenHarmony-v3.1-release.md @@ -190,7 +190,7 @@ repo forall -c 'git lfs pull' API变更请参考： -_[API差异报告](api-change/v3.1-Release/readme.md)_ +_[API差异报告](api-change/v3.1-Release/Readme-CN.md)_ ### 芯片及开发板适配 @@ -215,7 +215,7 @@ _[API差异报告](api-change/v3.1-Release/readme.md)_ | ArkUI | [拖拽](https://gitee.com/openharmony/app_samples/tree/master/ETSUI/Drag) | 本示例主要展示了拖拽操作的功能。 | eTS | | ArkUI | [动画](https://gitee.com/openharmony/app_samples/tree/master/ETSUI/ArkUIAnimation) | 本示例通过点击按钮触发动画，向用户展示属性动画与显示动画的效果。 | eTS | | 数据管理 | [分布式数据库-结果集和谓词查询](https://gitee.com/openharmony/app_samples/tree/master/data/DDMQuery) | 本示例展示了分布式数据管理中，如何通过构建query对象， 查询kvstore中的数据，获取结果集。 | eTS | -| 数据管理 | [关系型数据库](https://gitee.com/openharmony/app_samples/tree/master/data/Rdb) | 本示例展示了在eTS中关系型数据库的使用，包括增、删、改、查等操作。 | eTS | +| 数据管理 | [关系型数据库](https://gitee.com/openharmony/app_samples/tree/master/data/DistributedRdb) | 本示例展示了在eTS中关系型数据库的使用，包括增、删、改、查等操作。 | eTS | | 事件 | [后台代理提醒](https://gitee.com/openharmony/app_samples/tree/master/Notification/AlarmClock) | 本示例通过模拟闹钟来展示后台代理提醒的使用方法。 | eTS | | 事件 | [事件通知](https://gitee.com/openharmony/app_samples/tree/master/Notification/Emitter) | 本示例主要展示进程内事件通知，用户通过选择对应商品并提交订单后在订单列表显示所选商品。 | eTS | | 通信与连接 | [RPC通信](https://gitee.com/openharmony/app_samples/tree/master/Communication/RPC) | 本示例展示了同一设备中前后台的数据交互，用户前台选择相应的商品与数目，后台计算出结果，回传给前台展示。 | eTS | @@ -248,10 +248,10 @@ _[API差异报告](api-change/v3.1-Release/readme.md)_ | ISSUE单 | 问题描述 | | -------- | -------- | | [I4MGJM](https://gitee.com/openharmony/drivers_peripheral/issues/I4MGJM) | 【hdf/camera】RK3568单板跑camera HDI用例失败 | -| [I4OECR](https://gitee.com/openharmony/ark_js_runtime/issues/I4OECR) | XTS运行报ark异常栈（低概率问题） | -| [I4OBTW](https://gitee.com/openharmony/aafwk_standard/issues/I4OBTW) | 全量执行XTS用例，安装应用后出现批量aa start 失败，影响社区流水线稳定性测试 | -| [I4OLHF](https://gitee.com/openharmony/ark_js_runtime/issues/I4OLHF?from=project-issue) | 【ArkUI子系统】 由进程com.amsst.amsMissionSnapshotTest导致测试进程异常 | -| [I4OLUK](https://gitee.com/openharmony/ark_js_runtime/issues/I4OLUK) | 【ArkUI子系统】 由进程com.ohos.systemui导致进程栈异常 | +| I4OECR | XTS运行报ark异常栈（低概率问题） | +| I4OBTW | 全量执行XTS用例，安装应用后出现批量aa start 失败，影响社区流水线稳定性测试 | +| I4OLHF | 【ArkUI子系统】 由进程com.amsst.amsMissionSnapshotTest导致测试进程异常 | +| I4OLUK | 【ArkUI子系统】 由进程com.ohos.systemui导致进程栈异常 | ## 遗留缺陷列表 diff --git a/zh-cn/release-notes/OpenHarmony-v3.2-beta1.md b/zh-cn/release-notes/OpenHarmony-v3.2-beta1.md index 1a05a0e689fb773071c779e82d03e3be67a48889..1819cdbe09524576f272ccba0dd36b38790b2de9 100644 --- a/zh-cn/release-notes/OpenHarmony-v3.2-beta1.md +++ b/zh-cn/release-notes/OpenHarmony-v3.2-beta1.md @@ -173,7 +173,7 @@ ArkUI支持AbilityComponent组件将应用界面（Ability）作为控件嵌入 ### API变更 -_[API差异报告](api-change/v3.2-beta1/readme.md)_ +_[API差异报告](api-change/v3.2-beta1/Readme-CN.md)_ ### 芯片及开发板适配 diff --git a/zh-cn/release-notes/api-change/v3.1-Release/Readme-ZH.md b/zh-cn/release-notes/api-change/v3.1-Release/Readme-CN.md similarity index 100% rename from zh-cn/release-notes/api-change/v3.1-Release/Readme-ZH.md rename to zh-cn/release-notes/api-change/v3.1-Release/Readme-CN.md diff --git a/zh-cn/release-notes/api-change/v3.2-beta1/Readme-ZH.md b/zh-cn/release-notes/api-change/v3.2-beta1/Readme-CN.md similarity index 100% rename from zh-cn/release-notes/api-change/v3.2-beta1/Readme-ZH.md rename to zh-cn/release-notes/api-change/v3.2-beta1/Readme-CN.md diff --git a/zh-cn/release-notes/api-change/v3.2-beta2/Readme-ZH.md b/zh-cn/release-notes/api-change/v3.2-beta2/Readme-CN.md similarity index 100% rename from zh-cn/release-notes/api-change/v3.2-beta2/Readme-ZH.md rename to zh-cn/release-notes/api-change/v3.2-beta2/Readme-CN.md diff --git a/zh-cn/release-notes/api-change/v3.2-beta3/Readme-ZH.md b/zh-cn/release-notes/api-change/v3.2-beta3/Readme-CN.md similarity index 100% rename from zh-cn/release-notes/api-change/v3.2-beta3/Readme-ZH.md rename to zh-cn/release-notes/api-change/v3.2-beta3/Readme-CN.md