CN113849252B - Small program multi-screen display method, host system supporting small program multi-screen display and client device - Google Patents

Small program multi-screen display method, host system supporting small program multi-screen display and client device Download PDF

Info

Publication number
CN113849252B
CN113849252B CN202110943932.XA CN202110943932A CN113849252B CN 113849252 B CN113849252 B CN 113849252B CN 202110943932 A CN202110943932 A CN 202110943932A CN 113849252 B CN113849252 B CN 113849252B
Authority
CN
China
Prior art keywords
page
target
applet
display screen
management unit
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
CN202110943932.XA
Other languages
Chinese (zh)
Other versions
CN113849252A (en
Inventor
覃瑶
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alipay Hangzhou Information Technology Co Ltd
Original Assignee
Alipay Hangzhou Information Technology Co Ltd
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 Alipay Hangzhou Information Technology Co Ltd filed Critical Alipay Hangzhou Information Technology Co Ltd
Priority to CN202110943932.XA priority Critical patent/CN113849252B/en
Publication of CN113849252A publication Critical patent/CN113849252A/en
Application granted granted Critical
Publication of CN113849252B publication Critical patent/CN113849252B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
    • G06F16/9566—URL specific, e.g. using aliases, detecting broken or misspelled links
    • 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/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects

Landscapes

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

Abstract

The application provides an applet multi-screen display method, a host system supporting applet multi-screen display and a client device. The small program multi-screen display method comprises the following steps: monitoring a jump event of a target applet, wherein the target applet is parasitized in a target host application, the target host application is loaded in a target client device, the target client device comprises a plurality of display screens, the host application comprises a plurality of page management units, and one page management unit is configured to manage pages displayed by the applet on one display screen; after the jump event is monitored, determining a target page management unit from the plurality of page management units; and acquiring target page resource data based on the page management unit and displaying the target page resource data on a target display screen through a view unit, wherein the target display screen corresponds to the target page management unit.

Description

Small program multi-screen display method, host system supporting small program multi-screen display and client device
Technical Field
The present application relates to the field of applet technology, and in particular, to an applet multi-screen display method, a host system supporting applet multi-screen display, and a client device.
Background
In the internet age, every demand of people requires installation of APP. On the one hand, more and more APP applications occupy a large amount of storage space of client devices; on the other hand, each time the system of the client device is updated or updated, the APP installed in the client device is reinstalled, which brings great inconvenience to people.
An applet is an application that can be developed based on a particular programming language and used without downloading or installing. The biggest characteristic of the applet is that the use is convenient. The user does not need to manually install an applet in the operating system of the client device. The applet was used by means of large APP as a carrier.
In the prior art, the small program scheme only supports single-screen equipment, and the small program can adapt to multi-screen equipment in the prior art.
Disclosure of Invention
The application discloses an applet multi-screen display method, a host system supporting applet multi-screen display and a client device, which are used for solving the technical problem that an applet scheme in the prior art cannot support multi-screen devices.
The small program multi-screen display method comprises the following steps: monitoring a jump event of a target applet, wherein the target applet is parasitized in a target host application, the target host application is loaded in a target client device, the target client device comprises a plurality of display screens, the host application comprises a plurality of page management units, and one page management unit is configured to manage pages displayed by the applet on one display screen; after the jump event is monitored, determining a target page management unit from the plurality of page management units; and acquiring target page resource data based on the page management unit and displaying the target page resource data on a target display screen through a view unit, wherein the target display screen corresponds to the target page management unit.
In some embodiments, each of the plurality of page management units manages pages of the display screen corresponding to the page management unit in a stack structure.
In some embodiments, each page management unit includes a routing file, the routing file defines a rule of page skip on a display screen corresponding to the page management unit, each routing file includes a plurality of routing interfaces, and the obtaining, by the page management unit, the target page resource data includes: and calling a target routing interface matched with the jump event so as to acquire the target page resource data, wherein the target routing interface belongs to the target page management unit.
In some embodiments, wherein the client device includes a first display screen and a second display screen, the plurality of page management units includes: a first page management unit configured to manage pages displayed on a first display screen by the applet, including a first page stack, wherein a predetermined number of page instances are included in the first page stack, and the page instances in the first page station are preset to correspond to the first display screen; and a second page management unit configured to manage pages displayed on a second display screen by the applet, wherein the second page management unit comprises a second page stack, a preset number of page instances are included in the second page stack, and the page instances in the second page stack are preset to correspond to the second display screen.
In some embodiments, when the object of the user action triggering the page jump event is a first display screen, the target page management unit is the first page management unit, and the target display screen is the first display screen; when the object triggering the user behavior of the page jump event is a second display screen, the target page management unit is the second page management unit, and the target display screen is the second display screen.
In some embodiments, when the object of the user action triggering the page jump event is one of a first display screen and a second display screen, the target page management unit includes the first page management unit and the second page management unit, and the target display screen includes the first display screen and the second display screen.
In some embodiments, wherein said invoking a target routing interface that matches said jump event to obtain said target page resource data comprises: and retrieving the target page resource data from a target storage unit, wherein the target storage unit is used for storing data related to the applet, and the data comprise the data of the first page instance and the data of the second page instance.
In some embodiments, wherein the first page management unit is executed by a worker module of the applet; and the second page management unit is executed by the native module of the host application.
In some embodiments, wherein the first page management unit is executed by a worker module of the applet; and the second page management unit is executed by a worker module of the applet.
In some embodiments, wherein the jump event includes a url address of the target page, the applet multi-screen display method further comprises: analyzing the url address contained in the jump event, and obtaining a route matched with the url address, wherein the route matched with the url address is the target route.
The host system supporting the two-screen display of the small program comprises: a view unit configured to display page resource data of an applet hosted in the hosting system as a page on a client device display screen, and to generate an event triggering a page jump based on user behavior of the page; and a logic unit configured to receive event feedback from the view unit, acquire page data of the applet based on the event feedback and send the page data to the view unit to display the page data on the display screen through the view unit, wherein the client device comprises a plurality of display screens, the logic unit can control pages displayed on the plurality of display screens by the applet through the plurality of page management units, and one page management unit is configured to manage pages displayed on one display screen by the applet.
In some embodiments, each of the plurality of page management units manages pages of the display screen corresponding to the page management unit in a stack structure.
In some embodiments, each page management unit includes a routing file, the routing file defines a rule of page skip on a display screen corresponding to the page management unit, each routing file includes a plurality of routing interfaces, and the obtaining, by the page management unit, the target page resource data includes: and calling a target routing interface matched with the jump event so as to acquire the target page resource data, wherein the target routing interface belongs to the target page management unit.
In some embodiments, wherein the client device includes a first display screen and a second display screen, the plurality of page management units includes: a first page management unit configured to manage pages displayed on a first display screen by the applet, including a first page stack, wherein a predetermined number of page instances are included in the first page stack, and the page instances in the first page station are preset to correspond to the first display screen; and a second page management unit configured to manage pages displayed on a second display screen by the applet, wherein the second page management unit comprises a second page stack, a preset number of page instances are included in the second page stack, and the page instances in the second page stack are preset to correspond to the second display screen.
In some embodiments, when the object of the user action triggering the page jump event is a first display screen, the target page management unit is the first page management unit, and the target display screen is the first display screen; when the object triggering the user behavior of the page jump event is a second display screen, the target page management unit is the second page management unit, and the target display screen is the second display screen.
In some embodiments, when the object of the user action triggering the page jump event is one of a first display screen and a second display screen, the target page management unit includes the first page management unit and the second page management unit, and the target display screen includes the first display screen and the second display screen.
In some embodiments, wherein said invoking a target routing interface that matches said jump event to obtain said target page resource data comprises: and retrieving the target page resource data from a target storage unit, wherein the target storage unit is used for storing data related to the applet, and the data comprise the data of the first page instance and the data of the second page instance.
In some embodiments, wherein the first page management unit is managed by a framework of the applet; and the second page management unit is managed by the native module of the host system.
In some embodiments, wherein the first page management unit is managed by a framework management of the applet; and the second page management unit is managed by the framework management of the applet.
The client device includes: a memory storing at least one instruction set; and the processor is in communication connection with the memory and the display, and when the client runs, the processor reads and runs the at least one instruction set and executes the small-program double-screen display method according to the instruction of the at least one instruction set so as to control pages displayed by different display screens of the client device.
According to the applet multi-screen display method, the host system supporting the applet multi-screen display and the client device, the applet page multi-screen display is supported by creating a plurality of page stacks in the applet framework, a developer only needs to develop one applet, difficulty of the developer is reduced, only one applet needs to be updated when the applet is updated, and synchronous updating is easier; each page stack comprises respective page routing interfaces, so that each screen can support multiple pages and skip among the pages, the applet can support the same page to be started to different screens through the design of the multiple page stacks, the different screens correspond to different page stacks, communication is not needed among the routing interfaces of the different page stacks, and various problems caused by communication among the interfaces are avoided.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present description, the drawings that are needed in the description of the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present description, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 shows a schematic hardware structure of a client device according to an embodiment of the present application;
FIG. 2 illustrates an architecture of an applet provided in accordance with an embodiment of the application;
FIG. 3 illustrates a page management structure for an applet supporting only a single screen display according to an embodiment of the present application;
FIG. 4 illustrates a page management structure of an applet provided in accordance with an embodiment of the present application;
FIG. 5 is a schematic diagram of a page management unit for managing pages of a display screen according to an embodiment of the present application;
FIG. 6 is a schematic diagram of a page management unit managing pages of a display screen according to an embodiment of the present application; and
Fig. 7 illustrates a flow chart of an applet multi-screen display method provided in accordance with some embodiments of the application.
Detailed Description
The following description provides specific applications and requirements of the application to enable any person skilled in the art to make and use the application. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the application. Thus, the present application is not limited to the embodiments shown, but is to be accorded the widest scope consistent with the claims.
The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting.
These and other features of the present application, as well as the operation and function of the related elements of structure, as well as the combination of parts and economies of manufacture, may be significantly improved upon in view of the following description. With reference to the accompanying drawings, all of which form a part of this disclosure. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the application.
The following description may significantly improve the operation and function of these and other features of the present application, as well as related elements of structure, as well as the economic efficiency of the assembly and manufacture. All of which form part of the present application with reference to the accompanying drawings. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the application. It should also be understood that the drawings are not drawn to scale.
The application provides an applet multi-screen display method, a host system supporting applet multi-screen display and a client device.
As an example, fig. 1 shows a schematic hardware structure of a client device 100 according to an embodiment of the present application. Referring to fig. 1, the client device 100 may include a memory 230 and a processor 220.
Memory 230 may include a data storage device. The data storage device may be a non-transitory storage medium or a transitory storage medium. Such as one or more of magnetic disk 232, read Only Memory (ROM) 234, or Random Access Memory (RAM) 236. Memory 230 also includes at least one instruction set stored in the data storage device. The instruction set is computer program code which may include programs, routines, objects, components, data structures, procedures, modules, etc. that perform the methods shown in this application.
The processor 220 communicates with the memory 230 via an internal communication bus 210. The at least one processor 220 is configured to execute the at least one instruction set, and when the at least one processor 220 executes the at least one instruction set, the client device 100 implements the applet multi-screen display method illustrated in the present application. Processor 220 may perform some or all of the steps involved in the methods illustrated in the present application. Processor 220 may be in the form of one or more processors, in some embodiments processor 220 may include one or more hardware processors, such as microcontrollers, microprocessors, reduced Instruction Set Computers (RISC), application Specific Integrated Circuits (ASIC), application specific instruction set processors (ASIP), central Processing Units (CPU), graphics Processing Units (GPU), physical Processing Units (PPU), microcontroller units, digital Signal Processors (DSP), field Programmable Gate Arrays (FPGA), advanced RISC Machines (ARM), programmable Logic Devices (PLD), any circuit or processor capable of executing one or more functions, or the like, or any combination thereof. For illustrative purposes only, only one processor 220 is depicted in the client device 100 in the present application. It should be noted, however, that the client device 100 of the present application may also include multiple processors, and thus, the operations and/or method steps disclosed in the present application may be performed by one processor as described in the present application, or may be performed jointly by multiple processors. For example, if the processor 220 of the client device 100 performs steps a and B in the present application, it should be understood that steps a and B may also be performed by two different processors 220 in combination or separately (e.g., a first processor performs step a, a second processor performs step B, or the first and second processors together perform steps a and B).
In some embodiments, client device 100 may also include a communication port 250 and an internal communication bus 210. The communication port 250 is used for data communication between the client device 100 and the outside world. Internal communication bus 210 may connect the different system components including memory 230 and processor 220.
In some embodiments, client device 100 may also include I/O component 260. The I/O component 260 supports input/output between the client device 100 and other components.
In some embodiments, the I/O component 260 may comprise a display. The display may receive instructions from the processor 220 and display data as a human-machine interaction interface on the display.
By way of example, FIG. 2 illustrates an architecture of an applet provided in accordance with an embodiment of the present application. The architecture of the applet may be integrated within the host system 200 in the form of a framework document. The hosting system 200 is installed within the client device 100.
Host system 200 may be an Application (APP). The application program may comprise computer program code. The computer program code may include, but is not limited to, programs, routines, objects, components, data structures, procedures, modules, and the like. The operating system loaded in client device 200 may provide the environment for hosting system 100 to operate in.
As an example, host system 200 may be an open platform. The open platform allows external programs to add functionality or use resources of the open platform by exposing its Application Programming Interfaces (APIs) or functions (functions) without modifying the open platform's source code. External programs can access the open platform through the APIs or functions disclosed by the open platform. The open platform may provide a runtime environment (runtime) that runs external programs. That is, when an external program is accessed to the open platform, runtime of the open platform may run the code of the external program. By way of example, the open platform may include, but is not limited to, a digital living open platform, a social open platform, a shopping open platform, a gaming open platform, a content platform, and the like. The external program refers to a program outside the open platform. By way of example, the external programs may include, but are not limited to, mobile applications, web applications, public account numbers, third party platforms, and the like, external to the open platform. In some embodiments, the external program is an applet.
For convenience of description, in the following description of the present application, an external program accessing the open platform through the open API or function is denoted as "applet". The applet may be developed based on the host APP. For example, the host APP may be XX social software, and the applet may be an applet developed based on the environment of the XX social software, and accessed in the XX social software, or H5. For another example, the host APP may be XX payment software and the applet may be a merchant or service applet developed based on and accessed into the XX payment software.
In some embodiments, the host system 200 may include a native application (Native Application, NATIVE APP for short). The NATIVE APP may run based on a native operating system. In some embodiments, the applet may include a Web Application (Web APP) developed based on the NATIVE APP. The Web APP may run based on a browser.
Specifically, the applet architecture shown in FIG. 2 may include a view unit 001 and a logic unit 002.
The view unit 001 is configured to display page resource data of an applet hosted in the hosting system 200 as a page on a display screen of the client device 100, and to generate an event triggering a page jump based on a user's behavior of the page.
The logic unit 002 is configured to receive event feedback of the view unit 001, acquire page data of the applet based on the event feedback and transmit the page data to the view unit 001 to display the page data on the display screen through the view unit 001.
As an example, fig. 3 shows a page management structure of an applet supporting only a single screen display according to an embodiment of the present application. The page routing of the applet is managed by the applet's framework. The framework maintains all pages in a stack. Stacks, which are a data structure, are special linear tables that can only be inserted and deleted at one end. The method stores data according to the principle of last-in first-out, the first-in data is pressed into the stack bottom, the last-in data is at the stack top, and the data is popped from the stack top when the data needs to be read (the last data is read by the first). The page interactions of the applet are also done through the stack. When the applet is initialized, a new page is stacked; when a new page is opened, the new page is stacked; when the page is redirected, the current page is popped, and a new page is pushed into the stack; when the page returns, the page is continuously popped until a new page is popped; when tab is switched, the pages are all popped off, and only new tab pages are left; when reloading, the pages are all popped, and only new pages are left. The architecture shown in fig. 3 is used to maintain the pages displayed by the applet, so that the switching of multiple pages of the applet can be supported, but only one page (the page at the top of the stack) can be displayed on the display screen at the same time.
In accordance with the foregoing description, client device 100 may include a display. The display may receive instructions from the processor 220 and display data as a human-machine interaction interface on the display. In some embodiments, the client device 100 includes a plurality of display screens. In some embodiments, the plurality of display screens may be two screens presented on one display by split screen technology. In some embodiments, the plurality of display screens may be screens respectively displayed on different displays. Such as shown in fig. 2, the client device may include a first display 110 and a second display 120. The first display 110 and the second display 120 may belong to different displays.
When the client device 100 has multiple display screens, displaying different page content on different display screens of the client device 100 cannot be achieved using the applet architecture shown in fig. 3.
As an example, fig. 4 shows a page management structure of an applet provided according to an embodiment of the present application. A plurality of page management units 400 are shown in fig. 4. A page management unit 400 is configured to manage pages displayed by the applet on a display screen. The logic unit may control pages displayed by the applet on the plurality of display screens through the plurality of page management units. As an example, in the page management structure shown in fig. 4, each of the plurality of page management units 400 manages pages of a display screen corresponding thereto in a stack structure.
Taking the example that the client device 100 includes the first display 110 and the second display 120, the plurality of page management units may include a first page management unit 400-1 and a second page management unit 400-2.
The first page management unit 400-1 may be configured to manage pages displayed by the applet on the first display screen 110. The first page management unit 400-1 may include a first page stack. A predetermined number of page instances are included within the first page stack. The page instance in the first page station is preset to correspond to the first display screen 110. For example, the first display 110 may be a home screen of an applet, and the page instances within the first page stack may be page instances of the home screen, such as home screen page a, home screen page b, home screen page c, and so forth. The first page stack is used for maintaining page display and page-to-page skip of the main screen.
The second page management unit 400-2 is configured to manage pages displayed by the applet on the second display screen 120. The second page management unit 400-2 may include a second page stack. A predetermined number of page instances are included within the second page stack. The page instance in the second page stack is preset to correspond to the second display screen 120. For example, the second display 110 may be an expanded secondary screen of the applet, and the page instances within the second page stack may be page instances of the secondary screen, such as secondary screen page a, secondary screen page b, secondary screen page c, and so forth. And the second page stack is used for maintaining page display and page-to-page skip of the auxiliary screen.
In some embodiments, when the object of the user action triggering the page jump event is one of the first display screen 110 and the second display screen 120, the target page management unit includes the first page management unit 400-1 and the second page management unit 400-2, and the target display screen includes the first display screen 110 and the second display screen 120. As an example, fig. 5 shows a schematic diagram of managing pages of a display screen by a page management unit according to an embodiment of the present application. When the user performs an operation on the first display screen 110, for example, the user clicks a certain icon button on the first display screen or adds certain text content on the first display screen, according to a jump event triggered by the user behavior, the logic unit may control the page jump on the first display screen through the first page management unit, and simultaneously control the page jump on the second display screen through the second page management unit. That is, the user operates one display, and both the page displayed on the first display and the page displayed on the second display jump.
In some embodiments, when the object of the user action triggering the page jump event is the first display screen 110, the target page management unit is the first page management unit 400-1, and the target display screen is the first display screen 110; when the object of the user action triggering the page jump event is the second display screen 120, the target page management unit is the second page management unit 400-2, and the target display screen is the second display screen 120. As an example, fig. 6 shows a schematic diagram of managing pages of a display screen by a page management unit according to an embodiment of the present application. When the user only performs an operation on the first display screen 110, for example, the user clicks a certain icon button on the first display screen or adds certain text content on the first display screen, according to a skip event triggered by the user action, the logic unit may control page skip on the first display screen through the first page management unit, and the second page management unit may control pages on the second display screen not to skip. That is, the first page management unit can only maintain pages on the first display screen based on trigger events from the first display screen. The first page managing unit does not respond to an event related to the second display screen. Correspondingly, the second page managing unit is also responsive only to events from the second display screen. Therefore, the events and pages of the same display screen of one page management unit are in one-to-one correspondence, and errors are not easy to occur during the running of the program.
According to the previous description, each page management unit adopts a stack structure to manage and maintain the pages of the display screen corresponding to the page management unit. In some embodiments, each page management unit includes a routing file, the routing file defines a rule of page skip on a display screen corresponding to the page management unit, each routing file includes a plurality of routing interfaces, and the obtaining, by the page management unit, the target page resource data includes: and calling a target routing interface matched with the jump event so as to acquire the target page resource data, wherein the target routing interface belongs to the target page management unit. As examples, the routing interfaces may include, but are not limited to, switchTab interfaces, reLauncn interfaces, redirectTo interfaces, navigateTo interfaces, navigateBack interfaces, and so forth. The switchTab interface may be an API (Application Programming Interface, application program interface) that jumps to a specified tabbed page and closes all other non-tabbed pages. The reLauncn interface may be an API that closes all the current pages, jumps to a specified page within the applet. The redirectTo interface may be an API that closes the current page, jumps to some specified page within the applet. The navigateTo interface may be an API that jumps from the current page to some specified page within the applet. Opening a new page on the display screen can be achieved through the navigateTo interface. The navigateBack interface may be an API that closes the current page, returns to the previous level or levels of pages. The current page stack information may be obtained before the navigateBack interface may be invoked, determining that several layers need to be returned. In some embodiments, the current page list may also be obtained through the Pagelist interface. Every time a page is newly opened using the navigateTo interface, the page stack size may be increased by 1 until the page stack size is the maximum allowed number of layers (e.g., 5 layers) of the page stack. Correspondingly, when one layer of page is returned by using navigateBack interfaces, the size of the page stack can be reduced by 1 until the size of the page stack is 1.
With continued reference to the applet framework shown in fig. 2. In some embodiments, the framework further comprises a storage unit 003 for storing data. In some embodiments, the invoking the target routing interface that matches the jump event to obtain the target page resource data comprises: and retrieving the target page resource data from a target storage unit, wherein the target storage unit is used for storing data related to the applet, and the data comprise the data of the first page instance and the data of the second page instance. The storage unit 003 may be a storage space of the applet. The memory space may include a first data block, a second data block, and a third data block. The first data block is configured to store data related only to the first display screen page. The second data block is configured to store data related only to the second display screen page. The third data block may be a shared data block, that is, data shared by the first display screen and the second display screen may be stored in the third data block. If there is an order list, and data is added in the order list in the main screen page, the auxiliary screen page can directly know that the data is changed, that is, the main screen page and the auxiliary screen page can jointly change the same data. Therefore, on one hand, the utilization rate of the storage space is improved, and on the other hand, the data intercommunication between the main screen and the auxiliary screen is realized without transmitting data between the main screen and the auxiliary screen, so that the memory is saved, and the performance is improved.
In some embodiments, the first page management unit is managed by a worker module of the applet; the second page management unit is managed by the native module of the host application. For example, the first page management unit may be a page stack of a primary screen, which may be managed by an applet front end framework (e.g., front end worker layer), and the second page management unit may be a page stack of a secondary screen, which may be managed by a native container.
In some embodiments, the first page management unit is managed by a worker module of the applet; the second page management unit is executed by a worker module of the applet. For example, the first page management unit may be a page stack of a primary screen, and the second page management unit may be a page stack of a secondary screen, where the primary screen page stack and the secondary screen page stack may each be managed by an applet front end framework.
An applet may correspond to a worker module. The worker module may be a virtual space or a runtime space of the applet. As an example, the worker module may be a virtual process of the applet, which may be a process that specifically serves the applet to protect the consistency and integrity of the applet data from being perceived elsewhere. The native module may be a native module.
As an example, fig. 7 shows a flowchart of an applet multi-screen display method S100 provided according to some embodiments of the application. Some and/or all of the steps in flow S100 may be stored as at least one set of instructions in a non-transitory storage medium (such as memory 230) in client device 100 for controlling pages displayed by different display screens of the client device. At least one processor 220 is communicatively coupled to the at least one non-transitory storage medium, wherein when the client device 100 is running, the at least one processor 220 reads the at least one instruction set and performs the steps in flow S100 as directed by the at least one instruction set.
The operation of the illustrated flow S100 presented below is intended to be illustrative and not limiting. In some embodiments, flow S100 may add one or more additional operations not described and/or prune one or more operations described herein when implemented. Further, the order of operations shown in fig. 7 and described below is not limited thereto.
S110, monitoring a jump event of the target applet.
S120, determining a target page management unit from the plurality of page management units after the jump event is monitored.
The target applet is hosted in a target host application that is loaded in a target client device that includes a plurality of display screens, the host application including a plurality of page management units, one page management unit configured to manage pages displayed by the applet on one display screen.
The jump event may be triggered by an interactive behavior of the user to the display screen. For example, the interaction may be by clicking on an icon button on a display. For another example, the interactive behavior may be that the user has added content within a particular text box on a certain display screen.
S130, analyzing the url address contained in the jump event, and acquiring a route matched with the url address.
In some embodiments, the jump event includes a url address of the destination page. After monitoring the jump event, the processor may parse the url address contained in the jump event and obtain the route matching the url address.
S140, calling a target route interface matched with the jump event so as to acquire the target page resource data.
And S150, displaying the target page resource data on a target display screen through a view unit.
The target route interface is a route interface matched with the url address. The target route interface belongs to the target page management unit.
After acquiring the target page resource data based on the page management unit, the processor can display the target page resource data on a target display screen through a view unit, wherein the target display screen corresponds to the target page management unit.
In summary, the application provides an applet multi-screen display method, a host system supporting applet multi-screen display, and a client device: the multi-screen display of the small program pages is supported by creating a plurality of page stacks in the small program framework, a developer only needs to develop one small program, the difficulty of the developer is reduced, only one small program needs to be updated when the small program is updated, and the small program is easier to update synchronously; each page stack comprises respective page routing interfaces, so that each screen can support multiple pages and skip among the pages, the applet can support the same page to be started to different screens through the design of the multiple page stacks, the different screens correspond to different page stacks, communication is not needed among the routing interfaces of the different page stacks, and various problems caused by communication among the interfaces are avoided.
Another aspect of the present description provides a computer-readable storage medium. The storage medium has at least one set of computer instructions stored therein. When executed by a processor, the instructions direct the processor to perform the steps of the applet multi-screen display method described in this specification. In some possible implementations, aspects of the specification can also be implemented in the form of a program product including program code. The program code is for causing a signal processing device to perform the steps of the applet multi-screen display method described in the present specification when said program product is run on the signal processing device. The program product for implementing the above method may employ a portable compact disc read only memory (CD-ROM) comprising program code and may run on a signal processing device. However, the program product of this specification is not limited thereto, and in this specification, the readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system (e.g., processor 202). The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, 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), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. The computer readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable storage medium may also be any readable medium that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a readable storage 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. Program code for carrying out operations of the present specification may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the signal processing device, partly on the data processing apparatus 200, as a stand-alone software package, partly on the signal processing device, partly on a remote computing device or entirely on the remote computing device.
In view of the foregoing, it will be evident to a person skilled in the art that the foregoing detailed disclosure may be presented by way of example only and may not be limiting. Although not explicitly described herein, those skilled in the art will appreciate that the present application is intended to embrace a variety of reasonable alterations, improvements and modifications to the embodiments. Such alterations, improvements, and modifications are intended to be proposed by this application, and are intended to be within the spirit and scope of the exemplary embodiments of the application.
Furthermore, certain terms in the present application have been used to describe embodiments of the present application. For example, "one embodiment," "an embodiment," and/or "some embodiments" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the application. Thus, it is emphasized and should be appreciated that two or more references to "an embodiment" or "one embodiment" or "an alternative embodiment" in various portions of this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined as suitable in one or more embodiments of the application.
It should be appreciated that in the foregoing description of embodiments of the application, various features are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure. Or the application may be varied and features dispersed throughout a plurality of embodiments of the application. However, this is not to say that a combination of these features is necessary, and it is entirely possible for a person skilled in the art to extract some of them as separate embodiments to understand them when reading this application. That is, embodiments of the present application may also be understood as an integration of multiple secondary embodiments. While each secondary embodiment is satisfied by less than all of the features of a single foregoing disclosed embodiment.
In some embodiments, numbers expressing quantities or properties used to describe and claim certain embodiments of the application are to be understood as being modified in some instances by the term "about," approximately, "or" substantially. For example, unless otherwise indicated, "about," "approximately," or "substantially" may mean a change in a value of ±20% of what it describes. Accordingly, in some embodiments, the numerical parameters set forth in the written description and attached claims are approximations that may vary depending upon the desired properties sought to be obtained by the particular embodiment. In some embodiments, numerical parameters should be construed in light of the number of reported significant digits and by applying ordinary rounding techniques. Notwithstanding that the numerical ranges and parameters setting forth the broad scope of the embodiments of the application are approximations, the numerical values set forth in the specific examples are reported as precisely as possible.
Each patent, patent application, publication of patent application, and other materials, such as articles, books, specifications, publications, documents, articles, etc., cited herein are hereby incorporated by reference. The entire contents for all purposes, except for any prosecution file history associated therewith, may be any identical prosecution file history inconsistent or conflicting with this file, or any identical prosecution file history which may have a limiting influence on the broadest scope of the claims. Now or later in association with this document. For example, if there is any inconsistency or conflict between the description, definition, and/or use of terms associated with any of the incorporated materials, the terms in the present document shall prevail.
Finally, it is to be understood that the embodiments of the application disclosed herein are illustrative of the principles of embodiments of the present application. Other modified embodiments are also within the scope of the application. Accordingly, the disclosed embodiments are illustrative only and not limiting. Those skilled in the art can adopt alternative configurations to implement the application of the present application according to embodiments of the present application. Accordingly, embodiments of the application are not limited to those precisely described in the application.

Claims (20)

1. An applet multi-screen display method comprising:
Monitoring a jump event of a target applet, wherein the target applet is parasitized in a target host application, the target host application is loaded in target client equipment, the target client equipment comprises a plurality of display screens, the target host application comprises a plurality of page management units, and one page management unit is configured to manage pages displayed by the target applet on one display screen;
After the jump event is monitored, determining a target page management unit from the plurality of page management units; and
And acquiring target page resource data based on the target page management unit and displaying the target page resource data on a target display screen through a view unit, wherein the target display screen corresponds to the target page management unit.
2. The applet multi-screen display method according to claim 1, wherein each of the plurality of page management units manages pages of its corresponding display screen in a stack structure.
3. The applet multi-screen display method according to claim 1, wherein each page management unit comprises a routing file defining rules for page jumps on a display screen corresponding to the page management unit, each routing file comprising a number of routing interfaces,
The obtaining the target page resource data based on the target page management unit comprises the following steps:
And calling a target routing interface matched with the jump event so as to acquire the target page resource data, wherein the target routing interface belongs to the target page management unit.
4. The applet multi-screen display method according to claim 3, wherein the client device comprises a first display screen and a second display screen, the plurality of page management units comprising:
A first page management unit configured to manage pages displayed on a first display screen by the applet, including a first page stack, wherein a predetermined number of page instances are included in the first page stack, and the page instances in the first page station are preset to correspond to the first display screen; and
The second page management unit is configured to manage pages displayed on a second display screen by the applet, and comprises a second page stack, wherein a preset number of page instances are included in the second page stack, and the page instances in the second page stack are preset to correspond to the second display screen.
5. The applet multi-screen display method according to claim 4, wherein,
When the object triggering the user behavior of the page jump event is a first display screen, the target page management unit is the first page management unit, and the target display screen is the first display screen;
When the object triggering the user behavior of the page jump event is a second display screen, the target page management unit is the second page management unit, and the target display screen is the second display screen.
6. The applet multi-screen display method according to claim 4, wherein,
When the object triggering the user behavior of the page jump event is one of a first display screen and a second display screen, the target page management unit comprises the first page management unit and the second page management unit, and the target display screen comprises the first display screen and the second display screen.
7. The applet multi-screen display method according to claim 4, wherein the invoking a destination routing interface that matches the jump event to obtain the destination page resource data comprises:
And retrieving the target page resource data from a target storage unit, wherein the target storage unit is used for storing data related to the applet, and the data comprise the data of the first page instance and the data of the second page instance.
8. The applet multi-screen display method according to claim 4, wherein,
The first page management unit is executed by a worker module of the applet; and
The second page management unit is executed by the native module of the host application.
9. The applet multi-screen display method according to claim 4, wherein,
The first page management unit is executed by a worker module of the applet; and
The second page management unit is executed by a worker module of the applet.
10. The applet multi-screen display method according to claim 3, wherein the jump event includes a url address of the target page, the applet multi-screen display method further comprising:
analyzing the url address contained in the jump event, and obtaining a route matched with the url address, wherein the route matched with the url address is the target route.
11. A host system supporting an applet dual screen display, comprising:
A view unit configured to display page resource data of an applet hosted in the hosting system as a page on a client device display screen, and to generate an event triggering a page jump based on user behavior of the page;
And a logic unit configured to receive event feedback from the view unit, acquire page data of the applet based on the event feedback and send the page data to the view unit to display the page data on the display screen through the view unit, wherein the client device comprises a plurality of display screens, the logic unit can control pages displayed on the plurality of display screens by the applet through the plurality of page management units, and one page management unit is configured to manage pages displayed on one display screen by the applet.
12. The hosting system supporting dual-screen display of the applet as recited in claim 11, wherein each of the plurality of page management units manages pages of its corresponding display screen in a stack structure.
13. The hosting system supporting dual-screen display of applets as recited in claim 11 wherein each page management unit includes a routing file defining rules for page jumps on a display screen corresponding to the page management unit, each routing file including a plurality of routing interfaces,
The obtaining, by the page management unit, the target page resource data includes:
And calling a target routing interface matched with the jump event so as to acquire the target page resource data, wherein the target routing interface belongs to the target page management unit.
14. The hosting system supporting dual-screen display of an applet as recited in claim 13, wherein the client device comprises a first display screen and a second display screen, the plurality of page management units comprising:
A first page management unit configured to manage pages displayed on a first display screen by the applet, including a first page stack, wherein a predetermined number of page instances are included in the first page stack, and the page instances in the first page station are preset to correspond to the first display screen; and
The second page management unit is configured to manage pages displayed on a second display screen by the applet, and comprises a second page stack, wherein a preset number of page instances are included in the second page stack, and the page instances in the second page stack are preset to correspond to the second display screen.
15. The host system supporting dual-screen display of an applet as recited in claim 14, wherein,
When the object triggering the user behavior of the page jump event is a first display screen, the target page management unit is the first page management unit, and the target display screen is the first display screen;
When the object triggering the user behavior of the page jump event is a second display screen, the target page management unit is the second page management unit, and the target display screen is the second display screen.
16. The host system supporting dual-screen display of an applet as recited in claim 14, wherein,
When the object triggering the user behavior of the page jump event is one of a first display screen and a second display screen, the target page management unit comprises the first page management unit and the second page management unit, and the target display screen comprises the first display screen and the second display screen.
17. The host system supporting dual-screen display of claim 14, wherein said invoking a destination routing interface that matches said jump event to obtain said destination page resource data comprises:
And retrieving the target page resource data from a target storage unit, wherein the target storage unit is used for storing data related to the applet, and the data comprise the data of the first page instance and the data of the second page instance.
18. The host system supporting dual-screen display of an applet as recited in claim 14, wherein,
The first page management unit is managed by the framework of the applet; and
The second page management unit is managed by the native module of the host system.
19. The host system supporting dual-screen display of an applet as recited in claim 14, wherein,
The first page management unit is managed by the framework management of the applet; and
The second page management unit is managed by the framework management of the applet.
20. A client device, comprising:
A memory storing at least one instruction set; and
A processor in communication with the memory and the display, the processor, when the client is running, reading and running the at least one instruction set and executing the applet dual screen display method according to any one of claims 1-10 according to an indication of the at least one instruction set to control pages displayed by different display screens of the client device.
CN202110943932.XA 2021-08-17 2021-08-17 Small program multi-screen display method, host system supporting small program multi-screen display and client device Active CN113849252B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110943932.XA CN113849252B (en) 2021-08-17 2021-08-17 Small program multi-screen display method, host system supporting small program multi-screen display and client device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110943932.XA CN113849252B (en) 2021-08-17 2021-08-17 Small program multi-screen display method, host system supporting small program multi-screen display and client device

Publications (2)

Publication Number Publication Date
CN113849252A CN113849252A (en) 2021-12-28
CN113849252B true CN113849252B (en) 2024-05-10

Family

ID=78975831

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110943932.XA Active CN113849252B (en) 2021-08-17 2021-08-17 Small program multi-screen display method, host system supporting small program multi-screen display and client device

Country Status (1)

Country Link
CN (1) CN113849252B (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2325153A1 (en) * 2000-11-06 2002-05-06 Wintokens.Com Inc. A system and method for collecting consumer information
CN106293473A (en) * 2016-08-15 2017-01-04 珠海市魅族科技有限公司 Page display method and device
CN110083413A (en) * 2019-03-13 2019-08-02 维沃移动通信有限公司 A kind of small routine call method and terminal device
CN111026462A (en) * 2019-12-10 2020-04-17 百度在线网络技术（北京）有限公司 Applet control method, apparatus, device and medium
CN111694475A (en) * 2020-04-27 2020-09-22 华为技术有限公司 Terminal control method and device and terminal equipment

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2325153A1 (en) * 2000-11-06 2002-05-06 Wintokens.Com Inc. A system and method for collecting consumer information
CN106293473A (en) * 2016-08-15 2017-01-04 珠海市魅族科技有限公司 Page display method and device
CN110083413A (en) * 2019-03-13 2019-08-02 维沃移动通信有限公司 A kind of small routine call method and terminal device
CN111026462A (en) * 2019-12-10 2020-04-17 百度在线网络技术（北京）有限公司 Applet control method, apparatus, device and medium
CN111694475A (en) * 2020-04-27 2020-09-22 华为技术有限公司 Terminal control method and device and terminal equipment

Also Published As

Publication number Publication date
CN113849252A (en) 2021-12-28

Similar Documents

Publication Publication Date Title
US9754018B2 (en) Rendering interpreter for visualizing data provided from restricted environment container
US9928038B2 (en) Dynamically building locale objects or subsections of locale objects based on historical data
US9003312B1 (en) Method and apparatus for updating a web-based user interface
US9417793B2 (en) Global keyboard shortcuts management for web applications
AU2014207730B2 (en) Systems and methods for building and using hybrid mobile applications
US9465529B1 (en) Platform-independent environments for customizing user interfaces of native applications for portable electronic devices
CN106856485B (en) Data service publishing method and device
JP4971202B2 (en) Information processing apparatus and program
CN103370689A (en) Cross-environment application compatibility
CN111090823B (en) Page application integration system, application access method, device and equipment
CN108304234B (en) Page display method and device
US11895553B2 (en) Web application with components in different virtual environments
KR20160015295A (en) Multi-display system
CN111596916A (en) Application program management method, device and equipment and computer storage medium
CN115309470A (en) Method, device and equipment for loading widgets and storage medium
US9141353B2 (en) Dynamically building locale objects at run-time
CN113849252B (en) Small program multi-screen display method, host system supporting small program multi-screen display and client device
CN115934076B (en) Cross-platform client micro-service providing device and method and electronic equipment
US20130332568A1 (en) Method of data processing by a navigation module
CN110471737B (en) Immersive status bar setting method and related device
CN113741743A (en) Display method and device, equipment and storage medium
CN111273974A (en) Method and device for customizing menu setting function and electronic equipment
KR102676433B1 (en) Method and electronic device for processing order information
US20230063273A1 (en) Data transmission system across platforms and method of data transmission
US9778917B2 (en) Dynamically building subsections of locale objects at run-time

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant