Nothing Special   »   [go: up one dir, main page]

WO2023083071A1 - 视图交互方法、装置、电子设备及计算机可读介质 - Google Patents

视图交互方法、装置、电子设备及计算机可读介质 Download PDF

Info

Publication number
WO2023083071A1
WO2023083071A1 PCT/CN2022/129242 CN2022129242W WO2023083071A1 WO 2023083071 A1 WO2023083071 A1 WO 2023083071A1 CN 2022129242 W CN2022129242 W CN 2022129242W WO 2023083071 A1 WO2023083071 A1 WO 2023083071A1
Authority
WO
WIPO (PCT)
Prior art keywords
view
dynamic
interface
native
interaction
Prior art date
Application number
PCT/CN2022/129242
Other languages
English (en)
French (fr)
Inventor
李东耕
Original Assignee
北京沃东天骏信息技术有限公司
北京京东世纪贸易有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京沃东天骏信息技术有限公司, 北京京东世纪贸易有限公司 filed Critical 北京沃东天骏信息技术有限公司
Publication of WO2023083071A1 publication Critical patent/WO2023083071A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/34—Graphical or visual programming
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/38—Creation or generation of source code for implementing user interfaces

Definitions

  • the present application relates to the field of computer technology, and in particular to a view interaction method, device, electronic equipment and computer readable medium.
  • the dynamic view page cannot coexist with existing native page elements, so that the interaction between the dynamic page view on the same page and the existing native page view cannot be realized.
  • the embodiment of the present application provides a view interaction method, device, electronic device, and computer-readable medium, which can solve the existing problem that the interaction between the dynamic page view on the same page and the existing native page view cannot be realized .
  • a view interaction method including:
  • the method before calling the corresponding dynamic view code package, the method further includes:
  • performing view rendering to generate a dynamic view includes:
  • generating a native view includes:
  • the target interactive view is determined from the dynamic view and the native view according to the interface identifier, including:
  • each native view corresponding to the native interface is a target interaction view
  • the native view corresponding to the native interface and the dynamic view corresponding to the dynamic environment interface are target interaction views
  • the dynamic view corresponding to the routing interface is the target interaction view.
  • calling the interface corresponding to the interface identifier to perform interaction between each target interaction view includes:
  • the dynamic environment interface In response to determining that the interface identifier corresponds to the native interface and the dynamic environment interface, call the dynamic environment interface to write the method of the corresponding target dynamic view into the dynamic environment, and then call the dynamic view bridge to convert the method of the target dynamic view into a native method for the native The native view corresponding to the interface is called through the native interface.
  • calling the interface corresponding to the interface identifier to perform interaction between each target interaction view includes:
  • the dynamic view bridge In response to determining that the interface identifier corresponds to the native interface and the dynamic environment interface, determine the target native view based on the native interface, and then call the dynamic view bridge to write the method of the target native view into the dynamic environment for the target dynamic view corresponding to the dynamic environment interface to perform transfer.
  • calling the interface corresponding to the interface identifier to perform interaction between each target interaction view includes:
  • calling the interface corresponding to the interface identifier to perform interaction between each target interaction view includes:
  • the present application also provides a view interaction device, including:
  • a receiving unit configured to receive a view interaction request, and determine a view mix layout according to the view interaction request
  • the dynamic view rendering unit is configured to call the corresponding dynamic view code package according to the view mix layout to perform view rendering and generate a dynamic view;
  • the native view generation unit is configured to determine the page corresponding to the dynamic view, call the native view element, and generate the native view on the page based on the hybrid layout of the view;
  • the view interaction unit is configured to determine the interface identifier corresponding to the view interaction request, so as to determine the target interactive view from the dynamic view and the native view according to the interface identifier, call the interface corresponding to the interface identifier to perform interaction between each target interactive view, and then update Dynamic Views and Native Views.
  • the present application also provides a view interaction electronic device, including: one or more processors; a storage device for storing one or more programs, when the one or more programs are executed by the one or more processors, One or more processors are made to implement the above-mentioned view interaction method.
  • the present application also provides a computer-readable medium, on which a computer program is stored, and when the program is executed by a processor, the above view interaction method is realized.
  • FIG. 1 is a schematic diagram of the main flow of a view interaction method according to one or more embodiments of the present application
  • FIG. 2 is a schematic diagram of a main flow of a view interaction method according to one or more embodiments of the present application
  • Fig. 3 is a schematic diagram of an application scenario of a view interaction method according to one or more embodiments of the present application
  • Fig. 4 is a schematic diagram of execution logic in a dynamic view container in one or more embodiments of the present application.
  • Fig. 5 is a schematic diagram of execution logic of a dynamic view container in one or more embodiments of the present application.
  • Fig. 6a and Fig. 6b are schematic diagrams of registration and invocation logic of a dynamic view router in one or more embodiments of the present application;
  • Fig. 7 is a schematic diagram of main units of a view interaction device according to one or more embodiments of the present application.
  • FIG. 8 is an exemplary system architecture diagram that can be applied in one or more embodiments of the present application.
  • Fig. 9 is a schematic structural diagram of a computer system suitable for implementing a terminal device or a server in one or more embodiments of the present application.
  • Fig. 1 is a schematic diagram of the main flow of a view interaction method according to one or more embodiments of the present application. As shown in Fig. 1, the view interaction method includes:
  • Step S101 receiving a view interaction request, and determining a view mix layout according to the view interaction request.
  • the execution subject of the view interaction method may receive the view interaction request sent by the user through the terminal device through a wired connection or a wireless connection.
  • a view interaction request can be a request for interaction between a native view and a native view on the same page, or a request for interaction between a native view and a dynamic view on the same page, or between a dynamic view and a dynamic view on the same page interactive request.
  • the embodiment of the present application does not specifically limit the type of the view interaction request.
  • the execution subject can call the page configuration platform to configure the native view and dynamic view in the page according to the configuration parameters carried in the view interaction request. Specifically, the execution subject can obtain the configuration parameters carried in the view interaction request, and then determine the configuration location information of the native view and the configuration location information of the dynamic view in the page from the configuration parameters, as well as the page element information and Page element information in dynamic view.
  • the page element information may include the size of the page element and the acquisition address corresponding to the page element, etc.
  • the embodiment of the present application does not limit the specific content contained in the page element information.
  • the page configuration platform determines the specific implementation part of the hybrid page through the layout configuration of the native view and the dynamic view.
  • the generated configuration file is provided for end-side acquisition and loading.
  • the execution subject can specifically determine the mixed view layout of the dynamic view and the native view on the page according to the configuration location information of the dynamic view and the native view and the page element information in the configuration parameters carried in the view interaction request.
  • Step S102 call the corresponding dynamic view code package according to the view mix layout to perform view rendering and generate a dynamic view.
  • the execution subject can preset the view container according to the view mix layout. Specifically, when the execution subject presets the native view, it can directly load the native view elements to the native view layout position of the page. Native view elements, such as a button, a list, etc.
  • the execution subject presets the dynamic view container it can download the developed, debugged, compiled, packaged, and released dynamic view code package from the dynamic view platform to the end-side local (end-side, refers to PC, Mac, iOS, Android, etc.), if there is a dynamic view code package of the same version locally on the device side, the execution subject can directly load the dynamic view code package, and then perform view rendering at the layout position corresponding to the dynamic view to generate the final dynamic view.
  • the execution subject can start the dynamic view environment, load the dynamic view code package, and perform analysis, code command execution, and rendering processing to convert into native view elements, and then the execution subject can insert the rendered native view elements into the dynamic view
  • the preset layout position of the container can complete the dynamic view rendering.
  • the execution subject can call the device-side page layout configuration to preset native views and preset dynamic view containers.
  • the device-side page layout configuration obtains the configuration of the page configuration platform, analyzes and obtains the layout of native and dynamic views, and loads the dynamic view container in advance.
  • the dynamic view container is loaded to analyze and execute the dynamic view code package, and finally realize the rendering of the view and the interaction of the page.
  • End-side refers to the terminal where the current page is located, such as PC, Mac, iOS, and Android.
  • the preset can be based on the configuration in the acquisition page configuration platform, and if it is recognized as a dynamic view by parsing, then the dynamic view container will be added to the corresponding layout position.
  • Step S103 determine the page corresponding to the dynamic view, and call the native view element to generate a native view on the page based on the hybrid layout of the view.
  • generating the native view includes: determining the position of the native view corresponding to the view hybrid layout; loading elements of the native view to the position of the native view to generate the native view.
  • the native view element for example, may be a button, a list, etc.
  • the embodiment of the present application does not specifically limit the content contained in the native view element.
  • Step S104 determine the interface identifier corresponding to the view interaction request, so as to determine the target interactive view from the dynamic view and the native view according to the interface identifier, call the interface corresponding to the interface identifier to interact between each target interactive view, and then update the dynamic view and the native view view.
  • View interaction can be divided into three types of interaction: interaction between native view and native view, interaction between native view and dynamic view, and interaction between dynamic view and dynamic view.
  • the target interaction view is determined from the dynamic view and the native view according to the interface identifier, including:
  • each native view corresponding to the native interface is a target interaction view.
  • FIG. 3 is a schematic diagram of an application scenario of an embodiment of the present application. As shown by 3071 in FIG. 3 , direct interaction between native views can be performed through the native interface provided by the device. Standard view methods provided by the system or custom methods implemented by view controls can be stored in the native interface.
  • the native view corresponding to the native interface and the dynamic view corresponding to the dynamic environment interface as the target interaction view.
  • the execution subject determines that the interface identifier includes YS and HJ, it can be determined that the interface identifier corresponds to the native interface and the dynamic environment interface, and then the execution subject can set the corresponding relationship between the native interface and the target interaction view according to the preset correspondence between the interface
  • the dynamic view corresponding to the native view and the dynamic environment interface is the target interaction view.
  • the dynamic environment interface In response to determining that the interface identifier corresponds to the native interface and the dynamic environment interface, call the dynamic environment interface to write the method of the corresponding target dynamic view into the dynamic environment, and then call the dynamic view bridge to convert the method of the target dynamic view into a native method for the native
  • the native view corresponding to the interface is called through the native interface.
  • the method of calling the dynamic view by the native view is as follows: the dynamic view exports the method to the dynamic environment by calling the dynamic environment interface, and then converts it into a native method by the dynamic view bridge.
  • the dynamic view calls the method of the native view: the native view registers the method in the dynamic environment through the native interface and the dynamic view bridge, so that the dynamic view can call it in the dynamic environment.
  • calling the interface corresponding to the interface identifier to perform interaction between each target interaction view also includes:
  • the dynamic view bridge In response to determining that the interface identifier corresponds to the native interface and the dynamic environment interface, determine the target native view based on the native interface, and then call the dynamic view bridge to write the method of the target native view into the dynamic environment for the target dynamic view corresponding to the dynamic environment interface to perform transfer.
  • the dynamic view corresponding to the dynamic environment interface is the target interaction view.
  • the execution subject determines that the interface identifier includes HJ and QJ, it can be determined that the interface identifier corresponds to the dynamic environment interface and the bridging interface, and then the execution subject can determine two or more corresponding dynamic views according to the dynamic environment interface as the target interaction view .
  • the bridging interface can be an interface on the dynamic view bridge, as shown in 3073 in Figure 3, the execution subject can export the method corresponding to the dynamic view to the dynamic environment through the dynamic environment interface, and then the dynamic view bridge can Converted into a native method, the native method then registers the method name in the dynamic environment through the dynamic view bridge for secondary bridging, and provides another dynamic view for calling. During the calling process, the unique registration flag of the API is used to prevent self-cyclic calls.
  • a native method may be a method stored in a native interface. Native method refers to the function method provided by the current view or the system or customized by the developer, such as obtaining the size of the view, adding a view, and so on.
  • the dynamic view corresponding to the routing interface is the target interaction view.
  • the routing interface can be the interface on the dynamic view router, as shown in 3073 in Figure 3, when the dynamic view is added to the dynamic view container, the routing method provided externally is registered in the dynamic environment, and the routing method is generally in the form of URL Provided, the dynamic view can directly call the URL through the calling method of page jump, and pass the behavior and parameters of the URL to the specified dynamic view through the URL router, and then the specified dynamic view will analyze the behavior parameters and implement the specific interactive behavior implement.
  • the function method developed based on the dynamic view is stored in the dynamic environment interface, and specific functions corresponding to the function method are provided. For example, whether a certain view element in the dynamic view is displayed, obtain a certain data in the dynamic view, etc.
  • the view mix layout is determined according to the view interaction request; according to the view mix layout, the corresponding dynamic view code package is invoked to perform view rendering to generate a dynamic view; the page corresponding to the dynamic view is determined, and the native View elements, based on the mixed layout of views, generate native views on the page; determine the interface identifier corresponding to the view interaction request, determine the target interactive view from the dynamic view and native view according to the interface identifier, and call the interface corresponding to the interface identifier to perform each target Interaction between interactive views, and then update dynamic views and native views. Realize cross-terminal interaction between native views, dynamic views, native views and dynamic views on the same page, and dynamic update after view interaction on the same page.
  • Fig. 2 is a schematic flowchart of a view interaction method according to one or more embodiments of the present application. As shown in Fig. 2, the view interaction method includes:
  • step S201 a view interaction request is received, and a view mix layout is determined according to the view interaction request.
  • step S201 is similar to the principle of step S101, and will not be repeated here.
  • Step S202 determining the dynamic view position and dynamic view elements corresponding to the view mix layout.
  • the position of the dynamic view may be determined, for example, according to the position information carried in the view interaction request.
  • the carried position information may include the top, bottom, left, and right margins of the page where the dynamic view is located, and the dynamic view position is determined according to the top, bottom, left, and right margins.
  • Step S203 calling the dynamic view platform to generate a dynamic view code package based on the dynamic view elements.
  • the dynamic view elements may include different view modules for building a page. Such as a button, a list, etc.
  • the execution subject determines the location of the dynamic view and the elements of the dynamic view, it can call the dynamic view platform to develop, debug, compile, package, and release the dynamic view based on the dynamic view elements and actual requirements, and then generate the dynamic view code package.
  • the dynamic view platform creates and generates the corresponding dynamic view code package and releases it for synchronization to the page configuration platform and sends it to the terminal as required.
  • Step S204 calling the dynamic view container, loading the dynamic view code package, and then parsing the dynamic view code command, executing the dynamic view code command, and then rendering the command execution result to generate a corresponding native view element.
  • Step S205 inserting the corresponding native view element into the position of the dynamic view to generate the dynamic view.
  • the end-side starts the dynamic view environment, loads the dynamic package, and performs parsing, code command execution, rendering processing and conversion into native view elements.
  • the rendered native view elements are inserted into the preset layout position of the dynamic container, and the view presentation is completed. In this way, the interaction between views and view updates can be realized across terminals on the same page.
  • the dynamic view container is a dynamic view collection device that integrates dynamic view rendering and interaction, inserts native pages through dynamic view rendering, supports native hybrid rendering capabilities, and supports native views through dynamic view bridges and dynamic view routers. Dynamic interaction between views.
  • the steps of dynamic view rendering may be: dynamic view downloading-starting dynamic view environment-dynamic view analysis-dynamic view execution-dynamic view rendering-inserting native pages.
  • the dynamic view interaction in Figure 4 and Figure 5 when executing the dynamic view code, load the dynamic view code, inject the dynamic view code description, then configure the dynamic native component and install the dynamic code executor, then initialize the dynamic native component, and finally execute The method corresponding to the native component.
  • the steps of dynamic view interaction may be: calling the dynamic view code through the dynamic view bridge, and then loading it into the dynamic environment.
  • inject the corresponding dynamic code description inject the corresponding dynamic code description, analyze the description, configure and load the native component, initialize the native component when executing the code, call and execute the corresponding method of the native component, and then update the dynamic according to the execution result view and native view.
  • the dynamic view router provides the dynamic view with the ability to register the routing method to the routing dispatch center, and when other dynamic views are called, resolve to find the corresponding dynamic view, and execute the dynamic view method.
  • Fig. 6a it is a schematic diagram of the registration method of the dynamic view router, and the execution subject can call the dynamic view container 1 to register the routing method to the routing dispatch center.
  • FIG. 6b it is a schematic diagram of the calling method of the dynamic view router.
  • the execution subject can call the dynamic view container 2 to find the called routing method in the routing dispatch center, then parse the routing address corresponding to the routing method, and then call the dynamic view container 1 , to analyze the routing landing behavior and parameters based on the routing address, and then execute the corresponding method. For example, when calling, the execution subject invokes the dynamic view container 2 to resolve to the specific component ID (moduleID) and method methods according to the moduleConfig in the URL, searches in the cached data of the routing dispatch center, and then invokes.
  • moduleID specific component ID
  • step S206 the page corresponding to the dynamic view is determined, and the native view element is invoked to generate a native view on the page based on the hybrid layout of the view.
  • Step S207 determine the interface identifier corresponding to the view interaction request, so as to determine the target interactive view from the dynamic view and the native view according to the interface identifier, call the interface corresponding to the interface identifier to perform interaction between each target interactive view, and then update the dynamic view and the native view view.
  • steps S206-S207 are similar to those of steps S103-S104, and will not be repeated here.
  • URL Uniform resource locator
  • the interaction method between views can be other interaction methods, for example, by building a behavior server, the view control initiates a behavior request to the behavior server through the network, and then Then push the behavior to the specified view control through the server for behavior processing. The entire interaction process is transferred through the web server.
  • This application does not specifically limit the interaction manner between views.
  • Fig. 3 is a schematic diagram of an application scenario of a view interaction method according to one or more embodiments of the present application.
  • the view interaction method in the embodiment of the present application can be applied to a scene where views interact with each other in a cross-device mixed page.
  • the server 302 receives the view interaction request 301, and determines the view mixing layout 303 according to the view interaction request 301, specifically, the page configuration platform B can be called to perform page A
  • the configuration is specifically to configure the native view and the dynamic view in page A, and then obtain the view mix layout 303 (the embodiment of the present application does not specifically limit the arrangement positions of the dynamic view and the native view in the view mix layout).
  • the server 302 calls the corresponding dynamic view code package 304 according to the view mixing layout 303 (wherein, the dynamic view code package can be called by the server 302 to the dynamic view platform D, by performing dynamic view development, dynamic view debugging, dynamic view compilation, dynamic View packaging, dynamic view publishing to the dynamic view management background), to perform view rendering to generate dynamic views a, c.
  • the server 302 determines the page A corresponding to the dynamic views a and c, and calls the native view element 305 to generate native views b, d, and e on the page A based on the view mix layout 303 .
  • the server 302 determines the interface identifier 306 corresponding to the view interaction request 301, so as to determine the target interaction view 307 from the dynamic views a, c and native views b, d, and e according to the interface identifier 306, and calls the interface corresponding to the interface identifier 306, such as a native interface 3061, the dynamic environment interface 3062, the dynamic view bridge 3063 or the dynamic view router 3064 perform the interaction between the target interactive views 307 (for example, the native view b interacts with the native view e through the native interface 3061; the native view d interacts with the native view e through the native interface 3061 , dynamic view bridge 3063, dynamic environment interface 308 to interact with dynamic view c; dynamic view c can interact with dynamic view a through dynamic environment interface 308, dynamic view bridge 3063, native interface 3061 or dynamic view c through dynamic The view router 3064 then interacts with the dynamic view a based on the routing method 309), and then updates the dynamic views a, c and native views b,
  • the embodiment of this application adopts the fusion method of cross-end mixed pages, firstly through the page configuration and view container preset layout, the dynamic view container is dynamically updated and rendered into native elements inserted into the corresponding layout to complete the rendering, and then through the native interface and dynamic view bridging
  • the combination of the router and the dynamic view router realizes the interaction between native views, between dynamic views, and between native views and dynamic views, and realizes dynamic updates across terminals (partial or all pages) in the same page.
  • Fig. 7 is a schematic diagram of main units of a view interaction device according to one or more embodiments of the present application.
  • the view interaction device includes a receiving unit 701 , a dynamic view rendering unit 702 , a native view generating unit 703 and a view interaction unit 704 .
  • the receiving unit 701 is configured to receive a view interaction request, and determine a view mix layout according to the view interaction request.
  • the dynamic view rendering unit 702 is configured to call the corresponding dynamic view code package according to the view mix layout to perform view rendering and generate a dynamic view.
  • the native view generation unit 703 is configured to determine the page corresponding to the dynamic view, call the native view element, and generate the native view on the page based on the hybrid layout of the view.
  • the view interaction unit 704 is configured to determine the interface identifier corresponding to the view interaction request, so as to determine the target interactive view from the dynamic view and the native view according to the interface identifier, and call the interface corresponding to the interface identifier to perform interaction between each target interactive view, and then Update dynamic and native views.
  • the dynamic view rendering unit 702 is further configured to: determine the dynamic view position and dynamic view elements corresponding to the view hybrid layout; call the dynamic view platform to generate a dynamic view code package based on the dynamic view elements.
  • the dynamic view rendering unit 702 is further configured to: call the dynamic view container, load the dynamic view code package, and then parse the dynamic view code command, execute the dynamic view code command, and then render the command execution result to generate a corresponding The native view element of ; insert the corresponding native view element into the dynamic view position to generate the dynamic view.
  • the native view generation unit 703 is further configured to: determine the native view position corresponding to the view hybrid layout; load the native view element to the native view position, and generate the native view.
  • the view interaction unit 704 is further configured to: in response to determining that the interface identifier corresponds to a native interface, determine that each native view corresponding to the native interface is a target interaction view; in response to determining that the interface identifier corresponds to a native interface and a dynamic environment interface, Determine the native view corresponding to the native interface and the dynamic view corresponding to the dynamic environment interface as the target interaction view; in response to determining that the interface identifier corresponds to the dynamic environment interface and the bridge interface, determine the dynamic view corresponding to the dynamic environment interface as the target interaction view; in response to determining the interface Identify the corresponding routing interface, and determine the dynamic view corresponding to the routing interface as the target interaction view.
  • the view interaction unit 704 is further configured to: in response to determining that the interface identifier corresponds to the native interface and the dynamic environment interface, call the dynamic environment interface to write the method of the corresponding target dynamic view into the dynamic environment, and then call the dynamic view bridge
  • the converter converts the method of the target dynamic view into a native method, so that the native view corresponding to the native interface can be called through the native interface.
  • the view interaction unit 704 is further configured to: in response to determining that the interface identifier corresponds to the native interface and the dynamic environment interface, determine the target native view based on the native interface, and then call the dynamic view bridge to write the method of the target native view Enter the dynamic environment for the target dynamic view corresponding to the dynamic environment interface to call.
  • the view interaction unit 704 is further configured to: in response to determining that the interface identifier corresponds to the dynamic environment interface and the bridge interface, write the method of the target dynamic view corresponding to the dynamic environment interface into the dynamic environment, and then call the dynamic view bridge Converter into a native method, and then call the dynamic view bridge again to write the native method into the dynamic environment for secondary bridging, so that other target dynamic views corresponding to the dynamic environment interface can be called.
  • the view interaction unit 704 is further configured to: in response to determining that the interface identifier corresponds to the routing interface, add the target dynamic view corresponding to the routing interface to the dynamic view container, and write the route corresponding to the routing interface in the dynamic environment Method; call the routing interface to obtain the behavior and parameters corresponding to the routing method, parse the behavior and parameters, and then execute the interaction between the target dynamic views according to the parsing results.
  • Fig. 8 shows an exemplary system architecture 800 to which the view interaction method or view interaction device in one or more embodiments of the present application can be applied.
  • a system architecture 800 may include terminal devices 801 , 802 , and 803 , a network 804 and a server 805 .
  • the network 804 is used as a medium for providing communication links between the terminal devices 801 , 802 , 803 and the server 805 .
  • Network 804 may include various connection types, such as wires, wireless communication links, or fiber optic cables, among others.
  • terminal devices 801, 802, 803 Users can use terminal devices 801, 802, 803 to interact with server 805 through network 804 to receive or send messages and the like.
  • Various communication client applications can be installed on the terminal devices 801, 802, and 803, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (just examples).
  • Terminal devices 801, 802, and 803 may be various electronic devices that have view interaction processing screens and support web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.
  • the server 805 may be a server that provides various services, such as a background management server that provides support for view interaction requests submitted by users using terminal devices 801 , 802 , and 803 (just an example).
  • the background management server can receive the view interaction request, and determine the view mix layout according to the view interaction request; call the corresponding dynamic view code package according to the view mix layout to perform view rendering and generate a dynamic view; determine the page corresponding to the dynamic view, and call the native View elements, based on the mixed layout of views, generate native views on the page; determine the interface identifier corresponding to the view interaction request, determine the target interactive view from the dynamic view and native view according to the interface identifier, and call the interface corresponding to the interface identifier to perform each target Interaction between interactive views, and then update dynamic views and native views. Realize cross-terminal interaction between native views, dynamic views, native views and dynamic views on the same page, and dynamic update after view interaction on the same page.
  • the view interaction method provided in the embodiment of the present application is generally executed by the server 805 , and correspondingly, the view interaction device is generally set in the server 805 .
  • terminal devices, networks and servers in FIG. 8 are only illustrative. According to the implementation needs, there can be any number of terminal devices, networks and servers.
  • FIG. 9 shows a schematic structural diagram of a computer system 900 suitable for implementing a terminal device according to an embodiment of the present application.
  • the terminal device shown in FIG. 9 is only an example, and should not limit the functions and scope of use of this embodiment of the present application.
  • a computer system 900 includes a central processing unit (CPU) 901 that can be programmed according to a program stored in a read-only memory (ROM) 902 or a program loaded from a storage section 908 into a random access memory (RAM) 903 Instead, various appropriate actions and processes are performed.
  • ROM read-only memory
  • RAM random access memory
  • various programs and data necessary for the operation of the computer system 900 are also stored.
  • the CPU 901 , ROM 902 , and RAM 903 are connected to each other via a bus 904 .
  • An input/output (I/O) interface 905 is also connected to the bus 904 .
  • the following components are connected to the I/O interface 905: an input part 906 including a keyboard, a mouse, etc.; an output part 907 including a cathode ray tube (CRT), a liquid crystal credit investigation processor (LCD) and a loudspeaker; including a hard disk and a communication section 909 including a network interface card such as a LAN card, a modem, and the like.
  • the communication section 909 performs communication processing via a network such as the Internet.
  • a drive 910 is also connected to the I/O interface 905 as needed.
  • a removable medium 911 such as a magnetic disk, optical disk, magneto-optical disk, semiconductor memory, etc. is mounted on the drive 910 as necessary so that a computer program read therefrom is installed into the storage section 908 as necessary.
  • the processes described above with reference to the flowcharts can be implemented as computer software programs.
  • the embodiments disclosed in this application include a computer program product, which includes a computer program carried on a computer-readable medium, where the computer program includes program codes for executing the methods shown in the flowcharts.
  • the computer program may be downloaded and installed from a network via communication portion 909 and/or installed from removable media 911 .
  • this computer program is executed by a central processing unit (CPU) 901
  • CPU central processing unit
  • the computer-readable medium shown in this application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two.
  • a computer-readable storage medium may include, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to, electrical connections with one or more wires, portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable Programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.
  • a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.
  • a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, in which computer-readable program codes are carried. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • a computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.
  • Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
  • each block in a flowchart or block diagram may represent a module, program segment, or portion of code that includes one or more logical functions for implementing specified executable instructions.
  • the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or they may sometimes be executed in the reverse order, depending upon the functionality involved.
  • each block in the block diagrams or flowchart illustrations, and combinations of blocks in the block diagrams or flowchart illustrations can be implemented by a dedicated hardware-based system that performs the specified function or operation, or can be implemented by a A combination of dedicated hardware and computer instructions.
  • the units involved in the embodiments described in the present application may be implemented by means of software or by means of hardware.
  • the described units can also be set in a processor, for example, it can be described as: a processor includes a receiving unit, a dynamic view rendering unit, a native view generating unit and a view interaction unit. Wherein, the names of these units do not constitute a limitation of the unit itself under certain circumstances.
  • the present application also provides a computer-readable medium.
  • the computer-readable medium may be contained in the device described in the above embodiments, or may exist independently without being assembled into the device.
  • the above-mentioned computer-readable medium carries one or more programs, and when the above-mentioned one or more programs are executed by the device, the device receives a view interaction request, and determines the view mixing layout according to the view interaction request; according to the view mixing layout , call the corresponding dynamic view code package to perform view rendering to generate a dynamic view; determine the page corresponding to the dynamic view, and call the native view element to generate a native view on the page based on the mixed layout of the view; determine the interface identifier corresponding to the view interaction request , so as to determine the target interactive view from the dynamic view and the native view according to the interface identifier, call the interface corresponding to the interface identifier to perform interaction between each target interactive view, and then update the dynamic view and the native view.
  • the interaction among native views, between dynamic views, between native views and dynamic views and the dynamic update after view interaction in the same page are realized across terminals on the same page.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Stored Programmes (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

本申请公开了视图交互方法、装置、电子设备及计算机可读介质，具体实施方式包括接收视图交互请求，根据视图交互请求确定视图混编布局；根据视图混编布局，调用对应的动态视图代码包，以进行视图渲染生成动态视图；确定动态视图对应的页面，调用原生视图元素，以基于视图混编布局，在页面生成原生视图；确定视图交互请求对应的接口标识，以根据接口标识从动态视图和原生视图中确定目标交互视图，调用接口标识对应的接口进行各目标交互视图之间的交互，进而更新动态视图和原生视图。

Description

视图交互方法、装置、电子设备及计算机可读介质
相关申请的交叉引用
本申请要求享有2021年11月11日提交的名称为“一种视图交互方法、装置、电子设备及计算机可读介质”的中国专利申请No.202111335618.X的优先权，在此全文引用上述中国专利申请公开的内容以作为本申请的一部分或全部。
技术领域
本申请涉及计算机技术领域，尤其涉及一种视图交互方法、装置、电子设备及计算机可读介质。
背景技术
目前，在进行页面开发时，动态视图页面不能和已有原生页面进行页面元素共存，从而无法实现同一页面上的动态页面视图与已有的原生页面视图的交互。
发明内容
有鉴于此，本申请实施例提供一种视图交互方法、装置、电子设备及计算机可读介质，能够解决现有的无法实现同一页面上的动态页面视图与已有的原生页面视图的交互的问题。
为实现上述目的，根据本申请实施例的一个方面，提供了一种视图交互方法，包括：
接收视图交互请求，根据视图交互请求确定视图混编布局；
根据视图混编布局，调用对应的动态视图代码包，以进行视图渲染生成动态视图；
确定动态视图对应的页面，调用原生视图元素，以基于视图混编布局，在页面生成原生视图；
确定视图交互请求对应的接口标识，以根据接口标识从动态视图和原生视图中确定目标交互视图，调用接口标识对应的接口进行各目标交互视图之间的交互，进而更新动态视图和原生视图。
在本申请的一个或多个实施例中，在调用对应的动态视图代码包之前，方法还包括：
确定视图混编布局对应的动态视图位置和动态视图元素；
调用动态视图平台，以基于动态视图元素生成动态视图代码包。
在本申请的一个或多个实施例中，进行视图渲染生成动态视图，包括：
调用动态视图容器，加载动态视图代码包，进而解析得到动态视图代码命令，执行动态视图代码命令，进而对命令执行结果进行渲染生成对应的原生视图元素；
将对应的原生视图元素插入动态视图位置，以生成动态视图。
在本申请的一个或多个实施例中，生成原生视图，包括：
确定视图混编布局对应的原生视图位置；
加载原生视图元素至原生视图位置，生成原生视图。
在本申请的一个或多个实施例中，根据接口标识从动态视图和原生视图中确定目标交互视图，包括：
响应于确定接口标识对应原生接口，确定原生接口对应的各原生视图为目标交互视图；
响应于确定接口标识对应原生接口和动态环境接口，确定原生接口对应的原生视图和动态环境接口对应的动态视图为目标交互视图；
响应于确定接口标识对应动态环境接口和桥接接口，确定动态环境接口对应的动态视图为目标交互视图；
响应于确定接口标识对应路由接口，确定路由接口对应的动态视图为目标交互视图。
在本申请的一个或多个实施例中，调用接口标识对应的接口进行各目标交互视图之间的交互，包括：
响应于确定接口标识对应原生接口和动态环境接口，调用动态环境接口将对应的目标动态视图的方法写入动态环境，进而调用动态视图桥接器将目标动态视图的方法转换为原生方法，以供原生接口对应的原生视图通过原生接口进行调用。
在本申请的一个或多个实施例中，调用接口标识对应的接口进行各目标交互视图之间的交互，包括：
响应于确定接口标识对应原生接口和动态环境接口，基于原生接口确定目标原生视图，进而调用动态视图桥接器，将目标原生视图的方法写入动态环境，以供动态环境接口对应的目标动态视图进行调用。
在本申请的一个或多个实施例中，调用接口标识对应的接口进行各目标交互视图之间的交互，包括：
响应于确定接口标识对应动态环境接口和桥接接口，将动态环境接口对应的目标动态视图的方法写入动态环境中，进而调用动态视图桥接器转换成原生方法，进而再次调用动态视图桥接器将原生方法写入至动态环境中进行二次桥接，以供动态环境接口对应的其他目标动态视图进行调用。
在本申请的一个或多个实施例中，调用接口标识对应的接口进行各目标交互视图之间的交互，包括：
响应于确定接口标识对应路由接口，将路由接口对应的目标动态视图添加至动态视图容器中，在动态环境中写入路由接口对应的路由方法；
调用路由接口以获取路由方法对应的行为及参数，解析行为及参数，进而根据解析结果执行各目标动态视图之间的交互。
另外，本申请还提供了一种视图交互装置，包括：
接收单元，被配置成接收视图交互请求，根据视图交互请求确定视图混编布局；
动态视图渲染单元，被配置成根据视图混编布局，调用对应的动态视图代码包，以进行视图渲染生成动态视图；
原生视图生成单元，被配置成确定动态视图对应的页面，调用原生视图元素，以基于视图混编布局，在页面生成原生视图；
视图交互单元，被配置成确定视图交互请求对应的接口标识，以根据接口标识从动态视图和原生视图中确定目标交互视图，调用接口标识对应的接口进行各目标交互视图之间的交互，进而更新动态视图和原生视图。
另外，本申请还提供了一种视图交互电子设备，包括：一个或多个处理器；存储装置，用于存储一个或多个程序，当一个或多个程序被一个或多个处理器执行，使得一个或多个处理器实现如上述的视图交互方法。
另外，本申请还提供了一种计算机可读介质，其上存储有计算机程序，程序被处理器执行时实现如上述的视图交互方法。
上述的非惯用的可选方式所具有的进一步效果将在下文中结合具体实施方式加以说明。
附图说明
附图用于更好地理解本申请，不构成对本申请的不当限定。其中：
图1是根据本申请一个或多个实施例中的视图交互方法的主要流程的示意图；
图2是根据本申请一个或多个实施例中的视图交互方法的主要流程的示意图；
图3是根据本申请一个或多个实施例中的视图交互方法的应用场 景示意图；
图4是本申请一个或多个实施例中的动态视图容器中的执行逻辑示意图；
图5是本申请一个或多个实施例中的动态视图容器的执行逻辑示意图；
图6a、图6b分别是本申请一个或多个实施例中的动态视图路由器的注册和调用逻辑示意图；
图7是根据本申请一个或多个实施例中的视图交互装置的主要单元的示意图；
图8是本申请一个或多个实施例中可以应用于其中的示例性系统架构图；
图9是适于用来实现本申请一个或多个实施例中的终端设备或服务器的计算机系统的结构示意图。
具体实施方式
以下结合附图对本申请的示范性实施例做出说明，其中包括本申请实施例的各种细节以助于理解，应当将它们认为仅仅是示范性的。因此，本领域普通技术人员应当认识到，可以对这里描述的实施例做出各种改变和修改，而不会背离本申请的范围和精神。同样，为了清楚和简明，以下的描述中省略了对公知功能和结构的描述。
图1是根据本申请一个或多个实施例中的视图交互方法的主要流程的示意图，如图1所示，视图交互方法包括：
步骤S101，接收视图交互请求，根据视图交互请求确定视图混编布局。
本实施例中，视图交互方法的执行主体(例如，可以是服务器)可以通过有线连接或无线连接的方式，接收用户通过终端设备发送的视图交互请求。视图交互请求可以是同一页面中原生视图和原生视图之间的交互的请求，也可以是同一页面中原生视图和动态视图之间交互的请求，也可以是同一页面中动态视图和动态视图之间交互的请求。 本申请实施例对视图交互请求的类型不做具体限定。
执行主体在接收视图交互请求后，可以调用页面配置平台以根据视图交互请求中携带的配置参数进行页面中的原生视图和动态视图的配置。具体地，执行主体可以获取视图交互请求中携带的配置参数，然后从配置参数中确定出该页面中的原生视图的配置位置信息和动态视图的配置位置信息，以及原生视图中的页面元素信息和动态视图中的页面元素信息。页面元素信息可以包括页面元素的尺寸以及页面元素对应的获取地址等，本申请实施例对页面元素信息所包含的具体内容不做限定。页面配置平台，通过原生视图和动态视图的布局配置，决定混编页面的具体实现部分。生成的配置文件，提供端侧进行获取加载。
执行主体可以根据视图交互请求中携带的配置参数中的动态视图和原生视图的配置位置信息以及页面元素信息，来具体确定在该页面中，动态视图和原生视图的视图混编布局。
步骤S102，根据视图混编布局，调用对应的动态视图代码包，以进行视图渲染生成动态视图。
执行主体可以根据视图混编布局进行视图容器预置。具体地，执行主体在预置原生视图时，可以直接加载原生视图元素到页面的原生视图布局位置。原生视图元素，比如一个按钮、一个列表等。执行主体在预置动态视图容器时，可以通过从动态视图平台下载已经开发、调试、编译、打包、发布好的动态视图代码包到端侧本地(端侧，指的是PC、Mac、iOS、Android等端)，如果端侧本地已有同版本的动态视图代码包，则执行主体可以直接加载该动态视图代码包，进而在动态视图对应的布局位置进行视图渲染生成最终的动态视图。具体地，执行主体可以启动动态视图环境，加载动态视图代码包，并进行分析、代码命令执行、渲染处理以转换为原生视图元素，然后执行主体可以将渲染后得到的原生视图元素，插入动态视图容器预置的布局位置，即可完成动态视图呈现。具体地，执行主体可以调用端侧页面布局配置来预置原生视图和预置动态视图容器。端侧页面布局配置，通过获取页面配置平台的配置，解析得到原生和动态视图的布局，预置加载 动态视图容器。动态视图容器，加载进行动态视图代码包的解析，执行，最终实现视图的渲染和页面的交互。端侧指当前页面所在终端，比如PC、Mac、iOS、Android。预置，可以是根据获取页面配置平台中的配置，解析识别到是动态视图，则将动态视图容器，添加到对应的布局位置。
步骤S103，确定动态视图对应的页面，调用原生视图元素，以基于视图混编布局，在页面生成原生视图。
具体地，生成原生视图，包括：确定视图混编布局对应的原生视图位置；加载原生视图元素至原生视图位置，生成原生视图。原生视图元素，例如可以是一个按钮、一个列表等，本申请实施例对原生视图元素所包含的内容不做具体限定。
步骤S104，确定视图交互请求对应的接口标识，以根据接口标识从动态视图和原生视图中确定目标交互视图，调用接口标识对应的接口进行各目标交互视图之间的交互，进而更新动态视图和原生视图。
视图交互，可以分为原生视图与原生视图的交互、原生视图与动态视图的交互、动态视图与动态视图的交互三种交互形式。
具体地，根据接口标识从动态视图和原生视图中确定目标交互视图，包括：
响应于确定接口标识对应原生接口，确定原生接口对应的各原生视图为目标交互视图。
具体地，当执行主体确定接口标识对应原生接口时，例如接口标识为YS，则可以确定该接口标识对应原生接口，则目标交互视图可以是页面上的两个或多个原生视图。图3是本申请实施例的应用场景示意图。如图3中的3071所示，可以通过端侧提供的原生接口进行原生视图之间的直接交互。原生接口中可以存储有由系统提供的标准视图方法或者视图控件实现的自定义方法。
响应于确定接口标识对应原生接口和动态环境接口，确定原生接口对应的原生视图和动态环境接口对应的动态视图为目标交互视图。
具体地，当执行主体确定接口标识包括YS和HJ，则可以确定接口标识对应原生接口和动态环境接口，进而执行主体可以根据预先设 定的接口与目标交互视图的对应关系，将原生接口对应的原生视图和动态环境接口对应的动态视图为目标交互视图。本申请对与原生接口和动态环境接口对应的接口标识的具体表示不做限定。
具体地，调用接口标识对应的接口进行各目标交互视图之间的交互，包括：
响应于确定接口标识对应原生接口和动态环境接口，调用动态环境接口将对应的目标动态视图的方法写入动态环境，进而调用动态视图桥接器将目标动态视图的方法转换为原生方法，以供原生接口对应的原生视图通过原生接口进行调用。示例的，如图3中的3072所示，原生视图调用动态视图的方法为：动态视图通过调用动态环境接口将方法导出到动态环境中，然后再由动态视图桥接器转换成原生的方法，以供原生视图通过调用原生接口进行调用。动态视图调用原生视图的方法：原生视图通过原生接口和动态视图桥接器，将方法注册到动态环境中，以供动态视图在动态环境中进行调用。
具体地，调用接口标识对应的接口进行各目标交互视图之间的交互，还包括：
响应于确定接口标识对应原生接口和动态环境接口，基于原生接口确定目标原生视图，进而调用动态视图桥接器，将目标原生视图的方法写入动态环境，以供动态环境接口对应的目标动态视图进行调用。
响应于确定接口标识对应动态环境接口和桥接接口，确定动态环境接口对应的动态视图为目标交互视图。
具体地，当执行主体确定接口标识包括HJ和QJ，则可以确定接口标识对应动态环境接口和桥接接口，进而执行主体可以根据动态环境接口确定对应的两个或多个动态视图并作为目标交互视图。
具体地，调用接口标识对应的接口进行各目标交互视图之间的交互，包括：
响应于确定接口标识对应动态环境接口和桥接接口，将动态环境接口对应的目标动态视图的方法写入动态环境中，进而调用动态视图桥接器转换成原生方法，进而再次调用动态视图桥接器将原生方法写入至动态环境中进行二次桥接，以供动态环境接口对应的其他目标动 态视图进行调用。示例的，桥接接口可以是动态视图桥接器上的接口，如图3中的3073所示，执行主体可以通过动态环境接口将动态视图对应的方法导出到动态环境中，然后再由动态视图桥接器转换成原生方法，原生方法再通过动态视图桥接器，将方法指名注册到动态环境中进行二次桥接，供给另一个动态视图进行调用。调用过程中通过API唯一注册标志来防止自身循环调用。原生方法可以是存储于原生接口中的方法。原生方法是指当前视图或系统提供的或研发人员自定义的功能方法，比如获取视图的大小、添加视图的操作等。
响应于确定接口标识对应路由接口，确定路由接口对应的动态视图为目标交互视图。
具体地，调用接口标识对应的接口进行各目标交互视图之间的交互，包括：
响应于确定接口标识对应路由接口，将路由接口对应的目标动态视图添加至动态视图容器中，在动态环境中写入路由接口对应的路由方法；调用路由接口以获取路由方法对应的行为及参数，解析行为及参数，进而根据解析结果执行各目标动态视图之间的交互。示例的，路由接口可以是动态视图路由器上的接口，如图3中的3073所示，动态视图添加到动态视图容器中时，在动态环境中注册对外提供的路由方法，路由方法一般以URL形式进行提供，动态视图可以通过页面跳转的调用方式直接调用URL，将URL的行为及参数通过URL路由器传递到指定的动态视图中，再由指定的动态视图进行行为参数的解析和具体交互行为的执行。
本申请实施例中，动态环境接口中存储的是基于动态视图开发的功能方法，提供该功能方法对应的具体的功能。比如动态视图中某个视图元素是否显示，获取动态视图中某个数据等
本实施例通过接收视图交互请求，根据视图交互请求确定视图混编布局；根据视图混编布局，调用对应的动态视图代码包，以进行视图渲染生成动态视图；确定动态视图对应的页面，调用原生视图元素，以基于视图混编布局，在页面生成原生视图；确定视图交互请求对应的接口标识，以根据接口标识从动态视图和原生视图中确定目标交互 视图，调用接口标识对应的接口进行各目标交互视图之间的交互，进而更新动态视图和原生视图。实现在同一页面中跨端实现原生视图之间、动态视图之间、原生视图与动态视图之间的交互以及同一页面中视图交互后的动态更新。
图2是根据本申请一个或多个实施例中的视图交互方法的主要流程示意图，如图2所示，视图交互方法包括：
步骤S201，接收视图交互请求，根据视图交互请求确定视图混编布局。
步骤S201的原理与步骤S101的原理类似，此处不再赘述。
步骤S202，确定视图混编布局对应的动态视图位置和动态视图元素。
动态视图位置，例如可以是根据视图交互请求中携带的位置信息确定的，例如，携带的位置信息中可以包括动态视图所在的页面的上下左右边距，根据上下左右边距确定动态视图位置。
步骤S203，调用动态视图平台，以基于动态视图元素生成动态视图代码包。
具体地，动态视图元素可以包括搭建页面的不同视图模块。比如一个按钮、一个列表等。执行主体在确定动态视图位置和动态视图元素后，可以调用动态视图平台，以基于动态视图元素和实际需求进行动态视图开发、调试、编译、打包、发布，进而生成动态视图代码包。
动态视图平台，创建和生成对应动态视图代码包并进行发布，用于同步到页面配置平台，并根据需要下发到终端。
步骤S204，调用动态视图容器，加载动态视图代码包，进而解析得到动态视图代码命令，执行动态视图代码命令，进而对命令执行结果进行渲染生成对应的原生视图元素。
步骤S205，将对应的原生视图元素插入动态视图位置，以生成动态视图。
具体地，端侧启动动态视图环境，加载动态包，并进行解析、代码命令执行、渲染处理转换为原生视图元素。将渲染后的原生视图元 素，插入动态容器预置的布局位置，则完成了视图呈现。从而可以实现在同一个页面中跨端实现视图之间的交互以及视图更新。
具体地，动态视图容器，用于集成动态视图渲染与交互于一体的动态视图集合装置，通过动态视图渲染插入原生页面，支持原生混合渲染能力，通过动态视图桥接器和动态视图路由器支持原生视图、动态视图之间的交互。其中，如图4所示，动态视图渲染的步骤可以为：动态视图下载-启动动态视图环境-动态视图解析-动态视图执行-动态视图渲染-插入原生页面。如图4的动态视图交互和图5所示，执行动态视图代码时，加载动态视图代码，注入动态视图代码描述，然后配置动态原生组件并安装动态代码执行器，进而初始化动态原生组件，最终执行原生组件对应的方法。示例的，动态视图交互的步骤可以为：通过动态视图桥接器调用动态视图代码，进而加载至动态环境中。在执行动态视图代码时，通过注入对应的动态代码描述，对描述进行解析，配置并加载原生组件，并且在执行代码时初始化原生组件，调用原生组件对应的方法并执行，进而根据执行结果更新动态视图和原生视图。
动态代码描述：
用于描述动态代码方法与原生组件方法之间的映射关系及具体行为
如下举例说明
Figure PCTCN2022129242-appb-000001
Figure PCTCN2022129242-appb-000002
动态视图路由器，提供了动态视图将路由方法注册到路由调度中心，并在其他动态视图进行调用时，解析寻找对应的动态视图，并执行动态视图方法的能力。如图6a所示，为动态视图路由器的注册方法示意图，执行主体可以调用动态视图容器1注册路由方法至路由调度中心。示例的，注册时，执行主体调用动态视图容器1将moduleConfig注册到路由调度中心，路由调度中心缓存组件ID和对应的方法列表，用于调用，比如moduleI＝1和methods＝[“jumpUlr”]。如图6b所示，为动态视图路由器的调用方法示意图，执行主体可以调用动态视图容器2以在路由调度中心查找得到调用的路由方法，然后解析路由方法对应的路由地址，然后调用动态视图容器1，以基于路由地址解析路由落地行为及参数，然后执行对应方法。示例的，调用时，执行主体调用动态视图容器2根据URL中的moduleConfig解析到具体的组件ID(moduleID)和方法methods，在路由调度中心的缓存数据中进行查找，然后再调用。比如以下URL：
open.dynamic://openModule？moduleConfig＝{\"moduleID\":1,\"methods\":{\"jumpURL\":{\"type\":1,\"methodID\":1,\"param\":{\"URL\":\"https://xxx.xx/jump/test.html\"}}}}
步骤S206，确定动态视图对应的页面，调用原生视图元素，以基于视图混编布局，在页面生成原生视图。
步骤S207，确定视图交互请求对应的接口标识，以根据接口标识从动态视图和原生视图中确定目标交互视图，调用接口标识对应的接口进行各目标交互视图之间的交互，进而更新动态视图和原生视图。
步骤S206～步骤S207的原理与步骤S103～步骤S104的原理类似，此处不再赘述。
URL：统一资源定位系统(uniform resource locator，URL)是因特网的万维网服务程序上用于指定信息位置的表示方法。
此外，作为本申请实施例的另一种实现方式，视图与视图之间的交互方式，可以为其他交互方式，比如通过搭建行为服务器，视图控件内部通过网络方式，向行为服务器发起行为请求，然后再通过服务器将行为推送到指定的视图控件内部进行行为处理。整个交互流程，通过网络服务器进行中转。本申请对视图与视图之间的交互方式不做具体限定。
图3是根据本申请一个或多个实施例中的视图交互方法的应用场景示意图。本申请实施例的视图交互方法，可以应用于跨端混编页面中的视图之间进行交互的场景。如图3所示，服务器302(服务器302为本申请实施例的执行主体)接收视图交互请求301，根据视图交互请求301确定视图混编布局303，具体可以调用页面配置平台B对页面A进行页面配置，具体为在页面A中配置原生视图和配置动态视图，进而得到视图混编布局303(本申请实施例对视图混编布局中动态视图和原生视图的排布位置不做具体限定)。服务器302根据视图混编布局303，调用对应的动态视图代码包304(其中，动态视图代码包可以是由服务器302调用动态视图平台D，通过执行动态视图开发、动态视图调试、动态视图编译、动态视图打包、动态视图发布至动态视图管理后台而得到的)，以进行视图渲染生成动态视图a、c。服务器302确定动态视图a、c对应的页面A，调用原生视图元素305，以基于视图混编布局303，在页面A生成原生视图b、d、e。服务器302确定视图交互请求301对应的接口标识306，以根据接口标识306从动态视图a、c和原生视图b、d、e中确定目标交互视图307，调用接口标识306对应的接口，例如原生接口3061、动态环境接口3062、动态视图桥接器3063或动态视图路由器3064进行各目标交互视图307之间的交互(例如原生视图b通过原生接口3061与原生视图e进行交互；原生视图d通过原生接口3061、动态视图桥接器3063、动态环境接口308与动态视图c进行交互；动态视图c可以通过动态环境接口308、动态视图桥接器3063、原生接口3061与动态视图a进行交互或者动态视图c可以通过动态视图路由器3064进而基于路由方法309与动态视图a进 行交互)，进而更新页面A中的动态视图a、c和原生视图b、d、e。
本申请实施例通过跨端混编页面的融合方式，首先通过页面配置及视图容器预置布局，动态视图容器动态更新后渲染成原生元素插入对应布局完成渲染，然后是通过原生接口、动态视图桥接器、动态视图路由器三种方式组合实现原生视图之间、动态视图之间、原生视图与动态视图之间的交互，实现在同一个页面中跨端实现(部分及全部页面)动态更新。
图7是根据本申请一个或多个实施例中的视图交互装置的主要单元的示意图。如图7所示，视图交互装置包括接收单元701、动态视图渲染单元702、原生视图生成单元703和视图交互单元704。
接收单元701，被配置成接收视图交互请求，根据视图交互请求确定视图混编布局。
动态视图渲染单元702，被配置成根据视图混编布局，调用对应的动态视图代码包，以进行视图渲染生成动态视图。
原生视图生成单元703，被配置成确定动态视图对应的页面，调用原生视图元素，以基于视图混编布局，在页面生成原生视图。
视图交互单元704，被配置成确定视图交互请求对应的接口标识，以根据接口标识从动态视图和原生视图中确定目标交互视图，调用接口标识对应的接口进行各目标交互视图之间的交互，进而更新动态视图和原生视图。
在一些实施例中，动态视图渲染单元702进一步被配置成：确定视图混编布局对应的动态视图位置和动态视图元素；调用动态视图平台，以基于动态视图元素生成动态视图代码包。
在一些实施例中，动态视图渲染单元702进一步被配置成：调用动态视图容器，加载动态视图代码包，进而解析得到动态视图代码命令，执行动态视图代码命令，进而对命令执行结果进行渲染生成对应的原生视图元素；将对应的原生视图元素插入动态视图位置，以生成动态视图。
在一些实施例中，原生视图生成单元703进一步被配置成：确定 视图混编布局对应的原生视图位置；加载原生视图元素至原生视图位置，生成原生视图。
在一些实施例中，视图交互单元704进一步被配置成：响应于确定接口标识对应原生接口，确定原生接口对应的各原生视图为目标交互视图；响应于确定接口标识对应原生接口和动态环境接口，确定原生接口对应的原生视图和动态环境接口对应的动态视图为目标交互视图；响应于确定接口标识对应动态环境接口和桥接接口，确定动态环境接口对应的动态视图为目标交互视图；响应于确定接口标识对应路由接口，确定路由接口对应的动态视图为目标交互视图。
在一些实施例中，视图交互单元704进一步被配置成：响应于确定接口标识对应原生接口和动态环境接口，调用动态环境接口将对应的目标动态视图的方法写入动态环境，进而调用动态视图桥接器将目标动态视图的方法转换为原生方法，以供原生接口对应的原生视图通过原生接口进行调用。
在一些实施例中，视图交互单元704进一步被配置成：响应于确定接口标识对应原生接口和动态环境接口，基于原生接口确定目标原生视图，进而调用动态视图桥接器，将目标原生视图的方法写入动态环境，以供动态环境接口对应的目标动态视图进行调用。
在一些实施例中，视图交互单元704进一步被配置成：响应于确定接口标识对应动态环境接口和桥接接口，将动态环境接口对应的目标动态视图的方法写入动态环境中，进而调用动态视图桥接器转换成原生方法，进而再次调用动态视图桥接器将原生方法写入至动态环境中进行二次桥接，以供动态环境接口对应的其他目标动态视图进行调用。
在一些实施例中，视图交互单元704进一步被配置成：响应于确定接口标识对应路由接口，将路由接口对应的目标动态视图添加至动态视图容器中，在动态环境中写入路由接口对应的路由方法；调用路由接口以获取路由方法对应的行为及参数，解析行为及参数，进而根据解析结果执行各目标动态视图之间的交互。
需要说明的是，在本申请视图交互方法和视图交互装置在具体实 施内容上具有相应关系，故重复内容不再说明。
图8示出了可以应用本申请一个或多个实施例中的视图交互方法或视图交互装置的示例性系统架构800。
如图8所示，系统架构800可以包括终端设备801、802、803，网络804和服务器805。网络804用以在终端设备801、802、803和服务器805之间提供通信链路的介质。网络804可以包括各种连接类型，例如有线、无线通信链路或者光纤电缆等等。
用户可以使用终端设备801、802、803通过网络804与服务器805交互，以接收或发送消息等。终端设备801、802、803上可以安装有各种通讯客户端应用，例如购物类应用、网页浏览器应用、搜索类应用、即时通信工具、邮箱客户端、社交平台软件等(仅为示例)。
终端设备801、802、803可以是具有视图交互处理屏并且支持网页浏览的各种电子设备，包括但不限于智能手机、平板电脑、膝上型便携计算机和台式计算机等等。
服务器805可以是提供各种服务的服务器，例如对用户利用终端设备801、802、803所提交的视图交互请求提供支持的后台管理服务器(仅为示例)。后台管理服务器可以接收视图交互请求，根据视图交互请求确定视图混编布局；根据视图混编布局，调用对应的动态视图代码包，以进行视图渲染生成动态视图；确定动态视图对应的页面，调用原生视图元素，以基于视图混编布局，在页面生成原生视图；确定视图交互请求对应的接口标识，以根据接口标识从动态视图和原生视图中确定目标交互视图，调用接口标识对应的接口进行各目标交互视图之间的交互，进而更新动态视图和原生视图。实现在同一页面中跨端实现原生视图之间、动态视图之间、原生视图与动态视图之间的交互以及同一页面中视图交互后的动态更新。
需要说明的是，本申请实施例所提供的视图交互方法一般由服务器805执行，相应地，视图交互装置一般设置于服务器805中。
应该理解，图8中的终端设备、网络和服务器的数目仅仅是示意性的。根据实现需要，可以具有任意数目的终端设备、网络和服务器。
下面参考图9，其示出了适于用来实现本申请实施例的终端设备的计算机系统900的结构示意图。图9示出的终端设备仅仅是一个示例，不应对本申请实施例的功能和使用范围带来任何限制。
如图9所示，计算机系统900包括中央处理单元(CPU)901，其可以根据存储在只读存储器(ROM)902中的程序或者从存储部分908加载到随机访问存储器(RAM)903中的程序而执行各种适当的动作和处理。在RAM903中，还存储有计算机系统900操作所需的各种程序和数据。CPU901、ROM902以及RAM903通过总线904彼此相连。输入/输出(I/O)接口905也连接至总线904。
以下部件连接至I/O接口905：包括键盘、鼠标等的输入部分906；包括诸如阴极射线管(CRT)、液晶征信授权查询处理器(LCD)等以及扬声器等的输出部分907；包括硬盘等的存储部分908；以及包括诸如LAN卡、调制解调器等的网络接口卡的通信部分909。通信部分909经由诸如因特网的网络执行通信处理。驱动器910也根据需要连接至I/O接口905。可拆卸介质911，诸如磁盘、光盘、磁光盘、半导体存储器等等，根据需要安装在驱动器910上，以便于从其上读出的计算机程序根据需要被安装入存储部分908。
特别地，根据本申请公开的实施例，上文参考流程图描述的过程可以被实现为计算机软件程序。例如，本申请公开的实施例包括一种计算机程序产品，其包括承载在计算机可读介质上的计算机程序，该计算机程序包含用于执行流程图所示的方法的程序代码。在这样的实施例中，该计算机程序可以通过通信部分909从网络上被下载和安装，和/或从可拆卸介质911被安装。在该计算机程序被中央处理单元(CPU)901执行时，执行本申请的系统中限定的上述功能。
需要说明的是，本申请所示的计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质或者是上述两者的任意组合。计算机可读存储介质例如可以包括但不限于电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。计算机可读存储介质的更具体的例子可以包括但不限于：具有一个或多个导线的电 连接、便携式计算机磁盘、硬盘、随机访问存储器(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(EPROM或闪存)、光纤、便携式紧凑磁盘只读存储器(CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。在本申请中，计算机可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。而在本申请中，计算机可读的信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了计算机可读的程序代码。这种传播的数据信号可以采用多种形式，包括但不限于电磁信号、光信号或上述的任意合适的组合。计算机可读的信号介质还可以是计算机可读存储介质以外的任何计算机可读介质，该计算机可读介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。计算机可读介质上包含的程序代码可以用任何适当的介质传输，包括但不限于：无线、电线、光缆、RF等等，或者上述的任意合适的组合。
附图中的流程图和框图，图示了按照本申请各种实施例的系统、方法和计算机程序产品的可能实现的体系架构、功能和操作。在这点上，流程图或框图中的每个方框可以代表一个模块、程序段、或代码的一部分，上述模块、程序段、或代码的一部分包含一个或多个用于实现规定的逻辑功能的可执行指令。也应当注意，在有些作为替换的实现中，方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如，两个接连地表示的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行，这依所涉及的功能而定。也要注意的是，框图或流程图中的每个方框、以及框图或流程图中的方框的组合，可以用执行规定的功能或操作的专用的基于硬件的系统来实现，或者可以用专用硬件与计算机指令的组合来实现。
描述于本申请实施例中所涉及到的单元可以通过软件的方式实现，也可以通过硬件的方式来实现。所描述的单元也可以设置在处理器中，例如，可以描述为：一种处理器包括接收单元、动态视图渲染单元、原生视图生成单元和视图交互单元。其中，这些单元的名称在某种情况下并不构成对该单元本身的限定。
作为另一方面，本申请还提供了一种计算机可读介质，该计算机可读介质可以是上述实施例中描述的设备中所包含的；也可以是单独存在，而未装配入该设备中。上述计算机可读介质承载有一个或者多个程序，当上述一个或者多个程序被一个该设备执行时，使得该设备接收视图交互请求，根据视图交互请求确定视图混编布局；根据视图混编布局，调用对应的动态视图代码包，以进行视图渲染生成动态视图；确定动态视图对应的页面，调用原生视图元素，以基于视图混编布局，在页面生成原生视图；确定视图交互请求对应的接口标识，以根据接口标识从动态视图和原生视图中确定目标交互视图，调用接口标识对应的接口进行各目标交互视图之间的交互，进而更新动态视图和原生视图。
根据本申请实施例的技术方案，实现在同一页面中跨端实现原生视图之间、动态视图之间、原生视图与动态视图之间的交互以及同一页面中视图交互后的动态更新。
上述具体实施方式，并不构成对本申请保护范围的限制。本领域技术人员应该明白的是，取决于设计要求和其他因素，可以发生各种各样的修改、组合、子组合和替代。任何在本申请的精神和原则之内所作的修改、等同替换和改进等，均应包含在本申请保护范围之内。

Claims (12)

  1. 一种视图交互方法，包括：
    接收视图交互请求，根据所述视图交互请求确定视图混编布局；
    根据所述视图混编布局，调用对应的动态视图代码包，以进行视图渲染生成动态视图；
    确定所述动态视图对应的页面，调用原生视图元素，以基于所述视图混编布局，在所述页面生成原生视图；
    确定所述视图交互请求对应的接口标识，以根据所述接口标识从所述动态视图和所述原生视图中确定目标交互视图，调用所述接口标识对应的接口进行各所述目标交互视图之间的交互，进而更新所述动态视图和所述原生视图。
  2. 根据权利要求1所述的方法，其中，在所述调用对应的动态视图代码包之前，所述方法还包括：
    确定所述视图混编布局对应的动态视图位置和动态视图元素；
    调用动态视图平台，以基于所述动态视图元素生成动态视图代码包。
  3. 根据权利要求2所述的方法，其中，所述进行视图渲染生成动态视图，包括：
    调用动态视图容器，加载所述动态视图代码包，进而解析得到动态视图代码命令，执行所述动态视图代码命令，进而对命令执行结果进行渲染生成对应的原生视图元素；
    将所述对应的原生视图元素插入所述动态视图位置，以生成动态视图。
  4. 根据权利要求1所述的方法，其中，所述生成原生视图，包括：
    确定所述视图混编布局对应的原生视图位置；
    加载原生视图元素至所述原生视图位置，生成原生视图。
  5. 根据权利要求1所述的方法，其中，所述根据所述接口标识从所述动态视图和所述原生视图中确定目标交互视图，包括：
    响应于确定所述接口标识对应原生接口，确定所述原生接口对应的各原生视图为目标交互视图；
    响应于确定所述接口标识对应原生接口和动态环境接口，确定所述原生接口对应的原生视图和所述动态环境接口对应的动态视图为目标交互视图；
    响应于确定所述接口标识对应动态环境接口和桥接接口，确定所述动态环境接口对应的动态视图为目标交互视图；
    响应于确定所述接口标识对应路由接口，确定所述路由接口对应的动态视图为目标交互视图。
  6. 根据权利要求5所述的方法，其中，所述调用所述接口标识对应的接口进行各所述目标交互视图之间的交互，包括：
    响应于确定所述接口标识对应原生接口和动态环境接口，调用动态环境接口将对应的目标动态视图的方法写入动态环境，进而调用动态视图桥接器将所述目标动态视图的方法转换为原生方法，以供原生接口对应的原生视图通过所述原生接口进行调用。
  7. 根据权利要求5所述的方法，其中，所述调用所述接口标识对应的接口进行各所述目标交互视图之间的交互，包括：
    响应于确定所述接口标识对应原生接口和动态环境接口，基于所述原生接口确定目标原生视图，进而调用动态视图桥接器，将所述目标原生视图的方法写入动态环境，以供所述动态环境接口对应的目标动态视图进行调用。
  8. 根据权利要求5所述的方法，其中，所述调用所述接口标识对应的接口进行各所述目标交互视图之间的交互，包括：
    响应于确定所述接口标识对应动态环境接口和桥接接口，将所述 动态环境接口对应的目标动态视图的方法写入动态环境中，进而调用动态视图桥接器转换成原生方法，进而再次调用动态视图桥接器将所述原生方法写入至动态环境中进行二次桥接，以供所述动态环境接口对应的其他目标动态视图进行调用。
  9. 根据权利要求5所述的方法，其中，所述调用所述接口标识对应的接口进行各所述目标交互视图之间的交互，包括：
    响应于确定所述接口标识对应路由接口，将所述路由接口对应的目标动态视图添加至动态视图容器中，在动态环境中写入所述路由接口对应的路由方法；
    调用所述路由接口以获取所述路由方法对应的行为及参数，解析所述行为及参数，进而根据解析结果执行各所述目标动态视图之间的交互。
  10. 一种视图交互装置，包括：
    接收单元，被配置成接收视图交互请求，根据所述视图交互请求确定视图混编布局；
    动态视图渲染单元，被配置成根据所述视图混编布局，调用对应的动态视图代码包，以进行视图渲染生成动态视图；
    原生视图生成单元，被配置成确定所述动态视图对应的页面，调用原生视图元素，以基于所述视图混编布局，在所述页面生成原生视图；
    视图交互单元，被配置成确定所述视图交互请求对应的接口标识，以根据所述接口标识从所述动态视图和所述原生视图中确定目标交互视图，调用所述接口标识对应的接口进行各所述目标交互视图之间的交互，进而更新所述动态视图和所述原生视图。
  11. 一种视图交互电子设备，包括：
    一个或多个处理器；
    存储装置，用于存储一个或多个程序，
    当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如权利要求1-9中任一所述的方法。
  12. 一种计算机可读介质，其上存储有计算机程序，所述程序被处理器执行时实现如权利要求1-9中任一所述的方法。
PCT/CN2022/129242 2021-11-11 2022-11-02 视图交互方法、装置、电子设备及计算机可读介质 WO2023083071A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111335618.X 2021-11-11
CN202111335618.XA CN114064176A (zh) 2021-11-11 2021-11-11 一种视图交互方法、装置、电子设备及计算机可读介质

Publications (1)

Publication Number Publication Date
WO2023083071A1 true WO2023083071A1 (zh) 2023-05-19

Family

ID=80275100

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/129242 WO2023083071A1 (zh) 2021-11-11 2022-11-02 视图交互方法、装置、电子设备及计算机可读介质

Country Status (2)

Country Link
CN (1) CN114064176A (zh)
WO (1) WO2023083071A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114064176A (zh) * 2021-11-11 2022-02-18 北京沃东天骏信息技术有限公司 一种视图交互方法、装置、电子设备及计算机可读介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106445284A (zh) * 2016-09-13 2017-02-22 柚子（北京）科技有限公司 画面显示方法和装置
CN111273985A (zh) * 2020-01-20 2020-06-12 北京无限光场科技有限公司 页面渲染方法、装置、电子设备及计算机可读存储介质
US20210034225A1 (en) * 2019-07-31 2021-02-04 Servicenow, Inc. Templates for rapid development of native mobile application graphical user interfaces
CN113742014A (zh) * 2021-08-11 2021-12-03 深圳Tcl新技术有限公司 界面渲染方法、装置、电子设备及存储介质
CN114064176A (zh) * 2021-11-11 2022-02-18 北京沃东天骏信息技术有限公司 一种视图交互方法、装置、电子设备及计算机可读介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106445284A (zh) * 2016-09-13 2017-02-22 柚子（北京）科技有限公司 画面显示方法和装置
US20210034225A1 (en) * 2019-07-31 2021-02-04 Servicenow, Inc. Templates for rapid development of native mobile application graphical user interfaces
CN111273985A (zh) * 2020-01-20 2020-06-12 北京无限光场科技有限公司 页面渲染方法、装置、电子设备及计算机可读存储介质
CN113742014A (zh) * 2021-08-11 2021-12-03 深圳Tcl新技术有限公司 界面渲染方法、装置、电子设备及存储介质
CN114064176A (zh) * 2021-11-11 2022-02-18 北京沃东天骏信息技术有限公司 一种视图交互方法、装置、电子设备及计算机可读介质

Also Published As

Publication number Publication date
CN114064176A (zh) 2022-02-18

Similar Documents

Publication Publication Date Title
CN111158818B (zh) 一种页面渲染方法和装置
CN111176626B (zh) 跨编程语言的代码调用方法及装置、介质、设备
US20180295194A1 (en) Techniques for supporting remote micro-services as native functions in spreadsheet applications
CN111740948B (zh) 数据包发布方法、动态更新方法、装置、设备及介质
CN111338623B (zh) 一种开发用户界面的方法、装置、介质和电子设备
CN110716720A (zh) 一种实现应用热部署的方法和装置
WO2019029451A1 (zh) 发布移动应用的方法和电子设备
CN113760324A (zh) 构建微前端应用的方法和装置
CN111026439B (zh) 应用程序的兼容方法、装置、设备及计算机存储介质
CN112181542A (zh) 功能调用方法、装置、电子设备及存储介质
CN111857658A (zh) 一种渲染动态组件的方法、装置、介质和电子设备
WO2023083071A1 (zh) 视图交互方法、装置、电子设备及计算机可读介质
CN112631590A (zh) 组件库生成方法、装置、电子设备和计算机可读介质
CN116755788A (zh) 一种线上规则修改方法、装置、设备及存储介质
CN109725887B (zh) 基于消息研发框架的数据交互方法、装置及终端设备
CN111414154A (zh) 前端开发的方法、装置、电子设备和存储介质
CN109343970B (zh) 基于应用程序的操作方法、装置、电子设备及计算机介质
US10353700B1 (en) Code base sharing between standalone and web-based versions of an application via an emulated network communication channel
CN112015384A (zh) 一种接口映射方法和装置
EP3872630A2 (en) Request processing method and apparatus, electronic device, and computer storage medium
CN112905273A (zh) 一种服务调用方法和装置
CN110262841B (zh) 一种对字节码进行增强的方法和装置
CN112162755A (zh) 一种数据处理方法、装置、介质和电子设备
CN116541045B (zh) 一种应用资源更新方法、装置和系统
CN113590483B (zh) 一种用例运行方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22891866

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22891866

Country of ref document: EP

Kind code of ref document: A1