In the early summer, OpenAtom OpenHarmony ("OpenHarmony") 4.0 Beta1 version arrived as scheduled. On the basis of the 3.2 Release version, the 4.0 Beta1 version continues to improve the ArkUI, application framework, graphics media and other subsystem capabilities of the standard system, and provides the first batch of API Level 10 interfaces.
As the first Beta version of OpenHarmony 4.0, a series of new features have been introduced. We look forward to community developers actively experiencing new features, contributing wisdom and strength, and jointly promoting the maturity of the future 4.0 Release version, personally participating in and witnessing the development of OpenHarmony 4.0 version.
The following section introduces some new features of OpenHarmony 4.0 Beta1. To know the complete feature information of this version, please go to OpenHarmony 4.0 Beta1 Release Notes. Eco-partner commercial equipment or software releases that pass the compatibility test should use OpenHarmony 3.2 Release.
OpenHarmony 4.0 Beta1 Release Notes
zh-cn/release-notes/OpenHarmony-v4.0-beta1.md · OpenHarmony/docs - Gitee.com
application framework
1. Minimize the management of Extension capabilities, support various Extensions to open APIs according to business scenarios, and prevent sensitive API calls.
2. Support URI temporary authorization of data or files, and the application can authorize the read and write permissions of its own files to other applications.
3. The UIExtension mechanism is supported, which is used to realize the Extension with the interface, and the interface of the UIExtension can be embedded in the window of the calling application for display. At present, the basic capabilities of UIExtension have been built:
● Supports a unified UIExtension template, with clear interface meaning and standardized service development.
● Supports native default Extension interface display, which is convenient for developers to quickly implement Extension functions, and also provides interface customization capabilities.
4. Support the sharing of atomic services. Application developers can use the methods provided by the UIAbility component to set the data to be shared. Users can share atomic services and cards to another terminal device through the sharing box.
ArkUI
1. Changes in component properties support transitional animations. For example, the Divider component uses transitional animations when configuring the color and color properties of the divider to improve the user experience when component properties change.
2. The Text/Image/Video/ListItem/GridItem components support the user to long press the component to enter the default drag and drop behavior, and support developers to disable the default drag and drop to improve developer development efficiency.
3. The custom bullet box supports customization of mask color and pop-up animation (such as allowing developers to set parameters related to the pop-up animation effect), which enhances the developer's ability to customize the bullet box.
4. Support the ability to return the width and height of the input string in the text component. When the string is folded and displayed, the prompt box of the complete string will pop up when the mouse is hovered.
Application package management
1. Support the feature of application package installation without decompression, which optimizes system startup performance and application installation performance.
2. Support three-party ecological applications to use the shared package capabilities provided by system applications. Three-party applications do not need to integrate relevant content (including code, resources, and .so files, etc.) in their own installation packages, thereby reducing the integration cost and update of ecological applications cost purposes.
Distributed Data Management
1. Support system applications to silently access the DataShareExtension data of other system applications through the data management service agent, and support access to DataShareExtension data in Single mode applications through the data management service agent.
2. The DataShare client provides the ability to subscribe to DataShareExtension data changes according to the URI prefix. Any DataShareExtension data change under the subscribed URI prefix will notify the DataShare client.
3. Added a unified data management framework (Unified Data Management Framework, UDMF), which supports data standardization model, data drag and drop in the device, UDMF data storage adaptation, rights management, and lifecycle management.
file management
1. Support file classification and view management capabilities. Applications such as gallery manage media files in the form of albums (pictures and videos do not need to pay attention to the specific storage location), and provide functions such as adding and removing files in albums without involving specific FileIO behaviors. The API interface will be opened in subsequent versions.
2. Provide enhanced FileIO access capabilities, support randomAccessFile, moveDir, copyDir, watcher capabilities.
3. Provide URI-based temporary authorization access and deauthorization capabilities for files, and support cross-application local authorization or cross-device authorization for files.
graphic display
1. Support the attribute animation of the component's self-drawing content, and support the disappearance transition animation of the component.
2. Optimized the performance of the unified rendering mode, including IPC performance optimization (such as passing rendering resources through shared memory to reduce IPC communication traffic), supporting control-level occlusion culling, only needing to render upper-level controls to reduce GPU rendering workload, and enabling hardware compositing device to improve synthesis energy efficiency, etc.
3. Picture codec supports SVG decoding, and GIF format improves parameter analysis, such as total frame number, time interval, etc.
window
1. Support monitoring the focus state of the window: App developers in previous versions can only monitor the focus state of WindowStage, but cannot monitor the focus events for system windows and application sub-windows. Now, application developers can monitor the focus, focus, and show-hidden status of a single window by registering windowEvent on the window.
2. Support adjusting the z-axis order of sub-windows to the top layer: For multiple sub-windows created in the application in previous versions, the system always displays the last displayed window at the top of all sub-windows. At the same time, by default in the current system, the window touched by the user or clicked by the mouse will be promoted to the topmost level of all sub-windows. Now, through the raiseToAppTop method of the window object, application developers can adjust a sub-window to the topmost level among multiple sub-windows of WindowStage.
3. Refactor the immersive implementation, optimize the animation effects of app opening, exiting, and jumping: In previous versions, when the app is opened, the full-screen app window size does not include the area of the status bar and navigation bar by default, unless the app calls the immersive interface ( Via setWindowLayoutFullScreen or setSystemBarEnable). Calling the above interface during the opening process of an immersive application will cause a jump in the opening animation, affecting the experience of opening the application and switching animations between applications. In the new version, no matter whether the immersive display is set or not, the size of the full-screen application window includes the status bar and navigation bar area, while the avoidance of the status bar and navigation bar of non-immersive applications will be done through ArkUI to limit the application display area.
media
audio capability
1. Support audio playback and recording through the native interface.
2. Support to query or monitor the playback device with the highest current priority.
3. Audio focus is supported. There is no need to manually apply for the focus when the app is playing audio. The system will automatically apply for the focus in the background and automatically execute the focus strategy (such as pause, fade out, fade out recovery, etc.); the app only needs to register the focus event monitoring function to receive Focus event and update state like stop progress bar when paused.
Broadcast control framework
1. Support the transfer of custom media information between the media provider and the controller, and the application can expand the display method of media content. For example, the media controller can require the media provider to display song lyrics in a special form.
2. Support the framework capability of the media playlist, the media provider provides the content of the playlist, and the media controller obtains the content of the playlist and can select any media content to play.
3. Support the framework capability of playback history. The media session framework provides a list of query history playback applications, and the list items are sorted in order of playback (including currently playing and exited applications).
media player
1. Support HLS live streaming and datasource-based streaming playback capabilities, and support H.265 video hardware decoding playback capabilities.
2. Support playback sound effects, audio property settings, and support automatic rotation playback of videos with rotation angles.
3. Support acquisition and switching of multiple audio tracks, support setting and switching of external subtitles.
camera
1. Improve the error code and exception handling mechanism of ArkTS API, so that developers can locate error information by querying error codes.
2. Support the mirroring capability of the front preview. By default, the front preview screen is in a mirror state.
3. When different camera applications use the same camera, the camera framework has priority control and mutual exclusion strategies.