diff --git a/LICENSE b/LICENSE new file mode 100644 index 0000000..261eeb9 --- /dev/null +++ b/LICENSE @@ -0,0 +1,201 @@ + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + + Copyright [yyyy] [name of copyright owner] + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. diff --git a/OAT.xml b/OAT.xml new file mode 100644 index 0000000..5f9a1b2 --- /dev/null +++ b/OAT.xml @@ -0,0 +1,77 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/README_zh.md b/README_zh.md deleted file mode 100644 index 50672a1..0000000 --- a/README_zh.md +++ /dev/null @@ -1,363 +0,0 @@ -# Camera 源码开发说明 -## 1. 项目介绍 -相机应用是OpenHarmony标准系统中预置的系统应用，为用户提供基础的相机拍摄功能，包括预览、拍照、摄像、缩略图显示、跳转相册、多机位协同。 -Camera 采用纯 arkui-ts 语言开发，开发过程中不涉及任何 Java 部分的代码。 -## 2. 工程结构 -### 目录结构 -``` -/applications -├── common # 公共模块目录 -│ └── src -│ └── main -│ ├── ets # ets代码目录 -│ ├── default -│ ├── Camera # Camera组件管理目录 -│ ├── model # Model层代码目录 -│ ├── redux # 应用的状态容器 -│ ├── utils # 工具类代码目录 -│ ├── resources # 资源目录 -│ ├── config.json # 项目配置信息 -├── feature # feature层模块目录 -│ └── featurecommon # 主Camera模块目录 -│ └── src -│ └── main -│ ├── ets # ets代码目录 -│ ├── com -│ ├── ohos # ets代码目录 -│ ├── featurecommon # ets代码目录 -│ ├── animate # 动画目录 -│ ├── cameraswitcher # 前后置切换目录 -│ ├── customDialog # 弹窗目录 -│ ├── featureservice # feature服务 -│ ├── shutterbutton # 拍照目录 -│ ├── thumbnail # 缩略图目录 -│ ├── Mode.ets # 模式切换mode -│ ├── resources # 资源目录 -│ ├── config.json # 项目配置信息 -│ └── photo # 拍照模块目录 -│ └── src -│ └── main -│ ├── ets # ets代码目录 -│ ├── com -│ ├── ohos -│ ├── photo # 拍照ets代码目录 -│ ├── resources # 资源目录 -│ ├── config.json # 项目配置信息 -│ └── video # 摄像模块目录 -│ └── src -│ └── main -│ ├── ets # ets代码目录 -│ ├── com -│ ├── ohos -│ ├── video # 摄像ets代码目录 -│ ├── resources # 资源目录 -│ ├── config.json # 项目配置信息 -├── product # 产品层模块目录 -│ └── phone # phone模式模块目录 -│ └── src -│ └── main -│ ├── ets # ets代码目录 -│ ├── MainAbility -│ ├── common # ets代码目录 -│ ├── pages # 业务特性的View层目录 -│ ├── res # 业务特性涉及的图片目录 -│ ├── workers # worker多线程处理 -│ ├── resources # 资源目录 -│ ├── config.json # 项目配置信息 -│ └── tablet # tablet模式模块目录 -│ └── src -│ └── main -│ ├── ets # ets代码目录 -│ ├── MainAbility -│ ├── common # ets代码目录 -│ ├── pages # 业务特性的View层目录 -│ ├── res # 业务特性涉及的图片目录 -│ ├── workers # worker多线程处理 -│ ├── resources # 资源目录 -│ ├── config.json # 项目配置信息 -``` -### 整体架构 - -![](./figures/camera-en.png) - -Camera的Common层以Redux框架和Camera Worker为基础，向上扩展出Feature和Product层。 -应用整体采用了多模块的设计方式，每个模块都遵循上述架构原则。 - -各层的作用分别如下： -- Product层：区分不同产品，不同屏幕的各形态，含有应用窗口、个性化业务，组件的配置以及个性化资源包。 -- Feature层：抽象的公共特性组件集合，每个特性解耦独立可打包为har，可以被每个业务态所引用。 -- Common层：负责数据服务、UI组件、工具组、数据持久层、动效层、外部交互层等部件内公共能力，每个应用形态都必须要依赖的模块。 - - -应用各层中重要类及其功能如下表所示 -|模块|层级|模块名|作用| -|-|-|-|-| -|camera|Product层|Phone|手机模块。| -|camera|Product层|Tablet|平板模块。| -|camera|Product层|Watch|智能穿戴模块。| -|camera|Product层|PC|电脑模块。| -|camera|Feature层|Photo mode|拍照模式。| -|camera|Feature层|Video mode|录像模式。| -|camera|Feature层|分布式 mode|分布式模式。| -|camera|Common层|Common Function|公共能力模块。| -|camera|Common层|Common UI Components|公共UI组件。| -|camera|Common层|Redux frame|Redux框架。| -|camera|Common层|Utils|工具类合集。| -|camera|Common层|AsyncManager|异步通信管理。| -|camera|Common层|Camera worker|相机后台线程。| - -## 3 典型接口的使用 -1. 获取Camera能力 -```ets - import camera from '@ohos.multimedia.camera' - getCameras() { - cameras = camera.getCameraManager(null).getCameras() - if (cameras) { - console.info(`getCameras success.`) - for (let i = 0; i < cameras.length; i++) { - console.info(`--------------Camera Info-------------`) - console.info(`camera_id: ${cameras[i].cameraId}`) - console.info(`cameraPosition: ${cameras[i].cameraPosition}`) - console.info(`cameraType: ${cameras[i].cameraType}`) - console.info(`connectionType: ${cameras[i].cameraType}`) - } - } else { - console.info(`getCameras failed.`) - } - } -``` - -2. 启动相机 -```ets - startPreview() { - cameraInput = await cameraManager.createCameraInput(cameraId) - captureSession = await camera.createCaptureSession(null) - if (captureSession) { - console.info(`createCaptureSession success.`) - this.previewOutput = await camera.createPreviewOutput(this.previewId) - await this.captureSession.beginConfig() - await this.captureSession.addInput(this.cameraInput) - await this.captureSession.addOutput(this.previewOutput) - console.info(`startPreview success.`) - } else { - console.info(`createCaptureSession failed.`) - } -``` - -3. 拍照 -```ets - import image from '@ohos.multimedia.image' - takePicture() { - let mReceiver = image.createImageReceiver(imageWidth, imageHeight, 4, 8) - let mSurfaceId = await mReceiver.getReceivingSurfaceId() - await camera.createPhotoOutput(mSurfaceId).then((picture) => { - console.info(`createPhotoOutput called: ${picture}`) - }) - } -``` - -4. 切换镜头 -```ets - import camera from '@ohos.multimedia.camera' - switchCamera(cameraId) { - await captureSession.stop() - await cameraInput.release() - await captureSession.release() - cameraInput = await cameraManager.createCameraInput(cameraId) - captureSession = await camera.createCaptureSession(null) - if (captureSession) { - console.info(`createCaptureSession success.`) - this.previewOutput = await camera.createPreviewOutput(this.previewId) - await this.captureSession.beginConfig() - await this.captureSession.addInput(this.cameraInput) - await this.captureSession.addOutput(this.previewOutput) - console.info(`startPreview success.`) - } else { - console.info(`createCaptureSession failed.`) - } -``` - -## 4. 签名打包 -### 签名 -#### 签名文件的获取 -1. 拷贝 OpenHarmony 标准版的 prebuilts\signcenter 目录到操作目录。 -2. 拷贝 Camera 工程的 signature\Camera.p7b 到该目录下。 - -备注：如果需要生成并使用自己的签名文件可参考https://gitee.com/openharmony/docs/blob/master/zh-cn/application-dev/quick-start/configuring-openharmony-app-signature.md - -#### 签名文件的配置 -打开项目工程，选择 File → Project Structure - -![](./figures/signature_1.png) - -选择 Modules → Signing Configs，将对应的签名文件配置如下，完成后点击Apply，再点击OK。 -密码为生成签名文件时的密码，如果使用默认的签名文件，则使用默认密码123456。 - -![](./figures/signature_2.png) - -配置完成后，对应的build.gradle文件中会出现如下内容 - -![](./figures/signature_3.png) - -### 打包 -DevEco Studio 支持 debug 与 release 两种打包类型。可以在 OhosBuild Variants 窗口中进行切换。 - - ![](./figures/ds_ohosbuild_variants.png) - -#### release打包 -1. 代码准备完成后，在 OhosBuild Variants 窗口的 Selected Variant 中选择 release - - ![](./figures/ds_ohosbuild_variants_release.png) - -2. 选择Build → Build Haps(s)/APP(s) → Build Hap(s) - - ![](./figures/ds_build_haps.png) - -3. 编译完成后，hap包会生成在工程目录下的 `\build\outputs\hap\release\`路径下（如果没有配置签名，则只会生成未签名的hap包） - - ![](./figures/ds_ohosbuild_output_dir_release.png) - - -## 5. 安装、运行、调试 -### 应用安装 -配置 hdc： -进入SDK目录中的toolchains文件夹下，获取文件路径： - -![](./figures/sdk_catalogue.png) - - -并将此路径配置到环境变量中： - -![](./figures/sdk_environment_variable.png) - -连接开发板，打开一个新的cmd命令窗口，执行`hdc list targets`，弹出窗口如下： - -![](./figures/cmd1.png) - -等待一段时间后，窗口出现如下打印，可回到输入 hdc list targets 的命令窗口继续操作: - -![](./figures/cmd2.png) - -再次输入hdc list targets，出现如下结果，说明hdc连接成功 - -![](./figures/cmd3.png) - -获取 root 权限与读写权限： - -``` -hdc target mount -``` - -***T.B.D smode 不执行的情况下，hdc target mount 能否正常执行？*** - -将签名好的 hap 包放入设备的 `/system/app` 目录下，并修改hap包的权限。发送文件命令如下： - -``` -hdc file send 本地路径 /system/app/hap包名称 -``` -例：将当前本地目录的 `Camera.hap` 文件放入到 `system/app/Camera.hap` 文件中。 -``` -hdc file send Camera.hap /system/app/Camera.hap -``` -> 注意，如果设备不存在 `/system/app` 目录，则需要手动创建该目录并修改权限。 -> ``` -> hdc shell -> cd system -> mkdir app -> chmod 777 app -> ``` -> `/system/app` 目录放置系统应用，例如：Camera，SystemUI，Settings 等。 -> -> 但hap包需要在该目录下手动设置权限 -> ``` -> chmod 666 hap包名 -> ``` -> 此目录应用不用手动安装，系统自动拉起。 -### 应用运行 -Camera 属于系统应用，在将签名的 hap 包放入 `/system/app` 目录后，重启系统，应用会自动拉起。 -``` -hdc shell -reboot -（不可以直接执行hdc reboot，命令是无效的) -``` -***T.B.D 直接执行 `reboot`，还是执行`hdc shell reboot`？*** -> 注意，如果设备之前安装过系统应用，则需要执行如下两条命令清除设备中存储的应用信息才能够在设备重启的时候将我们装入设备的新 hap 包正常拉起。 -> ``` -> hdc shell rm -rf /data/accounts/ -> hdc shell rm -rf /data/misc_de/0/mdds/0/default/bundle_manager_service -> ``` -### 应用调试 -#### log打印 -- 在程序中添加 log -```JS -console.info("Camera log info"); -``` -可以在DevEco Studio中查看log -![](./figures/ds_hilog_window.png) -#### log获取及过滤 -- log获取 - -将log输出至文件 -``` -hdc shell hilog > 输出文件名称 -``` - -例： -在真实环境查看log，将全log输出到当前目录的hilog.log文件中 -``` -hdc shell hilog > hilog.log -``` - -- log过滤 - -在命令行窗口中过滤log -``` -hilog | grep 过滤信息 -``` - -例：过滤包含信息 Label 的 hilog -``` -hilog | grep Label -``` -## 6. 贡献代码 -### Fork 代码仓库 -1. 在码云上打开 Camera 代码仓库（[仓库地址](https://gitee.com/openharmony/applications_camera)）。 -2. 点击仓库右上角的 Forked 按钮 - ![](./figures/commit_source_fork_button.png) -3. 在弹出的画面中，选择将仓库 fork 到哪里，点击确认。 - ![](./figures/commit_source_fork_confirm.png) -4. Fork 成功之后，会在自己的账号下看见 fork 的代码仓库。 - ![](./figures/commit_source_forked_repo.png) - -### 提交代码 -1. 访问我们自己在码云账号上 fork 的代码仓库，点击“克隆/下载”按钮，选择 SSH，点击“复制”按钮。 - ![](./figures/commit_source_clone_page.png) - -2. 在本地新建 Camera 目录，在 Camera 目录中执行如下命令 - ``` - git clone 步骤1中复制的地址 - ``` - -3. 修改代码。 - > 将代码引入工程，以及编译工程等相关内容请参见 **3. 代码使用** 部分的相关内容。 -4. 提交代码到 fork 仓库。 - > 修改后的代码，首先执行 `git add` 命令，然后执行 `git commit` 命令与 `git push` 命令，将代码 push 到我们自己的 fork 仓中。 - > 关于代码提交的这部分内容涉及 git 的使用，可以参照 [git官网](https://git-scm.com/) 的内容，在此不再赘述。 - -### 发起 Pull Request (PR) -在将代码提交到 fork 仓之后，我们可以通过发起 Pull Request（PR）的方式来为 OpenHarmony 的相关项目贡献代码。 - -1. 打开 fork 仓库。选择 `Pull Requests` → `新建 Pull Request` - - ![](./figures/commit_source_new_pull_request.png) - -2. 在 `新建 Pull Request` 画面填入标题与说明，点击 `创建` 按钮。 - - ![](./figures/commit_source_new_pull_request_confirm.png) -3. 创建 Pull Request 完成。 PR 创建完成后，会有专门的代码审查人员对代码进行评审，评审通过之后会合入相应的代码库。 - - ![](./figures/commit_source_new_pr_done.png) - - - - diff --git a/figures/camera-en.png b/figures/camera-en.png deleted file mode 100644 index a497a47..0000000 Binary files a/figures/camera-en.png and /dev/null differ diff --git a/figures/cmd1.png b/figures/cmd1.png deleted file mode 100644 index 43cec74..0000000 Binary files a/figures/cmd1.png and /dev/null differ diff --git a/figures/cmd2.png b/figures/cmd2.png deleted file mode 100644 index b771fda..0000000 Binary files a/figures/cmd2.png and /dev/null differ diff --git a/figures/cmd3.png b/figures/cmd3.png deleted file mode 100644 index 75cc11c..0000000 Binary files a/figures/cmd3.png and /dev/null differ diff --git a/figures/commit_source_clone_page.png b/figures/commit_source_clone_page.png deleted file mode 100644 index 80462ad..0000000 Binary files a/figures/commit_source_clone_page.png and /dev/null differ diff --git a/figures/commit_source_fork_button.png b/figures/commit_source_fork_button.png deleted file mode 100644 index c65b206..0000000 Binary files a/figures/commit_source_fork_button.png and /dev/null differ diff --git a/figures/commit_source_fork_confirm.png b/figures/commit_source_fork_confirm.png deleted file mode 100644 index ca9a4ba..0000000 Binary files a/figures/commit_source_fork_confirm.png and /dev/null differ diff --git a/figures/commit_source_forked_repo.png b/figures/commit_source_forked_repo.png deleted file mode 100644 index 290bbbe..0000000 Binary files a/figures/commit_source_forked_repo.png and /dev/null differ diff --git a/figures/commit_source_new_pr_done.png b/figures/commit_source_new_pr_done.png deleted file mode 100644 index 7f8cd5a..0000000 Binary files a/figures/commit_source_new_pr_done.png and /dev/null differ diff --git a/figures/commit_source_new_pull_request.png b/figures/commit_source_new_pull_request.png deleted file mode 100644 index e047b33..0000000 Binary files a/figures/commit_source_new_pull_request.png and /dev/null differ diff --git a/figures/commit_source_new_pull_request_confirm.png b/figures/commit_source_new_pull_request_confirm.png deleted file mode 100644 index 32a814f..0000000 Binary files a/figures/commit_source_new_pull_request_confirm.png and /dev/null differ diff --git a/figures/ds_build_haps.png b/figures/ds_build_haps.png deleted file mode 100644 index eb6be46..0000000 Binary files a/figures/ds_build_haps.png and /dev/null differ diff --git a/figures/ds_hilog_window.png b/figures/ds_hilog_window.png deleted file mode 100644 index ac0f2db..0000000 Binary files a/figures/ds_hilog_window.png and /dev/null differ diff --git a/figures/ds_ohosbuild_output_dir_release.png b/figures/ds_ohosbuild_output_dir_release.png deleted file mode 100644 index 7b302a7..0000000 Binary files a/figures/ds_ohosbuild_output_dir_release.png and /dev/null differ diff --git a/figures/ds_ohosbuild_variants.png b/figures/ds_ohosbuild_variants.png deleted file mode 100644 index 67773eb..0000000 Binary files a/figures/ds_ohosbuild_variants.png and /dev/null differ diff --git a/figures/ds_ohosbuild_variants_release.png b/figures/ds_ohosbuild_variants_release.png deleted file mode 100644 index 423deb7..0000000 Binary files a/figures/ds_ohosbuild_variants_release.png and /dev/null differ diff --git a/figures/launcherl2-en.png b/figures/launcherl2-en.png deleted file mode 100644 index fae910c..0000000 Binary files a/figures/launcherl2-en.png and /dev/null differ diff --git a/figures/sdk_catalogue.png b/figures/sdk_catalogue.png deleted file mode 100644 index 4faa2aa..0000000 Binary files a/figures/sdk_catalogue.png and /dev/null differ diff --git a/figures/sdk_environment_variable.png b/figures/sdk_environment_variable.png deleted file mode 100644 index 789beda..0000000 Binary files a/figures/sdk_environment_variable.png and /dev/null differ diff --git a/figures/signature_1.png b/figures/signature_1.png deleted file mode 100644 index 42aeb45..0000000 Binary files a/figures/signature_1.png and /dev/null differ diff --git a/figures/signature_2.png b/figures/signature_2.png deleted file mode 100644 index cc28c02..0000000 Binary files a/figures/signature_2.png and /dev/null differ diff --git a/figures/signature_3.png b/figures/signature_3.png deleted file mode 100644 index 2b2e205..0000000 Binary files a/figures/signature_3.png and /dev/null differ