A pop-up view management method, apparatus, computer equipment, and storage medium

Abstract

This invention relates to the field of computer technology, and more particularly to a method, apparatus, computer device, and storage medium for managing pop-up views. Based on a received trigger event of a pop-up view, the corresponding pop-up component is invoked to generate the corresponding pop-up view. An interface utility class file for managing the pop-up views is obtained based on a pre-established base class inherited from the pop-up view, and the pop-up views are managed based on this interface utility class file. In this invention, by inheriting the base class of the pop-up view, only one set of code needs to be written and maintained for the same pop-up generation and disappearance, providing methods for business use. Subsequent adjustments or modifications only require maintenance within this method, simplifying the maintenance of the pop-up view code and improving the management efficiency of pop-up views.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a pop-up view management method, apparatus, computer equipment, and storage medium. Background Technology

[0002] Currently, to meet diverse user needs and increase user engagement, smartphone applications are offering increasingly diverse functionalities. Many of these functionalities are implemented through embedded third-party SDKs, or projects utilize component-based development, with modules divided according to function and pages relatively independent. Many software applications involve displaying multiple pop-up views simultaneously. In existing technologies, the root view controller of the topmost view is retrieved in real-time during page display, and the pop-up view to be displayed is shown through a system interface. However, the code for showing and disappearing each pop-up view must be implemented repeatedly. This excessive redundancy leads to a large workload and low management efficiency. Therefore, improving the management efficiency of pop-up views has become a pressing issue. Summary of the Invention

[0003] Therefore, it is necessary to provide a pop-up view management method, device, computer equipment, and storage medium to address the aforementioned technical problems and solve the problem of low management efficiency of pop-up views.

[0004] A first aspect of this application provides a pop-up view management method, the pop-up view management method comprising:

[0005] Based on the received trigger event of the pop-up view, the corresponding pop-up component is invoked to generate the corresponding pop-up view;

[0006] Based on the pre-established base class inherited from the pop-up view, an interface utility class file for managing the pop-up view is obtained;

[0007] The pop-up view is managed based on the interface utility class file.

[0008] A second aspect of this application provides a pop-up view management device, the pop-up view management device comprising:

[0009] The calling module is used to call the pop-up component corresponding to the pop-up view based on the received trigger event of the pop-up view, and generate the corresponding pop-up view;

[0010] The module is used to obtain a UI utility class file for managing the pop-up view based on a pre-established base class inherited from the pop-up view.

[0011] The management module is used to manage the pop-up view based on the interface tool class file.

[0012] A third aspect of this application provides a computer device, including: a memory, a processor, and computer-readable instructions stored in the memory and executable on the processor, the computer instructions being configured to cause the computer to perform the steps of the first aspect.

[0013] A fourth aspect of this application provides a computer-readable storage medium storing a computer program that is executed by a processor as the steps of the method of the first aspect.

[0014] The advantages of this invention compared to the prior art are:

[0015] Based on the received trigger event of the pop-up view, the corresponding pop-up component is invoked to generate the corresponding pop-up view. A UI utility class file for managing the pop-up view is obtained based on a pre-established base class inherited from the pop-up view, and the pop-up view is managed using this UI utility class file. In this invention, by inheriting the base class of the pop-up view, only one set of code needs to be written and maintained for the same pop-up generation and disappearance, providing methods for business use. Subsequent adjustments or modifications only require maintenance within this method, simplifying the maintenance of the pop-up view code and improving the management efficiency of the pop-up view. Attached Figure Description

[0016] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 This is a schematic diagram of an application environment for a pop-up view management method provided in an embodiment of the present invention;

[0018] Figure 2 This is a flowchart illustrating a pop-up view management method according to an embodiment of the present invention;

[0019] Figure 3 This is a flowchart illustrating a method for generating a corresponding pop-up view according to an embodiment of the present invention;

[0020] Figure 4 This is a flowchart illustrating a method for obtaining a pre-established base class according to an embodiment of the present invention;

[0021] Figure 5 This is a flowchart illustrating a method for obtaining an interface tool class file for managing pop-up views, according to an embodiment of the present invention.

[0022] Figure 6 This is a schematic diagram of the structure of a pop-up view management device provided in an embodiment of the present invention;

[0023] Figure 7 This is a schematic diagram of the structure of a computer device provided in an embodiment of the present invention. Detailed Implementation

[0024] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0025] It should be understood that, when used in this specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0026] It should also be understood that the term “and / or” as used in this specification and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0027] As used in this specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if [described condition or event] is detected" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once [described condition or event] is detected," or "in response to detection of [described condition or event]."

[0028] Furthermore, in the description of this invention and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0029] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of the invention include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0030] It should be understood that the sequence number of each step in the following embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0031] To illustrate the technical solution of the present invention, specific embodiments are described below.

[0032] The pop-up view management method provided in this embodiment of the invention can be applied to, for example... Figure 1 In this application environment, the client communicates with the server. Clients include, but are not limited to, PDAs, desktop computers, laptops, ultra-mobile personal computers (UMPCs), netbooks, and personal digital assistants (PDAs). The server can be implemented using a standalone server or a server cluster consisting of multiple servers.

[0033] See Figure 2 This is a flowchart illustrating a pop-up view management method provided in an embodiment of the present invention. The pop-up view management method can be applied to... Figure 1 The client-side computer connects to the target database via a pre-defined Application Programming Interface (API). When the target database is driven to execute corresponding tasks, corresponding logs are generated, which can be collected via the API. For example... Figure 2 As shown, the pop-up view management method may include the following steps:

[0034] S201: Based on the received trigger event of the pop-up view, call the pop-up component corresponding to the pop-up view to generate the corresponding pop-up view.

[0035] In step S201, the triggering event of the pop-up view can include multiple types of messages. Based on the received triggering event of the pop-up view, the corresponding pop-up component of the pop-up view is called to generate the corresponding pop-up view.

[0036] In this embodiment, the trigger event for the pop-up view can be a message received based on user triggering. This user trigger can be a gesture touch, a physical keyboard trigger, etc., or a message received based on service broadcasting, such as a service-pushed prize-winning information or advertising information. Upon receiving a pop-up view trigger event, a pop-up element corresponding to the trigger event is dynamically created. This target pop-up element is used to define the pop-up view. For example, the pop-up element is added to the end of the body of the HTML document. In this embodiment, since each created pop-up element is added to the end of the body, from a timeline perspective, pop-up elements created later in time are positioned further down the body, thus forming a queue effect and achieving effective management of each pop-up view.

[0037] Based on the received pop-up view trigger event, the corresponding pop-up component is invoked to generate the corresponding pop-up view. The pop-up component consists of corresponding pop-up input parameters, which vary depending on the pop-up view type. Pop-up elements are customized and dynamically created based on the input parameters and added to the end of the main body. For user-triggered pop-up events, the corresponding pop-up view is the user-clicked pop-up. Input parameters may include: pop-up view size, attached element (corresponding to the button clicked by the user; its position in the HTML webpage is fixed, and the button's position determines the pop-up view's position), and optional custom styles.

[0038] The popup element is a Vue component element, which can be encapsulated into a Vue component popup instance through a factory function. The factory function creates and encapsulates the instance based on the input parameters, and the Vue component popup instance is used to execute the popup view. The Vue component popup instance is added to the main body as a Vue component element.

[0039] For example, the input parameters include style attribute parameters and the size of the popup view. The Vue component popup view instance includes CSS code for position handling. If the style attribute parameters include inline CSS style code, the Vue component's style code is rewritten based on the inline CSS style code. Block tags (e.g., <html>) are added to the beginning and end of the Vue component popup view instance. 、This allows you to obtain Vue component elements. For example, you can add Vue component elements (also known as container elements) to the body of an HTML document using the native method `document.body.appendChild()`. Data and event passing are handled using methods provided by Vue components. For custom style requirements, inline CSS style code must be passed in, and the Vue component's styles will be rewritten internally. Centered pop-up views will have their CSS code calculated based on the passed-in pop-up view size. For pop-up views displaying custom dependency entry points, only the dependency element needs to be passed in; the Vue component internally retrieves the attribute of the passed-in element, combines it with the pop-up view size and custom style parameters, and calculates the display position.

[0040] It should be noted that the corresponding pop-up view type can be determined based on the pop-up view's identifier. This identifier uniquely identifies the pop-up view to be displayed on the page. For example, pop-up view types include, but are not limited to, native pop-ups, webview pop-ups, pinned announcement pop-ups, native location notification pop-ups, and bottom pop-ups. There are no restrictions on the pop-up type here; users can categorize and define pop-ups according to their actual needs. For example, the pop-up view type can be a native pop-up, a pinned announcement pop-up, a native location notification pop-up, or a bottom pop-up. It should be noted that this is only an illustrative example of different pop-up view types and does not limit the pop-up type or specific style; users can customize the settings according to their actual needs.

[0041] Specifically, the corresponding pop-up view type is determined based on the pop-up view identifier and a preset identifier type list. In one embodiment, the preset identifier type list contains at least one pop-up view identifier and a pop-up type corresponding to each pop-up view identifier. For example, when the pop-up view identifier is a number, the preset identifier type list contains at least one range of pop-up view identifiers and a pop-up view type corresponding to each range of pop-up view identifiers. For example, assuming the preset identifier type list includes [22001, 22010] and [22011, 22020], and the pop-up view types corresponding to the two pop-up view identifier ranges are the native pop-up view type and the pinned announcement pop-up view type, respectively, if the corresponding pop-up view identifier is 22015, then the corresponding pop-up view type is the pinned announcement pop-up type.

[0042] When the pop-up view type is a native pop-up, the `creatPopTask` method is called to create an initial pop-up view based on preset static pop-up data corresponding to the native pop-up. The `addStyle` method is then called to add the pop-up data to the initial pop-up view. In scenarios where the same pop-up view type is displayed on different pages, existing technologies require developers to create separate pop-up views for each page. These different pages may belong to different business logics and require different developers, making it difficult to unify the style of pop-up views of the same type, resulting in inconsistent user experiences. This invention addresses this by pre-defining preset static pop-up data corresponding to different pop-up view types, thereby achieving uniformity in the pop-up frame information for the same pop-up view type across different pages and ensuring a consistent user experience.

[0043] See Figure 3 This is a flowchart illustrating a method for generating a corresponding pop-up view according to an embodiment of the present invention.

[0044] Optionally, based on the received trigger event of the pop-up view, the corresponding page component of the pop-up view is invoked to generate the corresponding pop-up view, including...

[0045] S301: Based on the received trigger event from the pop-up view, obtain the trigger data corresponding to the trigger event;

[0046] S302: Determine whether the trigger data meets the triggering conditions of the initial pop-up view;

[0047] S303: When the triggering conditions for the initial pop-up view are met, the pop-up view corresponding to the triggering event will pop up;

[0048] S304: When the initial pop-up view triggering condition is not met, determine whether the triggering data meets the triggering condition of the pop-up probability event;

[0049] S305: When the triggering conditions of the pop-up probability event are met, the pop-up view corresponding to the triggering event will pop up.

[0050] In this embodiment, trigger data corresponding to the received pop-up view trigger event is obtained. The trigger data includes, but is not limited to, the number of times the pop-up view is called and the number of times the pop-up view has been triggered in the current cycle of the entire application.

[0051] For example, when a pop-up view is triggered, the server retrieves the configuration parameters of the application corresponding to the triggering event from the local disk, quickly obtaining the configuration parameters of the functional module without requesting the terminal management platform. These configuration parameters include, but are not limited to, the title displayed in the pop-up view corresponding to the application triggering the event, and the condition parameters required for the corresponding pop-up triggering event, such as the preset number of calls, pop-up probability parameters, or pop-up trigger probability parameters.

[0052] The system determines whether the triggered data meets the triggering conditions for the initial pop-up view. The initial pop-up event is triggered when the number of calls in the application reaches a preset number. This preset number of calls can be customized by IT personnel through the terminal management platform or dynamically determined by the terminal management platform based on the amount of evaluation data; no specific limitation is made here. This terminal management platform can be used to manage application evaluation data returned from different servers. When the triggering conditions for the initial pop-up view are met, the pop-up view corresponding to the triggered event appears.

[0053] When the initial pop-up event trigger conditions are met, the corresponding pop-up view appears. This pop-up view is used to receive online user feedback on the general application or new feature application. The pop-up frequency (e.g., once every 3 days) and the text content (e.g., "Are you satisfied with our features?") of different applications remain consistent to ensure the uniformity and universality of the pop-up views displayed across the application. This trigger data includes, but is not limited to, the number of calls and the number of times the pop-up view has been triggered within the current period. The number of calls reflects the number of times online users use the application. In this embodiment, the current period refers to the current day. The initial pop-up event corresponds to a preset number of calls, triggered when the number of calls to the new feature application reaches the preset number. Specifically, when the number of calls to the new feature application reaches the preset number, such as 3 times, it is considered that the user's usage of the new feature application is sufficiently objective.

[0054] If the initial pop-up view trigger conditions are not met, it is determined whether the trigger data meets the trigger conditions for the pop-up probability event. If the trigger conditions for the pop-up probability event are met, the pop-up view corresponding to the trigger event will appear. This pop-up probability parameter can be customized by IT personnel or other staff with modification permissions through the terminal management platform, or it can be dynamically determined by the terminal management platform based on the amount of evaluation data collected; no restrictions are imposed here.

[0055] For example, assuming the pop-up probability parameter is 0.3, the random function (which can be set to randomly select three numbers between 1 and 10 as the pop-up trigger count) is used to indicate when the application triggers the pop-up view on the Nth (i.e., the pop-up trigger count). In this embodiment, by receiving the triggered call event, trigger data is obtained so as to determine the pop-up view triggering mechanism based on the trigger data.

[0056] Optionally, before determining whether the triggering data meets the triggering conditions for the pop-up probability event, the following steps are also included:

[0057] If the initial pop-up event triggering conditions are not met, determine whether the triggering data meets the triggering conditions for the maximum pop-up event.

[0058] In this embodiment, the maximum pop-up trigger event corresponds to a maximum number of pop-up view triggers in the current period. The triggering condition for this maximum pop-up view trigger event is that the total number of pop-up view triggers in the entire application within the current period does not exceed the maximum number of pop-up view triggers in the current period. When the triggering condition for the maximum pop-up trigger event is met, it is then determined whether the triggering data meets the triggering condition for the pop-up probability event. In essence, determining whether the triggering data meets the triggering condition for the pop-up probability event when the maximum pop-up trigger event is met effectively ensures that at most a pop-up view will appear within the entire application period.

[0059] S202: Based on the pre-established base class inherited from the pop-up view, obtain the interface utility class file for managing the pop-up view.

[0060] In step S202, when the pop-up view appears, a UI utility class file for managing the pop-up view is obtained based on a pre-established base class inherited from the pop-up view. Managing the pop-up view requires determining the pop-up content and the start and end times of the pop-up view. The start and end times of the corresponding pop-up view are determined by the pre-established base class inherited from the pop-up view. There is no need for separate code to control the start and end times of the corresponding pop-up view. Only the pop-up content needs to be managed, which improves the management efficiency of the pop-up view.

[0061] In this embodiment, a utility class file that inherits from the root class NSObject is created to obtain the interface utility class file ControllerHelper used to manage the pop-up view. Then, the interface utility class file ControllerHelper.m used to manage the pop-up view is accessed to declare the properties of the pop-up view interface management and define the core methods.

[0062] See Figure 4 This is a flowchart illustrating a method for obtaining a pre-established base class according to an embodiment of the present invention.

[0063] Optionally, before obtaining the interface utility class file for managing pop-up views based on a pre-established base class inherited from the pop-up view, the following may also be included:

[0064] S401: Create a view class for handling request pop-up windows;

[0065] S402: Based on the configuration of the request pop-up view class for filtering, serialization, and initialization of query method attributes, the serialization view base class is obtained. The serialization view base class is a pre-established base class.

[0066] In this embodiment, when a pop-up event is triggered, a pre-created Django view class is established as the base class before accepting the data request sent by the application. Only the created Django view class can serialize the data corresponding to the received data request from the application, so that the serialized data can be applied to DataTables. Therefore, a serializable view base class is created before accepting the data request sent by the application.

[0067] Specifically, a request handling view class is created based on Django, and this view class inherits from the serialization view base class. Based on this request handling view class, filtering (lookup_mapping), serialization (serializer_class), and initial query method (get_initial_queryset) are configured. Filtering is configured by setting attributes such as lookup_mapping = ["name", "age", "city"]. For example, if the data to be displayed in the DataTables is user name (name), age (age), and city (city), then lookup_mapping needs to be configured with these three attributes. This attribute is used to filter data based on the associated Model fields of the Django Model, and the filtered data can then be queried and displayed in the DataTables. Serialization allows data to be serialized, and the serialization method and fields can be specified. For example, by writing a capitalization conversion method in the serialization class, the letters in the name can be converted to uppercase. The initial query method is the data query method, such as a join query.

[0068] Once the filtering, serialization, and initial query method properties of the request processing view class are configured, the request processing view class is determined to be the serialization view base class. Based on this serialization view base class, data requests sent by the application can be accepted, and the data requests and corresponding data can be processed to obtain the data applied by DataTables.

[0069] In this embodiment, by creating a request processing view class and configuring filtering, serialization, and initialization query method attributes based on the request processing view class, a serialization view base class is obtained. This realizes the creation of the view base class, enabling the application to quickly process the data sent by the application based on the view base class, improving data processing efficiency, and avoiding repeated configuration of the view base class when data serialization is required.

[0070] See Figure 5 This is a flowchart illustrating a method for obtaining an interface tool class file for managing pop-up views, provided by an embodiment of the present invention.

[0071] Optionally, based on a pre-established base class inherited from the pop-up view, a UI utility class file for managing the pop-up view is obtained, including:

[0072] S501: Using the preset development tool editor, select the file type applicable to application development in the pop-up file type options;

[0073] S502: In the pop-up window options, select the inheritance base class of the pop-up view. Based on the inheritance base class and file type, obtain the interface utility class file used to manage the pop-up view.

[0074] In this embodiment, using the Xcode editor, right-click and select "New File" to create a new file. In the pop-up file type options, select "CocoaTouchClass" for application development on iOS devices. In the pop-up view options, select "Inherit from base class NSObject" and name the created file "File" "ControllerHelper". Clicking "Finish" will generate a file inheriting from the Objective-C root class NSObject, namely "ControllerHelper". ControllerHelper is used for unified management of pop-up views. Navigate to the utility class file ControllerHelper.m, which manages pop-up views, to declare the properties and define the core methods for pop-up view management. This includes the following steps: Navigate to the implementation class ControllerHelper.m, declare the extension of the logging class ControllerHelper using the extended declaration method @interfaceControllerHelper(), for declaring private properties and methods. In the declaration section, declare the private property isPushing, which indicates whether the application is currently managing pop-up views, as follows: @property(nonatomic,assig n)BOOLisPushing, go to the implementation section @implementation, define the singleton method +(instanc etype)sharedInstance, which is used to implement the singleton function, ensure that there is only one ControllerHelper class object used for pop-up view management, and reduce the memory consumption of frequent and multiple creations.

[0075] S203: File management pop-up view based on interface tool class.

[0076] In step S203, the pop-up view is managed through the interface tool class file.

[0077] In this embodiment, managing pop-up views through the interface utility class file includes providing external API interfaces to the corresponding pop-up views, and establishing communication connections between pop-up management and pop-up functionality through these API interfaces. In this embodiment, a unified BaseViewController can be established through the interface utility class file to construct the pop-up view controller, which provides unified methods for displaying and closing pop-up views. When a trigger event for a pop-up view is received, the pop-up view controller constructs the pop-up view to be displayed. The pop-up view is the page containing the window content to be displayed, such as a survey page. The view controller configures the pop-up view according to the parameters passed in, matching the preset pop-up view size, display orientation, etc., and passes the pop-up view to the pop-up view controller. The pop-up view controller displays the pop-up view by calling the provided pop-up view display method. It can also add weak references to the displayed pop-up views and add them to the weak reference table to achieve unified management of the pop-up views. Additionally, when a pop-up view needs to be closed, the pop-up control unit can find the corresponding pop-up view in the weak reference table and call the pop-up view close method to remove the pop-up view object from the weak reference table, ensuring that the window is released correctly.

[0078] Based on the received trigger event of the pop-up view, the corresponding pop-up component is invoked to generate the corresponding pop-up view. A UI utility class file for managing the pop-up view is obtained based on a pre-established base class inherited from the pop-up view, and the pop-up view is managed using this UI utility class file. In this invention, by inheriting the base class of the pop-up view, only one set of code needs to be written and maintained for the same pop-up generation and disappearance, providing methods for business use. Subsequent adjustments or modifications only require maintenance within this method, simplifying the maintenance of the pop-up view code and improving the management efficiency of the pop-up view.

[0079] Please see Figure 6 , Figure 6 This is a schematic diagram of a pop-up view management device provided in an embodiment of the present invention. In this embodiment, the mobile terminal includes units used for executing... Figures 2 to 5 The steps in the corresponding embodiments. Please refer to the details. Figures 2 to 5 as well as Figures 2 to 5 The relevant descriptions in the corresponding embodiments are shown below. For ease of explanation, only the parts relevant to this embodiment are shown.

[0080] See Figure 6 The pop-up view management device 60 includes:

[0081] Module 61 is used to call the page component corresponding to the pop-up view and generate the corresponding pop-up view based on the received trigger event of the pop-up view.

[0082] Module 62 is obtained, which is used to obtain the interface utility class file for managing pop-up views based on the pre-established base class inherited from the pop-up view.

[0083] Management module 63 is used for a pop-up view of file management based on a user interface tool.

[0084] Optionally, the pop-up view management device 60 further includes:

[0085] Create a module to create a view class that handles request pop-ups.

[0086] The processing module is used to configure filtering, serialization, and initialization query method attributes based on the pop-up view class for processing requests, and to obtain the serialization view base class, which is a pre-established base class.

[0087] Optionally, the above-mentioned calling module 61 includes:

[0088] The acquisition unit is used to obtain the trigger data corresponding to the trigger event based on the received trigger event of the pop-up view.

[0089] The first judgment unit is used to determine whether the trigger data meets the triggering conditions of the initial pop-up view.

[0090] The first pop-up unit is used to pop up the pop-up view corresponding to the triggering event when the triggering conditions of the initial pop-up view are met.

[0091] The second judgment unit is used to determine whether the triggering data meets the triggering conditions of the pop-up probability event when the triggering conditions of the initial pop-up view are not met.

[0092] The second pop-up unit is used to pop up the pop-up view corresponding to the triggering event when the triggering conditions of the pop-up probability event are met.

[0093] Optionally, the above-mentioned calling module 61 includes:

[0094] The third judgment unit is used to determine whether the triggering data meets the triggering conditions of the maximum pop-up triggering event when the triggering conditions of the initial pop-up event are not met.

[0095] Optionally, the above-mentioned module 62 includes:

[0096] The first selection unit is used to select the file type applicable to application development in the pop-up window view by using the preset development tool editor and the pop-up file type options.

[0097] The second selection unit is used to select the inheritance base class of the pop-up view from the pop-up options. Based on the inheritance base class and file type, the interface utility class file used to manage the pop-up view is obtained.

[0098] It should be noted that the information interaction and execution process between the above-mentioned units are based on the same concept as the method embodiments of the present invention. For details on their specific functions and technical effects, please refer to the method embodiments section, which will not be repeated here.

[0099] Figure 7 This is a schematic diagram of the structure of a computer device provided in an embodiment of the present invention. Figure 7 As shown, the computer device of this embodiment includes: at least one processor ( Figure 7 Only one is shown in the diagram), a memory, and a computer program stored in the memory and capable of running on at least one processor, wherein the processor executes the computer program to implement the steps of any of the above pop-up view management methods.

[0100] This computer device may include, but is not limited to, a processor and memory. Those skilled in the art will understand that... Figure 7 The examples of computer devices are merely examples and do not constitute a limitation on computer devices. Computer devices may include more or fewer components than shown in the illustration, or combinations of certain components, or different components, such as network interfaces, displays, and input devices.

[0101] The processor referred to can be a CPU, but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0102] Memory includes readable storage media, internal memory, etc., wherein internal memory can be the RAM of a computer device, providing an environment for the operation of the operating system and computer-readable instructions stored in the readable storage media. The readable storage media can be the hard drive of a computer device, or in other embodiments, it can be an external storage device of the computer device, such as a plug-in hard drive, Smart Media Card (SMC), Secure Digital (SD) card, or Flash Card. Furthermore, memory can include both internal storage units and external storage devices of a computer device. Memory is used to store the operating system, applications, bootloader, data, and other programs, such as program code for computer programs. Memory can also be used to temporarily store data that has been output or will be output.

[0103] Those skilled in the art will understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is used as an example. In practical applications, the functions described above can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this invention. The specific working process of the units and modules in the above device can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here. If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present invention can implement all or part of the processes in the methods of the above embodiments by instructing related hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the above method embodiments. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. A computer-readable medium can include at least: any entity or device capable of carrying computer program code, a recording medium, a computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electrical carrier signals or telecommunication signals.

[0104] The present invention can implement all or part of the processes in the methods of the above embodiments, or it can be accomplished by a computer program product. When the computer program product is run on a computer device, the computer device executes the steps in the above method embodiments.

[0105] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0106] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0107] In the embodiments provided by this invention, it should be understood that the disclosed apparatus / computer devices and methods can be implemented in other ways. For example, the apparatus / computer device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0108] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0109] The above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included within the protection scope of the present invention.

Claims

1. A pop-up view management method, characterized by, The pop-up view management method comprises: According to the received trigger event of the pop-up view, the pop-up view corresponding to the pop-up component is called, and the corresponding pop-up view is generated; According to the pre-established base class inherited by the pop-up view, an interface tool class file for managing the pop-up view is obtained; The interface tool class file is used to manage the pop-up view; According to the received trigger event of the pop-up view, the pop-up view corresponding to the pop-up component is called, and the corresponding pop-up view is generated, comprising: According to the received trigger event of the pop-up view, the trigger data corresponding to the trigger event is obtained; Determine whether the trigger data meets the trigger condition of the initial pop-up view; When the trigger condition of the initial pop-up view is met, the pop-up view corresponding to the trigger event is popped up; When the trigger condition of the initial pop-up view is not met, it is determined whether the trigger data meets the trigger condition of the pop-up probability event; When the trigger condition of the pop-up probability event is met, the pop-up view corresponding to the trigger event is popped up; Before determining whether the trigger data meets the trigger condition of the pop-up probability event, it further comprises: When the trigger condition of the initial pop-up event is not met, it is determined whether the trigger data meets the trigger condition of the maximum pop-up trigger event; Before obtaining the interface tool class file for managing the pop-up view according to the pre-established base class inherited by the pop-up view, it further comprises: Create a processing request pop-up view class; Based on the processing request pop-up view class, filter, serialization, and initialization query mode attributes are configured to obtain a serialized view base class, which is a pre-established base class; According to the pre-established base class inherited by the pop-up view, the interface tool class file for managing the pop-up view is obtained, comprising: Through a preset development tool editor, a file type applied to the application development of the pop-up view is selected in the pop-up file type option, and an inheritance base class of the pop-up view is selected in the pop-up option, and according to the inheritance base class and the file type, the interface tool class file for managing the pop-up view is obtained.

2. A terminal device, characterized by comprising: The terminal device comprises a processor, a memory, and a computer program stored in the memory and executable on the processor, and the processor executes the computer program to realize the pop-up view management method of claim 1.

3. A computer-readable storage medium storing a computer program, the computer-readable storage medium being characterized by, The computer program is executed by the processor to realize the pop-up view management method of claim 1.

Images