Method and apparatus for processing interaction request in application, device, and medium

Abstract

Provided are a method and apparatus for processing an interaction request in an application, a device, and a medium. The application comprises a plurality of views respectively located at a plurality of levels, and the plurality of views comprise a parent view located at a first level, a collection view located at a second level, a unit view located at a third level, and a sub-view located at a fourth level. The method comprises: receiving an interaction request for a parent view; in response to determining that the parent view does not comprise a response procedure for the interaction request, determining a target view matching the interaction request among the plurality of views; and using the response procedure of the target view to process the interaction request. By means of the exemplary implementation of the present disclosure, a sub-view for processing an interaction request can be added to an application in a simpler and more effective manner, thereby improving the efficiency of processing the interaction request.

Description

Methods, apparatus, devices, and media for processing interactive requests in applications. Technical Field

[0001] Exemplary implementations of this disclosure generally relate to application management, and more particularly to methods, apparatus, devices, and computer-readable storage media for processing interactive requests in applications. Background Technology

[0002] An application can include multiple views, and in response to interactions with these views, the application can execute different response procedures to achieve the desired functionality. As the application becomes more complex, the functionality of each view also gradually increases. The concept of a collection view has been proposed, and multiple unit views can be added to a collection view. Subviews can be added to a unit view to handle interaction requests; however, this may require adjusting the layout of the individual unit views within the collection view. Therefore, a more flexible and efficient way to handle interaction requests within the application is desired.

[0003] Summary of the Invention

[0004] In a first aspect of this disclosure, a method for processing interaction requests in an application is provided. The application includes multiple views located at multiple levels, including a parent view at a first level, a collection view at a second level, a unit view at a third level, and child views at a fourth level. In the method, an interaction request for the parent view is received. In response to determining that a response process for the interaction request is not included in the parent view, a target view matching the interaction request is determined among the multiple views. The interaction request is processed using the response process of the target view.

[0005] In a second aspect of this disclosure, an apparatus for processing interaction requests in an application is provided. The application includes multiple views located at multiple levels, the multiple views including a parent view at a first level, a collection view at a second level, a unit view at a third level, and a child view at a fourth level. The apparatus includes: a receiving module configured to receive an interaction request for the parent view; a determining module configured to determine a target view matching the interaction request among the multiple views in response to a determination that a response to the interaction request is not included in the parent view; and a processing module configured to process the interaction request using the response of the target view.

[0006] In a third aspect of this disclosure, an electronic device is provided. The electronic device includes: at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions causing the electronic device to perform the method according to a first aspect of this disclosure when executed by the at least one processing unit.

[0007] In a fourth aspect of this disclosure, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, causes the processor to implement the method according to a first aspect of this disclosure.

[0008] In a fifth aspect of this disclosure, a computer program product is provided, comprising a computer program that, when executed by a processor, implements the method according to a first aspect of this disclosure.

[0009] It should be understood that the content described in this content section is not intended to limit the key or essential features of the implementation of this disclosure, nor is it intended to restrict the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0010] In the following detailed description, the above and other features, advantages, and aspects of the various implementations of this disclosure will become more apparent, taken in conjunction with the accompanying drawings. In the accompanying drawings, the same or similar reference numerals denote the same or similar elements, wherein:

[0011] Figure 1 shows a block diagram of an application environment according to an exemplary implementation of the present disclosure;

[0012] Figure 2 shows a block diagram of some implementations of this disclosure for handling interactive requests in an application;

[0013] Figure 3 shows a block diagram illustrating the hierarchical relationship of multiple views according to some implementations of this disclosure;

[0014] Figure 4A shows a block diagram of the parent view according to some implementations of this disclosure;

[0015] Figure 4B shows a block diagram of an extended parent view according to some implementations of this disclosure;

[0016] Figure 5 shows a block diagram of the area of ​​a subview according to some implementations of this disclosure;

[0017] Figure 6 shows a block diagram for determining a target view matching an interaction request according to some implementations of this disclosure;

[0018] Figure 7 shows a block diagram of the layout of multiple views according to some implementations of this disclosure;

[0019] Figure 8 shows a flowchart of a method for handling interactive requests in an application according to some implementations of this disclosure;

[0020] Figure 9 shows a block diagram of an apparatus for processing interactive requests in an application, according to some implementations of the present disclosure; and

[0021] Figure 10 shows a block diagram of a device capable of implementing various implementations of the present disclosure. Detailed Implementation

[0022] Implementations of this disclosure will now be described in more detail with reference to the accompanying drawings. While some implementations of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the implementations set forth herein. Rather, these implementations are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and implementations of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0023] In the description of the implementation methods disclosed herein, the term "comprising" and similar terms should be understood as open inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "one implementation" or "the implementation" should be understood as "at least one implementation". The term "some implementations" should be understood as "at least some implementations". Other explicit and implicit definitions may also be included below. As used herein, the term "model" can represent the relationships between various data. For example, the aforementioned relationships can be obtained based on various technical solutions that are currently known and / or will be developed in the future.

[0024] It is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and related provisions.

[0025] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this disclosure through appropriate means in accordance with relevant laws and regulations, and user authorization should be obtained.

[0026] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the software or hardware, such as the electronic device, application, server, or storage medium performing the operations of this disclosed technical solution, based on the prompt message.

[0027] As an optional but non-restrictive implementation, in response to a user's active request, a prompt message can be sent to the user, for example, via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose whether to "agree" or "disagree" to provide personal information to the electronic device.

[0028] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

[0029] The term "in response to" as used herein refers to a state in which a corresponding event occurs or a condition is satisfied. It will be understood that the timing of subsequent actions performed in response to such event or condition is not necessarily strongly correlated with the time when the event occurs or the condition is met. For example, in some cases, subsequent actions may be performed immediately upon the occurrence of the event or the fulfillment of the condition; while in others, they may be performed some time after the occurrence of the event or the fulfillment of the condition.

[0030] Example Environment

[0031] An application may include multiple views. In response to receiving interactions with these views, the application can execute different response procedures to achieve the desired functionality. As the application's functionality becomes more complex, the functionality of each view also gradually increases. The concept of a collection view has been proposed, and multiple unit views can be added to a collection view. Referring to Figure 1, which describes an application environment according to some implementations of this disclosure, Figure 1 shows a block diagram 100 of an application environment according to an exemplary implementation of this disclosure.

[0032] As shown in Figure 1, application 110 can have multiple functions. For ease of description, in the context of this disclosure, only the inbox in the application is used as an example to describe the process of handling interactive requests in the application. A collection view 120 can be provided, and one or more cell views, such as cell views 130, 132, etc., can be added to the collection view. In different development environments, the collection view can be implemented using different classes.

[0033] In a development environment, collection views can be implemented using UICollectionView. UICollectionView is a class in the web development toolset used to display data collections. This class supports horizontal and vertical scrolling and allows for custom layouts to display complex data structures, etc. UICollectionView is commonly used to display data collections such as images, lists, and grids, and provides rich user interactions such as scrolling, selection, and dragging. One or more cell views (corresponding to CellViews in UICollectionView) can be added to a collection view. For example, the cell views in Figure 1 can each correspond to a different user in the application (i.e., the sender).

[0034] During application development, it is expected that page 140 will be provided. This page 140 may include a bubble 142 displayed near the user icon. This bubble 142 may display, for example, a user greeting, status, etc. It is expected that bubble 142 will provide interactive functionality, such as displaying detailed information after the user clicks the bubble. To implement this interactive functionality, subviews 150 for handling interaction requests need to be added to the unit views; however, this may require adjusting the layout of the individual unit views within the collection view. For example, the size of the unit views needs to be adjusted so that the adjusted unit view 103' can accommodate the subview 150. However, the size of the collection view also needs to be adjusted accordingly so that the adjusted collection view 120' can accommodate the unit view 130'. Furthermore, the layout of the individual unit views within the collection view 120' also needs to be adjusted.

[0035] The above approach involves a complex adjustment process and may require modifications to the layout of various visual elements within a unit view. Therefore, a more flexible and efficient way to handle the various views in the application is desired to support the processing of interactive requests.

[0036] Summary of handling interactive requests

[0037] To at least partially address the shortcomings of the prior art, a method for processing interactive requests in an application is proposed according to an exemplary implementation of the present disclosure. Referring to Figure 2, which describes an overview of an exemplary implementation of the present disclosure, Figure 2 illustrates a block diagram 200 for processing interactive requests in an application according to some implementations of the present disclosure.

[0038] As shown in Figure 2, a subview 220 can be added to the unit view 130, and the parent view 210 of the collection view 120 can be determined. At this time, the application can include multiple views located at multiple levels, with parent-child relationships between these levels. Specifically, the multiple views can include the parent view 210 at the first level, the collection view 120 at the second level, the unit view 130 at the third level, and the subview 220 at the fourth level. During the application's operation, it can receive user interaction requests 230. It should be understood that since the subview 220 is located outside the collection view, it cannot directly receive the interaction request 230.

[0039] At this point, parent view 210 can receive the interaction request 230. In response to determining that a response procedure for the interaction request is not included in the parent view, a target view matching the interaction request 230 can be determined among multiple views (i.e., each of the parent view 210's child views). Furthermore, the interaction request 230 can be processed using the target view's response procedure.

[0040] Using the exemplary implementation of this disclosure, received interaction requests for parent view 210 can be passed to lower-level child view 220 without adjusting the position and size of the cell view or the positions and sizes of other cell views in the collection view. In this way, child views for handling interaction requests can be added to the application in a simpler and more efficient manner, thereby improving the efficiency of handling interaction requests.

[0041] Detailed process of handling interactive requests

[0042] Having described an overview of some implementations according to this disclosure, further details regarding methods for handling interactive requests in an application will be described below. Figure 3 shows a block diagram 300 illustrating the hierarchical relationship of multiple views according to some implementations of this disclosure. As shown in Figure 3, a parent-child relationship may exist between the multiple views. In descending order of hierarchy, the multiple views may include a parent view 210 at the first level, a collection view 120 at the second level, a unit view 130 at the third level, and a child view 220 at the fourth level. In this case, the collection view 120 is a child node of the parent view 210, the unit view 130 is a child node of the collection view 120, and the child view 220 is a child node of the unit view 130.

[0043] When adding subviews 220 and parent views 210 to the application, the views can be organized according to the above hierarchical relationship so that access requests for parent view 210 can be passed to subviews 220 in descending order.

[0044] In the following description, further details of adding subview 220 and parent view 210 to the application are illustrated with reference to FIG4A. FIG4A shows a block diagram 400A of the parent view according to some implementations of this disclosure. As shown in FIG4A, a subview 420 can be added to unit view 130. Subview 420 can implement the function of bubble 142 in FIG1, for presenting desired information, and the user can click on the bubble to trigger an interaction request. According to some implementations of this disclosure, the position of subview 420 can be set; for example, at least a portion of the area of ​​subview 420 can be located outside the area of ​​unit view 130. In this way, a layered visual effect of displaying bubbles and user icons can be achieved, thereby improving the interactivity and functionality of the application page.

[0045] According to some implementations of this disclosure, the initial parent view 410 of the collection view 120 can be determined. The size and position of the initial parent view 410 can be set; for example, in the initial stage, the bottom edge of the initial parent view 410 can be aligned with the bottom edge of the collection view 120, and the top edge of the initial parent view 410 can be aligned with the top edge of the collection view 120. It should be understood that although there are distances between the edges of the various views shown in the figures for clarity, the actual positions of the edges may overlap. For example, the vertical coordinates of the bottom edge of the subview, the top edge of the unit view, the top edge of the parent view, and the top edge of the collection view may be the same; that is, the edges may overlap. Alternatively and / or additionally, the vertical edges may also overlap.

[0046] According to some implementations of this disclosure, the area of ​​the parent view can be extended to include the area of ​​the child views. In this way, the interaction detection function provided in the page development toolset can be directly used to determine the interaction requests between the user and the parent view.

[0047] According to some implementations of this disclosure, the region of the collection view includes the region of the unit view. For example, the top edge of unit view 130 may coincide with the top edge of collection view 120, and at least a portion of the region of subview 420 may be located outside collection view 120. For example, subview 420 may be located outside collection view 120, or a portion of subview 420 may be located outside collection view 120. For ease of description, further details regarding the extension of the parent view are provided using the example of subview 420 being located outside collection view 120.

[0048] According to some implementations of this disclosure, the positional relationship between the area of ​​a subview and the area of ​​a unit view can be determined; based on the positional relationship, the expansion direction for expanding the area of ​​the parent view can be determined; and the area of ​​the parent view can be expanded along the expansion direction. Using some implementations of this disclosure, the parent view can be expanded in a simple and effective way, so that the area of ​​the parent view includes the area of ​​the subview.

[0049] Figure 4B shows a block diagram 400B of the extended parent view according to some implementations of this disclosure. As shown in Figure 4B, the positional relationship indicates that the subview 420 is located above the unit view 130, and the extension direction 430 can be determined to be "upward". The positions of the left, right, and bottom edges of the parent view can be kept unchanged, and the position of the top edge of the parent view can be moved upward to determine the extended parent view 440. At this time, the top edge of the extended parent view 440 can coincide with the top edge of the subview 420 so that the parent view 440 can include the entire area of ​​the subview 420.

[0050] According to some implementations of this disclosure, in determining the expansion direction based on positional relationships, at least one edge of the area of ​​the unit view can be determined based on the positional relationships; and the expansion direction can be determined based on the direction perpendicular to at least one edge. Referring again to FIG4B, the aforementioned at least one edge (e.g., the horizontal edge 440) can be determined based on the overlapping edges in the subview 420 and the unit view 130. Further, the vertical direction can be determined as the expansion direction 430. The expansion direction 430 can point from the position of the unit view to the position of the subview 420, that is, vertically upward. Using some implementations of this disclosure, the expansion direction can be determined quickly and accurately so that the area of ​​the expanded parent view 440 can include the area of ​​the subview 420.

[0051] It should be understood that although Figure 4B shows the case where subview 420 is located outside unit view 130, alternatively and / or additionally, a portion of the subview may be located within the unit view, i.e., there is an intersection between the subview and the unit view. See Figure 5 for further details, which shows a block diagram 500 of the region of a subview according to some implementations of this disclosure. As shown in Figure 5, subview 510 overlaps with unit view 130, and the top edge (edge ​​520) of unit view 130 is located within subview 510. In this case, the expansion direction can be determined based on the vertical direction of edge 520 and the direction from unit view 130 to subview 510. Subsequently, the top edge of parent view 440 can be set to overlap with the top edge of subview 510.

[0052] According to some implementations of this disclosure, in response to receiving an interaction request for a subview, the subview's response procedure is used to handle the interaction request. Specifically, for the example in Figure 5, if the interaction request is located in the overlapping area of ​​subview 510 and unit view 130, subview 510 can directly receive the interaction request and directly call the corresponding response procedure. Using some implementations of this disclosure, functions in the page development toolset can be directly invoked to handle the interaction request. If the interaction request is located outside unit view 130, the parent view 440 needs to detect the interaction request. In this way, interactive functions can be added to different locations in the application.

[0053] According to some implementations of this disclosure, a target view matching an interaction request can be determined among multiple views. Specifically, the interaction position of the interaction request within the area of ​​the parent view can be obtained; and a view matching the interaction position can be selected from multiple views as the target view. Using some implementations of this disclosure, an interaction request for a parent view can be passed to a child view used to implement the interaction function, thereby achieving the desired functionality of the application.

[0054] See Figure 6 for further details, which illustrates a block diagram 600 for determining a target view matching an interaction request according to some implementations of this disclosure. As shown in Figure 6, the interaction location 610 of the interaction request (e.g., specific coordinates within the application page) can be determined. Further, the views can be traversed hierarchically to determine the target view matching the interaction request. Specifically, it can be determined whether a response procedure for the interaction request is included in the parent view. In the context of this disclosure, since the parent view 440 was added to capture interactions with the child views, and this parent view 440 does not include its own response procedure, the determination result is "No".

[0055] According to some implementations of this disclosure, in the process of selecting a target view among multiple views, the area of ​​the view can be determined for each view among the multiple views. Specifically, the target view can be determined among the multiple views in a multi-level order. In other words, it can be determined one by one whether each subordinate view matches the interaction request. The parent view 440 can pass the interaction request to the subordinate views in the order of collection view, unit view, and subview. Using some implementations of this disclosure, it can be ensured that each subordinate view is traversed to find the subview 420 used to provide the interaction function.

[0056] According to some implementations of this disclosure, in response to determining that the interaction location is within the area of ​​a view, the view can be identified as the target view. For example, the interaction location 610 can be compared with the area of ​​the collection view 120. Since the interaction location 610 is outside the area of ​​the collection view 120, the collection view 120 does not match the interaction request. The collection view 120 can further pass the interaction request down to the lower-level unit view 130. The interaction location 610 can be compared with the area of ​​the unit view 130. Since the interaction location 610 is outside the area of ​​the unit view 130, the unit view 130 does not match the interaction request. The unit view 130 can further pass the interaction request down to the lower-level subview 420. The interaction location 610 can be compared with the area of ​​the subview 420. Since the interaction location 610 is within the area of ​​the subview 420, it can be determined that the subview 420 matches the interaction request. In other words, the target view is the subview 420, and the interaction request can be processed using the response process of the target view.

[0057] According to some implementation methods of this disclosure, response procedures can be defined in subview 510. For example, different response procedures can be invoked based on the type of interaction request. Specifically, for a "click" type interaction request, more information in the "bubble" can be presented; for a "long press" type interaction request, a message can be sent to the user corresponding to the "bubble," and so on. Using some implementation methods of this disclosure, customized response procedures can be added to the application without adjusting the position, size, and layout of the collection view and other unit views in that collection view.

[0058] According to some implementations of this disclosure, the collection view may further include another unit view located at a third level, and the method further includes: in response to receiving an interaction request for the other unit view, processing the other interaction request using the response process of the other unit view. Using some implementations of this disclosure, it is not necessary to modify the position, size, and layout of other unit views in the collection view (e.g., unit view 132 in Figure 2), but rather existing functionalities in the page development toolset can be used to handle interactions for other unit views. In this way, it is possible to support including different types of unit views in the collection view, thereby enabling the application to have richer functionality.

[0059] It should be understood that although the individual unit views in the collection view described above are arranged horizontally, alternatively and / or additionally, the individual unit views may be arranged vertically, along both vertical and horizontal directions, or randomly, as described in more detail in Figure 7. Figure 7 shows a block diagram 700 of the layout of multiple views according to some implementations of this disclosure. As shown in Figure 7, the collection view 720 may include unit views 730, 732, etc. To add interactive functionality to the unit view 730, a subview 720 may be added, and the parent view 710 of the collection view may be extended horizontally to the left. In this case, the area of ​​the parent view 710 covers the area of ​​the subview 740. Further, as described above, the parent view 710 may pass the collected interaction request to the subview 740, thereby invoking the response procedure of the subview 740 to handle the interaction request.

[0060] Alternatively and / or additionally, subviews can be added to other locations within the unit view 730. For example, a subview can be added outside the top-left corner of the unit view 730. In this case, the left and top edges of the parent view can be expanded along the direction towards the top left (i.e., both the horizontal and vertical directions are expanded). In this way, interactive areas can be added to any desired location within the application.

[0061] Using the exemplary implementation of this disclosure, received interaction requests for a parent view can be passed to lower-level child views without adjusting the position and size of the cell view or the positions and sizes of other cell views in the collection view. In this way, child views for handling interaction requests can be added to the application in a simpler and more efficient manner, thereby improving the efficiency of handling interaction requests.

[0062] Example process

[0063] Figure 8 illustrates a flowchart of a method 800 for processing interaction requests in an application according to some implementations of this disclosure. The application includes multiple views located at multiple levels, including a parent view at a first level, a collection view at a second level, a unit view at a third level, and child views at a fourth level. At block 810, an interaction request for the parent view is received. At block 820, in response to determining that a response process for the interaction request is not included in the parent view, a target view matching the interaction request is determined among the multiple views. At block 830, the interaction request is processed using the response process of the target view.

[0064] According to some implementations of this disclosure, determining the target view that matches the interaction request among multiple views includes: obtaining the interaction position of the interaction request in the area of ​​the parent view; and selecting the view that matches the interaction position from among multiple views as the target view.

[0065] According to some implementations of this disclosure, selecting a target view from multiple views includes: determining the region of a view among the multiple views; and identifying the view as the target view in response to determining that the interaction location is within the region of the view.

[0066] According to some implementations of this disclosure, determining the target view corresponding to the interaction request among multiple views includes: determining the target view among multiple views in a multi-level order.

[0067] According to some implementations of this disclosure, at least a portion of the area of ​​the subview is located outside the area of ​​the unit view, and the area of ​​the parent view is extended to include the area of ​​the subview.

[0068] According to some implementations of this disclosure, the area of ​​the collection view includes the area of ​​the unit view, and the area of ​​the parent view is extended by the following steps: determining the positional relationship between the area of ​​the child view and the area of ​​the unit view; determining the extension direction for extending the area of ​​the parent view based on the positional relationship; and extending the area of ​​the parent view along the extension direction.

[0069] According to some implementations of this disclosure, determining the expansion direction based on positional relationships includes: determining at least one edge of the region of the cell view based on positional relationships; and determining the expansion direction based on a direction perpendicular to at least one edge.

[0070] According to some implementations of this disclosure, the method further includes: in response to receiving an interaction request for a subview, processing the interaction request for the subview using the subview's response process.

[0071] According to some implementations of this disclosure, the collection view further includes another unit view located at a third level, and the method further includes: in response to receiving an interaction request for the other unit view, processing the other interaction request using the response process of the other unit view.

[0072] Example devices and equipment

[0073] Figure 9 shows a block diagram of an apparatus 900 for processing interaction requests in an application according to some implementations of the present disclosure. The application includes multiple views located at multiple levels, including a parent view at a first level, a collection view at a second level, a unit view at a third level, and a child view at a fourth level. The apparatus 900 includes: a receiving module 910 configured to receive an interaction request for the parent view; a determining module 920 configured to determine a target view matching the interaction request among the multiple views in response to determining that a response process for the interaction request is not included in the parent view; and a processing module 930 configured to process the interaction request using the response process of the target view.

[0074] According to some implementations of this disclosure, the determining module is further configured to: obtain the interaction position of the interaction request in the area of ​​the parent view; and select a view from multiple views that matches the interaction position as the target view.

[0075] According to some implementations of this disclosure, the determining module is further configured to: determine the region of a view among multiple views; and identify the view as a target view in response to determining that the interaction location is within the region of the view.

[0076] According to some implementations of this disclosure, the determining module is further configured to: determine the target view among multiple views in a multi-level order.

[0077] According to some implementations of this disclosure, at least a portion of the area of ​​the subview is located outside the area of ​​the unit view, and the area of ​​the parent view is extended to include the area of ​​the subview.

[0078] According to some implementations of this disclosure, the area of ​​the collection view includes the area of ​​the unit view, and the area of ​​the parent view is extended by the following steps: determining the positional relationship between the area of ​​the child view and the area of ​​the unit view; determining the extension direction for extending the area of ​​the parent view based on the positional relationship; and extending the area of ​​the parent view along the extension direction.

[0079] According to some implementations of this disclosure, determining the expansion direction based on positional relationships includes: determining at least one edge of the region of the cell view based on positional relationships; and determining the expansion direction based on a direction perpendicular to at least one edge.

[0080] According to some implementations of this disclosure, the processing module is further configured to: in response to receiving an interaction request for a subview, process the interaction request for the subview using the subview's response process.

[0081] According to some implementations of this disclosure, the collection view further includes another unit view located at the third level, and the processing module is further configured to: in response to receiving an interaction request for the other unit view, process the other interaction request using the response process of the other unit view.

[0082] Figure 10 shows a block diagram of a device 1000 capable of implementing various implementations of the present disclosure. It should be understood that the computing device 1000 shown in Figure 10 is merely exemplary and should not constitute any limitation on the functionality and scope of the implementations described herein. The computing device 1000 shown in Figure 10 can be used to implement the methods described above.

[0083] As shown in Figure 10, the computing device 1000 is in the form of a general-purpose computing device. Components of the computing device 1000 may include, but are not limited to, one or more processors or processing units 1010, memory 1020, storage devices 1030, one or more communication units 1040, one or more input devices 1050, and one or more output devices 1060. The processing unit 1010 may be a physical or virtual processor and is capable of performing various processes according to programs stored in memory 1020. In a multiprocessor system, multiple processing units execute computer-executable instructions in parallel to improve the parallel processing capability of the computing device 1000.

[0084] Computing device 1000 typically includes multiple computer storage media. Such media can be any available media accessible to computing device 1000, including but not limited to volatile and non-volatile media, removable and non-removable media. Memory 1020 can be volatile memory (e.g., registers, cache, random access memory (RAM)), non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. Storage device 1030 can be removable or non-removable media and may include machine-readable media, such as flash drives, disks, or any other media capable of storing information and / or data (e.g., training data for training) and accessible within computing device 1000.

[0085] The computing device 1000 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not shown in FIG. 10, disk drives for reading from or writing to removable, non-volatile disks (e.g., "floppy disks") and optical disk drives for reading from or writing to removable, non-volatile optical disks may be provided. In these cases, each drive may be connected to a bus (not shown) via one or more data media interfaces. The memory 1020 may include a computer program product 1025 having one or more program modules configured to perform various methods or actions of various implementations of this disclosure.

[0086] The communication unit 1040 enables communication with other computing devices via a communication medium. Additionally, the components of the computing device 1000 can function as a single computing cluster or multiple computing machines capable of communicating via communication connections. Therefore, the computing device 1000 can operate in a networked environment using logical connections to one or more other servers, network personal computers (PCs), or another network node.

[0087] Input device 1050 can be one or more input devices, such as a mouse, keyboard, trackball, etc. Output device 1060 can be one or more output devices, such as a monitor, speaker, printer, etc. Computing device 1000 can also communicate with one or more external devices (not shown) via communication unit 1040 as needed. These external devices include storage devices, display devices, etc., and can communicate with one or more devices that enable user interaction with computing device 1000, or with any device (e.g., network card, modem, etc.) that enables computing device 1000 to communicate with one or more other computing devices. Such communication can be performed via input / output (I / O) interface (not shown).

[0088] According to exemplary implementations of this disclosure, a computer-readable storage medium is provided that stores computer-executable instructions thereon, wherein the computer-executable instructions are executed by a processor to implement the methods described above. According to exemplary implementations of this disclosure, a computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, which are executed by a processor to implement the methods described above. According to exemplary implementations of this disclosure, a computer program product is provided that stores a computer program thereon, which, when executed by a processor, implements the methods described above.

[0089] Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatuses, devices, and computer program products implemented according to this disclosure. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0090] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processing unit of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0091] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions that execute on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0092] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing the specified logical function. In some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0093] Various implementations of this disclosure have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is chosen to best explain the principles, practical applications, or improvements to technology in the market, or to enable others skilled in the art to understand the various implementations disclosed herein.

Claims

1. A method for processing interactive requests in an application, the application comprising multiple views located at multiple levels, the multiple views including a parent view at a first level, a collection view at a second level, a unit view at a third level, and a child view at a fourth level, the method comprising: Receive interaction requests for the parent view; In response to determining that a response process for the interaction request is not included in the parent view, a target view matching the interaction request is determined among the plurality of views; as well as The interaction request is processed using the response process of the target view.

2. The method of claim 1, wherein determining the target view matching the interaction request among the plurality of views comprises: Obtain the interaction location of the interaction request within the area of ​​the parent view; as well as Select the view that matches the interaction location from the plurality of views, and use it as the target view.

3. The method of claim 2, wherein selecting the target view from the plurality of views comprises: For each of the multiple views, determine the region of that view; as well as In response to determining that the interaction location is within the area of ​​the view, the view is identified as the target view.

4. The method of claim 1, wherein determining, among the plurality of views, the target view that corresponds to the interaction request comprises: The target view is determined from among the multiple views in the order of the multiple levels.

5. The method of claim 1, wherein at least a portion of the region of the subview is located outside the region of the unit view, and the region of the parent view is extended to include the region of the subview.

6. The method of claim 5, wherein the region of the collection view includes the region of the unit view, and the region of the parent view is expanded by the following steps: Determine the positional relationship between the region of the subview and the region of the unit view; Based on the positional relationship, determine the expansion direction of the area used to expand the parent view; as well as Expand the area of ​​the parent view along the expansion direction.

7. The method of claim 6, wherein determining the expansion direction based on the positional relationship comprises: Based on the positional relationship, at least one edge of the region of the unit view is determined; as well as The expansion direction is determined based on the direction perpendicular to the at least one edge.

8. The method of claim 1, further comprising: In response to receiving an interaction request for the subview, the interaction request for the subview is processed using the subview's response procedure.

9. The method of claim 1, wherein the collective view further comprises another unit view at the third level, and the method further comprises: In response to receiving an interaction request for the other unit view, the other interaction request is processed using the response process of the other unit view.

10. An apparatus for processing interactive requests in an application, the application comprising a plurality of views located at multiple levels, the plurality of views including a parent view at a first level, a collection view at a second level, a unit view at a third level, and a child view at a fourth level, the apparatus comprising: A receiving module is configured to receive interaction requests for the parent view; A determination module is configured to determine a target view matching the interaction request among the plurality of views in response to determining that a response process for the interaction request is not included in the parent view; as well as The processing module is configured to process the interaction request using the response process of the target view.

11. An electronic device, comprising: At least one processing unit; as well as At least one memory, coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, which, when executed by the at least one processing unit, cause the electronic device to perform the method according to any one of claims 1 to 9.

12. A computer-readable storage medium having a computer program stored thereon, the computer program causing the processor to implement the method according to any one of claims 1 to 9 when executed by a processor.

13. A computer program product comprising a computer program, wherein the computer program, when executed by a processor, implements the method according to any one of claims 1 to 9.

Images