CN112631482A - Page processing method and device - Google Patents
Page processing method and device Download PDFInfo
- Publication number
- CN112631482A CN112631482A CN202110017887.5A CN202110017887A CN112631482A CN 112631482 A CN112631482 A CN 112631482A CN 202110017887 A CN202110017887 A CN 202110017887A CN 112631482 A CN112631482 A CN 112631482A
- Authority
- CN
- China
- Prior art keywords
- page
- environment
- routing
- display
- page display
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
- G06F3/0483—Interaction with page-structured environments, e.g. book metaphor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Human Computer Interaction (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The application provides a page processing method and a page processing device, wherein the page processing method comprises the steps of receiving a display request aiming at a page, wherein the display request carries a routing identifier of the page; determining the routing type of the page from a routing table of the current page display environment based on the routing identification; and under the condition that the routing type of the page is not matched with the current page display environment, receiving a page display result of the page displayed in the page display environment matched with the routing type of the page based on a preset routing method. Specifically, the page processing method determines the routing type of the page based on the routing table of the current page display environment, and realizes that users between the pages jump without perception under different page display environments through a preset routing method under the condition that the routing type of the page is not matched with the current page display environment, so that the fluency of the jump between the pages under different page display environments is greatly ensured.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a page processing method. The application also relates to a page processing device, a computing device and a computer readable storage medium.
Background
With the development of computer networks and the popularization of smart phones, users often use terminal devices to browse contents in networks, and often browse pictures, characters, videos, audios and the like in the networks by accessing pages in the networks, so developers who need the pages develop related pages to be placed in websites, and different pages may need the developers to develop in different development environments, and then the websites may have pages developed in different development environments.
Disclosure of Invention
In view of this, the present application provides a page processing method. The application also relates to a page processing device, a computing device and a computer readable storage medium, which are used for solving the technical defect that the page jump between pages developed in different development environments is not smooth in the prior art.
According to a first aspect of an embodiment of the present application, there is provided a page processing method, including:
receiving a display request aiming at a page, wherein the display request carries a route identifier of the page;
determining the routing type of the page from a routing table of the current page display environment based on the routing identification;
and under the condition that the routing type of the page is not matched with the current page display environment, receiving a page display result of the page displayed in the page display environment matched with the routing type of the page based on a preset routing method.
According to a second aspect of the embodiments of the present application, there is provided a page processing apparatus, including:
the system comprises a request receiving module, a routing module and a display module, wherein the request receiving module is configured to receive a display request aiming at a page, and the display request carries a routing identifier of the page;
a routing type determination module configured to determine a routing type of the page from a routing table of a current page presentation environment based on the routing identifier;
and the page display module is configured to receive a page display result of the page displayed in the page display environment matched with the routing type of the page based on a preset routing method under the condition that the routing type of the page is not matched with the current page display environment.
According to a third aspect of embodiments of the present application, there is provided a computing device comprising a memory, a processor and computer instructions stored on the memory and executable on the processor, the processor implementing the steps of the page processing method when executing the computer instructions.
According to a fourth aspect of embodiments of the present application, there is provided a computer-readable storage medium storing computer instructions which, when executed by a processor, implement the steps of the page processing method.
The page processing method comprises the steps of receiving a display request aiming at a page, wherein the display request carries a routing identifier of the page; determining the routing type of the page from a routing table of the current page display environment based on the routing identification; and under the condition that the routing type of the page is not matched with the current page display environment, receiving a page display result of the page displayed in the page display environment matched with the routing type of the page based on a preset routing method. Specifically, the page processing method determines the routing type of the page based on the routing table of the current page display environment, and realizes that users between the pages jump without perception under different page display environments through a preset routing method under the condition that the routing type of the page is not matched with the current page display environment, so that the fluency of the jump between the pages under different page display environments is greatly ensured.
Drawings
Fig. 1 is a flowchart of a page processing method according to an embodiment of the present application;
fig. 2 is an interaction flowchart of a page processing method applied to a page in a Flutter environment to open a Native environment according to an embodiment of the present application;
fig. 3 is an interaction flowchart of a page processing method applied to a Native environment to open a page of a Flutter environment according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a page processing apparatus according to an embodiment of the present application;
fig. 5 is a block diagram of a computing device according to an embodiment of the present application.
Detailed Description
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. This application is capable of implementation in many different ways than those herein set forth and of similar import by those skilled in the art without departing from the spirit of this application and is therefore not limited to the specific implementations disclosed below.
The terminology used in the one or more embodiments of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of the present application. As used in one or more embodiments of the present application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used in one or more embodiments of the present application refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It will be understood that, although the terms first, second, etc. may be used herein in one or more embodiments of the present application to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first aspect may be termed a second aspect, and, similarly, a second aspect may be termed a first aspect, without departing from the scope of one or more embodiments of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
First, the noun terms to which one or more embodiments of the present application relate are explained.
Flutter: the method is a cross-platform development tool, and the developed APP (Application) can run on an iOS (mobile operating system developed by apple) system and an Android (operating system of free and open source codes based on a Linux kernel) system at the same time.
Native: android and iOS native code runtime environments.
Flutter environment: runtime environment of Flutter code.
Hybrid routing: and the addressing capability of mutual calling between Native and Flutter is supported.
iOS host: the host APP source code of the iOS operating system.
Android host: and the host APP source code of the Android operating system.
Flutter app (client): APP containing Flutter.
MethodChanel: with Flutter method channel, Flutter is a way to communicate across platforms.
AppDelegate: is the entry class name of the iOS APP.
Flutteviewcontroller: is a class implementation of Flutter based on the iOS platform for rendering and event delivery.
iOS platform APIs: the iOS operating system has its own application program interface.
3rd-Party APIs for iOS: the third party provides an application program interface for the iOS.
Activity: is the class name of Android interface control.
Flutter View: and the Flutter is based on class implementation of an Android platform and is used for rendering and event delivery.
PageLifeCycleChannel: encapsulating the fluttmethodchannel for transmitting the page life cycle information; in the embodiment of the application, a channel for synchronizing the life cycle of a page between a Flutter environment and a Native environment uses a codec officially provided by Flutter methodchannel at the bottom layer, and a parameter protocol: { "status": xxx, "data": { "pageName": xxx, "extra": xxx, "UUID": xxx } }.
NavigationChannel: packaging the flutttermethodchannel for transmitting navigation information; in the embodiment of the application, the Flutter environment actively calls the channel of the page method of the Native environment, the bottom layer uses the codec provided by the Flutter method channel official, and the parameter protocol is as follows: { "action": xxx, "data": { "pageName": xxx, "extra": xxx, "UUID": xxx } }.
In practical application, the page processing method provided by the application can be applied to a scene of page jump between a Flutter environment and a Native environment. The method and the device can also be applied to other scenes for page jump between different environments, and the method and the device are not limited in this respect. Specifically, Flutter is a cross-platform development tool, and the developed APP can run on the iOS system and the Android system at the same time. Thus, Flutter needs the ability to communicate with Native. The communication capability between the Flutter environment and the Native environment is realized by building Platform Channels between the Flutter environment and the Native environment, and in the prior art, in order to realize page jump in the two different environments, additional plug-in codes need to be written for realization. In addition, in order to realize page jump under different environments, page stack confusion is caused after multi-level nesting, and management cannot be performed; when pages in different environments jump, data transmission is difficult, and an additional plug-in needs to be defined; when a plurality of Flutter pages exist simultaneously, a plurality of engine instances are created, and the memory pressure is large.
In the present application, a page processing method is provided, and the present application relates to a page processing apparatus, a computing device, and a computer-readable storage medium, which are described in detail in the following embodiments one by one.
Referring to fig. 1, fig. 1 is a flowchart illustrating a page processing method according to an embodiment of the present application, which specifically includes the following steps.
Step 102: receiving a display request aiming at a page, wherein the display request carries a route identifier of the page.
Here, a page may be understood as a page of any type, any website, such as a merchandise page of a shopping website, a payment page, or a video viewing page of an entertainment website, a music appreciation page, and so on.
Specifically, a display request for a page is received in a current page display environment, wherein the display request carries a routing identifier of the page; the routing identifier of the page may be a character string composed of numbers and/or letters, etc.
Step 104: and determining the routing type of the page from a routing table of the current page display environment based on the routing identification.
In specific implementation, the page processing method provided by the embodiment of the application is applied to a scene of performing page jump between a Flutter environment and a Native environment, and the current page display environment is the Flutter environment or the Native environment; specifically, the current page display environment is different according to different practical applications.
Specifically, after the routing identifier of the page is determined, the routing type of the page is determined from the routing table of the current page display environment based on the routing identifier of the page; and determining the page display environment corresponding to the page according to the routing type of the page. For example, if the Route type is Native Route, it may be determined that the page display environment corresponding to the Route type is Native environment.
Step 106: and under the condition that the routing type of the page is not matched with the current page display environment, receiving a page display result of the page displayed in the page display environment matched with the routing type of the page based on a preset routing method.
Specifically, after determining the routing type of the page from the routing table of the current page display environment based on the routing identifier, the method further includes:
and under the condition that the routing type of the page is matched with the current page display environment, determining the page in a routing table displayed by the current page based on the routing identifier of the page, and displaying the page in the current page display environment.
The routing table maps the association relation among the routing identification, the routing type and the page.
In practical application, after the routing type of a page is determined, whether the routing type of the page is matched with the current page display environment is judged, if yes, the page corresponding to the routing identifier is determined from a routing table of the current page display environment based on the routing identifier of the page, and the page is displayed in the current page display environment; and if not, receiving a page display result for displaying the page in a page display environment matched with the routing type of the page based on a preset routing method.
For example, if the current page display environment is a Flutter environment and the page display environment corresponding to the routing type of the page is a Native environment, it may be determined that the routing type of the page is not matched with the current page display environment, and a display result of the page displayed in the Native environment is received based on a preset routing method; if the current page display environment is a Native environment and the page display environment corresponding to the routing type of the page is a Native environment, then it can be determined that the routing type of the page matches the current page display environment, then the page is determined in a routing table maintained by the Native environment based on the routing identifier of the page, and the page is displayed in the Native environment.
According to the page processing method provided by the embodiment of the application, under the condition that the routing type of the page is determined based on the routing table of the current page display environment and is not matched with the current page display environment, the user among the pages can jump without perception under different page display environments through a preset routing method, and the fluency of the jump among the pages under different page display environments is greatly ensured.
In a specific implementation, the current page display environment and the page display environment to be displayed on the page may be the same environment or may not be the same environment, and specifically, under the condition that the current page display environment and the page display environment to be displayed on the page are not the same environment, the two page display environments may be any two different types of page display environments. In the following, the first page display environment is taken as the flute environment, and the second page display environment is taken as the Native environment for example.
In another embodiment of the present specification, the current page display environment is a first page display environment;
correspondingly, the receiving, based on the preset routing method, a page display result that the page is displayed in a page display environment matched with the routing type of the page includes:
determining a second page display environment matched with the routing type of the page based on the routing type of the page;
determining page display information based on the page attribute information of the page and the routing identifier of the page, and sending the page display information to the second page display environment;
and receiving the page display result of the page determined and displayed in the routing table of the second page display environment based on the page display information of the second page display environment.
The first page display environment can be understood as a flute environment, and the second page display environment can be understood as a Native environment.
In specific implementation, when the routing type of the page and the current page display environment: and under the condition that the Flutter environment is not matched, determining a second page display environment matched with the routing type of the page based on the routing type of the page: the Native environment determines page display information based on the page attribute information of the page and the routing identifier of the page, and sends the page display information to the Native environment; receiving a Native environment, determining and displaying a page display result of the page in a Native routing table based on the page display information; the page attribute information of the page includes, but is not limited to, a user identifier, a page identifier of the page, a name of the page, a type of the page, and the like.
In the embodiment of the present description, under the condition that the page display environment of the page is not matched with the current page display environment, the page display information carrying the page attribute information of the page and the routing identifier of the page is sent to the page display environment of the page, so that after the page display environment of the page receives the page display information, the corresponding page can be directly queried in the routing table maintained by the page display environment of the page and displayed, and the user of the page can jump without sensing without adding additional plug-in codes in the current page display environment and the page display environment of the page.
Specifically, the determining page display information based on the page attribute information of the page and the routing identifier of the page includes:
generating a page display object based on the page attribute information of the page and the routing identification of the page, and putting the page display object into a routing table of the first page display environment;
and generating page display information carrying the page display object based on the page display object.
Specifically, the first page display page generates a page display object based on page attribute information of the page and a routing identifier of the page, where the page display object is a routing class abstract to the page in a Native environment in a Flutter environment.
After the page display object of the page is created, page display information sent to a Native environment is generated based on the page display object, and the page display information carries the page display object.
In specific implementation, after receiving the page display information, the Native environment analyzes the packaged page display object, determines the page from the routing table maintained by the Native environment through the page attribute information of the page in the page display object obtained after analysis and the routing identifier of the page, and constructs and displays the page based on the page attribute information of the page. For example, if the page is a dynamic page, then after determining the page, it is necessary to obtain dynamic parameters of the page based on the page attribute information to construct the page.
In this embodiment of the present description, when the first page presentation environment sends page presentation information to the second page presentation environment, the route class of the page abstraction is encapsulated based on the route identifier of the page and the page attribute information of the page, the page in the second page presentation environment is determined based on the mapping relationship of the route class in the second page presentation environment, and then the constructed page may be presented in the second page presentation environment without being jammed.
In specific implementation, the receiving the second page display environment determines and displays a page display result of the page in a routing table of the second page display environment based on the page display information, and the page display result includes:
and receiving the page display object carried in the page display information by the second page display environment, and determining and displaying the page display result of the page in a routing table of the second page display environment.
In specific implementation, after receiving the page display information, the Native environment parses the encapsulated page display object, determines the page from the routing table maintained by the Native environment through the page attribute information of the page in the page display object and the routing identifier of the page obtained after parsing, and constructs and displays the page based on the page attribute information of the page, wherein the page is used as a mapping of a page call object created by the Flutter environment, and after performing the page display in the Native environment, the page life cycle event of the page is synchronized to the Flutter environment through a third-party communication mechanism (for example, PageLifeCycleChannel), and the Flutter environment monitors the page life cycle event of the third-party communication mechanism to receive a page display result of the page in the Native environment, for example, a page display result successfully displayed by the page, and the like.
In practical application, a page life cycle event is monitored, and when the page cannot be displayed in a Native environment, an error notification prompt, such as a popup prompt or a 404 page error notification prompt, can be returned to a user in a Flutter environment.
In the embodiment of the present specification, after the display notification of the page is sent to the page display environment of the page, various page display results of the page in the page display environment are also received, so as to monitor the display state of the page in real time through the received page display results, thereby ensuring real-time communication of page jump in two environments.
In another embodiment of the present specification, after receiving a page showing result showing the page in a page showing environment matching with the routing type of the page, the method further includes:
receiving a closing request aiming at the page, wherein the closing request carries a route identifier of the page;
determining the page display object based on the routing identifier of the page, and sending a closing request carrying the page display object to the second page display environment through a third-party communication mechanism;
and receiving the page determined by the second page display environment based on the page display object in the page closing request and a page closing result for closing the page, and deleting the page display object in the routing table of the first page display environment.
In specific implementation, when a closing request for the page is received in a Flutter environment, the page display object is determined and deleted based on the routing identifier of the page carried in the closing request, and the closing request carrying the page display object is sent to a Native environment through a third-party communication mechanism; and analyzing the page display object in the process of receiving the closing request by the Native environment, determining the page to be closed based on the page routing identifier in the page display object, and closing the page. And the Flutter environment monitors through a third-party communication mechanism and receives a page determined by the Native environment based on the page display object in the page closing request and a page closing result for closing the page.
In the embodiment of the application, when the page in the second page display environment is closed in the first page display environment, the page to be closed is rapidly determined and closed through the mapping relation between the page display object created in the first page display environment and the routing table of the second page display environment, and the page display object is deleted under the condition that the page closing result of the second page display environment is received, so that the space occupation is saved.
In addition, after receiving a page showing result of showing the page in a page showing environment matched with the routing type of the page, the method further includes:
under the condition that the second page display environment receives a closing request of the page, closing the page based on the routing identifier of the page carried in the closing request;
and receiving a page closing result of the page sent by the second page display environment, and deleting the page display object in a routing table of the first page display environment based on the routing identifier of the page carried in the page closing result.
In specific implementation, when a closing request of a page is received in a Native environment, the page is closed based on a page routing identifier carried in the closing request, a page closing result is sent to a Flutter environment through a third-party communication mechanism, and when the Flutter environment receives a notification of the page closing result, the page display object created in the Flutter environment is deleted based on the page routing identifier.
In the embodiment of the application, when the page in the second page display environment is closed in the second page display environment, the page can be quickly closed based on the routing identifier of the page carried in the closing request of the page, and the page display object is deleted under the condition that the page closing result of the second page display environment is received in the first page display environment, so that the space occupation is saved.
In another embodiment of the present specification, the current page display environment is a second page display environment;
correspondingly, the receiving, based on the preset routing method, a page display result that the page is displayed in a page display environment matched with the routing type of the page includes:
determining a first page showing environment matched with the routing type of the page based on the routing type of the page;
sending page display information to the first page display environment, wherein the page display information carries a routing identifier and page attribute information of the page;
receiving a page display notification sent by the first page display environment based on the routing identification of the page and the page attribute information of the page;
rendering a page display object carried in the page display notification to generate the page when it is determined that the rendered page in the first page display environment does not exist in the routing table of the second page display environment, and receiving a page display result of the page displayed in the first page environment.
The first page display environment is a flute environment, and the second page display environment is a Native environment.
Specifically, in a Native environment, a Flutter environment matched with the routing type of the page is determined based on the routing type of the page, and then page display information carrying a routing identifier of the page and page attribute information is sent to the Flutter environment through a third-party communication mechanism; the method comprises the steps that a Flutter environment creates a page display object based on a routing identification and page attribute information of a page, the page display object is placed in a routing table of the Flutter environment, when the page display object is to be displayed, a third-party communication mechanism is called to notify a Native environment, after the Native environment receives a page display notice carrying the page display object, a rendering page in the Flutter environment does not exist in the routing table of the Native environment, the page display object carried in the page display notice is rendered to generate a Flutter page, and a page display result of the page displayed in the Flutter environment is received.
In this embodiment of the present description, when a page of a first page display environment is opened in a second page display environment, after the second page display environment receives a page display notification of the first page display environment, and when it is determined that page rendering of the first page display environment does not exist in a routing table of the second page display environment, a page display object carried in the page display notification is rendered to generate the page, and a page display result that shows the page in the first page environment is received; and rendering the page of the first page environment in a rendering container of the second page display environment so as to save the occupation of rendering space in the first page display environment.
Specifically, the rendering the page display object carried in the page display notification to generate the page includes:
creating a rendering container corresponding to the page, and binding the rendering container with an engine of the first page display environment;
rendering the page display object carried in the page display notification in the rendering container to generate the page.
In practical application, when a rendering page in a Flutter environment does not exist in a routing table in a Native environment, a Flutter rendering container corresponding to the page is created, the Flutter rendering container is bound with an engine in the Flutter environment, and a page display object carried in the page display notification is rendered in the Flutter rendering container to generate a Flutter page.
In practical application, in order to avoid the situation that threads are contended for page rendering, a Flutter rendering container corresponding to the page is created in a Native environment, and the Flutter rendering container and the Flutter environment engine are bound to realize rendering of the page in the Flutter rendering container.
In another embodiment of this specification, after receiving page display information sent by the first page display environment based on the routing identifier of the page and the page attribute information of the page, the method further includes:
and when determining that the last rendering page in the first page display environment exists in the routing table of the second page display environment, removing the binding relationship between the rendering container of the last rendering page and the engine of the first page display environment.
In practical application, if a previous rendered page in the Flutter environment exists in the routing table of the Native environment, the binding relationship between the Flutter rendered container corresponding to the previous rendered page and the engine of the Flutter environment needs to be released, so that the binding relationship between the Flutter rendered container of the current page and the engine of the Flutter environment can be established, page rendering is performed, and page rendering is prevented from being disordered.
In specific implementation, after receiving a page display result that is displayed on the page in a page display environment matched with the routing type of the page, the method further includes:
under the condition that a closing request aiming at the page is received, sending the closing request to the first page display environment, wherein the closing request carries a routing identifier of the page;
receiving the page display object determined by the first page display environment based on the routing identifier of the page, the page determined based on the page display object and a page closing result for closing the page;
and releasing the binding relationship between the rendering container corresponding to the page and the engine of the first page display environment.
Specifically, under the condition that a closing request aiming at a Flutter page is received in a Native environment, the closing request carrying a routing identifier of the page is sent to the Flutter environment, the Flutter environment determines and closes a page corresponding to a page display object from a routing table of the Flutter environment based on the routing identifier of the page, then a page closing result is sent to the Native environment through a third-party communication mechanism, under the condition that the Flutter environment receives the page closing result, the binding relationship between a Flutter rendering container corresponding to the page in the Native environment and an engine of the Flutter environment is released based on the page identifier in the page closing result, then it is judged that the Flutter page still exists in the routing table, if the Flutter page exists, the nearest Flutter rendering container and the engine of the Flutter environment are bound, so that the next Flutter page is rendered, and the occupation of the engine of the Flutter environment is avoided.
In the embodiment of the application, a page stack (namely, the routing table) is maintained in each of a first page display environment and a second page display environment, and is used for monitoring changes of the page stacks of both sides, performing state synchronization through a fluttmeter method channel, defining a general protocol for data transmission of both sides, simplifying data transmission in two different environments, encapsulating a name of a route and a parameter (namely, the page display object) needing to be transmitted by using a dictionary, using a codec provided by a third party in a bottom layer (namely, the bottom layer of the Flutter environment or a Native environment), and transmitting the parameter through the fluttmeter method channel after serialization, wherein the parameter supports a basic data type, String, Map, an array and the like; and aiming at a second page display environment (Native environment), the display and closing of the page do not need to add extra operation in the code logic of the second page display environment any more, only the page of the second page display environment needs to be regarded as the page of the first page display environment (Flutter environment), the page jump operation can be completed by using the self-contained routing capability of the first page display environment, the use mode is the same as the mode of operating the page inside the first page display environment, the calling party does not care about the internal implementation, the parameter transmission is supported, the result is returned, and the page jump without perception of the user is realized.
The following description will further describe the page processing method with reference to fig. 2 by taking an example of an application of the page processing method provided by the present application to open a page in a Native environment in a Flutter environment. Fig. 2 shows an interaction flowchart of a page processing method applied to a page in a Flutter environment to open a Native environment according to an embodiment of the present application, which specifically includes the following steps.
Step 202: the method comprises the steps that a Fluter environment receives a display request of a page aiming at a Native environment sent by a user, wherein the display request carries a route identification of the page of the Native environment.
Step 204: determining the routing type of the page of the Native environment and the Native environment corresponding to the routing type of the page of the Native environment in a routing table of the router environment based on the routing identifier, and encoding the routing identifier of the page of the Native environment and the page attribute information of the page of the Native environment to create the routing class of the page of the Native environment as the mapping of the page of the Native environment in the Native environment, and adding the routing class of the page of the Native environment into the routing table.
Step 206: the Flutter environment calls the navigation channel to send a notification of opening the page of the Native environment to the Native environment, wherein the notification carries the routing class of the page of the Native environment.
Step 208: the Native environment decodes the routing class of the page of the Native environment, finds the page of the Native environment corresponding to the routing identification of the page of the Native environment obtained by decoding, and constructs and displays the page of the Native environment based on the page attribute information of the page of the Native environment.
And the page of the Native environment is used as the mapping of the page of the Flutter environment.
Step 210: after the page of the Native environment is displayed, the Native environment synchronizes the life cycle event of the page of the Native environment to the Flutter environment through the PageLifeCycleChannel.
The life cycle events of the pages in the Native environment include, but are not limited to, presentation events, presentation results, specific presentation contents, and the like of the pages in the Native environment.
Step 212: and the Flutter environment receives a monitoring result of the life cycle event of the page of the Native environment through the PageLifecCyclerChanel.
Step 214: in a Native environment, receiving a closing request of a user for a page of the Native environment, wherein the closing request carries a route identifier of the page of the Native environment.
Step 216: and the Native environment closes the page of the Native environment based on the routing identification, and removes the page of the Native environment from the routing table of the Native environment.
Step 218: and the Native environment calls the NavigationChannel to send the closed routing identification of the page of the Native environment and the result of closing the page of the Native environment in the Native environment to the Flutter environment.
Step 220: after receiving the result, the Flutter environment determines and deletes the created routing class of the page of the Native environment from the routing table of the Flutter environment based on the routing identifier of the page of the Native environment.
Step 222: receiving a closing request of a user for a page of the Native environment in the Flutter environment, wherein the closing request carries a route identifier of the page of the Native environment.
Step 224: and the Flutter environment determines and deletes the created routing class of the page of the Native environment from a routing table of the Flutter environment based on the routing identification.
Step 226: and the Flutter environment calls the Navigationchannel to send a notification for closing the page of the Native environment to the Native environment, wherein the notification carries the route identifier.
Step 228: and after receiving the notification, the Native environment determines and closes the corresponding page of the Native environment from the routing table based on the routing identifier.
In the embodiment of the application, by the page processing method, when the page of the Native environment is opened in the Flutter environment, the use is simple, the plug-in code does not need to be written, and a general protocol is defined to decode and encode data, so that the data transmission is simple and rapid; and aiming at a Native environment, two modes of displaying and closing the page are adopted, no additional operation is needed to be added in Native code logic, the Native page is only needed to be regarded as a Flutter page, the page jump operation can be completed by using the self-contained routing capability of the Flutter environment, the use mode is the same as the mode of operating the page in the Flutter environment, the calling party does not care about internal implementation, parameter transmission is supported, and the result is returned.
The following description will further describe the page processing method with reference to fig. 3, by taking an application of the page processing method provided by the present application to open a page in a Flutter environment in a Native environment as an example. Fig. 3 shows an interaction flowchart of a page processing method applied to a Native environment to open a page of a router environment according to an embodiment of the present application, which specifically includes the following steps.
Step 302: and receiving a display request of a page aiming at the Flutter environment sent by a user in the Native environment.
The display request carries the routing identifier and the page attribute information of the page of the Flutter environment.
Step 304: the Native environment calls the NavigationChannel to send an opening notice for opening the page of the Flutter environment to the Flutter environment.
The opening notification carries the routing identifier and the page attribute information of the page of the Flutter environment.
Step 306: the Flutter environment creates a routing class of the page of the Flutter environment based on the routing identifier and the page attribute information of the page of the Flutter environment, and adds the routing class to the navigation stack.
Wherein the navigation stack can be understood as a routing table.
Step 308: the Flutter context determines the routing class to be exposed.
Step 310: and calling the navigation channel to send the route type display notice to the Native environment.
Step 312: after receiving the notification, the Native environment judges whether a page of the Flutter environment already exists in the navigation stack, if so, the Native environment unbundles the Flutter rendering container and the Flutter engine corresponding to the previous page of the Flutter environment, and creates a corresponding Flutter rendering container and a corresponding Flutter engine binding for the page of the Flutter environment again, so that the Flutter engine is reused; if the page does not exist (namely Native is at the bottom), a corresponding Flutter rendering container and Flutter engine binding are directly created for the page of the Flutter environment. And then rendering the routing class in a Flutter rendering container of the Native environment to generate a page of the Flutter environment.
After the page of the Flutter environment is generated, the page of the Flutter environment is put into a navigation stack of a Native environment, and a mapping relation between the routing class and the page of the Flutter environment is established in the navigation stack.
Step 314: the Flutter environment shows the rendered pages of the Flutter environment.
Step 316: receiving a closing request of a user for a page of the Flutter environment in a Native environment, wherein the closing request carries a route identifier of the page of the Flutter environment.
Step 318: the Native environment calls the NavigationChannel to send a notification to the Flutter environment that the page of the Flutter environment is closed.
Wherein, the notification carries the route identifier of the page of the Flutter environment.
Step 320: the Flutter environment pops the corresponding route class from its navigation stack based on the route identification.
Step 322: and the Flutter environment calls the Navigationchannel to send a page closing notification to the Native environment, wherein the notification carries the route class.
Step 324: and under the condition that the Native environment receives the notification, determining a corresponding Flutter environment page from the navigation stack based on the routing class, and terminating the binding relationship between a Flutter rendering container corresponding to the Flutter environment page and an engine of the Flutter environment.
In specific implementation, after the binding relationship between the Flutter rendering container corresponding to the page of the Flutter environment and the engine of the Flutter environment is terminated, the page of the Flutter environment is also closed; judging whether a page of the Flutter environment still exists in the navigation stack, if so, binding a Flutter rendering container corresponding to the page of the nearest Flutter environment with an engine of the Flutter environment; if not (namely the next route is a Native page route), the corresponding Flutter rendering container and the Flutter engine of the previous Flutter environment page are unbound, and a corresponding Flutter rendering container and a Flutter engine binding are created for the Flutter environment page again, so that the Flutter engine is reused.
Step 326: the Flutter environment deletes the route class in its navigation stack.
In the embodiment of the application, a navigation stack is respectively maintained in a Flutter environment and a Native environment, and is used for monitoring the changes of page stacks of two parties, performing state synchronization through a Flutter method channel, defining a general protocol for data transmission of the two parties, simplifying data transmission in two different environments, encapsulating a name of a route and a parameter (namely a page display object) needing to be transmitted by using a dictionary, using a codec provided by a third party at a bottom layer (namely the bottom layer of the Flutter environment or the Native environment), and transmitting the parameter through the Flutter method channel after serialization, wherein the parameter supports basic data types, String, Map, arrays and the like; and aiming at the Native environment, the display and closing of the page do not need to add extra operation in the code logic of the Native environment, only the page of the Native environment is needed to be regarded as the page of the Flutter environment, the page jump operation can be completed by using the self-contained routing capability of the Flutter environment, the use mode is the same as the mode of operating the page in the Flutter environment, the calling party does not care about internal implementation, parameter transmission is supported, the result is returned, and the page jump without perception of the user is realized.
Corresponding to the above method embodiment, the present application further provides an embodiment of a page processing apparatus, and fig. 4 shows a schematic structural diagram of a page processing apparatus provided in an embodiment of the present application. As shown in fig. 4, the apparatus includes:
a request receiving module 402, configured to receive a display request for a page, where the display request carries a routing identifier of the page;
a route type determination module 404 configured to determine a route type of the page from a route table of a current page presentation environment based on the route identifier;
a page display module 406, configured to receive, based on a preset routing method, a page display result that the page is displayed in the page display environment that matches the routing type of the page, when the routing type of the page does not match the current page display environment.
Optionally, the current page display environment is a first page display environment;
accordingly, the page presentation module 406 is further configured to:
determining a second page display environment matched with the routing type of the page based on the routing type of the page;
determining page display information based on the page attribute information of the page and the routing identifier of the page, and sending the page display information to the second page display environment;
and receiving the page display result of the page determined and displayed in the routing table of the second page display environment based on the page display information of the second page display environment.
Optionally, the page presentation module 406 is further configured to:
generating a page display object based on the page attribute information of the page and the routing identification of the page, and putting the page display object into a routing table of the first page display environment;
and generating page display information carrying the page display object based on the page display object.
Optionally, the page presentation module 406 is further configured to:
and receiving the page display object carried in the page display information by the second page display environment, and determining and displaying the page display result of the page in a routing table of the second page display environment.
Optionally, the current page display environment is a second page display environment;
accordingly, the page presentation module 406 is further configured to:
determining a first page showing environment matched with the routing type of the page based on the routing type of the page;
sending page display information to the first page display environment, wherein the page display information carries a routing identifier and page attribute information of the page;
receiving a page display notification sent by the first page display environment based on the routing identification of the page and the page attribute information of the page;
rendering a page display object carried in the page display notification to generate the page when it is determined that the rendered page in the first page display environment does not exist in the routing table of the second page display environment, and receiving a page display result of the page displayed in the first page environment.
Optionally, the page presentation module 406 is further configured to:
creating a rendering container corresponding to the page, and binding the rendering container with an engine of the first page display environment;
rendering the page display object carried in the page display notification in the rendering container to generate the page.
Optionally, the apparatus further comprises:
and the binding module is configured to release the binding relation between the rendering container of the previous rendering page and the engine of the first page display environment when the previous rendering page in the first page display environment is determined to exist in the routing table of the second page display environment.
Optionally, the apparatus further comprises:
a first shutdown module configured to:
receiving a closing request aiming at the page, wherein the closing request carries a route identifier of the page;
determining the page display object based on the routing identifier of the page, and sending a closing request carrying the page display object to the second page display environment through a third-party communication mechanism;
and receiving the page determined by the second page display environment based on the page display object in the page closing request and a page closing result for closing the page, and deleting the page display object in the routing table of the first page display environment.
Optionally, the apparatus further includes:
a second shutdown module configured to:
under the condition that the second page display environment receives a closing request of the page, closing the page based on the routing identifier of the page carried in the closing request;
and receiving a page closing result of the page sent by the second page display environment, and deleting the page display object in a routing table of the first page display environment based on the routing identifier of the page carried in the page closing result.
Optionally, the apparatus further comprises:
a third shutdown module configured to:
under the condition that a closing request aiming at the page is received, sending the closing request to the first page display environment, wherein the closing request carries a routing identifier of the page;
receiving the page display object determined by the first page display environment based on the routing identifier of the page, the page determined based on the page display object and a page closing result for closing the page;
and releasing the binding relationship between the rendering container corresponding to the page and the engine of the first page display environment.
Optionally, the apparatus further comprises:
and the matching module is configured to determine the page in a routing table displayed by the current page based on the routing identifier of the page and display the page in the current page display environment under the condition that the routing type of the page is matched with the current page display environment.
According to the page processing method provided by the embodiment of the application, under the condition that the routing type of the page is determined based on the routing table of the current page display environment and is not matched with the current page display environment, the user among the pages can jump without perception under different page display environments through a preset routing method, and the fluency of the jump among the pages under different page display environments is greatly ensured.
The above is a schematic scheme of a page processing apparatus of this embodiment. It should be noted that the technical solution of the page processing apparatus and the technical solution of the page processing method belong to the same concept, and details that are not described in detail in the technical solution of the page processing apparatus can be referred to the description of the technical solution of the page processing method.
FIG. 5 illustrates a block diagram of a computing device 500 provided in accordance with one embodiment of the present description. The components of the computing device 500 include, but are not limited to, a memory 510 and a processor 520. Processor 520 is coupled to memory 510 via bus 530, and database 550 is used to store data.
Computing device 500 also includes access device 540, access device 540 enabling computing device 500 to communicate via one or more networks 560. Examples of such networks include the Public Switched Telephone Network (PSTN), a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), or a combination of communication networks such as the internet. The access device 540 may include one or more of any type of network interface, e.g., a Network Interface Card (NIC), wired or wireless, such as an IEEE802.11 Wireless Local Area Network (WLAN) wireless interface, a worldwide interoperability for microwave access (Wi-MAX) interface, an ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a bluetooth interface, a Near Field Communication (NFC) interface, and so forth.
In one embodiment of the present description, the above-described components of computing device 500, as well as other components not shown in FIG. 5, may also be connected to each other, such as by a bus. It should be understood that the block diagram of the computing device architecture shown in FIG. 5 is for purposes of example only and is not limiting as to the scope of the present description. Those skilled in the art may add or replace other components as desired.
Computing device 500 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., tablet, personal digital assistant, laptop, notebook, netbook, etc.), mobile phone (e.g., smartphone), wearable computing device (e.g., smartwatch, smartglasses, etc.), or other type of mobile device, or a stationary computing device such as a desktop computer or PC. Computing device 500 may also be a mobile or stationary server.
The processor 520 is configured to execute the following computer-executable instructions, and the steps of the page processing method are implemented when the processor 520 executes the computer-executable instructions.
The above is an illustrative scheme of a computing device of the present embodiment. It should be noted that the technical solution of the computing device and the technical solution of the above-mentioned page processing method belong to the same concept, and details that are not described in detail in the technical solution of the computing device can be referred to the description of the technical solution of the above-mentioned page processing method.
An embodiment of the present application further provides a computer-readable storage medium, which stores computer instructions, and when the instructions are executed by a processor, the instructions implement the steps of the page processing method as described above.
The above is an illustrative scheme of a computer-readable storage medium of the present embodiment. It should be noted that the technical solution of the storage medium belongs to the same concept as the technical solution of the above-mentioned page processing method, and details that are not described in detail in the technical solution of the storage medium can be referred to the description of the technical solution of the above-mentioned page processing method.
The foregoing description of specific embodiments of the present application has been presented. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
The computer instructions comprise computer program code which may be in the form of source code, object code, an executable file or some intermediate form, or the like. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
It should be noted that, for the sake of simplicity, the above-mentioned method embodiments are described as a series of acts or combinations, but those skilled in the art should understand that the present application is not limited by the described order of acts, as some steps may be performed in other orders or simultaneously according to the present application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
The preferred embodiments of the present application disclosed above are intended only to aid in the explanation of the application. Alternative embodiments are not exhaustive and do not limit the invention to the precise embodiments described. Obviously, many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the application and its practical applications, to thereby enable others skilled in the art to best understand and utilize the application. The application is limited only by the claims and their full scope and equivalents.
Claims (14)
1. A page processing method is characterized by comprising the following steps:
receiving a display request aiming at a page, wherein the display request carries a route identifier of the page;
determining the routing type of the page from a routing table of the current page display environment based on the routing identification;
and under the condition that the routing type of the page is not matched with the current page display environment, receiving a page display result of the page displayed in the page display environment matched with the routing type of the page based on a preset routing method.
2. The page processing method according to claim 1, wherein said current page presentation environment is a first page presentation environment;
correspondingly, the receiving, based on the preset routing method, a page display result that the page is displayed in a page display environment matched with the routing type of the page includes:
determining a second page display environment matched with the routing type of the page based on the routing type of the page;
determining page display information based on the page attribute information of the page and the routing identifier of the page, and sending the page display information to the second page display environment;
and receiving the page display result of the page determined and displayed in the routing table of the second page display environment based on the page display information of the second page display environment.
3. The method for processing a page according to claim 2, wherein said determining page display information based on the page attribute information of the page and the routing identifier of the page comprises:
generating a page display object based on the page attribute information of the page and the routing identification of the page, and putting the page display object into a routing table of the first page display environment;
and generating page display information carrying the page display object based on the page display object.
4. The page processing method according to claim 3, wherein the receiving the second page display environment determines and displays a page display result of the page in a routing table of the second page display environment based on the page display information, and comprises:
and receiving the page display object carried in the page display information by the second page display environment, and determining and displaying the page display result of the page in a routing table of the second page display environment.
5. The page processing method according to claim 1, wherein said current page display environment is a second page display environment;
correspondingly, the receiving, based on the preset routing method, a page display result that the page is displayed in a page display environment matched with the routing type of the page includes:
determining a first page showing environment matched with the routing type of the page based on the routing type of the page;
sending page display information to the first page display environment, wherein the page display information carries a routing identifier and page attribute information of the page;
receiving a page display notification sent by the first page display environment based on the routing identification of the page and the page attribute information of the page;
rendering a page display object carried in the page display notification to generate the page when it is determined that the rendered page in the first page display environment does not exist in the routing table of the second page display environment, and receiving a page display result of the page displayed in the first page environment.
6. The page processing method according to claim 5, wherein the rendering the page display object carried in the page display notification to generate the page includes:
creating a rendering container corresponding to the page, and binding the rendering container with an engine of the first page display environment;
rendering the page display object carried in the page display notification in the rendering container to generate the page.
7. The page processing method according to claim 6, after receiving page display information sent by said first page display environment based on said page routing identifier and said page attribute information, further comprising:
and when determining that the last rendering page in the first page display environment exists in the routing table of the second page display environment, removing the binding relationship between the rendering container of the last rendering page and the engine of the first page display environment.
8. The page processing method according to claim 4, wherein said receiving a page showing result showing the page in a page showing environment matching the routing type of the page further comprises:
receiving a closing request aiming at the page, wherein the closing request carries a route identifier of the page;
determining the page display object based on the routing identifier of the page, and sending a closing request carrying the page display object to the second page display environment through a third-party communication mechanism;
and receiving the page determined by the second page display environment based on the page display object in the page closing request and a page closing result for closing the page, and deleting the page display object in the routing table of the first page display environment.
9. The page processing method according to claim 4, wherein said receiving a page showing result showing the page in a page showing environment matching the routing type of the page further comprises:
under the condition that the second page display environment receives a closing request of the page, closing the page based on the routing identifier of the page carried in the closing request;
and receiving a page closing result of the page sent by the second page display environment, and deleting the page display object in a routing table of the first page display environment based on the routing identifier of the page carried in the page closing result.
10. The page processing method according to claim 6 or 7, wherein said receiving a page showing result showing the page in a page showing environment matching the routing type of the page further comprises:
under the condition that a closing request aiming at the page is received, sending the closing request to the first page display environment, wherein the closing request carries a routing identifier of the page;
receiving the page display object determined by the first page display environment based on the routing identifier of the page, the page determined based on the page display object and a page closing result for closing the page;
and releasing the binding relationship between the rendering container corresponding to the page and the engine of the first page display environment.
11. The method for processing a page according to claim 1, wherein after determining the routing type of the page from the routing table of the current page display environment based on the routing identifier, the method further comprises:
and under the condition that the routing type of the page is matched with the current page display environment, determining the page in a routing table displayed by the current page based on the routing identifier of the page, and displaying the page in the current page display environment.
12. A page processing apparatus, comprising:
the system comprises a request receiving module, a routing module and a display module, wherein the request receiving module is configured to receive a display request aiming at a page, and the display request carries a routing identifier of the page;
a routing type determination module configured to determine a routing type of the page from a routing table of a current page presentation environment based on the routing identifier;
and the page display module is configured to receive a page display result of the page displayed in the page display environment matched with the routing type of the page based on a preset routing method under the condition that the routing type of the page is not matched with the current page display environment.
13. A computing device comprising a memory, a processor, and computer instructions stored on the memory and executable on the processor, wherein the processor implements the steps of the method of any one of claims 1-11 when executing the computer instructions.
14. A computer-readable storage medium storing computer instructions, which when executed by a processor, perform the steps of the method of any one of claims 1 to 11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110017887.5A CN112631482A (en) | 2021-01-07 | 2021-01-07 | Page processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110017887.5A CN112631482A (en) | 2021-01-07 | 2021-01-07 | Page processing method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112631482A true CN112631482A (en) | 2021-04-09 |
Family
ID=75291034
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110017887.5A Pending CN112631482A (en) | 2021-01-07 | 2021-01-07 | Page processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112631482A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109508436A (en) * | 2018-11-14 | 2019-03-22 | 北京锐安科技有限公司 | Front end method for routing and device based on asynchronous loading page |
| CN110489621A (en) * | 2019-07-09 | 2019-11-22 | 北京字节跳动网络技术有限公司 | A kind of method, apparatus, medium and the electronic equipment of dynamic adjustment routing |
| CN111639275A (en) * | 2019-03-01 | 2020-09-08 | 阿里巴巴集团控股有限公司 | Routing information processing method and device, electronic equipment and computer storage medium |
| CN112073488A (en) * | 2020-08-28 | 2020-12-11 | 青岛海尔科技有限公司 | Method and device for processing request |
-
2021
- 2021-01-07 CN CN202110017887.5A patent/CN112631482A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109508436A (en) * | 2018-11-14 | 2019-03-22 | 北京锐安科技有限公司 | Front end method for routing and device based on asynchronous loading page |
| CN111639275A (en) * | 2019-03-01 | 2020-09-08 | 阿里巴巴集团控股有限公司 | Routing information processing method and device, electronic equipment and computer storage medium |
| CN110489621A (en) * | 2019-07-09 | 2019-11-22 | 北京字节跳动网络技术有限公司 | A kind of method, apparatus, medium and the electronic equipment of dynamic adjustment routing |
| CN112073488A (en) * | 2020-08-28 | 2020-12-11 | 青岛海尔科技有限公司 | Method and device for processing request |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109358936B (en) | Information processing method, device, storage medium, electronic device and system | |
| CN111726399B (en) | Docker container secure access method and device | |
| CN104137520B (en) | A kind of information push method and device | |
| CN111324343B (en) | Code generation method and device | |
| CN110119294A (en) | The generation method of menu page, apparatus and system | |
| CN105141567B (en) | Interaction data processing method and system, the exchange method of terminal applies and server-side | |
| WO2018082465A1 (en) | Notification bar message displaying method and apparatus, mobile terminal, and server | |
| US11824826B2 (en) | System and method for multi-channel group communications | |
| US20140007113A1 (en) | Method and apparatus for task based remote services | |
| CN114138372B (en) | Front-end component loading method and device | |
| US11818491B2 (en) | Image special effect configuration method, image recognition method, apparatus and electronic device | |
| JP2023522266A (en) | Method, apparatus, device and medium for multimedia data delivery | |
| CN108021564A (en) | A kind of method and apparatus of page reorientation | |
| CN112073465A (en) | Dynamic desensitization method and device based on SFTP transmission | |
| US10504277B1 (en) | Communicating within a VR environment | |
| CN114422468A (en) | Message processing method, device, terminal and storage medium | |
| CN113162977A (en) | Information processing method and device, equipment and storage medium | |
| CN112631482A (en) | Page processing method and device | |
| WO2022001647A1 (en) | Theme rendering method and apparatus, and electronic device and computer readable storage medium | |
| CN115686458A (en) | Virtual world application development method and device | |
| CN114566173A (en) | Audio mixing method, device, equipment and storage medium | |
| CN115061785A (en) | Information issuing method and device, storage medium and server | |
| CN105373466B (en) | A kind of log processing method and equipment | |
| US10679391B1 (en) | Mobile phone notification format adaptation | |
| CN111078215A (en) | Software product application method and device, storage medium and electronic equipment |
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 |