提交 d5aca1f8 编写于 作者: G Gloria

Update docs against 16592+16444+16455

Signed-off-by: wusongqing<wusongqing@huawei.com>
上级 9efd4487
......@@ -131,13 +131,13 @@ A class that stores the color picked.
## ColorPicker
A class used to obtain the main color of an image from its data. Before calling any method of **ColorPicker**, use [createColorPicker](#effectkitcreatecolorpicker) to create a **ColorPicker** instance.
A class used to obtain the color from an image. Before calling any method of **ColorPicker**, use [createColorPicker](#effectkitcreatecolorpicker) to create a **ColorPicker** instance.
### getMainColor
getMainColor(): Promise\<Color>
Obtains the main color of the image and writes the result to a **[Color](#color)** instance. This API uses a promise to return the result.
Obtains the main color from the image and writes the result to a [Color](#color) instance. This API uses a promise to return the result.
**System capability**: SystemCapability.Multimedia.Image.Core
......@@ -162,7 +162,7 @@ colorPicker.getMainColor().then(color => {
getMainColorSync(): Color
Obtains the main color of the image and writes the result to a **[Color](#color)** instance. This API returns the result in synchronous mode.
Obtains the main color from the image and writes the result to a [Color](#color) instance. This API returns the result in synchronous mode.
**System capability**: SystemCapability.Multimedia.Image.Core
......@@ -180,6 +180,93 @@ console.log('get main color =' + color);
```
![en-us_image_Main_Color.png](figures/en-us_image_Main_Color.png)
### getLargestProportionColor<sup>10+</sup>
getLargestProportionColor(): Color
Obtains the color with the largest proportion from the image and writes the result to a [Color](#color) instance. This API returns the result in synchronous mode.
**System capability**: SystemCapability.Multimedia.Image.Core
**Return value**
| Type | Description |
| :------------- | :---------------------------------------------- |
| [Color](#color) | Color value of the color with the largest proportion. If the operation fails, **null** is returned.|
**Example**
```js
let color = colorPicker.getLargestProportionColor();
console.log('get largest proportion color =' + color);
```
![en-us_image_Largest_Proportion_Color.png](figures/en-us_image_Largest_Proportion_Color.png)
### getHighestSaturationColor<sup>10+</sup>
getHighestSaturationColor(): Color
Obtains the color with the highest saturation from the image and writes the result to a [Color](#color) instance. This API returns the result in synchronous mode.
**System capability**: SystemCapability.Multimedia.Image.Core
**Return value**
| Type | Description |
| :------------- | :---------------------------------------------- |
| [Color](#color) | Color value of the color with the highest saturation. If the operation fails, **null** is returned.|
**Example**
```js
let color = colorPicker.getHighestSaturationColor();
console.log('get highest saturation color =' + color);
```
![en-us_image_Highest_Saturation_Color.png](figures/en-us_image_Highest_Saturation_Color.png)
### getAverageColor<sup>10+</sup>
getAverageColor(): Color
Obtains the average color from the image and writes the result to a [Color](#color) instance. This API returns the result in synchronous mode.
**System capability**: SystemCapability.Multimedia.Image.Core
**Return value**
| Type | Description |
| :------------- | :---------------------------------------------- |
| [Color](#color) | Average color value. If the operation fails, **null** is returned.|
**Example**
```js
let color = colorPicker.getAverageColor();
console.log('get average color =' + color);
```
![en-us_image_Average_Color.png](figures/en-us_image_Average_Color.png)
### isBlackOrWhiteOrGrayColor<sup>10+</sup>
isBlackOrWhiteOrGrayColor(color: number): boolean
Checks whether this image is black, white, and gray.
**System capability**: SystemCapability.Multimedia.Image.Core
**Return value**
| Type | Description |
| :------------- | :---------------------------------------------- |
| boolean | Returns **true** if the image is black, white, and gray; returns **false** otherwise.|
**Example**
```js
let bJudge = colorPicker.isBlackOrWhiteOrGrayColor(0xFFFFFFFF);
console.log('is black or white or gray color[bool](white) =' + bJudge);
```
## Filter
A class used to add a specified effect to an image. Before calling any method of **Filter**, use [createEffect](#effectkitcreateeffect) to create a **Filter** instance.
......
......@@ -231,3 +231,10 @@ If the **distroFilter** tag is used, an error is reported during compilation on
**Adaptation Guide**<br>
Replace **distroFilter** with **distributionFilter** in the configuration file.
## cl.bundlemanager.20 Changed standard of launchType to multiton in the module.json Configuration File
The **standard** mode of the [launchType](../../../application-dev/quick-start/module-configuration-file.md) tag in the **module.json** file is changed to **multiton**.
**Adaptation Guide**<br>
Replace **standard** of **launchType** to **multiton** in the configuration file.
......@@ -25,49 +25,31 @@ Beta is a branch pulled from Master in the OpenHarmony community irregularly. Th
A tag version is a stable and reliable version created by applying patches to an LTS or a Release branch, with the purpose of fixing individual bugs, security vulnerabilities, and other necessary adaptation modifications.
### Commands for Downloading Branches
The release versions are available in the [**Release Notes** folder](../release-notes).
| Branch | Download Command (repo + https) | Download Command (repo + ssh) |
| ------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
| 1.0.1-Release | repo init -u https://gitee.com/openharmony/manifest -b OpenHarmony_1.0.1_release -m default.xml --no-repo-verify<br>repo sync -c<br>repo forall -c 'git lfs pull' | repo init -u git@gitee.com:openharmony/manifest.git -b OpenHarmony-3.1-Release -m default.xml --no-repo-verify<br>repo sync -c<br>repo forall -c 'git lfs pull' |
| 3.0-LTS | repo init -u https://gitee.com/openharmony/manifest.git -b OpenHarmony-3.0-LTS --no-repo-verify<br>repo sync -c<br>repo forall -c 'git lfs pull' | repo init -u git@gitee.com:openharmony/manifest.git -b OpenHarmony-3.0-LTS --no-repo-verify<br>repo sync -c<br>repo forall -c 'git lfs pull' |
| 3.1-Release | repo init -u git@gitee.com:openharmony/manifest.git -b OpenHarmony-3.1-Release -m default.xml --no-repo-verify<br>repo sync -c<br>repo forall -c 'git lfs pull' | repo init -u git@gitee.com:openharmony/manifest.git -b OpenHarmony-3.1-Release -m default.xml --no-repo-verify<br>repo sync -c<br>repo forall -c 'git lfs pull' |
## Maintenance Policies
### Lifecycle Policies
OpenHarmony provides lifecycle management services for LTS and Release branches as follows:
#### Release -> Stop proactive maintenance
​ The Release SIG periodically makes and maintains tag version plans to resolve individual bugs, security vulnerabilities, and other major issues to ensure continuously stable and available branches.
## Lifecycle Policies
#### Stop proactive maintenance -> Stop maintenance
The OpenHarmony community provides maintenance and technical support for Release and LTS branches based on the OpenHarmony Version Lifecycle Management. The OpenHarmony community provides maintenance and technical support based on the *OpenHarmony Version Lifecycle Management*.
​ The Release SIG no longer proactively plans and releases tag versions. It only fixes security vulnerabilities and major defects in corresponding branches.
### LTS and Release Maintenance Policies
For an LTS branch, the OpenHarmony community provides 2-year proactive maintenance and 1.5-year passive maintenance since its release.
### Maintenance Schedule
For a Release branch, the OpenHarmony community provides 1-year proactive maintenance and 1-year passive maintenance since its release.
The following table lists the maintenance schedule of the LTS and Release branches that have been released in the OpenHarmony community.
### Branch Merge Policies
| Branch Name | Branch Type| Release Date | End of Proactive Maintenance| End of Maintenance |
| ------------- | -------- | --------- | ------------ | --------- |
| 1.0.1-Release | Release | 2021-03-30| 2022-03-30 | 2023-03-30|
| 3.0-LTS | LTS | 2021-09-30| 2023-09-30 | 2025-03-30|
| 3.1-Release | Release | 2022-03-30| 2023-03-30 | 2024-03-30|
The Release SIG is responsible for lifecycle management of an LTS or a Release branch. During the maintenance period, the SIG accepts only code updates that resolve security vulnerabilities, ACTS issues, and other major issues. All code updates can be merged into the branch only after the related pull request has been approved by the [owner](https://gitee.com/openharmony/community/blob/master/zh/BRANCHOWNER).
Run the following commands to download the source code of each branch:
### Maintenance Schedule
| Branch | Download Command (repo + https) | Download Command (repo + ssh) |
| ------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
| 1.0.1-Release | repo init -u https://gitee.com/openharmony/manifest -b OpenHarmony_1.0.1_release -m default.xml --no-repo-verify<br>repo sync -c<br>repo forall -c 'git lfs pull' | repo init -u git@gitee.com:openharmony/manifest.git -b OpenHarmony-3.1-Release -m default.xml --no-repo-verify<br>repo sync -c<br>repo forall -c 'git lfs pull' |
| 3.0-LTS | repo init -u https://gitee.com/openharmony/manifest.git -b OpenHarmony-3.0-LTS --no-repo-verify<br>repo sync -c<br>repo forall -c 'git lfs pull' | repo init -u git@gitee.com:openharmony/manifest.git -b OpenHarmony-3.0-LTS --no-repo-verify<br>repo sync -c<br>repo forall -c 'git lfs pull' |
| 3.1-Release | repo init -u git@gitee.com:openharmony/manifest.git -b OpenHarmony-3.1-Release -m default.xml --no-repo-verify<br>repo sync -c<br>repo forall -c 'git lfs pull' | repo init -u git@gitee.com:openharmony/manifest.git -b OpenHarmony-3.1-Release -m default.xml --no-repo-verify<br>repo sync -c<br>repo forall -c 'git lfs pull' |
The following table lists the maintenance schedule of the LTS and Release branches that have been released in the OpenHarmony community.
| No. | Branch Name | Branch Type| Release Date | End of Proactive Maintenance| End of Maintenance |
| :--- | ------------- | :------- | :-------- | :----------- | :-------- |
| 1 | 1.0.1-Release | Release | 2021-03-30| 2022-03-30 | 2023-03-30|
| 2 | 3.0-LTS | LTS | 2021-09-30| 2023-09-30 | 2025-03-30|
| 3 | 3.1-Release | Release | 2022-03-30| 2023-03-30 | 2024-03-30|
### Version Plan
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册