CN114090145B - Page jump determining method and device, storage medium and electronic device - Google Patents
Page jump determining method and device, storage medium and electronic device Download PDFInfo
- Publication number
- CN114090145B CN114090145B CN202111250919.2A CN202111250919A CN114090145B CN 114090145 B CN114090145 B CN 114090145B CN 202111250919 A CN202111250919 A CN 202111250919A CN 114090145 B CN114090145 B CN 114090145B
- Authority
- CN
- China
- Prior art keywords
- page
- container
- jump
- determining
- target
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 75
- 239000007858 starting material Substances 0.000 claims description 25
- 238000004590 computer program Methods 0.000 claims description 18
- 230000006870 function Effects 0.000 claims description 16
- 239000003999 initiator Substances 0.000 claims description 16
- 230000009191 jumping Effects 0.000 claims description 6
- 230000008859 change Effects 0.000 claims description 5
- 238000011161 development Methods 0.000 abstract description 12
- 238000010586 diagram Methods 0.000 description 8
- 230000008569 process Effects 0.000 description 8
- 230000005540 biological transmission Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000008901 benefit Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
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
- 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/957—Browsing optimisation, e.g. caching or content distillation
-
- 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/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- 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/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
-
- 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/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
Abstract
The invention provides a method and a device for determining page skip, a storage medium and an electronic device, wherein the method comprises the following steps: obtaining jump information on a front-end page of a target application, wherein the jump information is used for indicating the type of the page to be jumped of the front-end page; performing target jump configuration of a target container on a page management module in a target application according to the jump information, and determining a calling interface corresponding to the target jump configuration; according to the method, the display content of the front-end page on the target application after the front-end page executes the page skip is determined according to the call interface, so that the problems that page skip among different types of front-end pages cannot be performed due to different page skip requirements corresponding to different containers in the prior art are solved, development efficiency is improved, development cost is further saved, and flexibility of the target object in page skip among different containers is ensured.
Description
Technical Field
The present invention relates to the field of communications, and in particular, to a method and apparatus for determining page skip, a storage medium, and an electronic device.
Background
In the current environment where modular technology and various large front end technologies are popular, various different types of pages are produced. There are more and more mixed-editing scenes of applications, so that the applications can use native technology (Android, iOS), H5 page (exact, vue), flutter technology and the like at the same time. Thus, in such a large environment, more and more scenarios may involve different types of front-end page jumps, such as native interface and H5 page jumps, native interface and Flutter interface jumps, and H5 interface and Flutter interface jumps. This places higher demands on page jumps.
Aiming at the problems that page skip among different types of front-end pages cannot be performed due to different page skip requirements corresponding to different containers in the related art, an effective technical scheme has not been proposed.
Disclosure of Invention
The embodiment of the invention provides a method and a device for determining page skip, a storage medium and an electronic device, which at least solve the problems that page skip among different types of front-end pages cannot be performed due to different page skip requirements corresponding to different containers in the related art.
According to an embodiment of the present invention, there is provided a method for determining page skip, including: obtaining jump information on a front-end page of a target application, wherein the jump information is used for indicating the type of the page to be jumped of the front-end page; performing target jump configuration of a target container on a page management module in the target application according to the jump information, and determining a calling interface corresponding to the target jump configuration; and determining the display content on the target application after the front-end page executes page skip according to the calling interface.
In an exemplary embodiment, determining, according to the call interface, presentation content on the target application after the front-end page performs page skipping, including: acquiring a uniform resource location identifier associated with the calling interface; determining an address jump protocol to be used by the front-end page according to the uniform resource location identifier so as to determine a target container to be started according to the address jump protocol; and displaying the target container to be started in the front-end page to determine the display content on the target application after the front-end page executes page skip.
In an exemplary embodiment, before performing the target jump configuration of the target container on the page management module located in the target application according to the jump information, the method further includes: determining a container set of the page container matched with the jump information, wherein the container set is used for indicating the page container allowing the page management module to perform initialization configuration; determining registration information of each page container in the container set in the page management module; and determining a target container from the container set according to the registration information.
In one exemplary embodiment, determining registration information of each of the page containers in the container set at the page management module includes: determining a container type corresponding to each page container in the container set; loading a container plug-in the page management module according to the container type, and establishing a page starter for the page container loaded by the container plug-in the page management module; and determining the registration information of each page container in the page management module according to the page initiator.
In an exemplary embodiment, after loading a container plug-in at the page management module according to the container type and establishing a page initiator at the page management module for a page container completing the container plug-in loading, the method further includes: determining a jump parameter of the page container according to the container plug-in, wherein the jump parameter is used for indicating a callback function corresponding to the page container when the page container is initialized; and determining the page information to be displayed of the page container through the jump parameter. In one exemplary embodiment, obtaining jump information on a front-end page of a target application includes: determining a jump requirement corresponding to the front-end page, wherein the jump requirement is used for indicating interface change of the front-end page; determining a first target page type and a second target page type which correspond to the front-end page before and after executing the jump according to the jump requirement; and determining the jump information on the front-end page of the target application according to the first target page type and the second target page type.
In an exemplary embodiment, after determining, according to the call interface, the presentation content on the target application after the front-end page performs the page jump, the method further includes: receiving an operation instruction of a target object for the display content, wherein the operation instruction is used for indicating whether to execute the page jumping operation again; and performing jump updating on the front-end page according to the operation instruction.
According to another embodiment of the present invention, there is provided a device for determining page skip, including: the acquisition module is used for acquiring jump information on a front-end page of a target application, wherein the jump information is used for indicating the type of the page to be jumped of the front-end page; the configuration module is used for carrying out target jump configuration of a target container on a page management module in the target application according to the jump information and determining a calling interface corresponding to the target jump configuration; and the first determining module is used for determining the display content on the target application after the front-end page executes page skip according to the calling interface.
In an exemplary embodiment, the first determining module is further configured to obtain a uniform resource locator associated with the call interface; determining an address jump protocol to be used by the front-end page according to the uniform resource location identifier so as to determine a target container to be started according to the address jump protocol; and displaying the target container to be started in the front-end page to determine the display content on the target application after the front-end page executes page skip.
In an exemplary embodiment, the above apparatus further includes: the second determining module is used for determining a container set of the page containers matched with the jump information, wherein the container set is used for indicating the page containers allowing the page management module to perform initialization configuration; determining registration information of each page container in the container set in the page management module; and determining a target container from the container set according to the registration information.
In an exemplary embodiment, the second determining module is further configured to determine a container type corresponding to each of the page containers in the container set; loading a container plug-in the page management module according to the container type, and establishing a page starter for the page container loaded by the container plug-in the page management module; and determining the registration information of each page container in the page management module according to the page initiator.
In an exemplary embodiment, the second determining module further includes: the jump unit is used for determining jump parameters of the page container according to the container plug-in, wherein the jump parameters are used for indicating corresponding callback functions when the page container is initialized; and determining the page information to be displayed of the page container through the jump parameter.
In an exemplary embodiment, the obtaining module is further configured to determine a jump requirement corresponding to the front end page, where the jump requirement is used to indicate an interface change of the front end page; determining a first target page type and a second target page type which correspond to the front-end page before and after executing the jump according to the jump requirement; and determining the jump information on the front-end page of the target application according to the first target page type and the second target page type.
In an exemplary embodiment, the above apparatus further includes: the updating module is used for receiving an operation instruction of the target object for the display content, wherein the operation instruction is used for indicating whether to execute the page jumping operation again; and performing jump updating on the front-end page according to the operation instruction.
According to a further embodiment of the invention, there is also provided a storage medium having stored therein a computer program, wherein the computer program is arranged to perform the steps of any of the method embodiments described above when run.
According to a further embodiment of the invention, there is also provided an electronic device comprising a memory having stored therein a computer program and a processor arranged to run the computer program to perform the steps of any of the method embodiments described above.
According to the method and the device for obtaining the jump information of the front-end page of the target application, jump information is used for indicating the type of the page to be jumped of the front-end page; under the condition that the page type in the jump information does not comprise a native interface, carrying out target jump configuration of a target container on a page management module in a target application according to the jump information, and determining a calling interface corresponding to the target jump configuration; according to the call interface, the display content of the front-end page after the front-end page executes the page skip on the target application is determined, that is, the problem that in the prior art, page skip among different types of front-end pages cannot be executed due to different page skip requirements corresponding to different containers can be solved, development efficiency is improved, development cost is further saved, and flexibility of the target object in page skip among different containers is ensured.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiments of the invention and together with the description serve to explain the invention and do not constitute a limitation on the invention. In the drawings:
FIG. 1 is a block diagram showing the hardware configuration of a computer terminal according to a method for determining page jumps according to an embodiment of the present invention;
FIG. 2 is a flow chart of a method of determining page jumps according to an embodiment of the invention;
FIG. 3 is an overall timing diagram of a page jump according to an alternative embodiment of the invention;
FIG. 4 is a timing diagram of a Flutter page jumping Flutter page according to an alternative embodiment of the present invention;
FIG. 5 is a timing diagram of a Flutter page jump H5 page according to an alternative embodiment of the present invention;
fig. 6 is a block diagram of a structure of a determination apparatus of page skip according to an embodiment of the present invention.
Detailed Description
The invention will be described in detail hereinafter with reference to the drawings in conjunction with embodiments. It should be noted that, in the case of no conflict, the embodiments and features in the embodiments may be combined with each other.
It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order.
The method embodiments provided by the embodiments of the present application may be executed in a computer terminal or a computing device similar to a device terminal. Taking the operation on a computer terminal as an example, fig. 1 is a block diagram of a hardware structure of a computer terminal according to a method for determining page jumps according to an embodiment of the present invention. As shown in fig. 1, the computer terminal may include one or more (only one is shown in fig. 1) processors 102 (the processor 102 may include, but is not limited to, a microprocessor MCU or a processing device such as a programmable logic device FPGA) and a memory 104 for storing data, and in one exemplary embodiment, may also include a transmission device 106 for communication functions and an input-output device 108. It will be appreciated by those skilled in the art that the configuration shown in fig. 1 is merely illustrative and is not intended to limit the configuration of the computer terminal described above. For example, a computer terminal may also include more or fewer components than shown in FIG. 1, or have a different configuration than the equivalent functions shown in FIG. 1 or more than the functions shown in FIG. 1.
The memory 104 may be used to store a computer program, for example, a software program of application software and a module, such as a computer program corresponding to a method for determining page skip in an embodiment of the present invention, and the processor 102 executes the computer program stored in the memory 104 to perform various functional applications and data processing, that is, implement the above-mentioned method. Memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory remotely located relative to the processor 102, which may be connected to the computer terminal via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The transmission device 106 is used to receive or transmit data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of a computer terminal. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, simply referred to as NIC) that can connect to other network devices through a base station to communicate with the internet. In one example, the transmission device 106 may be a Radio Frequency (RF) module, which is configured to communicate with the internet wirelessly.
In this embodiment, a method for determining page skip is provided, and fig. 2 is a flowchart of a method for determining page skip according to an embodiment of the present invention, where the flowchart includes the following steps:
step S202, obtaining jump information on a front-end page of a target application, wherein the jump information is used for indicating the type of a page to be jumped of the front-end page;
step S204, performing target jump configuration of a target container on a page management module in the target application according to the jump information, and determining a call interface corresponding to the target jump configuration;
it can be understood that, in order to jump the front-end page on the same target application, then display the display interfaces corresponding to different containers, firstly determine the page type of the front-end page to be jumped to the page, and determine the corresponding interface (corresponding to the calling interface in the embodiment of the present invention) for executing jump in the page management module included in the target application according to the page type;
step S206, determining the display content on the target application after the front-end page executes page skip according to the calling interface.
Through the steps, the jump information on the front-end page of the target application is obtained, wherein the jump information is used for indicating the type of the page to be jumped of the front-end page; under the condition that the page type in the jump information does not comprise a native interface, carrying out target jump configuration of a target container on a page management module in a target application according to the jump information, and determining a calling interface corresponding to the target jump configuration; according to the call interface, the display content of the front-end page on the target application after the front-end page executes the page skip is determined, namely, the skip information of the front-end page is determined, the target skip configuration of the target container is carried out in the page management module according to the skip information, and the call interface corresponding to the target application when executing the target skip configuration is determined, so that the process of page skip among different containers is realized, and therefore the problems that page skip among different types of front-end pages cannot be carried out due to different page skip requirements corresponding to different containers in the prior art are solved, development efficiency is improved, development cost is further saved, and flexibility of the target object in carrying out page skip among different containers is ensured.
In an exemplary embodiment, determining, according to the call interface, presentation content on the target application after the front-end page performs page skipping, including: acquiring a uniform resource location identifier associated with the calling interface; determining an address jump protocol to be used by the front-end page according to the uniform resource location identifier so as to determine a target container to be started according to the address jump protocol; and displaying the target container to be started in the front-end page to determine the display content on the target application after the front-end page executes page skip.
In short, in order to accurately acquire the display content of the calling interface after executing the page skip, acquiring an address skip protocol to be used by the front-end page through a uniform resource location identification (URL) associated with the calling interface, and determining whether a corresponding page starter exists in the page management module or not in the address skip protocol to be used by the front-end page, wherein the page starter is used for indicating to start the page skip and displaying the display content on the front-end page in a corresponding manner with a target container according to the address skip protocol.
For example, a jump port is called in a router module, a plug-in method is called by a router page, then the jump port is called in a native method of the router plug-in, the page management module is called by a page management module, the page management module obtains an address jump protocol through a URL, searches a registered page starter according to the address jump protocol, calls a container starting method through the page starter, displays a designated URL, further determines container display content corresponding to the jump port through the page management module, and starts a corresponding container through the corresponding page starter to finish page display.
In an exemplary embodiment, before performing the target jump configuration of the target container on the page management module located in the target application according to the jump information, the method further includes: determining a container set of the page container matched with the jump information, wherein the container set is used for indicating the page container allowing the page management module to perform initialization configuration; determining registration information of each page container in the container set in the page management module; and determining a target container from the container set according to the registration information.
In short, when the target container is configured on the front-end page, in order to ensure that the configured target container can be called by the target application, different target containers need to be registered in the page management module in advance, so that the page management module can effectively manage the target container when the configuration is called, and the target container is controlled to be initialized, so that page jump interference caused by the target container corresponding to the non-page management module is avoided.
In one exemplary embodiment, determining registration information of each of the page containers in the container set at the page management module includes: determining a container type corresponding to each page container in the container set; loading a container plug-in the page management module according to the container type, and establishing a page starter for the page container loaded by the container plug-in the page management module; and determining the registration information of each page container in the page management module according to the page initiator.
In an exemplary embodiment, after loading a container plug-in at the page management module according to the container type and establishing a page initiator at the page management module for a page container completing the container plug-in loading, the method further includes: determining a jump parameter of the page container according to the container plug-in, wherein the jump parameter is used for indicating a callback function corresponding to the page container when the page container is initialized; and determining the page information to be displayed of the page container through the jump parameter.
For example, the Flutter business layer starts the address of the Flutter page by calling the method of the dart layer of the Flutter plug-in, the Flutter plug-in can transmit the URL and the jump parameter to a callback function configured when the plug-in original Flutter Container is initialized through the plug-in, and optionally, when the Flutter Boost is used, the corresponding callback function is open Container; and then loading the display content by using the corresponding Page starter according To the Page management module so as To display the Page by calling the method of turning To the Page go Page.
In one exemplary embodiment, obtaining jump information on a front-end page of a target application includes: determining a jump requirement corresponding to the front-end page, wherein the jump requirement is used for indicating interface change of the front-end page; determining a first target page type and a second target page type which correspond to the front-end page before and after executing the jump according to the jump requirement; and determining the jump information on the front-end page of the target application according to the first target page type and the second target page type.
In order to make the page skip of the front-end page more efficient, determining whether the skip of the page is the additional skip of the page with the same type or the skip of the page with different types by determining the skip requirement corresponding to the front-end page, and then accurately configuring the front-back distinction when the corresponding target skip configuration is configured through the page management module, so as to ensure that the page display type corresponding to the target container can be rapidly determined during the subsequent call.
In an exemplary embodiment, after determining, according to the call interface, the presentation content on the target application after the front-end page performs the page jump, the method further includes: receiving an operation instruction of a target object for the display content, wherein the operation instruction is used for indicating whether to execute the page jumping operation again; and performing jump updating on the front-end page according to the operation instruction.
In order to better understand the process of the above-mentioned method for determining page jumps, the following description will describe the flow of the above-mentioned method for determining page jumps in connection with several alternative embodiments.
As an alternative implementation manner, the front-end pages in the application generally include H5 pages, flutter pages, native pages, etc., in principle, the resources displayed by the front-end may be configured to the server, and then the resources are issued to the front-end for loading and displaying through URL (uniform resource locator, uniform resource location system, abbreviated as URL), so each front-end page may correspond to a link address, and the page jump protocol corresponding to the loaded page resources is different.
In an alternative embodiment of the present invention, a non-native page skip mode is mainly provided, such as an H5 page, and a router page. For the page of H5, the resource is generally configured and issued at the server, the front end loads the page resource through the URL link through the H5 container, and the page is displayed. For the Flutter pages, the display needs to be performed in a container of Flutter (an open source building user interface toolkit), and there are many schemes, such as a manner that Flutter Boost provides a registered page address, so each Flutter page can also have a unique URL corresponding to it. Based on the premise, each page can be configured with a jump address, and each jump link corresponds to different jump protocols, so that the management of containers and the display of pages can be carried out as the types of front-end pages, and the jump of the pages among different types of front-end pages is achieved.
Optionally, as shown in fig. 3, an overall timing diagram of a page skip according to an alternative embodiment of the present invention is shown in detail as follows:
step 1-9, initializing a native module, initializing an H5 container module, initializing a router container, initializing a VDN plug-in, and completing relevant configuration; loading a router module, completing relevant initialization through a router plug-in, registering a router counter and H5 counter, and completing registration; the flutter launcher is configured by scheme (flutter), and the H5 launcher is configured by scheme (http, https); the method comprises the steps of initializing a primary module, initializing relevant logic, completing configuration of a container, including configuration of a Flutter container and configuration of an H5 container, and simultaneously completing initialization and configuration of a relevant H5 Launcher (desktop starter);
Alternatively, since the launcher is a tool for launching the container to present the page, it may be defined as a page launcher (for convenience of explanation, description of related functional logic will be continued by the launcher), through the launcher management module (i.e., the page launcher management module, the VDN component in the drawing is the launcher management module, which corresponds to the page management module in the embodiment of the present invention), the launcher of h5 is registered according to the h5 jump protocol (http/https, the schema in the drawing is the address jump protocol), the following description will be described by the address jump protocol, because the launcher of the launching of the h5 page is registered, and the Flutter module also completes loading and initializing simultaneously with the initialization of the app.
Step 10-11, calling a VDN interface by a flutter through a flutter VDN plug-in to jump, and calling a jump interface by a VDN component;
optionally, the plug-in is loaded by a router (a building user interface toolkit of a google open source) module. And in the loading process of the router module, the related plug-in is subjected to dependent updating and related configuration and initialization work are completed, wherein the creation of the router desktop (namely a router page starter) by the native part of the router jump plug-in is included, and the registration and configuration work are completed in the desktop management module through a link jump protocol.
Step 12-17, obtaining a corresponding launcher of the page through a jump protocol, comprising: acquiring a scheme schema through a URL; inquiring a corresponding page starter by using a URL schema, and if the schema of the URL is a router, completing the jump by the router starter; the router host starts a router container to finish the page skip of the router; if the schema of the URL is http or https, the jump needs to be completed through H5 Launcher; h5 And (5) starting the H5 container by using the launcher, loading the webpage and finishing the webpage.
Optionally, a jump interface is called in the router module for example, after the plug-in method is called by the router page, the jump interface is called by calling a launcher management module (VDN component) in the method, the launcher management module obtains an address jump protocol through a URL, searches for a registered launcher according to the address jump protocol, and displays a designated URL by calling a method of starting a container through the launcher. And further determining the display content of the container corresponding to the jump interface through the launcher management module, and starting the corresponding container through the corresponding launcher page starter to complete the display of the page.
In short, for the caller of the jump interface, the caller does not need to care what container the corresponding page should be presented with, gives the judging process to the launcher management module, and can complete the presentation of the page by starting the corresponding container through the launcher.
As an alternative implementation manner, fig. 4 is a timing chart of the Flutter page skip Flutter page according to an alternative embodiment of the present invention, and the corresponding operation timing is as follows:
step S402, a business layer corresponding to the Flutter page sends go to page ('Flutter:// xxx') information transferred to the page to a dart layer of the Flutter plug-in;
step S404, the dart layer sends open ('router:// xxx') information to the Up vdn plugin native layer;
step S406, up vdn plugin native, executing an open Container;
step S408, up VDN plugin native layer jumps to the formulated page by calling VDN plug-in method;
step S410, the VDN foundation component determines whether there is a Launcher page initiator process;
step S412, calling the counter starter of the Flutter through the configuration information of the counter page starter;
step S414, up vdn plugin native, carrying out Launcher treatment;
steps S416, up vdn plugin native layer determines to execute Flutter Boost activity with New Engine (). Url ('router:// xxx');
Step S418, the router business layer calls back register page builders of the router boost;
that is, the Flutter business layer starts the address of the Flutter page by calling the method of the dart layer of the Flutter plug-in, the Flutter plug-in transmits the URL and the jump parameter to the callback function configured when the plug-in original Flutter Container is initialized through the plug-in, and optionally, when the Flutter Boost is used, the corresponding callback function is open Container; the method for starting the Fluter Page provided by the Fluter container is not used for displaying the Fluter Page in the callback function, and the link jump request is called by the VDN component To be transferred To the Page go To Page To display the Page; the VDN (virtual data network, VDN for short) module searches whether registered Launcher exists according to the URL, because here, the router page corresponds to the Launcher registered in the initialization of the router's jump plug-in, and calls the Launcher into the method of the router Launcher; the method provided by using the Flutter container starts the specified Flutter page, for example, in the current scheme, the Flutter page is displayed by the Flutter Boost correspondingly because the display of the Flutter page is completed by the Flutter Boost.
As an alternative implementation manner, FIG. 5 is a timing chart of the Fluter page skip H5 page according to an alternative embodiment of the present invention, and the corresponding operation timing is as follows:
step S502, a business layer corresponding to the Flutter page sends go to page ('Flutter:// xxx') information transferred to the page to the dart layer of the Flutter plug-in;
step S504, the dart layer sends open ('router:// xxx') information to the Up vdn plugin native layer;
step S506, up vdn plugin native, executing an open Container;
step S508, the VDN foundation component goes to page operation, and executes go to page ('http:// test.html');
step S510, starting a corresponding H5 interface;
it should be noted that, when the Flutter page jumps to the H5 page, the previous sequence is consistent with the sequence from S402 to S406 of the Flutter page started by the Flutter, and the callback method is called and then the launcher is searched by the VDN component. However, since the H5 page is to be displayed after the jump, the H5 host is found, and the method is called to the host, the H5 container is started by the method provided by the H5 container frame, and the specified web page is displayed.
As an alternative implementation, in the target application, the native page completes the corresponding relationship between the page and the URL by:
Step 1, generating a page DNS (DomainName system, a domain name system, DNS for short) and a routing table through annotation, completing initialization configuration of a URL and activity (which is an application program component used for being in charge of interaction with a user), and inquiring a corresponding original page through the table through the designated URL;
step 2, the native page initiator Native Page Laucher loads and manages information in the DNS and the routing table during initialization;
step 3, after the user invokes the jump Page go Page method, the corresponding initiator launcher is found through the URL, if the native Page is the native Page, the native Page initiator Native Page Laucher is found, and then when the initiator laucher executes the start Page launch Page method, the designated native Page is found through the DNS and the routing information, so that the designated Page is started.
In summary, through an alternative embodiment of the present invention, a method for managing a plurality of containers in an application to start a page is provided, by using a launcher management module, a launcher defined by different containers is unified to manage the types of the containers in the application to start the page, and this process is handed to the launcher management module to be unified to maintain, and further, a page skip scheme is provided, in which the types of the containers are determined according to links of front-end pages, and different launcher (page initiator) are defined by sub types, after registering in the launcher management module, when the page is started, the method is called to a corresponding launcher by using the launcher management module, and the specified page is displayed by starting the container in the launcher. For a developer, the adoption of the alternative implementation mode has better development interface use experience: the user does not need to pay attention to the container type corresponding to the link, the container type distinction is converted into the identifier type distinction, the judging process is finished by the identifier management module, and the interface calling experience of the interface caller is improved. And then the interface calling experience of development is improved, the development efficiency is necessarily improved, the cost can be further saved, the development productivity is improved, and the economic benefit is improved.
From the description of the above embodiments, it will be clear to a person skilled in the art that the method according to the above embodiments may be implemented by means of software plus the necessary general hardware platform, but of course also by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method according to the embodiments of the present invention.
The embodiment also provides a device for determining page skip, which is used for implementing the above embodiment and the preferred embodiment, and is not described in detail. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. While the means described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.
Fig. 6 is a block diagram of a page skip determining apparatus according to an embodiment of the present invention, as shown in fig. 6, including:
the obtaining module 62 is configured to obtain jump information on a front-end page of a target application, where the jump information is used to indicate a page type to be jumped by the front-end page;
the configuration module 64 is configured to perform target jump configuration of a target container on a page management module located in the target application according to the jump information, and determine a call interface corresponding to the target jump configuration;
optionally, the target jump configuration includes a page initiator corresponding to the target container and a corresponding jump link;
and the first determining module 66 is configured to determine, according to the call interface, the content displayed on the target application after the front-end page performs page skip.
The device is used for acquiring the jump information on the front-end page of the target application, wherein the jump information is used for indicating the type of the page to be jumped of the front-end page; under the condition that the page type in the jump information does not comprise a native interface, carrying out target jump configuration of a target container on a page management module in a target application according to the jump information, and determining a calling interface corresponding to the target jump configuration; according to the call interface, the display content of the front-end page on the target application after the front-end page executes the page skip is determined, namely, the skip information of the front-end page is determined, the target skip configuration of the target container is carried out in the page management module according to the skip information, and the call interface corresponding to the target application when executing the target skip configuration is determined, so that the process of page skip among different containers is realized, and therefore the problems that page skip among different types of front-end pages cannot be carried out due to different page skip requirements corresponding to different containers in the prior art are solved, development efficiency is improved, development cost is further saved, and flexibility of the target object in carrying out page skip among different containers is ensured.
In an exemplary embodiment, the first determining module is further configured to obtain a uniform resource locator associated with the call interface; determining an address jump protocol to be used by the front-end page according to the uniform resource location identifier so as to determine a target container to be started according to the address jump protocol; and displaying the target container to be started in the front-end page to determine the display content on the target application after the front-end page executes page skip.
In short, in order to accurately acquire the display content of the calling interface after executing the page skip, acquiring an address skip protocol to be used by the front-end page through a uniform resource location identification (URL) associated with the calling interface, and determining whether a corresponding page starter exists in the page management module or not in the address skip protocol to be used by the front-end page, wherein the page starter is used for indicating to start the page skip and displaying the display content on the front-end page in a corresponding manner with a target container according to the address skip protocol.
For example, a jump port is called in a router module, a plug-in method is called by a router page, then the jump port is called in a native method of the router plug-in, the page management module is called by a page management module, the page management module obtains an address jump protocol through a URL, searches a registered page starter according to the address jump protocol, calls a container starting method through the page starter, displays a designated URL, further determines container display content corresponding to the jump port through the page management module, and starts a corresponding container through the corresponding page starter to finish page display.
In an exemplary embodiment, the above apparatus further includes: the second determining module is used for determining a container set of the page containers matched with the jump information, wherein the container set is used for indicating the page containers allowing the page management module to perform initialization configuration; determining registration information of each page container in the container set in the page management module; and determining a target container from the container set according to the registration information.
In short, when the target container is configured on the front-end page, in order to ensure that the configured target container can be called by the target application, different target containers need to be registered in the page management module in advance, so that the page management module can effectively manage the target container when the configuration is called, and the target container is controlled to be initialized, so that page jump interference caused by the target container corresponding to the non-page management module is avoided.
In an exemplary embodiment, the second determining module is further configured to determine a container type corresponding to each of the page containers in the container set; loading a container plug-in the page management module according to the container type, and establishing a page starter for the page container loaded by the container plug-in the page management module; and determining the registration information of each page container in the page management module according to the page initiator.
In an exemplary embodiment, the second determining module further includes: the jump unit is used for determining jump parameters of the page container according to the container plug-in, wherein the jump parameters are used for indicating corresponding callback functions when the page container is initialized; and determining the page information to be displayed of the page container through the jump parameter.
For example, the Flutter business layer starts the address of the Flutter page by calling the method of the dart layer of the Flutter plug-in, the Flutter plug-in can transmit the URL and the jump parameter to a callback function configured when the plug-in original Flutter Container is initialized through the plug-in, and optionally, when the Flutter Boost is used, the corresponding callback function is open Container; and then loading the display content by using the corresponding Page starter according To the Page management module so as To display the Page by calling the method of turning To the Page go Page.
In an exemplary embodiment, the obtaining module is further configured to determine a jump requirement corresponding to the front end page, where the jump requirement is used to indicate an interface change of the front end page; determining a first target page type and a second target page type which correspond to the front-end page before and after executing the jump according to the jump requirement; and determining the jump information on the front-end page of the target application according to the first target page type and the second target page type.
In order to make the page skip of the front-end page more efficient, determining whether the skip of the page is the additional skip of the page with the same type or the skip of the page with different types by determining the skip requirement corresponding to the front-end page, and then accurately configuring the front-back distinction when the corresponding target skip configuration is configured through the page management module, so as to ensure that the page display type corresponding to the target container can be rapidly determined during the subsequent call.
In an exemplary embodiment, the above apparatus further includes: the updating module is used for receiving an operation instruction of the target object for the display content, wherein the operation instruction is used for indicating whether to execute the page jumping operation again; and performing jump updating on the front-end page according to the operation instruction.
It should be noted that each of the above modules may be implemented by software or hardware, and for the latter, it may be implemented by, but not limited to: the modules are all located in the same processor; alternatively, the above modules may be located in different processors in any combination.
An embodiment of the invention also provides a storage medium having a computer program stored therein, wherein the computer program is arranged to perform the steps of any of the method embodiments described above when run.
In an exemplary embodiment, in the present embodiment, the above-described storage medium may be configured to store a computer program for performing the steps of:
s1, obtaining jump information on a front-end page of a target application, wherein the jump information is used for indicating the type of a page to be jumped of the front-end page;
s2, performing target jump configuration of a target container on a page management module in the target application according to the jump information, and determining a calling interface corresponding to the target jump configuration;
s3, determining the display content on the target application after the front-end page executes page skip according to the calling interface.
In an exemplary embodiment, in the present embodiment, the storage medium may include, but is not limited to: a usb disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing a computer program.
An embodiment of the invention also provides an electronic device comprising a memory having stored therein a computer program and a processor arranged to run the computer program to perform the steps of any of the method embodiments described above.
In an exemplary embodiment, the electronic apparatus may further include a transmission device connected to the processor, and an input/output device connected to the processor.
In an exemplary embodiment, in this embodiment, the above-mentioned processor may be configured to execute the following steps by a computer program:
s1, obtaining jump information on a front-end page of a target application, wherein the jump information is used for indicating the type of a page to be jumped of the front-end page;
s2, performing target jump configuration of a target container on a page management module in the target application according to the jump information, and determining a calling interface corresponding to the target jump configuration;
s3, determining the display content on the target application after the front-end page executes page skip according to the calling interface.
In an exemplary embodiment, reference may be made to the examples described in the foregoing embodiments and optional implementations, and this embodiment is not repeated herein.
It will be apparent to those skilled in the art that the modules or steps of the invention described above may be implemented in a general purpose computing device, they may be concentrated on a single computing device, or distributed across a network of computing devices, and in one exemplary embodiment they may be implemented in program code executable by a computing device, so that they may be stored in a memory device for execution by a computing device, and in some cases, the steps shown or described may be performed in a different order than what is shown or described, or they may be separately fabricated into individual integrated circuit modules, or a plurality of modules or steps in them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only of the preferred embodiments of the present invention and is not intended to limit the present invention, but various modifications and variations can be made to the present invention by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the principle of the present invention should be included in the protection scope of the present invention.
Claims (8)
1. A method for determining a page jump, comprising:
obtaining jump information on a front-end page of a target application, wherein the jump information is used for indicating the type of the page to be jumped of the front-end page;
performing target jump configuration of a target container on a page management module in the target application according to the jump information, and determining a calling interface corresponding to the target jump configuration;
determining the display content on the target application after the front-end page executes page skip according to the calling interface;
wherein before the target container is configured on the page management module in the target application according to the jump information, the method further comprises:
determining a container set of the page container matched with the jump information, wherein the container set is used for indicating the page container allowing the page management module to perform initialization configuration;
Determining registration information of each page container in the container set in the page management module;
determining a target container from the container set according to the registration information;
wherein said determining registration information of each of said page containers in said container set at said page management module comprises:
determining a container type corresponding to each page container in the container set;
loading a container plug-in the page management module according to the container type, and establishing a page starter for the page container loaded by the container plug-in the page management module;
and determining the registration information of each page container in the page management module according to the page initiator.
2. The method for determining page skip according to claim 1, wherein determining, according to the call interface, presentation content on the target application after the front-end page performs page skip includes:
acquiring a uniform resource location identifier associated with the calling interface;
determining an address jump protocol to be used by the front-end page according to the uniform resource location identifier so as to determine a target container to be started according to the address jump protocol;
And displaying the target container to be started in the front-end page to determine the display content on the target application after the front-end page executes page skip.
3. The method for determining a page jump according to claim 1, wherein a container plug-in is loaded at the page management module according to the container type, and after a page initiator is established at the page management module for a page container for which the container plug-in loading is completed, the method further comprises:
determining a jump parameter of the page container according to the container plug-in, wherein the jump parameter is used for indicating a callback function corresponding to the page container when the page container is initialized;
and determining the page information to be displayed of the page container through the jump parameter.
4. The method for determining page jumps according to claim 1, wherein obtaining jump information on a front page of the target application includes:
determining a jump requirement corresponding to the front-end page, wherein the jump requirement is used for indicating interface change of the front-end page;
determining a first target page type and a second target page type which correspond to the front-end page before and after executing the jump according to the jump requirement;
And determining the jump information on the front-end page of the target application according to the first target page type and the second target page type.
5. The method for determining page skip according to claim 1, wherein after determining, according to the call interface, presentation content on the target application after the front-end page performs page skip, the method further comprises:
receiving an operation instruction of a target object for the display content, wherein the operation instruction is used for indicating whether to execute the page jumping operation again;
and performing jump updating on the front-end page according to the operation instruction.
6. A page jump determination apparatus, comprising:
the acquisition module is used for acquiring jump information on a front-end page of a target application, wherein the jump information is used for indicating the type of the page to be jumped of the front-end page;
the configuration module is used for carrying out target jump configuration of a target container on a page management module in the target application according to the jump information and determining a calling interface corresponding to the target jump configuration;
the first determining module is used for determining the display content on the target application after the front-end page executes page skip according to the calling interface;
The apparatus further comprises: the second determining module is used for determining a container set of the page containers matched with the jump information, wherein the container set is used for indicating the page containers allowing the page management module to perform initialization configuration; determining registration information of each page container in the container set in the page management module; determining a target container from the container set according to the registration information;
the second determining module is used for determining the container type corresponding to each page container in the container set; loading a container plug-in the page management module according to the container type, and establishing a page starter for the page container loaded by the container plug-in the page management module; and determining the registration information of each page container in the page management module according to the page initiator.
7. A computer-readable storage medium, characterized in that the storage medium has stored therein a computer program, wherein the computer program is arranged to execute the method of any of the claims 1 to 5 when run.
8. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to run the computer program to perform the method of any of the claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111250919.2A CN114090145B (en) | 2021-10-26 | 2021-10-26 | Page jump determining method and device, storage medium and electronic device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111250919.2A CN114090145B (en) | 2021-10-26 | 2021-10-26 | Page jump determining method and device, storage medium and electronic device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114090145A CN114090145A (en) | 2022-02-25 |
| CN114090145B true CN114090145B (en) | 2024-03-22 |
Family
ID=80297734
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111250919.2A Active CN114090145B (en) | 2021-10-26 | 2021-10-26 | Page jump determining method and device, storage medium and electronic device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114090145B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107679061A (en) * | 2017-07-26 | 2018-02-09 | 上海壹账通金融科技有限公司 | Mix APP page navigation method, device, terminal and storage medium |
| CN108700984A (en) * | 2017-01-20 | 2018-10-23 | 微软技术许可有限责任公司 | Desktop starter |
| CN111459581A (en) * | 2019-01-22 | 2020-07-28 | 阿里巴巴集团控股有限公司 | Page switching method and device, electronic equipment and computer readable medium |
| CN111459685A (en) * | 2019-01-18 | 2020-07-28 | 阿里巴巴集团控股有限公司 | Communication method, device, equipment and readable medium of page end and native end |
| CN111552463A (en) * | 2020-03-27 | 2020-08-18 | 深圳壹账通智能科技有限公司 | Page jump method and device, computer equipment and storage medium |
| CN111652580A (en) * | 2020-05-29 | 2020-09-11 | 平安医疗健康管理股份有限公司 | Method and device for processing data of nodes |
| US10803167B1 (en) * | 2018-02-20 | 2020-10-13 | NortonLifeLock, Inc. | Systems and methods for executing application launchers |
| CN112417337A (en) * | 2020-11-27 | 2021-02-26 | 贝壳技术有限公司 | Page jump implementation method and device, electronic equipment and storage medium |
| CN112905933A (en) * | 2021-01-29 | 2021-06-04 | 挂号网（杭州）科技有限公司 | Page jump method and device, electronic equipment and storage medium |
| CN113296859A (en) * | 2021-04-28 | 2021-08-24 | 青岛海尔科技有限公司 | Page loading method and device, storage medium and electronic device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10762204B2 (en) * | 2013-11-28 | 2020-09-01 | Blackberry Limited | Managing containerized applications |
-
2021
- 2021-10-26 CN CN202111250919.2A patent/CN114090145B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108700984A (en) * | 2017-01-20 | 2018-10-23 | 微软技术许可有限责任公司 | Desktop starter |
| CN107679061A (en) * | 2017-07-26 | 2018-02-09 | 上海壹账通金融科技有限公司 | Mix APP page navigation method, device, terminal and storage medium |
| US10803167B1 (en) * | 2018-02-20 | 2020-10-13 | NortonLifeLock, Inc. | Systems and methods for executing application launchers |
| CN111459685A (en) * | 2019-01-18 | 2020-07-28 | 阿里巴巴集团控股有限公司 | Communication method, device, equipment and readable medium of page end and native end |
| CN111459581A (en) * | 2019-01-22 | 2020-07-28 | 阿里巴巴集团控股有限公司 | Page switching method and device, electronic equipment and computer readable medium |
| CN111552463A (en) * | 2020-03-27 | 2020-08-18 | 深圳壹账通智能科技有限公司 | Page jump method and device, computer equipment and storage medium |
| CN111652580A (en) * | 2020-05-29 | 2020-09-11 | 平安医疗健康管理股份有限公司 | Method and device for processing data of nodes |
| CN112417337A (en) * | 2020-11-27 | 2021-02-26 | 贝壳技术有限公司 | Page jump implementation method and device, electronic equipment and storage medium |
| CN112905933A (en) * | 2021-01-29 | 2021-06-04 | 挂号网（杭州）科技有限公司 | Page jump method and device, electronic equipment and storage medium |
| CN113296859A (en) * | 2021-04-28 | 2021-08-24 | 青岛海尔科技有限公司 | Page loading method and device, storage medium and electronic device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114090145A (en) | 2022-02-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110187912B (en) | Node selection method and device | |
| CN106713004B (en) | Router adaptation method and system | |
| CN104980297A (en) | Virtual machine resource changing method and device, and virtualized network function device | |
| WO2015143794A1 (en) | Creating and upgrading methods, server, terminal, upgrading system, and storage media | |
| CN108376078A (en) | Upgrade method, device and the household appliance of equipment | |
| CN110543324B (en) | Plug-in increment updating method and device for application program | |
| CN112737816B (en) | Equipment binding method and device | |
| CN111885594A (en) | Equipment binding method and device | |
| CN111885115A (en) | Equipment binding change method and device | |
| CN114327349B (en) | Smart card determining method and device, storage medium and electronic device | |
| CN110990008B (en) | Page updating method and device, storage medium and electronic equipment | |
| CN113296859A (en) | Page loading method and device, storage medium and electronic device | |
| CN111135581A (en) | Game updating method and device | |
| CN109067735B (en) | Dynamic configuration method of communication protocol, wireless communication device and intelligent equipment | |
| CN114090145B (en) | Page jump determining method and device, storage medium and electronic device | |
| CN112214701A (en) | Page display method and system, storage medium and electronic device | |
| CN104135503B (en) | Method, Apparatus and system that data are downloaded | |
| CN112738019A (en) | Method and device for displaying device information, storage medium and electronic device | |
| CN112416617A (en) | Control method and device of Bluetooth equipment, storage medium and electronic device | |
| CN113190565B (en) | Data updating method and device, storage medium and electronic device | |
| CN111026995A (en) | Method and device for information association between applications and storage medium | |
| CN116701004A (en) | Cloud function development method, device, electronic device and storage medium | |
| CN108170536B (en) | Expanding method and device of WEB program | |
| CN111507447A (en) | Label identification method and device | |
| CN111078571A (en) | Test method for simulation response, terminal device and computer readable storage medium |
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 |