CN114968209A - Page management method, system, electronic equipment and storage medium - Google Patents

Abstract

The invention relates to the technical field of page development and provides a page management method, a page management system, electronic equipment and a storage medium. The page management method is applied to a multi-page structure developed based on a cross-platform mobile application development framework RN, and comprises the following steps: responding to a page calling request, analyzing a calling parameter of the page calling request, and acquiring a target specific strategy class corresponding to the calling parameter; the multi-page structure is configured with a plurality of specific strategy classes based on a strategy mode, and page logic corresponding to the RN page is configured in each specific strategy class; calling the target specific strategy class and a view component of the multi-page structure, wherein the view component is configured with a display style of the multi-page structure; and loading and generating a target RN page according to the page logic and the display style configured in the target specific strategy class. The method and the device can realize the logic decoupling of the multiple RN pages, the efficient loading of the RN pages and other management processes, and realize the effective management of the multiple RN pages.

Description

Page management method, system, electronic equipment and storage medium

Technical Field

The present invention relates to the field of page development technologies, and in particular, to a page management method, a page management system, an electronic device, and a storage medium.

Background

The fact Native (RN for short) is a cross-platform mobile application development framework, supports two major platforms of iOS (a mobile operating system) and Android (a mobile operating system), has rich UI (User Interface) experience effects, has become a popular mobile development technology, and more mobile applications use the RN for page development.

At present, for management of RN pages, under a condition of multiple RN pages (for example, a live broadcast scene), all RN pages are managed by one Manager object, which has the following problems: the logics of all RN pages are mixed and written together, so that not only is the code redundant, but also the basic logic needs to be written once for each RN page, and the maintenance and the expansion are inconvenient, each logic needs to be changed when one RN page is modified, the basic logic needs to be written once when one RN page is newly added each time, in addition, the coupling is serious, the page calling is complicated, and the performance of a client is influenced.

Therefore, the conventional RN page management mode cannot realize effective management of multiple RN pages.

It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the invention and therefore may include information that does not constitute prior art that is already known to a person of ordinary skill in the art.

Disclosure of Invention

In view of this, the present invention provides a page management method, system, electronic device and storage medium, which configure the logic of each RN page in different policy classes based on at least a policy mode, so that each RN page has an independent logic cohesive in its policy class and is not coupled with other service logics, thereby implementing the logic independence of each RN page, not only avoiding code redundancy, improving development efficiency, but also facilitating subsequent maintenance and expansion, and reducing maintenance cost; in addition, when the RN page is loaded by the client, the client does not need to pay attention to specific page logic, the corresponding strategy class can be called by transferring call parameters, and the target RN page can be efficiently loaded and generated based on the called strategy class and the view component of the multi-page structure, so that the performance experience of the client is improved, and the effective management of the multi-RN page is realized.

According to one aspect of the invention, a page management method is provided, which is applied to a multi-page structure developed based on a cross-platform mobile application development framework (RN), and comprises the following steps: responding to a page calling request, analyzing a calling parameter of the page calling request, and acquiring a target specific strategy class corresponding to the calling parameter; the multi-page structure is configured with a plurality of specific strategy classes based on a strategy mode, and page logic corresponding to the RN page is configured in each specific strategy class; calling the target specific strategy class and a view component of the multi-page structure, wherein the view component is configured with a display style of the multi-page structure; and loading and generating a target RN page according to the page logic and the display style configured in the target specific strategy class.

In some embodiments, the multi-page structure is further configured with a context component that depends on the view component and each of the particular policy classes; and configuring a mapping relation between the calling parameters and the specific strategy classes in the context component based on the factory mode.

In some embodiments, the page logic configured in the target specific policy class includes: and the target RN page comprises loading logic, callback logic, removing logic and refreshing logic.

In some embodiments, the multi-page structure is further configured with abstract policy classes, each of the concrete policy classes inheriting the abstract policy class.

In some embodiments, the page management method further includes: responding to a policy adding request, configuring an added concrete policy class in the multi-page structure, enabling the added concrete policy class to inherit the abstract policy class of the multi-page structure, and enabling a context component of the multi-page structure to depend on the added concrete policy class.

In some embodiments, the page management method further includes: and responding to a policy modification request, and modifying the corresponding specific policy class in the multi-page structure.

In some embodiments, the view component performs RN page layout in a frame layout manner.

According to an aspect of the present invention, there is provided a page management system applied to a multi-page structure developed based on a cross-platform mobile application development framework RN, the page management system including: the analysis module is used for responding to a page calling request, analyzing a calling parameter of the page calling request and obtaining a target specific strategy class corresponding to the calling parameter; the multi-page structure is configured with a plurality of specific strategy classes based on a strategy mode, and page logic corresponding to the RN page is configured in each specific strategy class; the calling module is used for calling the target specific strategy class and a view component of the multi-page structure, and the view component is configured with a display style of the multi-page structure; and the loading module is used for loading and generating a target RN page according to the page logic and the display style configured in the target specific strategy class.

According to an aspect of the present invention, there is provided an electronic apparatus including: a processor; a memory having executable instructions stored therein; wherein the executable instructions, when executed by the processor, implement the page management method as in any of the embodiments described above.

According to an aspect of the present invention, there is provided a computer-readable storage medium storing a program which, when executed by a processor, implements a page management method as described in any of the embodiments above.

Compared with the prior art, the invention has the beneficial effects that:

according to the page management scheme, the page logic of each RN page is configured in different specific strategy classes at least based on the strategy mode, so that each RN page has independent logic gathered in the specific strategy class of the RN page and is not coupled with other business logics, the logic independence of each RN page is realized, code redundancy is avoided, the basic logic is not required to be written for each RN page independently, the development efficiency is improved, the subsequent maintenance and expansion are facilitated, and only a single RN page needs to be modified when the RN page is modified/newly added, so that the maintenance cost is reduced; in addition, when the RN page is loaded by the client, the client can call the corresponding target specific strategy class without paying attention to specific page logic and transmitting a call parameter, so that simple and convenient page call is realized; based on the called target specific strategy class and the view component with the multi-page structure, the target RN page can be efficiently loaded and generated, the performance experience of the client is improved, and the effective management of the multi-RN page is realized.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention. It is obvious that the drawings described below are only some embodiments of the invention, and that for a person skilled in the art, other drawings can be derived from them without inventive effort.

FIG. 1 is a diagram illustrating steps of a page management method according to an embodiment of the present invention;

FIG. 2 illustrates a class diagram for a multi-page structure in an embodiment of the invention;

FIG. 3 is a block diagram of a page management system according to an embodiment of the invention;

fig. 4 is a schematic structural diagram of an electronic device in an embodiment of the invention.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art.

The drawings are merely schematic illustrations of the invention and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.

In addition, the flow shown in the drawings is only an exemplary illustration, and not necessarily includes all the steps. For example, some steps may be divided, some steps may be combined or partially combined, and the actual execution sequence may be changed according to the actual situation. It should be noted that features of the embodiments of the invention and of the different embodiments may be combined with each other without conflict.

The page management method provided by the embodiment of the invention is applied to a multi-page structure developed based on a cross-platform mobile application development framework RN, and is used for managing multiple RN pages of an Android mobile platform. In a scene of multiple RN pages, for example, a live broadcast scene of an e-commerce platform, there are cases where multiple RN pages are nested in association with each other, such as a live broadcast room, a live broadcast review area, a live broadcast gift list, and a live broadcast shopping card. In the current RN page management mode, all RN pages are managed through one Manager object, and all page logics are mixed and written together, so that the logic independence of the RN pages is not ensured, and the effective management of the RN pages is not realized. The page management method provided by the embodiment of the invention realizes effective management of multiple RN pages by ensuring the logic independence of different RN pages and uniformly managing the loading and other behaviors of different RN pages aiming at the conditions of multiple RN pages such as a live broadcast scene.

Hereinafter, the page management method according to the embodiment of the present invention will be described by taking multi-RN page management in a live broadcast scenario as an example, and in the following embodiment, a called RN page specifically refers to a full screen View (View) nested in a live broadcast page.

Fig. 1 shows the main steps of a page management method, fig. 2 shows a class diagram of a multi-page structure, and in combination with fig. 1 and fig. 2, in an embodiment, the page management method includes:

step S110, responding to the page calling request, analyzing the calling parameter of the page calling request, and obtaining a target specific strategy class corresponding to the calling parameter; the multi-page structure is configured with a plurality of specific strategy classes based on the strategy mode, and page logic corresponding to the RN page is configured in each specific strategy class.

The policy (Strategy) mode is suitable for managing a group of algorithms of the same type, the algorithms are packaged in different classes, and the corresponding algorithms are called according to execution scenes. Specifically, in the policy mode, some independent specific policy classes are defined to encapsulate page logics of different RN pages, where the page logic of each RN page corresponds to one specific policy class, that is, each specific policy class encapsulates the page logic of one RN page. In order to ensure the consistency of the concrete strategy classes, an abstract strategy class is also used for defining the basic logic of each RN page.

The page logic configured in the target specific policy class comprises: load logic (e.g., create RN link), callback logic (i.e., load success/failure callback), remove logic, and flush logic for the target RN page. The conventional RN refreshing logic and loading logic are written in different methods, and are easy to miss during modification.

In fig. 2, "Live Shop Card Strategy" (specific policy class of Live shopping Card) 210 is illustrated, and the multi-page structure may be configured with other specific policy classes, which is not limited to that shown in fig. 2. In the specific policy class 210 of the live shopping card, the page logic of the RN page corresponding to the live shopping card is configured, including an attribute "live Goods" (live Goods) and a type "String" (character String); the method "get Tag" (get Tag), return value type "String"; the method "get Bundle" (gets Bundle, an executable file), returns a value type of "Bundle"; method "get URL" (get URL, Uniform Resource Locator), return value type is "String"; method "get Id" (get Id, Identity document, unique identification), return value type "Int" (integer); the method "notify Update", no value ("void") is returned; the method "view Display Lister" (View Display listening), returns no value; method "on Error" (Error handling), no value is returned.

The multi-page structure is also configured with abstract policy classes, and each concrete policy class inherits the abstract policy class. With continued reference to FIG. 2, a "Live Base RN Strategy" (a policy Base class, i.e., abstract policy class, of the Live RN) 220 is illustrated. In the abstract policy class 220, the basic logic of the RN page in the Live scene is configured, including an attribute "Room Param" (Room parameter), and the type is "I Live Room Base Data" (Live Room basic Data); the method is inherited by the specific policy class 210 of the live shopping card, and the description is not repeated.

And page logic of each RN page is configured in different specific strategy classes through a strategy mode, so that each RN page has independent logic gathered in the specific strategy class of the RN page and is not coupled with other service logic, the logic independence of each RN page is realized, and the basic logic of the RN page is multiplexed, thereby simplifying page development codes and improving the page development efficiency.

Step S120, calling a target specific strategy class and a view component of the multi-page structure, and configuring a display style of the multi-page structure in the view component.

The target specific policy class is a specific policy class corresponding to a call parameter of the page call request, in which a page logic of a target page to be generated is configured. The multi-page structure is also provided with a context component, and the context component depends on the view component and each specific strategy class; and in the context component, based on the factory mode, a mapping relation between the calling parameter and the specific strategy class is configured.

In the context component, the use logic, such as call logic, for configuring the algorithm, and the specific implementation of the algorithm is configured in a specific policy class.

Referring to FIG. 2, a "Live RN Linear Context" (policy Context of Live RN, i.e. Context component) 230 is illustrated, the Context component 230 relying on the specific policy class 210 of the Live shopping card and a "Live RN View" (Live RN View, i.e. View component) 240. The context component 230 is configured to respond to a page call request of the client, and the client needs to call which policy, and only needs to communicate with the context component 230, and does not need to communicate with a specific implementation, so that decoupling between the client and the specific implementation can be achieved. In the context component 230, based on the factory model, an attribute "RN Map" (RN mapping relationship) and methods "show Shop Card" (display shopping Card) and "hide Shop Card" are configured.

In the view component 240, the attributes "room Context", "RN Fragment" (RN Fragment) and "strategy", and the methods "show" (loaded) and "remove" (removed) are configured. The view component 240 may perform RN page Layout in a Frame Layout (Frame Layout) manner 250.

The context component 230 can determine a target specific policy class corresponding to the invocation parameters of the page invocation request based on the Map and invoke the target specific policy class and the view component 240.

And step S130, loading and generating a target RN page according to the page logic and the display style configured in the target specific strategy class.

The RN loading process is optimized through the strategy mode and the factory mode, the loading logic of the RN page is guaranteed to be complete through the strategy mode, a calling party (namely a client) does not need to pay attention to specific page logic when loading the RN page through the factory mode, the corresponding target specific strategy class can be called only by inputting calling parameters (for example, a shopping card button on a live broadcast page is triggered), and the related logic of the RN page can be realized through simple and convenient page calling. Based on the called target specific strategy class and the view component, the target RN page can be efficiently loaded and generated on the client, the RN page loading process of the client is optimized, and the loading performance and experience of the client are improved.

In one embodiment, the page management method further comprises: responding to a policy adding request, configuring a newly added concrete policy class in the multi-page structure, enabling the newly added concrete policy class to inherit an abstract policy class of the multi-page structure, and enabling a context component of the multi-page structure to depend on the newly added concrete policy class; and responding to the strategy modification request, and modifying the corresponding specific strategy class in the multi-page structure.

Through the strategy mode, the logic of the RN page is more cohesive, the maintenance and the expansion are more convenient, the newly added/modified page logic is configured in the strategy class of the page logic, the logic of other RN pages is not coupled, and the logic of other pages cannot be influenced by changing one RN page.

In summary, in the above-mentioned page management scheme, based on the policy mode and the factory mode, the page logic of each RN page is configured in each specific policy class, so that each RN page has independent logic cohesive in its specific policy class, and is not coupled with other business logic, thereby realizing logic independence of each RN page, not only avoiding code redundancy, but also realizing multiplexing of the basic logic without independently writing a basic logic for each RN page, thereby improving development efficiency, facilitating subsequent maintenance and expansion, and modifying/newly adding RN pages only by aiming at a single RN page, thereby reducing maintenance cost; in addition, when the RN page is loaded by the client, the client can call the corresponding target specific strategy class without paying attention to specific page logic and transmitting a call parameter, so that simple and convenient page call is realized; based on the called target specific strategy class and the view component with the multi-page structure, the target RN page can be efficiently loaded and generated, the loading performance and other management experiences of the client are improved, and the effective management of the multi-RN page is realized.

The embodiment of the invention also provides a page management system which can be used for realizing the page management method described in any embodiment. The features and principles of the page management method described in any of the above embodiments may be applied to the following page management system embodiments. In the following page management system embodiments, the features and principles already set forth with respect to multi-RN page management will not be repeated.

FIG. 3 illustrates the main modules of the page management system, and referring to FIG. 3, in one embodiment, the page management system 300 is applied to a multi-page structure developed based on a cross-platform mobile application development framework RN, and includes: the analysis module 310 is configured to, in response to the page call request, analyze a call parameter of the page call request to obtain a target specific policy class corresponding to the call parameter; the multi-page structure is configured with a plurality of specific strategy classes based on a strategy mode, and page logic corresponding to the RN page is configured in each specific strategy class; the calling module 320 is used for calling a target specific strategy class and a view component of a multi-page structure, and the view component is configured with a display style of the multi-page structure; and the loading module 330 is configured to load and generate a target RN page according to the page logic and the display style configured in the target specific policy class.

Further, the page management system 300 may further include modules for implementing other process steps of the above-mentioned embodiments of the page management method, the specific principle of each module may refer to the description of the above-mentioned embodiments of the page management method, and the class diagram of the page management system 300 may specifically refer to fig. 2, and will not be described again here.

As described above, the page management system of the present invention can configure the page logic of each RN page in each specific policy class based on the policy mode and the factory mode, so that each RN page has independent logic cohesive in its specific policy class, and is not coupled with other business logic, thereby realizing the logic independence of each RN page, not only avoiding code redundancy, but also realizing multiplexing of the basic logic without writing the basic logic for each RN page separately, thereby improving development efficiency, facilitating subsequent maintenance and expansion, and modifying/newly adding RN pages by only modifying a single RN page, thereby reducing maintenance cost; in addition, when the RN page is loaded by the client, the client can call the corresponding target specific strategy class without paying attention to specific page logic and transmitting a call parameter, so that simple and convenient page call is realized; based on the called target specific strategy class and the view component with the multi-page structure, the target RN page can be efficiently loaded and generated, the loading performance and other management experiences of the client side are improved, and the effective management of the multi-RN page is realized.

The embodiment of the present invention further provides an electronic device, which includes a processor and a memory, where the memory stores executable instructions, and when the executable instructions are executed by the processor, the page management method described in any of the above embodiments is implemented.

The electronic equipment can logically configure the page of each RN page in each specific strategy class based on the strategy mode and the factory mode, so that each RN page has independent logic gathered in the specific strategy class of the RN page and is not logically coupled with other services, the logic independence of each RN page is realized, code redundancy is avoided, basic logic does not need to be independently written for each RN page, the multiplexing of the basic logic is realized, the development efficiency is improved, the subsequent maintenance and expansion are facilitated, and only a single RN page needs to be modified when the RN page is modified/newly added, so that the maintenance cost is reduced; in addition, when the RN page is loaded, the client can call the corresponding target specific strategy class by transmitting a call parameter without paying attention to specific page logic, so that simple and convenient page call is realized; based on the called target specific strategy class and the view component with the multi-page structure, the target RN page can be efficiently loaded and generated, the loading performance and other management experiences of the client are improved, and the effective management of the multi-RN page is realized.

Fig. 4 is a schematic structural diagram of an electronic device in an embodiment of the present invention, and it should be understood that fig. 4 only schematically illustrates various modules, and these modules may be virtual software modules or actual hardware modules, and the combination, the splitting, and the addition of the remaining modules of these modules are within the scope of the present invention.

As shown in fig. 4, electronic device 400 is embodied in the form of a general purpose computing device. The components of electronic device 400 include, but are not limited to: at least one processing unit 410, at least one memory unit 420, a bus 430 connecting different platform components (including memory unit 420 and processing unit 410), a display unit 440, and the like.

The storage unit 420 stores program code that can be executed by the processing unit 410 such that the processing unit 410 performs the steps of the page management method described in any of the embodiments above. For example, processing unit 410 may perform the steps shown in fig. 1.

The storage unit 420 may include readable media in the form of volatile storage units, such as a random access memory unit (RAM)4201 and/or a cache memory unit 4202, and may further include a read only memory unit (ROM) 4203.

The storage unit 420 may also include a program/utility 4204 having one or more program modules 4205, such program modules 4205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.

Bus 430 may be any bus representing one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

The electronic device 400 may also communicate with one or more external devices, which may be one or more of a keyboard, a pointing device, a bluetooth device, etc. These external devices enable a user to interactively communicate with the electronic device 400. Electronic device 400 can also communicate with one or more other computing devices, including routers, modems. Such communication may occur via input/output (I/O) interfaces 450. Also, the electronic device 400 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via the network adapter 460. The network adapter 460 may communicate with other modules of the electronic device 400 via the bus 430. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with electronic device 400, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage platforms, to name a few.

The embodiment of the present invention further provides a computer-readable storage medium, which is used for storing a program, and when the program is executed, the page management method described in any of the above embodiments is implemented. In some possible embodiments, the aspects of the present invention may also be implemented in the form of a program product, which includes program code for causing a terminal device to perform the page management method described in any of the above embodiments, when the program product is run on the terminal device.

When the storage medium is executed by the processor, the page logic of each RN page can be configured in each specific strategy class based on the strategy mode and the factory mode, so that each RN page has independent logic gathered in the specific strategy class of the RN page and is not coupled with other business logic, the logic independence of each RN page is realized, code redundancy is avoided, basic logic does not need to be written for each RN page independently, the multiplexing of the basic logic is realized, the development efficiency is improved, the subsequent maintenance and expansion are facilitated, and only a single RN page needs to be modified when the RN page is modified/newly added, so that the maintenance cost is reduced; in addition, when the RN page is loaded by the client, the client can call the corresponding target specific strategy class without paying attention to specific page logic and transmitting a call parameter, so that simple and convenient page call is realized; based on the called target specific strategy class and the view component with the multi-page structure, the target RN page can be efficiently loaded and generated, the loading performance and other management experiences of the client are improved, and the effective management of the multi-RN page is realized.

The storage medium may employ a portable compact disc read only memory (CD-ROM) and include program codes, and may be run on a terminal device, such as a personal computer. However, the storage medium of the present invention is not limited thereto, and may be any tangible medium that contains or stores a program, which can be used by or in connection with an instruction execution system, apparatus, or device.

A storage medium may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of readable storage media include, but are not limited to: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

A readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a readable signal medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In situations involving remote computing devices, the remote computing devices may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to external computing devices, such as through the internet using an internet service provider.

The foregoing is a further detailed description of the invention in connection with specific preferred embodiments and it is not intended to limit the invention to the specific embodiments described. For those skilled in the art to which the invention pertains, several simple deductions or substitutions can be made without departing from the spirit of the invention, and all shall be considered as belonging to the protection scope of the invention.

Claims (10)

1. A page management method is applied to a multi-page structure developed based on a cross-platform mobile application development framework (RN), and is characterized by comprising the following steps:

responding to a page calling request, analyzing a calling parameter of the page calling request, and acquiring a target specific strategy class corresponding to the calling parameter; the multi-page structure is configured with a plurality of specific strategy classes based on a strategy mode, and page logic corresponding to the RN page is configured in each specific strategy class;

calling the target specific strategy class and a view component of the multi-page structure, wherein the view component is configured with a display style of the multi-page structure;

and loading and generating a target RN page according to the page logic and the display style configured in the target specific strategy class.

2. The page management method of claim 1, wherein said multi-page structure is further configured with a context component, said context component depending on said view component and each of said specific policy classes;

and configuring a mapping relation between the calling parameters and the specific strategy classes in the context component based on the factory mode.

3. The page management method of claim 1, wherein the page logic configured in the target specific policy class comprises:

and the target RN page comprises loading logic, callback logic, removing logic and refreshing logic.

4. The method of page management according to claim 1, wherein said multi-page structure is further configured with abstract policy classes, each of said concrete policy classes inheriting said abstract policy class.

5. The page management method of claim 1, further comprising:

responding to a policy adding request, configuring an added concrete policy class in the multi-page structure, enabling the added concrete policy class to inherit an abstract policy class of the multi-page structure, and enabling a context component of the multi-page structure to depend on the added concrete policy class.

6. The page management method of claim 1, further comprising:

and responding to a policy modification request, and modifying the corresponding specific policy class in the multi-page structure.

7. The page management method of claim 1, wherein the view component performs RN page layout in a frame layout manner.

8. A page management system is applied to a multi-page structure developed based on a cross-platform mobile application development framework (RN), and is characterized by comprising:

the analysis module is used for responding to a page calling request, analyzing a calling parameter of the page calling request and obtaining a target specific strategy class corresponding to the calling parameter; the multi-page structure is configured with a plurality of specific strategy classes based on a strategy mode, and page logic corresponding to the RN page is configured in each specific strategy class;

the calling module is used for calling the target specific strategy class and a view component of the multi-page structure, and the view component is configured with a display style of the multi-page structure;

and the loading module is used for loading and generating a target RN page according to the page logic and the display style configured in the target specific strategy class.

9. An electronic device, comprising:

a processor;

a memory having executable instructions stored therein;

wherein the executable instructions, when executed by the processor, implement the page management method of any of claims 1-7.

10. A computer-readable storage medium storing a program, wherein the program, when executed by a processor, implements the page management method according to any one of claims 1 to 7.

Images