# applications_calendar **Repository Path**: zcl987/applications_calendar ## Basic Information - **Project Name**: applications_calendar - **Description**: No description available - **Primary Language**: Unknown - **License**: Apache-2.0 - **Default Branch**: master - **Homepage**: https://gitee.com/openharmony-sig/applications_calendar - **GVP Project**: No ## Statistics - **Stars**: 0 - **Forks**: 2 - **Created**: 2023-07-06 - **Last Updated**: 2023-07-08 ## Categories & Tags **Categories**: Uncategorized **Tags**: None ## README # Calendar ## 1. Introduction The calendar application is a preset application in OpenHarmony that displays user dates and views. ## 2. Directory Structure ``` ├─AppScope │ └─resources # resource file ├─common │ └─src │ └─main │ └─ets │ └─default # basic components and methods of the interface ├─features │ ├─monthview # monthly view Properties │ ├─settings # settings properties │ └─yearview # year view properties ├─product │ ├─pc # flat panel module │ │ └─src │ │ └─main │ │ ├─ets │ │ │ ├─abilities # ability of pages │ │ │ ├─common # common components │ │ │ └─pages # pages │ └─phone # phone module │ └─src │ └─main │ ├─ets │ │ ├─common # common components │ │ ├─MainAbility # ability of pages │ │ └─pages # pages ├── signature # certificate file ``` ### Architecture ![](./figures/architecture.png) - **product** Business form layer: Distinguish various forms of applications for different products and screens, including personalized business, component configuration, and personalized resource packages。 - **feature** Common feature layer: An abstract collection of common feature components that can be referenced by various application forms。 - **common** Common capability layer: Basic capability set, modules that each application form must rely on, including tool classes and common resource packages。 ## 3. Signature And Packaging ### Signature #### Signature File Configuration Open project engineering by DevEco Studio, choose: File → Project Structure。 ![](./figures/signature_1.png) Choose Modules → Signing Configs, Configure the corresponding signature file as follows, Click Apply after completion, Click OK again ![](./figures/signature_2.png) After the configuration is completed, the following content will appear in the corresponding build.gradle file ![](./figures/signature_3.png) ### Packaging Choose: Build → Build Haps(s)/APP(s) → Build Hap(s) ![](./figures/build_haps.png) After compilation, the HAP package will be generated in the `\build\outputs` path in the project directory (if no signature is configured, only unsigned HAP packages will be generated) ![](./figures/build_output_dir_release.png) ### Install Install the compiled hap package using the command: hdc_std install "HAP packet address" ![](./figures/calendar_install.png) ## Constraint - Development Environment - **DevEco Studio for OpenHarmony**: Version number greater than 3.0.0.992, Download and Install OpenHarmony SDK API Version 9(The initial IDE configuration can refer to the IDE usage documentation) - Language - ArkTS - Limitation - This example only supports running on standard systems