Xr application editing method, device, and storage medium

Abstract

Embodiments of the present application provide an XR application editing method. In one embodiment, a runtime container is integrated in a content generator, and application content of an XR application is generated based on a runtime environment provided by the runtime container. When the application content is generated, the XR application is generated from the application content and the runtime container. The runtime container runs between the application content and an operating system to provide the runtime environment for the application content. Because the runtime container is added between the application content and the operating system, the running of the application content is no longer strongly dependent on the operating system, enabling the development and running of the XR application to be cross-platform and cross-device. This makes the development of the XR application simple and easy to implement, solving problems of XR application development and cross-device running.

What is claimed is: 
     
         1 . A content generator, comprising:
 a runtime container integrated within the content generator and configured to generate an extended reality (XR) application, wherein the runtime container is configured to provide a runtime environment during a generation process or a running process of the XR application;   a 3D scene effect editing module, configured to, in response to an XR application generation operation, load 3D scene static resources, and based on the runtime environment provided by the runtime container, edit 3D scene dynamic information for the 3D scene static resources to obtain 3D scene resource data; and   a 3D application logic editing module, configured to, based on the runtime environment provided by the runtime container, edit application logic code for the 3D scene resource data to obtain application content of the XR application,   wherein the application content and the runtime container form the XR application, and the runtime container in the XR application provides the runtime environment for the application content during the running process of the XR application.   
     
     
         2 . The content generator according to  claim 1 , wherein the runtime container comprises: a framework layer, a runtime environment layer, and a software library layer, and wherein:
 the software library layer comprises a plurality of software engines and provides second-type application programming interfaces (APIs) for the plurality of software engines, wherein a second-type API enables encapsulation of a first-type API;   the framework layer is configured to provide a first-type API to an application developer, thereby enabling the application developer to write the application logic code of the XR application based on the first-type API, and during the generation process or the running process of the XR application, sense a target event, run a function entity of at least one first-type API corresponding to the target event, and provide a target API encapsulated in the function entity to the runtime environment layer, wherein the target API is a second-type API; and   the runtime environment layer is configured to, according to the target API, call a corresponding software engine in the software library layer to respond to the target event.   
     
     
         3 . The content generator according to  claim 2 , wherein the software library layer is further configured to: provide a second-type API to the runtime environment layer, and encapsulate a first-type API based on the second-type API, and provide the first-type API to the framework layer, for the framework layer to provide the first-type API to the application developer;
 or   the software library layer is further configured to: provide a second-type API to the runtime environment layer; and the runtime environment layer is further configured to: encapsulate a first-type API based on the second-type API, and provide the first-type API to the framework layer, for the framework layer to provide the first-type API to the application developer.   
     
     
         4 . The content generator according to  claim 2 , wherein the 3D scene effect editing module is specifically configured to:
 in response to a loading operation of the 3D scene static resources, start the runtime container, and run the 3D scene static resources in the runtime environment provided by the runtime container to obtain a 3D static image;   in response to an editing operation on the 3D static image, edit the 3D scene dynamic information for the 3D scene static resources to obtain first intermediate-state resource data;   in response to a scene effect viewing operation, re-invoke the runtime container, and run the first intermediate-state resource data in the runtime environment provided by the runtime container to obtain a first intermediate-state 3D image; and   when the first intermediate-state 3D image does not satisfy a scene effect, adjust the 3D scene dynamic information until the scene effect is satisfied to obtain the 3D scene resource data.   
     
     
         5 . The content generator according to  claim 2 , wherein the 3D application logic editing module is specifically configured to:
 in response to a loading operation of the 3D scene resource data, start the runtime container, and run the 3D scene resource data in a runtime environment provided by the runtime container to obtain a first intermediate-state 3D image;   in response to an editing operation of the application logic code, generate second intermediate-state resource data according to the 3D scene resource data and the application logic code, and re-invoke the runtime container to run the second intermediate-state resource data in the runtime environment provided by the runtime container to obtain a second intermediate-state 3D image; and   when the second intermediate-state 3D image does not satisfy an interactive effect, adjust the application logic code until the interactive effect is satisfied, to obtain the application content of the XR application.   
     
     
         6 . An XR application editing method, applied to a content generator, wherein a runtime container is integrated in the content generator, the runtime container is configured to provide a runtime environment during a generation process and a running process of an XR application, the method comprising:
 in response to an XR application generation operation, loading 3D scene static resources;   based on the runtime environment provided by the runtime container, adding 3D scene dynamic information to the 3D scene static resources to obtain 3D scene resource data; and   based on the runtime environment provided by the runtime container, editing application logic code for the 3D scene resource data to obtain application content of the XR application;   wherein the application content and the runtime container form the XR application, and the runtime container in the XR application provides the runtime environment for the application content during a running process of the XR application.   
     
     
         7 . The method according to  claim 6 , wherein the adding of the 3D scene dynamic information to the 3D scene static resources comprises:
 in response to a loading operation of the 3D scene static resources, starting the runtime container, and running the 3D scene static resources in the runtime environment provided by the runtime container to obtain a 3D static image;   in response to an editing operation on the 3D static image, editing the 3D scene dynamic information for the 3D scene static resources to obtain first intermediate-state resource data;   in response to a scene effect viewing operation, re-invoking the runtime container, and running the first intermediate-state resource data in the runtime environment provided by the runtime container to obtain a first intermediate-state 3D image; and   when the first intermediate-state 3D image does not satisfy a scene effect, adjusting the 3D scene dynamic information until the scene effect is satisfied, to obtain the 3D scene resource data.   
     
     
         8 . The method according to  claim 7 , wherein the runtime container comprises a framework layer, a runtime environment layer, and a software library layer, and
 wherein the running of the 3D scene static resources in the runtime environment provided by the runtime container to obtain the 3D static image comprises:   the framework layer sensing a first loading event of the 3D scene static resources, and running a function entity of at least one first-type API corresponding to the first loading event;   when running to a first target API encapsulated in the function entity, providing the first target API to the runtime environment layer, wherein the first target API is a second-type API; and   the runtime environment layer, according to the first target API, calling a corresponding software engine in the software library layer to respond to the first loading event;   wherein the first-type API is formed by encapsulating the second-type API, and the second-type API is an API corresponding to a software engine included in the software library layer.   
     
     
         9 . The method according to  claim 7 , wherein the runtime container comprises a framework layer, a runtime environment layer, and a software library layer, and
 wherein the running of the first intermediate-state resource data in the runtime environment provided by the runtime container to obtain the first intermediate-state 3D image comprises:   the framework layer sensing a first editing event on the 3D static image, and running a function entity of at least one first-type API corresponding to the first editing event;   when running to a first target API encapsulated in the function entity, providing the first target API to the runtime environment layer, wherein the first target API is a second-type API; and   the runtime environment layer, according to the first target API, calling a corresponding software engine in the software library layer to respond to the first editing event;   wherein the first-type API is formed by encapsulating the second-type API, and the second-type API is an API corresponding to a software engine included in the software library layer.   
     
     
         10 . The method according to  claim 6 , wherein the editing of the application logic code for the 3D scene resource data comprises:
 in response to a loading operation of the 3D scene resource data, starting the runtime container, and running the 3D scene resource data in the runtime environment provided by the runtime container to obtain a first intermediate-state 3D image;   in response to an editing operation of the application logic code, generating second intermediate-state resource data according to the 3D scene resource data and the application logic code, and re-invoking the runtime container to run the second intermediate-state resource data in the runtime environment provided by the runtime container to obtain a second intermediate-state 3D image; and   when the second intermediate-state 3D image does not satisfy an interactive effect, adjusting the application logic code until the interactive effect is satisfied, to obtain the application content of the XR application.   
     
     
         11 . The method according to  claim 10 , wherein the runtime container comprises a framework layer, a runtime environment layer, and a software library layer, and
 wherein the running of the 3D scene resource data in the runtime environment provided by the runtime container to obtain the first intermediate-state 3D image comprises:   the framework layer sensing a second loading event of the 3D scene resource data, and running a function entity of at least one first-type API corresponding to the second loading event;   when running to a second target API encapsulated in the function entity, providing the second target API to the runtime environment layer, wherein the second target API is a second-type API; and   the runtime environment layer, according to the second target API, calling a corresponding software engine in the software library layer to respond to the second loading event;   wherein the first-type API is formed by encapsulating the second-type API, and the second-type API is an API corresponding to a software engine included in the software library layer.   
     
     
         12 . The method according to  claim 10 , wherein the runtime container comprises a framework layer, a runtime environment layer, and a software library layer, and
 wherein the running of the second intermediate-state resource data in the runtime environment provided by the runtime container to obtain the second intermediate-state 3D image comprises:   the framework layer sensing a second editing event of the application logic code, and running a function entity of at least one first-type API corresponding to the second editing event;   when running to a second target API encapsulated in the function entity, providing the second target API to the runtime environment layer, wherein the second target API is a second-type API; and   the runtime environment layer, according to the second target API, calling a corresponding software engine in the software library layer to respond the second editing event;   wherein the first-type API is formed by encapsulating the second-type API, and the second-type API is an API corresponding to a software engine included in the software library layer.   
     
     
         13 . An electronic device comprising:
 one or more processors; and   one or more computer-readable memories coupled to the one or more processors and having instructions stored thereon that are executable by the one or more processors to perform one or more operations comprising:   providing a runtime container, which is configured to provide a runtime environment during a generation process and a running process of an XR application;   in response to an XR application generation operation, loading 3D scene static resources;   based on a runtime environment provided by a runtime container, adding 3D scene dynamic information to the 3D scene static resources to obtain 3D scene resource data; and   based on the runtime environment provided by the runtime container, editing application logic code for the 3D scene resource data to obtain application content,   wherein the application content and the runtime container form an XR application, and the runtime container in the XR application provides the runtime environment for the application content during a running process of the XR application.   
     
     
         14 . The electronic device according to  claim 13 , wherein the adding of the 3D scene dynamic information to the 3D scene static resources comprises:
 in response to a loading operation of the 3D scene static resources, starting the runtime container, and running the 3D scene static resources in the runtime environment provided by the runtime container to obtain a 3D static image;   in response to an editing operation on the 3D static image, editing the 3D scene dynamic information for the 3D scene static resources to obtain first intermediate-state resource data;   in response to a scene effect viewing operation, re-invoking the runtime container, and running the first intermediate-state resource data in the runtime environment provided by the runtime container to obtain a first intermediate-state 3D image; and   when the first intermediate-state 3D image does not satisfy a scene effect, adjusting the 3D scene dynamic information until the scene effect is satisfied, to obtain the 3D scene resource data.   
     
     
         15 . The electronic device according to  claim 14 , wherein the runtime container comprises a framework layer, a runtime environment layer, and a software library layer, and
 wherein the running of the 3D scene static resources in the runtime environment provided by the runtime container to obtain the 3D static image comprises:   the framework layer sensing a first loading event of the 3D scene static resources, and running a function entity of at least one first-type API corresponding to the first loading event;   when running to a first target API encapsulated in the function entity, providing the first target API to the runtime environment layer, wherein the first target API is a second-type API; and   the runtime environment layer, according to the first target API, calling a corresponding software engine in the software library layer to respond to the first loading event;   wherein the first-type API is formed by encapsulating the second-type API, and the second-type API is an API corresponding to a software engine included in the software library layer.   
     
     
         16 . The electronic device according to  claim 14  wherein the runtime container comprises a framework layer, a runtime environment layer, and a software library layer, and
 wherein the running of the first intermediate-state resource data in the runtime environment provided by the runtime container to obtain the first intermediate-state 3D image comprises: 
 the framework layer sensing a first editing event on the 3D static image, and running a function entity of at least one first-type API corresponding to the first editing event; 
 when running to a first target API encapsulated in the function entity, providing the first target API to the runtime environment layer, wherein the first target API is a second-type API; and 
 the runtime environment layer, according to the first target API, calling a corresponding software engine in the software library layer to respond to the first editing event; 
 wherein the first-type API is formed by encapsulating the second-type API, and the second-type API is an API corresponding to a software engine included in the software library layer. 
 
     
     
         17 . The electronic device according to  claim 13 , wherein the editing of the application logic code for the 3D scene resource data comprises:
 in response to a loading operation of the 3D scene resource data, starting the runtime container, and running the 3D scene resource data in the runtime environment provided by the runtime container to obtain a first intermediate-state 3D image;   in response to an editing operation of the application logic code, generating second intermediate-state resource data according to the 3D scene resource data and the application logic code, and re-invoking the runtime container to run the second intermediate-state resource data in the runtime environment provided by the runtime container to obtain a second intermediate-state 3D image; and   when the second intermediate-state 3D image does not satisfy an interactive effect, adjusting the application logic code until the interactive effect is satisfied, to obtain the application content of the XR application.   
     
     
         18 . The electronic device according to  claim 17 , wherein the runtime container comprises a framework layer, a runtime environment layer, and a software library layer, and
 wherein the running of the 3D scene resource data in the runtime environment provided by the runtime container to obtain the first intermediate-state 3D image comprises:   the framework layer sensing a second loading event of the 3D scene resource data, and running a function entity of at least one first-type API corresponding to the second loading event;   when running to a second target API encapsulated in the function entity, providing the second target API to the runtime environment layer, wherein the second target API is a second-type API; and   the runtime environment layer, according to the second target API, calling a corresponding software engine in the software library layer to respond to the second loading event;   wherein the first-type API is formed by encapsulating the second-type API, and the second-type API is an API corresponding to a software engine included in the software library layer.   
     
     
         19 . The electronic device according to  claim 17 , wherein the runtime container comprises a framework layer, a runtime environment layer, and a software library layer, and
 wherein the running of the second intermediate-state resource data in the runtime environment provided by the runtime container to obtain the second intermediate-state 3D image comprises:   the framework layer sensing a second editing event of the application logic code, and running a function entity of at least one first-type API corresponding to the second editing event;   when running to a second target API encapsulated in the function entity, providing the second target API to the runtime environment layer, wherein the second target API is a second-type API; and   the runtime environment layer, according to the second target API, calling a corresponding software engine in the software library layer to respond to the second editing event;   wherein the first-type API is formed by encapsulating the second-type API, and the second-type API is an API corresponding to a software engine included in the software library layer.