UI service package generation and registration method and apparatus, and UI service loading method and apparatus
A UI service loading method is applied to a loading apparatus. One example method includes: receiving a loading request including a reuse path of a to-be-loaded UI service, where the loading request requests to load the to-be-loaded UI service; determining a dependency of the to-be-loaded UI service based on a dependency graph; and loading the to-be-loaded UI service and the dependency of the to-be-loaded UI service, where the reuse path of the to-be-loaded UI service indicates an access path of the to-be-loaded UI service, and the dependency graph indicates a dependency of at least one UI service in at least one UI service package, and indicates a UI service that references a UI service in the at least one UI service package as a dependency.
1. A user interface (UI) service loading method, wherein the method comprises:
receiving a loading request, wherein the loading request requests to load a to-be-loaded UI service, the loading request comprises a reuse path of the to-be-loaded UI service, and the reuse path of the to-be-loaded UI service indicates an access path of the to-be-loaded UI service, wherein the reuse path of the to-be-loaded UI service comprises a fuzzy version number of a UI service package comprising the to-be-loaded UI service, and the fuzzy version number indicates whether the UI service package meets a preset version condition;
determining a dependency of the to-be-loaded UI service based on a dependency graph, wherein the dependency graph indicates a dependency of at least one UI service in at least one UI service package, and indicates a UI service that references a UI service in the at least one UI service package as a dependency; and
loading the to-be-loaded UI service and the dependency of the to-be-loaded UI service.
2. The method according to claim 1 , wherein the dependency graph is obtained based on dependency relationship sets of one or more of the at least one UI service package.
3. The method according to claim 2 , wherein the dependency relationship sets comprise a dependency relationship of at least one UI service in the one or more of the at least one UI service package, and the dependency relationship of the at least one UI service in the one or more of the at least one UI service packages indicates a dependency of the at least one UI service in the one or more of the at least one UI service package.
4. The method according to claim 1 , wherein code of each UI service in the at least one UI service package comprises a reuse path, and the reuse path in the code of the UI service indicates an access path of a dependency of the UI service.
5. The method according to claim 1 , wherein the at least one UI service package is a UI service package registered in at least one UI service package registration apparatus.
6. The method according to claim 5 , wherein the at least one UI service package comprises a first UI service package, and a reuse path in code of a first UI service in the first UI service package meets at least one of the following conditions: the reuse path in the code of the first UI service indicates an access path of a second UI service, wherein the second UI service is a dependency of the first UI service, the second UI service is a UI service in a second UI service package, and the second UI service package is a UI service package different from the first UI service package; or
the reuse path in the code of the first UI service indicates an access path of a runtime dependency item, wherein the runtime dependency item is a dependency of the first UI service, the runtime dependency item is a runtime dependency item in at least one common dependency UI service package, the at least one common dependency UI service package comprises at least one runtime dependency item, and the at least one common dependency UI service package provides a dependency for a UI service in at least one UI service package registered in the at least one UI service package registration apparatus, wherein
the first UI service package is a UI service package in the at least one UI service package, and the first UI service is a UI service in the first UI service package.
7. The method according to claim 6 , wherein the method further comprises:
when the dependency of the to-be-loaded UI service is a runtime dependency item, starting a driver of the runtime dependency item when the runtime dependency item is loaded for a first time in a process of loading the at least one UI service and the dependency of the to-be-loaded UI service.
8. The method according to claim 1 , wherein the determining a dependency of the to-be-loaded UI service based on the dependency graph comprises:
determining a reuse path of the dependency of the to-be-loaded UI service based on the dependency graph.
9. The method according to claim 8 , wherein before the loading the to-be-loaded UI service and the dependency of the to-be-loaded UI service, the method further comprises:
downloading the to-be-loaded UI service and the dependency of the to-be-loaded UI service based on the reuse path of the to-be-loaded UI service and the reuse path of the dependency of the to-be-loaded UI service; and
the loading the to-be-loaded UI service and the dependency of the to-be-loaded UI service comprises:
loading the downloaded to-be-loaded UI service and the downloaded dependency of the to-be-loaded UI service.
10. The method according to claim 9 , wherein the loading the downloaded to-be-loaded UI service and the downloaded dependency of the to-be-loaded UI service comprises:
sequentially loading the downloaded to-be-loaded UI service and the downloaded dependency of the to-be-loaded UI service based on a dependency relationship indicated by the dependency graph.
11. The method according to claim 1 , wherein the method further comprises:
updating the dependency graph.
12. The method according to claim 1 , wherein the method is applied to a loading apparatus, the loading apparatus comprises a first loading apparatus and a second loading apparatus, the first loading apparatus is isolated from the second loading apparatus, and both the first loading apparatus and the second loading apparatus are configured to load a UI service for a software system.
13. A chip system, wherein the chip system comprises one or more interface circuits and one or more processors; and the interface circuit and the one or more processors are interconnected through a bus; the interface circuit is configured to receive a signal from a memory, and send the signal to the processor, wherein the signal comprises computer instructions stored in the memory; and wherein the computer instructions, when executed by the one or more processors, cause the chip system to perform the following steps:
receiving a loading request, wherein the loading request requests to load a to-be-loaded UI service, the loading request comprises a reuse path of the to-be-loaded UI service, and the reuse path of the to-be-loaded UI service indicates an access path of the to-be-loaded UI service, wherein the reuse path of the to-be-loaded UI service comprises a fuzzy version number of a UI service package comprising the to-be-loaded UI service, and the fuzzy version number indicates whether the UI service package meets a preset version condition;
determining a dependency of the to-be-loaded UI service based on a dependency graph, wherein the dependency graph indicates a dependency of at least one UI service in at least one UI service package, and indicates a UI service that references a UI service in the at least one UI service package as a dependency; and
loading the to-be-loaded UI service and the dependency of the to-be-loaded UI service.
14. The chip system of claim 13 , wherein the dependency graph is obtained based on dependency relationship sets of one or more of the at least one UI service package.
15. The chip system of claim 14 , wherein the dependency relationship sets comprise a dependency relationship of at least one UI service in the one or more of the at least one UI service package, and the dependency relationship of the at least one UI service in the one or more of the at least one UI service packages indicates a dependency of the at least one UI service in the one or more of the at least one UI service package.
16. The chip system of claim 13 , wherein code of each UI service in the at least one UI service package comprises a reuse path, and the reuse path in the code of the UI service indicates an access path of a dependency of the UI service.
17. The chip system of claim 13 , wherein the at least one UI service package is a UI service package registered in at least one UI service package registration apparatus.
18. A computer device, comprising at least one processor and a memory, wherein the memory stores computer instructions, and the computer instructions, when executed by the at least one processor, cause the computer device to perform the following steps:
receiving a loading request, wherein the loading request requests to load a to-be-loaded UI service, the loading request comprises a reuse path of the to-be-loaded UI service, and the reuse path of the to-be-loaded UI service indicates an access path of the to-be-loaded UI service, wherein the reuse path of the to-be-loaded UI service comprises a fuzzy version number of a UI service package comprising the to-be-loaded UI service, and the fuzzy version number indicates whether the UI service package meets a preset version condition;
determining a dependency of the to-be-loaded UI service based on a dependency graph, wherein the dependency graph indicates a dependency of at least one UI service in at least one UI service package, and indicates a UI service that references a UI service in the at least one UI service package as a dependency; and
loading the to-be-loaded UI service and the dependency of the to-be-loaded UI service.
19. The computer device of claim 18 , wherein the dependency graph is obtained based on dependency relationship sets of one or more of the at least one UI service package.
20. The computer device of claim 19 , wherein the dependency relationship sets comprise a dependency relationship of at least one UI service in the one or more of the at least one UI service package, and the dependency relationship of the at least one UI service in the one or more of the at least one UI service packages indicates a dependency of the at least one UI service in the one or more of the at least one UI service package.