WO2018205557A1

WO2018205557A1 - Page logic control method and apparatus, computer apparatus and readable storage medium

Info

Publication number: WO2018205557A1
Application number: PCT/CN2017/112953
Authority: WO
Inventors: 张磊; 张文明; 陈少杰
Original assignee: 武汉斗鱼网络科技有限公司
Priority date: 2017-05-09
Filing date: 2017-11-24
Publication date: 2018-11-15
Also published as: CN107145357B; CN107145357A

Abstract

A page logic control method and apparatus (200), a computer apparatus and a readable storage medium, wherein the page logic control method is applied to a software development model, and the software development model comprises a data layer, a control layer and a view layer. The method comprises: a data layer acquiring data (S210); the data layer converting the acquired data into data of a pre-set format through an interface protocol between the data layer and a control layer, and then transmitting same to the control layer (S220); the control layer parsing the data of the pre-set format to obtain presentation data corresponding to the data of the pre-set format (S230); the control layer, based on the presentation data, searching for, from at least one interface port of the control layer and the view layer, an interface port for displaying the presentation data, and transmitting the corresponding presentation data to the view layer through the found interface port (S240); and the view layer, according to the found interface port, performing page presentation on the presentation data (S250). The page logic control method and apparatus (200), the computer apparatus and the readable storage medium can effectively reduce the coupling relationship between the view layer and the control layer, greatly improving the scalability and maintainability of the software.

Description

Page logic control method, device, computer device and readable storage medium

The present application claims the priority of the Chinese Patent Application No. PCT Application No. PCT Application No.

Technical field

The present invention relates to the field of computer technologies, and in particular, to a page logic control method, apparatus, computer device, and readable storage medium.

Background technique

In the current software development model, the control layer closely links the view layer to the model layer. This contact is established using a direct reference relationship, which is a strong reference relationship. The existence of such a strong reference relationship will increase the relationship between the control layer and the view layer and the model layer as the complexity of the business logic increases, and the software cannot continue to be maintained. In addition, under such a strong coupling relationship, it is extremely difficult to implement software expansion and maintenance.

Summary of the invention

In order to overcome the above-mentioned deficiencies in the prior art, an object of the present invention is to provide a page logic control method and apparatus, which can effectively reduce the coupling relationship between the view layer and the control layer, and greatly improve the scalability and software of the software. Maintenance.

In order to achieve the above object, the technical solution adopted by the embodiment of the present invention is as follows:

A preferred embodiment of the present invention provides a page logic control method applied to a software development model including a data layer, a control layer, and a view layer. The method includes:

The data layer acquires data;

Transmitting, by the data layer, the acquired data to the preset layer by using an interface protocol between the data layer and the control layer, and transmitting the data to the control layer;

The control layer parses the preset format data to obtain presentation data corresponding to the preset format data;

The control layer searches for an interface interface for displaying the presentation data from the control layer and at least one interface interface of the view layer based on the presentation data, and transmits corresponding presentation data through the found interface interface. To the view layer. Wherein each interface interface corresponds to a type of presentation logic;

The view layer performs page rendering on the presentation data according to the found interface interface.

In a preferred embodiment of the present invention, the data layer converts the acquired data into the preset format data through an interface protocol between the data layer and the control layer, and then transmits the data to the control layer, including :

Obtaining a preset interface protocol between the data layer and the control layer. The preset interface protocol includes a format conversion function;

Converting the format of the acquired data by using a format conversion function in the preset interface protocol;

After the format conversion of the acquired data is successful, a string of a preset format is generated.

In a preferred embodiment of the present invention, the method further includes:

Creating a preset interface protocol between the data layer and the control layer;

The step of creating a preset interface protocol between the data layer and the control layer includes:

The preset interface protocol is created in response to a request to create a preset interface protocol between the data layer and the control layer. The preset interface protocol is used to implement communication between the data layer and the control layer.

In a preferred embodiment of the present invention, the control layer searches for the interface interface for displaying the presentation data from the control layer and the at least one interface interface of the view layer based on the presentation data, including :

Obtaining at least one rendering logic that the rendering data needs to be presented;

An interface interface of the view layer corresponding to each rendering logic is obtained according to each rendering logic.

In a preferred embodiment of the present invention, the step of the view layer performing page presentation on the presentation data according to the found interface interface includes:

Packaging the interface interface by a packaging layer between the control layer and each interface of the view layer, wherein the packaged interface interface forms a weak reference layer to enable a computer device running the software development model Leaking the leaked memory when there is a memory leak in the view layer;

The rendered data is page rendered based on the wrapped interface interface.

In a preferred embodiment of the present invention, the method further includes: before packaging the interface interface by a packaging layer between the control layer and each interface of the view layer, the method further includes:

In response to a request to set a wrapper layer between the control layer and an interface interface of the view layer, a wrapper layer is created between the control layer and an interface interface of the view layer in accordance with the request.

Another preferred embodiment of the present invention further provides a page logic control apparatus, which is applied to a software development model, and the software development model includes a data layer, a control layer, and a view layer. The device includes:

An obtaining module, configured to acquire data by the data layer;

a conversion module, configured to convert, by the data layer, the acquired data into a preset format data by using an interface protocol between the data layer and the control layer, and then transmitting the data to the control layer;

a parsing module, configured to parse the preset format data by the control layer, to obtain presentation data corresponding to the preset format data;

a search module, configured by the control layer to search for an interface interface for displaying the presentation data from the control layer and at least one interface interface of the view layer based on the presentation data, and by using the found interface interface Corresponding presentation data is transmitted to the view layer. Wherein each interface interface corresponds to a type of presentation logic;

And a rendering module, configured by the view layer to perform page rendering on the presentation data according to the found interface interface.

In a preferred embodiment of the present invention, the conversion module includes:

a protocol acquisition sub-module, configured to acquire a preset interface protocol between the data layer and the control layer, where the preset interface protocol includes a format conversion function;

a conversion submodule, configured to convert a format of the acquired data by using a format conversion function in the preset interface protocol;

And generating a submodule, configured to generate a string of a preset format after the format conversion of the acquired data is successful.

In a preferred embodiment of the present invention, the device further includes:

Creating a module, configured to create a preset interface protocol between the data layer and the control layer;

The manner of creating a preset interface protocol between the data layer and the control layer includes:

Creating the preset interface protocol in response to a request to create a preset interface protocol between the data layer and the control layer, wherein the preset interface protocol is used to implement the data layer and the control layer Communication between.

In a preferred embodiment of the present invention, the searching module includes:

a logic acquisition submodule, configured to acquire at least one rendering logic that the rendering data needs to be presented;

The interface acquisition sub-module is configured to acquire an interface interface of a view layer corresponding to each presentation logic according to each rendering logic.

In a preferred embodiment of the present invention, the manner in which the presentation module is configured to display the presentation data by the view layer according to the found interface interface includes:

The rendered data is page rendered based on the wrapped interface interface.

In a preferred embodiment of the present invention, the creating module is further configured to respond to the request at the control layer according to the request in response to a request to set a wrapper layer between an interface interface of the control layer and the view layer. A wrapper layer is created between the interface interfaces of the view layer.

Another preferred embodiment of the present invention further provides a computer device comprising a processor and a non-volatile memory storing a plurality of computer instructions, the computer device performing the above implementation when the computer instructions are executed by the processor The page logic control method described in the example.

Other preferred embodiments of the present invention further provide a readable storage medium, the readable storage medium comprising a computer program, the computer program controlling the electronic device where the readable storage medium is located to perform the operations described in the above embodiments Page logic control method.

Compared with the prior art, the present invention has the following beneficial effects:

The page logic control method, device, computer device and readable storage medium provided by the embodiment of the present invention obtain data through a data layer; the data layer converts the acquired data into an interface through an interface protocol between the data layer and the control layer. The format data is transmitted to the control layer; the control layer parses the preset format data to obtain presentation data corresponding to the preset format data; and the control layer searches for at least one interface interface of the control layer and the view layer based on the presentation data for searching The interface interface for presenting the data is displayed, and the corresponding presentation data is transmitted to the view layer through the found interface interface; the view layer performs page presentation on the presentation data according to the found interface interface. The above design can effectively reduce the coupling relationship between the view layer and the control layer, and greatly improve the scalability and maintainability of the software.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the embodiments will be briefly described below. It should be understood that the following drawings show only certain embodiments of the present invention, and therefore It should be seen as a limitation on the scope, and those skilled in the art can obtain other related drawings according to these drawings without any creative work.

1 is a block diagram of a computer device according to a preferred embodiment of the present invention;

2 is a schematic flowchart of a page logic control method according to a preferred embodiment of the present invention;

3 is another schematic flowchart of a page logic control method according to a preferred embodiment of the present invention;

4 is a schematic flow chart of each sub-step included in step S220 shown in FIG. 2;

FIG. 5 is a schematic flow chart of each sub-step included in step S240 shown in FIG. 2;

FIG. 6 is a schematic flow chart of each sub-step included in step S250 shown in FIG. 2;

FIG. 7 is a functional block diagram of a page logic control apparatus according to another preferred embodiment of the present invention; FIG.

FIG. 8 is another functional block diagram of a page logic control apparatus according to another embodiment of the present invention; FIG.

9 is a functional block diagram of each submodule included in the conversion module shown in FIG. 7;

FIG. 10 is a functional block diagram of each submodule included in the lookup module shown in FIG. 7.

Icon: 100-computer device; 110-memory; 120-processor; 130-communication unit; 140-storage controller; 150-display unit; 200-page logic control device; 209-creation module; 210-acquisition module; - conversion module; 221 - protocol acquisition submodule; 222 - conversion submodule; 223 - generation submodule; 230 - parsing module; 240 - lookup module; 241 - logical acquisition submodule; 242 - interface acquisition submodule; 250 - rendering Module.

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are a part of the embodiments of the present invention, but not all embodiments. The components of the embodiments of the invention, which are generally described and illustrated in the figures herein, may be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the invention in the claims All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

It should be noted that similar reference numerals and letters indicate similar items in the following figures, so once an item is in one The definitions in the drawings are not required to be further defined and explained in the subsequent figures.

Some embodiments of the present invention are described in detail below with reference to the accompanying drawings. The features of the embodiments and examples described below can be combined with each other without conflict.

Please refer to FIG. 1. FIG. 1 is a block diagram of a computer device 100 according to a preferred embodiment of the present invention. In the embodiment of the present invention, the computer device 100 may be an electronic device for running a software development model. For example, the computer device 100 may be, but not limited to, a personal computer (PC), a notebook computer, a tablet computer, a personal digital assistant (PDA), and a mobile Internet device (MID). Wait. The operating system of the computer device 100 may be, but not limited to, a Windows system, a Linux system, an OSX system, and the like. Preferably, in this embodiment, the operating system of the computer device 100 may be a Windows system.

As shown in FIG. 1, the computer device 100 can include a memory 110, a processor 120, a communication unit 130, a memory controller 140, and a display unit 150. The memory 110, the processor 120, the communication unit 130, the storage controller 140, and the display unit 150 are electrically connected directly or indirectly to each other to implement data transmission or interaction. For example, the components can be electrically connected to one another via one or more communication buses or signal lines. A page logic control device 200 is stored in the memory 110, and the page logic control device 200 includes at least one software function module that can be stored in the memory 110 in the form of software or firmware, and the processor 120 runs the storage. The software program and the module in the memory 110, such as the page logic control device 200 in the embodiment of the present invention, thereby performing various functional applications and data processing, that is, implementing the page logic control method in the embodiment of the present invention.

The memory 110 may include a high speed random access memory, and may also include a non-volatile memory such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory. In some examples, memory 110 can further include memory remotely located relative to processor 120, which can be connected to computer device 100 over a network. Examples of such networks may include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof. Access to the memory 110 by the processor 120 and other possible components can be performed under the control of the memory controller 140. Optionally, the communication unit 130 couples various input/output devices to the processor 120 and the memory 110. The software programs and modules within the memory 110 may also include an operating system, which may include various functions for managing system tasks. Software components and/or drivers (such as memory management, storage device control, power management, etc.) that communicate with various hardware or software components to provide an operating environment for other software components.

The processor 120 can be an integrated circuit chip with signal processing capabilities. The processor 120 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), and the like. It can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out. A general purpose processor can be The microprocessor or the processor 120 can also be any conventional processor or the like.

The communication unit 130 can be configured to receive and transmit electromagnetic waves, and realize mutual conversion between electromagnetic waves and electrical signals, thereby communicating with the communication network or the computer device 100. The communication unit 130 can communicate with various networks, such as the Internet, an intranet, a wireless network, or communicate with the computer device 100 over a wireless network. The wireless network described above may include a cellular telephone network, a wireless local area network, or a metropolitan area network. The above wireless network can use various communication standards, protocols and technologies, including but not limited to global mobile communication systems, enhanced mobile communication technologies, wideband code division multiple access technology, code division multiple access technology, time division multiple access technology, Bluetooth , wireless fidelity technology, VoIP, global microwave access, other protocols for mail, instant messaging and short messages, and any other suitable communication protocols, even those that are not currently being developed.

The display unit 150 can be used to provide an interactive interface (such as a user interface) or to display image data. In this embodiment, the display unit 150 can be a liquid crystal display or a touch display. For a touch display, it can be a capacitive touch screen or a resistive touch screen that supports single-point and multi-touch operations. Supporting single-point and multi-touch operations means that the touch display can sense a touch operation generated from one or more positions on the touch display, and the touch operation is performed by the processor 120. Calculation and processing.

In this embodiment, the computer device 100 may include a software development model, and the software development model may include a data layer, a control layer, and a view layer. The data layer is used for acquiring data logic, and the control layer is configured to acquire data of the data layer and perform data conversion and data transportation on the acquired data, where the view layer is used according to the The data transmitted by the control layer is displayed in a software view.

The technical solution of the embodiment is described in detail below by using the software development model as an example. Alternatively, the software development model may adopt an MVC development model.

Please refer to FIG. 2. FIG. 2 is a schematic flowchart diagram of a page logic control method according to a preferred embodiment of the present invention. The page logic control method is applied to the software development model. It should be understood that the method provided by the embodiments of the present invention is not limited to the specific order described in FIG. 2 and the following. The specific process of the method is as follows:

In step S210, the data layer acquires data.

In this embodiment, the manner in which the data layer acquires data is not specifically limited. For example, the data layer may acquire data from a certain database, or obtain data from a certain network layer, or Get data in a file, etc. Regardless of the manner in which the data is acquired, all acquired data is stored in the data layer.

In the traditional MVC development model, the data layer and the control layer are directly coupled, that is, a "strong reference relationship." Simply put, if an object has the "strong reference relationship", it can be understood that the object is indispensable, then the object will not be recovered by the computer device 100, precisely because this layer is "strong" a reference relationship, if the data source acquired by the data layer changes, the control layer cannot obtain the data layer to transmit The changed data source results in a low scalability and maintainability of the software development model. In order to solve the above problem, referring to FIG. 3, the method may further include:

Step S209, creating a preset interface protocol between the data layer and the control layer.

Specifically, in this embodiment, a preset interface protocol for accessing between the data layer and the control layer may be created, where the preset interface protocol may be created by: the computer device Responding to a request to create a preset interface protocol between the data layer and the control layer, creating a preset interface protocol for implementing communication between the data layer and the control layer, the preset interface A protocol conversion function for converting data acquired by the data layer is included in the protocol.

Referring to FIG. 2 again, after the preset interface protocol is created, referring to step S220, the data layer converts the acquired data into a preset format data by using an interface protocol between the data layer and the control layer, and then transmits the data. Give the control layer.

Specifically, as an implementation manner, referring to FIG. 4, in this embodiment, the step S220 may include the following sub-steps:

Sub-step S221, acquiring a preset interface protocol between the data layer and the control layer.

Sub-step S222, converting the format of the acquired data by using a format conversion function in the preset interface protocol.

In this embodiment, the format conversion function may adopt a convert function to implement conversion of the format of the acquired data. Specifically, the convert function may convert data acquired by the data layer into data in a JSON format in the preset interface protocol, that is, regardless of what type of data the data layer acquires, acquired. The data is converted into data in JSON format, so that any data acquired by the data layer is a JSON format data for the control layer.

Sub-step S223, after the format conversion of the acquired data is successful, generating a character string of a preset format.

In this embodiment, after the format conversion of the acquired data is successful, a JSON string may be generated, and the generated JSON string is transmitted to the control layer.

Through the above design, the data layer and the control layer are coupled by a preset interface protocol. The weak coupling relationship between the data layer and the control layer can be achieved by coupling the relationship between the data layer and the control layer through a fixed preset interface protocol. If you need to replace the data of the data layer, you only need to redefine a set of data interface protocols, and then re-acquire the data and convert it into the corresponding JSON format data. Thus, the data received by the control layer is still in JSON format. Data, so the control layer does not have any impact on the replacement of the data source, thus achieving a weak coupling relationship between the data layer and the control layer, and the data source can be easily extended later. deal with.

Referring to FIG. 2 again, in step S230, the control layer parses the preset format data, and obtains the The presentation data corresponding to the preset format data.

In this embodiment, the control layer may parse the acquired data in the JSON format by using an existing JSON parsing tool, so as to obtain the rendering data corresponding to the data in the JSON format.

Step S240, the control layer searches for an interface interface for displaying the presentation data from at least one interface interface of the control layer and the view layer based on the presentation data, and displays corresponding presentation data through the found interface interface. Transfer to the view layer.

As an implementation manner, referring to FIG. 5, the step S240 may include the following sub-steps:

Sub-step S241, acquiring at least one rendering logic that the presentation data needs to be presented.

Sub-step S242, acquiring an interface interface of the view layer corresponding to each rendering logic according to each rendering logic.

Since the variations of the software view are various, the presentation logic for different view layers is also diverse. In this embodiment, each of the interface interfaces corresponds to a type of presentation logic. Briefly, the same category of rendering logic can be rendered through the same interface interface, while different rendering logic requires different interface interfaces to implement the rendering of the respective view functions.

The interface interface is designed by using an interface function, and the interface function performs design on the interface interface according to the interface that the developed software needs to present. For example, the developed software requires three interfaces: A, B, and C, then the interface is The function abstracts the interface interfaces of the three interfaces A, B, and C, so that the control layer can directly control the rendering logic of the view layer through each interface interface. That is, after the control layer obtains the presentation logic of the presentation data for presentation, the interface interface corresponding to the presentation logic can be obtained, so that the view layer can be controlled to display the presentation through the corresponding interface interface. The data is presented. The presentation data reaching the view layer is the final data that needs to be presented. At this time, the view layer is only responsible for rendering the presentation data according to the corresponding presentation logic, without any processing on the presentation data.

Step S250, the view layer performs page presentation on the presentation data according to the found interface interface.

As an implementation manner, referring to FIG. 6, the step S250 may include the following sub-steps:

Sub-step S251, the interface interface is packaged by a packaging layer between the control layer and each interface of the view layer. The interface interface after the packaging forms a weak reference layer, so that the computer device running the software development model recovers the leaked memory when there is a memory leak in the view layer.

Sub-step S252, performing page rendering on the presentation data based on the packaged interface interface.

Specifically, since the view layer occupies a large memory, the memory of the view layer needs to be strictly managed, otherwise the memory leakage problem is likely to occur. In this embodiment, a layer of packaging layer may be disposed before each interface of the control layer and the view layer. As an implementation manner, the packaging layer may be packaged by a reference queue (WeakReference). The packaging layer can then package the interface interface to form a weak reference layer, which can form a weak reference relationship between the view layer and the control layer. If weak If there is a memory leak in the object referenced by the reference layer (eg, the view layer), then the computer device 100 will recycle the leaked memory. Specifically, the garbage collection period in the JAVA virtual machine running on the computer device 100 can be recovered, so that the memory leak caused by the view layer can be effectively avoided.

Through the above design, not only the strong coupling relationship between the view layer and the control layer is effectively reduced, but also the risk of memory leakage in the view layer can be effectively avoided.

In this embodiment, before the sub-step S251, the method may further include:

Referring to FIG. 7, another preferred embodiment of the present invention further provides a page logic control apparatus 200. The apparatus is stored in a memory 110 of the computer device 100, and the processor 120 performs the corresponding operation of the apparatus. The operation of each functional module. Wherein, the device is applied to a software development model, and the software development model includes a data layer, a control layer, and a view layer. The device can include:

The obtaining module 210 is configured to acquire data by the data layer.

The conversion module 220 is configured to convert, by the data layer, the acquired data into the preset format data by using an interface protocol between the data layer and the control layer, and then transmit the data to the control layer.

The parsing module 230 is configured to parse the preset format data by the control layer to obtain presentation data corresponding to the preset format data.

The searching module 240 is configured to, by the control layer, searching for an interface interface for displaying the presentation data from the control layer and at least one interface interface of the view layer based on the presentation data, and by using the found interface interface The corresponding presentation data is transmitted to the view layer. Wherein each interface interface corresponds to a type of presentation logic;

The presentation module 250 is configured to perform page presentation on the presentation data according to the found interface interface.

Optionally, referring to FIG. 8, the apparatus may further include:

a creating module 209, configured to create a preset interface protocol between the data layer and the control layer;

Optionally, referring to FIG. 9, the conversion module 220 may include:

The protocol acquisition sub-module 221 is configured to acquire a preset interface protocol between the data layer and the control layer. The preset interface protocol includes a format conversion function.

The conversion sub-module 222 is configured to convert the format of the acquired data by using a format conversion function in the preset interface protocol.

The generating sub-module 223 is configured to generate a string of a preset format after the format conversion of the acquired data is successful.

Optionally, referring to FIG. 10, the searching module 240 may include:

The logic acquisition sub-module 241 is configured to acquire at least one rendering logic that the presentation data needs to be presented.

The interface obtaining sub-module 242 is configured to acquire an interface interface of a view layer corresponding to each rendering logic according to each rendering logic.

Optionally, the manner in which the presentation module 250 performs page presentation on the presentation data according to the found interface interface by using the view layer may include:

The rendered data is page rendered based on the wrapped interface interface.

Optionally, in this embodiment, the creating module 209 is further configured to respond to the request for setting a wrapper layer between the control layer and an interface interface of the view layer, according to the request A wrapper layer is created between the control layer and the interface interface of the view layer.

For the specific operation method of each function module in this embodiment, reference may be made to the detailed description of the corresponding steps in the foregoing method embodiments, and details are not repeated herein.

In the several embodiments provided by the present invention, it should be understood that the disclosed apparatus and method may also be implemented in other manners. The above described apparatus and method embodiments are merely illustrative, for example, the flowchart and block diagrams in the figures illustrate the architecture of possible implementations of systems, methods, and computer program products according to various embodiments of the invention, Features and operations. In this regard, each block of the flowchart or block diagram can represent a module, a program segment, or a portion of code that includes one or more of the Executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the blocks may also occur in a different order than those illustrated in the drawings. For example, two consecutive blocks may be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending upon the functionality involved. It is also noted that each block of the block diagrams and/or flowcharts, and combinations of blocks in the block diagrams and/or flowcharts, can be implemented in a dedicated hardware-based system that performs the specified function or function. Or it can be implemented by a combination of dedicated hardware and computer instructions.

In addition, each functional module in each embodiment of the present invention may be integrated to form a separate part, or each module may exist separately, or two or more modules may be integrated to form a separate part.

The functions, if implemented in the form of software functional modules and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used to cause a computing device (which may be a personal computer, an electronic device, or a network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.

It is to be understood that the term "comprising", "comprising", or any other variants thereof is intended to encompass a non-exclusive inclusion, such that a process, method, article, or device that comprises a plurality of elements includes those elements. It also includes other elements that are not explicitly listed, or elements that are inherent to such a process, method, item, or device. An element defined by the phrase "comprising a ..." does not exclude the presence of additional elements in the process, method, item, or device that comprises the element.

It is apparent to those skilled in the art that the present invention is not limited to the details of the above-described exemplary embodiments, and the present invention can be embodied in other specific forms without departing from the spirit or essential characteristics of the invention. Therefore, the present embodiments are to be considered as illustrative and not restrictive, and the scope of the invention is defined by the appended claims instead All changes in the meaning and scope of equivalent elements are included in the present invention. Any reference signs in the claims should not be construed as limiting the claim.

Industrial applicability

The above design of the embodiment of the present application can effectively reduce the coupling relationship between the view layer and the control layer, and greatly improve the scalability and maintainability of the software. .

Claims

A page logic control method is applied to a software development model, where the software development model includes a data layer, a control layer, and a view layer, wherein the method includes:

The data layer acquires data;

Transmitting, by the data layer, the acquired data to the preset layer by using an interface protocol between the data layer and the control layer, and transmitting the data to the control layer;

The control layer parses the preset format data to obtain presentation data corresponding to the preset format data;

The control layer searches for an interface interface for displaying the presentation data from the control layer and at least one interface interface of the view layer based on the presentation data, and transmits corresponding presentation data through the found interface interface. To the view layer, wherein each interface interface corresponds to a type of presentation logic;

The view layer performs page rendering on the presentation data according to the found interface interface.
The page logic control method according to claim 1, wherein the data layer converts the acquired data into a preset format data through an interface protocol between the data layer and the control layer, and then transmits the data to the The steps of the control layer include:

Obtaining a preset interface protocol between the data layer and the control layer, where the preset interface protocol includes a format conversion function;

Converting the format of the acquired data by using a format conversion function in the preset interface protocol;

After the format conversion of the acquired data is successful, a string of a preset format is generated.
The page logic control method according to claim 1, wherein before the obtaining a preset interface protocol between the data layer and the control layer, the method further comprises:

Creating a preset interface protocol between the data layer and the control layer;

The step of creating a preset interface protocol between the data layer and the control layer includes:

Creating the preset interface protocol in response to a request to create a preset interface protocol between the data layer and the control layer, wherein the preset interface protocol is used to implement the data layer and the control layer Communication between.
The page logic control method according to claim 1, wherein the control layer searches for at least one interface interface of the control layer and the view layer for displaying the presentation data based on the presentation data. The steps of the interface interface include:

Obtaining at least one rendering logic that the rendering data needs to be presented;

An interface interface of the view layer corresponding to each rendering logic is obtained according to each rendering logic.
The page logic control method according to claim 1, wherein the view layer is found according to The interface interface performs the step of page rendering the presentation data, including:

Packaging the interface interface by a packaging layer between the control layer and each interface of the view layer, wherein the packaged interface interface forms a weak reference layer to enable a computer device running the software development model Leaking the leaked memory when there is a memory leak in the view layer;

The rendered data is page rendered based on the wrapped interface interface.
The page logic control method according to claim 5, wherein the method further comprises: before packaging the interface interface by a packaging layer between the control layer and each interface of the view layer, :

In response to a request to set a wrapper layer between the control layer and an interface interface of the view layer, a wrapper layer is created between the control layer and an interface interface of the view layer in accordance with the request.
The page logic control method according to claim 1, wherein the manner in which the data layer acquires data comprises at least one of the following:

Get data from the database;

Get data from the network layer; or

Get data from a file.
A page logic control device is applied to a software development model, the software development model comprising a data layer, a control layer and a view layer, wherein the device comprises:

An obtaining module configured to acquire data through the data layer;

The conversion module is configured to convert the acquired data to the preset format data through an interface protocol between the data layer and the control layer, and then transmit the data to the control layer;

The parsing module is configured to parse the preset format data by using the control layer to obtain presentation data corresponding to the preset format data;

a search module configured to search, by the control layer, an interface interface for displaying the presentation data from the control layer and at least one interface interface of the view layer based on the presentation data, and by using the found interface interface Transmitting corresponding presentation data to the view layer, wherein each interface interface corresponds to a type of presentation logic;

And a presentation module configured to perform page presentation on the presentation data according to the found interface interface by using the view layer.
The page logic control device according to claim 8, wherein the conversion module comprises:

The protocol acquisition sub-module is configured to acquire a preset interface protocol between the data layer and the control layer, where the preset interface protocol includes a format conversion function;

The conversion submodule is configured to convert the format of the acquired data by using a format conversion function in the preset interface protocol;

Generating a submodule, configured to generate a word in a preset format after the format conversion of the acquired data is successful String.
The page logic control device according to claim 8, wherein the device further comprises:

Creating a module, configured to create a preset interface protocol between the data layer and the control layer;

The creation module is further configured to:

Creating the preset interface protocol in response to a request to create a preset interface protocol between the data layer and the control layer, wherein the preset interface protocol is used to implement the data layer and the control layer Communication between.
The page logic control device according to claim 8, wherein the searching module comprises:

a logic acquisition submodule configured to acquire at least one rendering logic that the rendering data needs to be presented;

The interface acquires a sub-module configured to acquire an interface interface of a view layer corresponding to each presentation logic according to each rendering logic.
The page logic control apparatus according to claim 8, wherein the presentation module is further configured to:

Packaging the interface interface by a packaging layer between the control layer and each interface of the view layer, wherein the packaged interface interface forms a weak reference layer to enable a computer device running the software development model Leaking the leaked memory when there is a memory leak in the view layer;

The rendered data is page rendered based on the wrapped interface interface.
The page logic control apparatus according to claim 12, wherein the creation module is further configured to:

In response to a request to set a wrapper layer between the control layer and an interface interface of the view layer, a wrapper layer is created between the control layer and an interface interface of the view layer in accordance with the request.
The page logic control apparatus according to claim 8, wherein the manner in which the data layer acquires data comprises at least one of the following:

Get data from the database;

Get data from the network layer; or

Get data from a file.
A computer device comprising a processor and a non-volatile memory storing a plurality of computer instructions, wherein the computer device performs any one of claims 1-7 when the computer instructions are executed by the processor The page logic control method described in the item.
A readable storage medium, the readable storage medium comprising a computer program, characterized by:

The computer program controlling the electronic device in which the readable storage medium is located to execute the page logic control method according to any one of claims 1-7.