A navigation tree view management method, device, equipment and storage medium

Abstract

Embodiments of the present disclosure provide a navigation tree view management method and device, equipment and a medium. The method displays an object making interface of a target object making tool, the object making interface includes a navigation tree view, a root component set displayed in the navigation tree view represents an object content category of the target object, and a sub-component set under the root component set belongs to the object content category; an interactive operation acting on the object making interface is received; when the interactive operation meets a set division update condition in the navigation tree view, a target sub-component set associated with the interactive operation is updated, and / or a root component set to which the target sub-component set belongs is updated and displayed on the navigation tree view. By using the method, the problem of inaccurate classification caused by manual division of component sets in the existing navigation tree view can be solved, accurate division of the classification to which the component set belongs is realized, the learning cost of the designer is reduced, and the accuracy and correctness of the navigation tree view are ensured.

Description

Technical Field

[0001] This disclosure relates to the field of computer application technology, and in particular to a method, apparatus, device, and storage medium for managing a navigation tree view. Background Technology

[0002] With the development of computer technology, designers can use visual interface design tools or special effects / scene creation tools to create interfaces, special effects / scenes, etc. Generally, when designing / creating a target object (such as an interface, special effects, or scene), it is often necessary to construct the component data involved in the creation of the target object.

[0003] Current creation tools allocate the constructed component data to appropriate component sets, and construct a tree structure for component sets with parent-child relationships. Component sets without parent nodes are recorded as the root component sets in the tree structure. Thus, the target object being created can be considered to consist of multiple root component sets and their contained child component sets. Furthermore, multiple root set sets and their child component data sets can be presented as navigation information for the target object in the navigation box on the creation interface, forming a navigation tree view.

[0004] In practical applications, the resulting interfaces, special effects, or scenes often contain rich content, resulting in a relatively large number of component data sets. To ensure that the numerous component data sets constituting the target object are organized and managed according to a certain paradigm, the component data sets can be divided based on the categories of the content contained in the target object. For example, component data sets representing content of type A objects can be grouped together, and component data sets representing content of type B objects can be grouped together, etc. This facilitates better support for the rendering and presentation of the target object's content.

[0005] However, the division and management of the aforementioned component data sets are primarily implemented manually by designers. The entire classification process is highly dependent on the individual designer's behavior and cannot guarantee the accuracy of the component data set classification. When the completed target objects are delivered to a system for runtime, if the system intends to uniformly process component data sets containing a certain type of object content, runtime problems will arise due to the incorrect division of the component data sets. Summary of the Invention

[0006] This disclosure provides a method, apparatus, device, and storage medium for managing navigation tree views, so as to achieve effective management of navigation tree views involved in the object creation process.

[0007] In a first aspect, embodiments of this disclosure provide a method for managing a navigation tree view, the method comprising:

[0008] The object creation interface of the target object creation tool is displayed. The object creation interface includes a navigation tree view. The root component set displayed in the navigation tree view represents the object content category of the target object. The sub-component set under the root component set belongs to the object content category.

[0009] Receive interactive operations performed on the object creation interface;

[0010] When the interactive operation satisfies the set partitioning update condition in the navigation tree view, update the target sub-component set associated with the interactive operation, and / or update the root component set to which the target sub-component set belongs, and display it on the navigation tree view.

[0011] Secondly, embodiments of this disclosure also provide a management device for a navigation tree view, the management device for the navigation tree view comprising:

[0012] The interface display module is used to display the object creation interface of the target object creation tool. The object creation interface includes a navigation tree view. The root component set displayed in the navigation tree view represents the object content category of the target object, and the sub-component set under the root component set belongs to the object content category.

[0013] An operation receiving module is used to receive interactive operations performed on the object creation interface.

[0014] The view display module is used to update the target sub-component set associated with the interactive operation when the interactive operation satisfies the set partitioning update condition in the navigation tree view, and / or update the root component set to which the target sub-component set belongs, and display it on the navigation tree view.

[0015] Thirdly, embodiments of this disclosure also provide an electronic device, the electronic device comprising:

[0016] One or more processors;

[0017] Storage device for storing one or more programs.

[0018] When the one or more programs are executed by the one or more processors, the one or more processors implement the navigation tree view management method as described in any embodiment of the present invention.

[0019] Fourthly, embodiments of this disclosure also provide a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform a navigation tree view management method as described in any embodiment of the present invention.

[0020] This disclosure provides a method, apparatus, device, and storage medium for managing a navigation tree view. First, it can display an object creation interface for creating target objects. The object creation interface includes a navigation tree view, and the root component set displayed in the navigation tree view represents the object content category of the target object. The sub-component sets under the root component set all belong to the same object content category. Then, it can receive interactive operations performed on the object creation interface. When the interactive operation satisfies the set partitioning update conditions in the navigation tree view, it can update the target sub-component set associated with the interactive operation, and also update the root component set to which the target sub-component set belongs, ultimately presenting it on the navigation tree view. This embodiment provides a management method for a navigation tree view, specifically adjusting the representation of the root component set presented in the navigation tree view. This differs from existing methods that select a root component set from multiple component sets and manually classify and assign component data to the same category of object content. This technical solution directly adds root component sets representing different object content categories, and the sub-component sets contained under each root component set can be considered to belong to the represented object content category. Meanwhile, this technical solution also automatically adjusts the content category of the component set. Unlike existing methods that manually adjust the category of a component set, this solution automatically determines and updates the target sub-component set associated with the interaction when the interaction meets the update conditions for component set division in the navigation tree view. It also updates the root component set to which the target sub-component set belongs and displays it in the navigation tree view. This solution solves the problem of inaccurate component classification caused by manual component set division in existing navigation tree views, achieving precise classification of component sets, effectively reducing the learning cost for designers, ensuring the accuracy of the navigation tree view, and improving the correctness of subsequent operation. Attached Figure Description

[0021] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0022] Figure 1 A flowchart illustrating a method for managing a navigation tree view according to an embodiment of this disclosure is provided;

[0023] Figure 1a A diagram showing the effect of a tree-structured collection of components in a conventional navigation tree view is provided.

[0024] Figure 1bA diagram showing the display effect of a navigation tree view presented in a navigation tree view management method provided in an embodiment of this disclosure is given.

[0025] Figure 1c The present invention provides a display diagram of the navigation tree view updated based on interactive operation in the navigation tree view management method provided in the embodiments of this disclosure;

[0026] Figure 2 A flowchart illustrating a method for managing a navigation tree view according to an embodiment of this disclosure is provided;

[0027] Figure 3 A schematic diagram of the structure of a navigation tree view management device provided in an embodiment of this disclosure is given;

[0028] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure is given. Detailed Implementation

[0029] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments 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 embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0030] It should be understood that the steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect.

[0031] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.

[0032] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0033] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0034] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0035] 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 in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0036] 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.

[0037] As an optional but non-limiting implementation, in response to a user's active request, sending a prompt message to the user can be done 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 "agree" or "disagree" to provide personal information to the electronic device.

[0038] 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.

[0039] 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.

[0040] It's important to note that when building games, animations, and simulations, interface design tools or special effects creation tools are often used to construct the interface or effects. Generally, these tools provide designers with a visual interface and generate component data for the target object. Designers can categorize numerous components into corresponding sets by dragging and dropping them in a navigation tree. Subsequent processing is based on these categorized sets, allowing for different types of processing to achieve the desired effect. However, this categorization relies on the designer's subjective judgment of the component data. After the designer's actions, the tool does not check or correct the category to which the component data belongs. Incorrect judgment by the designer can lead to problems in subsequent operation.

[0041] Based on this, this embodiment provides a method for managing a navigation tree view based on interactive operations. Figure 1 A flowchart illustrating a navigation tree view management method provided in this disclosure is given. This disclosure is applicable to situations where navigation tree views are automatically managed based on interactive operations. The method can be executed by a navigation tree view management device, which can be implemented in software and / or hardware, and optionally, through an electronic device.

[0042] like Figure 1 As shown, the method in this embodiment may specifically include:

[0043] S101. Display the object creation interface of the target object creation tool. The object creation interface includes a navigation tree view. The root component collection displayed in the navigation tree view represents the object content category of the target object, and the sub-component collection under the root component collection belongs to the object content category.

[0044] In this embodiment, the target object creation tool can be a tool that creates target objects such as special effects and scenes through a visual interface. The target object can be a game scene, multimedia data effects, etc. Accordingly, the target object creation tool can be a tool for creating game scenes; or it can be a tool for creating special effects in multimedia data (such as long / short videos, images, etc.). The object creation interface can be a visual interactive interface used for creating target objects, and this object creation interface includes a navigation tree view.

[0045] In this embodiment, the navigation tree view can be considered as a view bar that visualizes the component data upon which the target object depends. Generally, the navigation tree view can be empty. As component data is continuously added during the creation process, the amount of component data-related information (such as component data names or other component data labels) contained in the navigation tree view gradually increases. The navigation tree view displays component data information with interrelationships (tree structure). For example, the navigation tree view contains multiple root component sets, each root component set contains multiple child component sets, and each child component set contains multiple component data names, etc. As the target object is created, the navigation tree view is presented in a tree structure.

[0046] For example, Figure 1a A diagram illustrating the tree-structured collection of components in a typical navigation tree view is provided. For example... Figure 1a As shown, the first navigation tree view 11 contains multiple first root component sets 12, each root component set belonging to a related first sub-component set 13. Each first sub-component set 13 can also include new sub-component sets continuously added as the target object is created. Figure 1a In the conventional navigation tree view shown, whether it is the root component collection or the child component collection, they all correspond to the first component data 14 involved in the creation of the target object. The component data contained in the first root component collection 12 is essentially no different from other component collections.

[0047] In this embodiment, the content displayed in the navigation tree view gradually increases as the target object is created, and the displayed content is also presented in a tree structure, which can contain multiple root component sets, each of which can contain sub-component sets, etc. Unlike existing conventional navigation tree view presentations, the root component set in the navigation tree view presented in this embodiment only represents one type of object content category and does not include component data involved in the creation of the target object. However, the sub-component sets under the root component set still correspond to the component data involved in the creation of the target object, and it can also be considered that all sub-component sets under the root component set belong to the object content category represented by the root component set.

[0048] In this embodiment, the object content category can be considered as the result of dividing all object content included in the target object according to a set category classification method. The root component set can include multiple sub-component sets, and all its sub-component sets can be considered to belong to the object content category corresponding to the root component set. For example, when the target object is a scene, and the scene includes five object contents—pedestrians, cars, trucks, trees, grass, and flowers—the corresponding object content category can be plants, people, and vehicles. When the target object is a special effect, and the effect sets different colors and brightness for different areas of the face, the corresponding object content category can be color and brightness.

[0049] For example, Figure 1b The diagram shows the display effect of the navigation tree view presented in the navigation tree view management method provided in this embodiment. For example... Figure 1b As shown, the second navigation tree view 15 also contains multiple second root component sets 16, and each second root component set 16 can also contain multiple second sub-component sets 17. Unlike existing navigation tree views, each second root component set 16 in this navigation tree view 15 represents a type of object content content contained in the target object, and each second component set 16 corresponds only to the component data representing that object content type.

[0050] What we can know is that, with Figure 1a compared to, Figure 1b The second root component set 16 represents a type of object content category of the target object, while the second sub-component set 17 displayed under the second root component set 16 is equivalent to... Figure 1a The first root component set 12, the second child component set 17, and the child component set 171 contained within it, can be equivalent to... Figure 1a The first sub-component set is 13. It can be seen that, unlike the construction of the navigation tree in a conventional navigation tree view, the management of the navigation tree view provided in this embodiment has adjusted the structure of the displayed navigation tree. At the display level, labels for different object content categories of the target object have been added for the automatic classification and division of component data.

[0051] S102, Receive interactive operations performed on the object creation interface.

[0052] In this embodiment, when creating the target object, the designer can perform various interactive operations on the object creation interface. This step can receive various interactive operations performed on the object creation interface. This embodiment can achieve interaction with the designer through buttons or controls provided on the object creation interface.

[0053] The interactive operation can be considered as any interactive operation involved in the creation of the target object, such as adding components involved in object creation, clicking, dragging, and changing component data parameters on the content displayed in the navigation tree view. This interactive operation can be applied to any location on the object creation interface; it can be an interactive control, such as a component addition button, or a blank area, such as a right-click on a blank area to display a menu item, or data information of a component or a collection of components in the displayed navigation tree view. This embodiment can receive the generated interactive operation by listening to the information input by the designer.

[0054] S103. When the interactive operation satisfies the set partitioning update condition in the navigation tree view, update the target sub-component set associated with the interactive operation, and / or update the root component set to which the target sub-component set belongs, and display it on the navigation tree view.

[0055] In this embodiment, different interactive operations often act on different objects, and the operation behavior events performed relative to the interactive object are also different. This embodiment can determine whether the interactive operation received in the above steps meets the set partitioning update conditions in the navigation tree view by analyzing the interactive operation. When the conditions are met, the target sub-component set involved in the interactive operation on the navigation tree view can be updated. At the same time, the root component set to which the target sub-component set belongs can also be updated, and the updated result can be displayed on the navigation tree view.

[0056] It's important to understand that existing methods may result in changes to the root component set to which a set of child components belongs after an interaction, and these root component sets may differ only slightly. Designers may not be able to accurately determine the root component set to which a set of child components belongs after an interaction. The navigation tree view management method provided in this embodiment effectively achieves the division of the child component set into the root component set involved in the interaction.

[0057] First, considering that this embodiment involves the management of a navigation tree view, it is necessary to analyze the interactive operations to determine whether they can trigger the management of the navigation tree view. For example, if the target of the received interactive operation is unrelated to the navigation tree view, it can be considered that the interactive operation cannot trigger the management logic of the navigation tree view. Specifically, to execute this step, it is first necessary to determine whether the target of the interactive operation and / or the operation behavior event can trigger the execution of the navigation tree view management logic. For example, if it is determined that the operation behavior event belongs to a navigation tree operation behavior, it can be determined that at least the triggering of navigation tree management is currently satisfied.

[0058] As described above, when an interactive action is determined to be a navigation tree action, it can be further determined whether the action type (e.g., add, delete, or modify) satisfies the requirement to update the collection of components in the navigation tree view. Ultimately, if the action type belongs to a certain defined action type, it can be determined that the interactive action satisfies the collection partitioning update condition in the navigation tree view.

[0059] It is important to understand that the fact that an interactive operation satisfies the set partitioning and updating conditions in the navigation tree view mainly means that only the set of components affected by the interactive operation's action event has the conditions for set partitioning and updating. The set that meets the conditions is often a set of one or more sub-components in the navigation tree view. Therefore, only the set of one or more sub-components affected by the interactive operation participates in the partitioning and updating of the sub-component set. In this embodiment, the set of one or more sub-components affected by the interactive operation can be identified as the target sub-component set associated with the interactive operation.

[0060] The updating of the target sub-component set, and the updating of the root component set to which the target sub-component set belongs, involve different objects and methods of updating depending on the different operation behavior events corresponding to the interactive operation. For example, when the interactive operation is analyzed as an operation to add new component data, the relevant information of the new component data (object label information) can be directly added to the existing sub-component set in the navigation tree view to update the target sub-component set;

[0061] As described above, for updating the root component set to which the target sub-component set belongs, one update implementation is that the target sub-component set remains unchanged and belongs to its original root component set; another update implementation is that, according to a pre-given root component set partitioning strategy, a new root component set is determined for the target sub-component set, and when the new root component set is already displayed in the navigation tree view, the target sub-component set can be moved from its original root component set to the newly determined root component set.

[0062] Another update implementation is to first construct the newly determined root component set in the navigation tree view when the newly determined root component set does not yet exist in the navigation tree view, and then move the target child component set from its original root component set to the newly determined root component set.

[0063] For example, in order to facilitate understanding of the solution provided by the present invention, in Figure 1b Based on the displayed navigation tree view, taking the received interaction operation as an example of modifying component data 5, Figure 1cThe present invention provides a display diagram of the updated navigation tree view based on interactive operation in the navigation tree view management method provided in the embodiments of this disclosure.

[0064] like Figure 1c As shown, the system receives an interactive operation that modifies component data 5 in the object creation interface. This interactive operation is a type of navigation tree operation that triggers navigation tree actions, and the corresponding operation type is a modification operation, belonging to the setting operation type. Therefore, the set partitioning update condition in the navigation tree view is met, thus determining that the sub-component set corresponding to component data 5 is B1. The original root component set to which sub-component set B1 belonged was B. After judging the component data included in sub-component set B1 using a pre-defined root component set partitioning strategy, it is determined that the sub-component set B1 after the interactive operation should belong to root component set A, which is different from its original root component set B. Therefore, sub-component set B1 is moved to root component set A. The final displayed navigation tree view is shown in the third navigation tree view. Figure 1b Comparing the second navigation tree view in the middle, it can be seen that the second child component collection B1 consists of... Figure 1b The subcomponent set belonging to the root component set B is changed to belong to the root component set A, which realizes the automatic division of the subcomponent set after the interaction operation and ensures the accuracy of the position of each subcomponent set in the navigation tree view.

[0065] It can be seen that the navigation tree characteristics presented by the navigation tree view in this embodiment meet the display requirements after performing the above steps. That is, the navigation tree view can be managed by performing the above steps, so that each root component set in the presented navigation tree view is used to represent the object content category of the target object, and the sub-component sets contained under each root component set are the collections of component data involved in the creation of the target object, and all belong to the object content category represented by the root component set.

[0066] This embodiment provides a method for managing a navigation tree view, essentially offering a management approach. Specifically, it adjusts the representation of the root component set presented in the navigation tree view, differing from existing methods that select a root component set from multiple component sets and manually categorize and assign component data to objects of the same type. This embodiment directly adds root component sets representing different object content categories, and the sub-component sets contained under each root component set can be considered to belong to the represented object content category. This embodiment also automatically adjusts the object content category to which a component set belongs. Unlike existing methods that manually adjust the category of a component set, this technical solution can automatically determine and update the target sub-component set associated with the received interactive operation when the interactive operation meets the update conditions for component set division in the navigation tree view. Simultaneously, it can also update the root component set to which the target sub-component set belongs and display it on the navigation tree view. This technical solution solves the problem of inaccurate component classification caused by manually dividing component sets in existing navigation tree views. It achieves accurate classification of component sets, effectively reducing the learning cost for designers, while ensuring the accuracy of the navigation tree view and improving the correctness of subsequent operation.

[0067] It should be noted that the reason why the above-mentioned technical solution in this embodiment can update the navigation tree view based on the interactive operation of the object creation interface at the visualization level can be considered as being based on the underlying logic provided for the target object creation tool. This embodiment is equivalent to improving the underlying logic of the target object creation tool. Specifically, it can optimize the target object creation tool by constructing a set of strategies and interfaces for updating the navigation tree view, so that the target object creation tool can respond to the provided strategies and interfaces.

[0068] Considering that not all interactive operations will affect the updating of the navigation tree view, firstly, we can provide criteria for judging the operation type corresponding to the interactive operation, so as to determine whether the interactive operation can trigger the management of the navigation tree view; secondly, we can obtain different classifications for different object content categories, and provide corresponding judgment strategies for different categories, so as to form a set of judgment strategies corresponding to all object content categories, thereby providing a standard for object content category division when updating the navigation tree view; we can also optimize the content displayed in the navigation tree view to display the root component set corresponding to the object content category, and encapsulate the included specifications and strategies to form the corresponding interface form.

[0069] Based on the above embodiments, the determination step for whether the interactive operation satisfies the set partitioning update condition in the navigation tree view can be optimized as follows:

[0070] a1) Analyze the interactive operation and determine the corresponding operation behavior event.

[0071] In this embodiment, an operation behavior event can be understood as the behavior corresponding to changes in data within the object creation tool caused by an interactive operation. For example, if the interactive operation is clicking the plus button corresponding to the root component collection, then the operation behavior event corresponds to adding a new root component collection.

[0072] Specifically, a relationship table between each interactive operation and its corresponding operation behavior event can be established in advance. The processor can parse the received interactive operation and determine the operation behavior event corresponding to the interactive operation through the relationship table.

[0073] b1) If the action event exists in the pre-built navigation tree action event set, then determine the action type to which the action event belongs.

[0074] In this embodiment, the navigation tree operation behavior set can be understood as the set of all operation behavior events in the object creation tool that affect the navigation tree. Operation type can be understood as the type that affects the set in the navigation tree, such as add, delete, modify, query, and other types.

[0075] Specifically, the processor can compare the operation behavior event with each navigation tree operation behavior included in the navigation tree operation behavior set. If the operation behavior event exists in the pre-built navigation tree operation behavior set, the operation type to which the operation behavior event belongs can be determined according to the pre-determined association table between operation behavior events and operation types.

[0076] For example, behavioral events can include actions such as adding, deleting, copying, dragging, instantiating models, instantiating prefabs, and modifying parameters on any set in the navigation tree. Operation types can include add, delete, modify, and other types. Specifically, adding, copying, instantiating models, and instantiating prefabs are add types; deleting is a delete type; and modifying parameters and dragging are modify types.

[0077] c1) If the operation type belongs to the set operation type, then determine that the interaction operation satisfies the set partition update condition in the navigation tree view.

[0078] In this embodiment, setting the operation type can be understood as the judgment criteria corresponding to the operation that will affect the change of the collection position in the navigation tree.

[0079] Specifically, the operation type corresponding to the operation that will affect the change of the collection position in the navigation tree can be determined in advance and set as the set operation type. Then the processor can determine whether the operation type belongs to the set operation type. If the operation type belongs to the set operation type, it is determined that the interaction operation meets the collection partitioning update condition in the navigation tree view.

[0080] For example, the operation type can include adding data, deleting data, and modifying data. In one example, the interactive operation is querying the collection using a query control; the corresponding operation event is a query operation, and the corresponding operation type is a query type. This operation type does not belong to the set operation type, so the collection partitioning update condition in the navigation tree view is not met. In another example, the interactive operation is adding to the collection using a plus button; the corresponding operation event is an add operation, and the corresponding operation type is an add type. This operation type belongs to the set operation type, so the collection partitioning update condition in the navigation tree view is met.

[0081] The above-mentioned technical implementation in this step provides the judgment logic and basis for determining whether the component set needs to be updated based on interactive operations. It realizes the automation of judging whether the interactive operation meets the set partitioning update conditions, and can be used as the basis for condition judgment in the encapsulation, providing underlying support for the management of the upper-level navigation tree view.

[0082] As a first optional embodiment of the present disclosure, based on the above embodiments, the first optional embodiment can further optimize the navigation tree view so that the sub-component set under the root component set includes component label information, and each component label information is associated with a component data.

[0083] In this embodiment, each root component set displayed on the navigation tree view can be considered to contain component tag information in its sub-component sets. Each component tag information corresponds to a component data, and each component data can be considered to be the data content of the relevant components involved in the creation of the target object.

[0084] It is understandable that after the target object is created and a component data is added or constructed, the relevant attribute information of the component data can be used to determine which root component set and which sub-component set the component data should belong to. In this embodiment, the component tag information representing the component data can be presented under the sub-component set to which the root component set belongs. The component tag information can be considered as key information for distinguishing component data, and this component tag information is preferably the component name information of the component data.

[0085] Based on the above optimizations, before updating the target sub-component set associated with the interactive operation and / or updating the root component set to which the target sub-component set belongs, this first optional embodiment may further optimize the following steps:

[0086] It should be noted that, through the execution of the steps provided in the above embodiments, it can be considered that the steps added in this optional embodiment can be specifically executed after the interactive operation satisfies the set partitioning update condition in the navigation tree view, and before updating the target sub-component set associated with the interactive operation, and / or before updating the root component set to which the target sub-component set belongs.

[0087] a2) The component data involved in the interaction operation after the response is determined as the target component data.

[0088] Specifically, in this embodiment, as long as an interactive operation is received, the associated operation behavior event can be responded to, and the response to the operation behavior event involves updating at least one component's data. In this embodiment, the component data involved after the interactive operation response is determined to be the target component data.

[0089] b2) Obtain the target component tag information corresponding to the target component data, and determine the set of sub-components containing the target component tag information as the target sub-component set.

[0090] In this embodiment, considering that the interactive operation satisfies the set partitioning update condition in the navigation tree view, it can be assumed that the component data involved after its response is essentially associated with the component tag information in at least one sub-component set in the navigation tree view. Therefore, this embodiment can regard the component tag information associated with the target component data as its associated target component tag information within the navigation tree view. This step can obtain the target component tag information.

[0091] It can be seen that after determining that the target component data has corresponding target component label information in the navigation tree view, the set of sub-components to which the target component label information belongs in the navigation tree view can be further determined. This step can determine the set of sub-components as the target sub-component set.

[0092] For example, the interactive operation event is to change the brightness of the face from a1 to a12. The brightness can be used as the target component data, and the specific brightness value is changed to a12. In the navigation tree view, the set of sub-components whose brightness is a1 and which is associated with the component label information can be used as the target sub-component set.

[0093] The first optional embodiment described above provides an implementation for determining the target sub-component set associated with an interactive operation. This embodiment is equivalent to first deducing, based on the component data involved in the interactive operation, which specific target sub-component set to be updated is associated with the interactive operation. Through the technical solution provided by this first optional embodiment, the effective positioning of the target sub-component set is achieved, providing basic data support for the management of the navigation tree view in this embodiment.

[0094] As a second optional embodiment of this example, based on the above embodiment, this second optional embodiment can further specify the updating of the target sub-component set associated with the interactive operation, and / or the updating of the root component set to which the target sub-component set belongs, into the following steps:

[0095] a3) Update the target component tag information contained in the target sub-component set, wherein the target component tag information is associated with the target component data involved after the interaction operation response.

[0096] In this embodiment, updating the target sub-component set can specifically be an update of the target component label information, wherein the target component label information is associated with the target component data involved after the interactive operation response.

[0097] In this embodiment, all component data added or constructed during the creation of the target object is associated with a component tag information. Therefore, the target component data also has component tag information, which is denoted as the target component tag information in this embodiment. Considering that the sub-component sets under the root component set in the navigation tree view mainly include component tag information, updating the target component tag information is equivalent to updating the sub-component sets.

[0098] For example, updating the target component tag information can be done by adding the target component tag information to the target sub-component collection, deleting the target component tag information, or updating the content of the component data associated with the target component tag information.

[0099] And / or, b3) update the target sub-component set to the determined target root component set according to the pre-built object content category partitioning strategy set.

[0100] In this embodiment, the collection of sub-components in the navigation tree view exists under the collection of root components. Based on the above description, each root component collection in the navigation tree view represents a content category of the target object. Therefore, this embodiment can automatically categorize sub-component collections according to their respective root component collections.

[0101] As described above, for the target sub-component, after the target sub-component set itself is updated, the object content category to which the target sub-component set belongs may also change accordingly. In this embodiment, it is necessary to update the root component set to which the target sub-component set belongs in order to achieve automatic classification of the updated target sub-component set to the correct object content category.

[0102] For example, this embodiment can use a pre-built set of object content category classification strategies to determine the target root component set to which the target sub-component set should belong after the update, and update the target sub-component set to the target root component set.

[0103] In this embodiment, the object content category classification strategy set can be understood as a strategy used to determine the object content category to which a component set belongs. Each object content category corresponds to one object content category classification strategy, and these strategies are mutually orthogonal. The mutual orthogonality between the object content category classification strategies can be understood as the fact that the judgment conditions used for object category classification within each strategy are different from one another.

[0104] In one implementation of determining the target root component set, the information to be determined corresponding to the target sub-component set can be compared sequentially with each object content category classification strategy in the pre-built object content category classification strategy set to determine which object content category classification strategy matches the target sub-component set. The object content category corresponding to the matching object content category classification strategy can be used as the object content category to which the target sub-component set is reassigned after the update. In this embodiment, the root component set corresponding to the object content category can be used as the target root component set of the target sub-component set.

[0105] The technical solution provided in the above embodiments gives a specific update implementation when the interactive operation satisfies the set partitioning update conditions in the navigation tree view. It includes updating the target sub-component set and updating the target root component set to which the target sub-component set belongs. This avoids the inaccuracy in component classification caused by manually partitioning component sets in existing navigation tree views, achieving accurate classification of component sets, effectively reducing the learning cost for designers, while ensuring the accuracy of the navigation tree view and improving the correctness of subsequent operation.

[0106] Based on the second optional embodiment, the third optional embodiment can further specify the updating of the target sub-component set to the determined target root component set according to the pre-built object content category division strategy set as follows:

[0107] b31) Obtain the first root component set to which the target sub-component set belongs before the update.

[0108] In this embodiment, the first root component set can be understood as the root component set to which the target sub-component set belongs before the object content category is determined, i.e., before the target sub-component set is updated. This first root component set can be the initial root component set to which the target sub-component set belongs when it is initially presented in the navigation tree view; it can also be the previous root component set to which it belonged after the previous root component set update in the navigation tree view before the current root component update; or it can be a historical root component set to which the target sub-component set pre-assigned its historical affiliation according to a set algorithm.

[0109] b32) Based on the object content category, divide the strategy set and determine the second root component set to which the target sub-component set belongs after the update.

[0110] In this embodiment, the second root component set can be understood as the root component set to which the target sub-component set belongs after being divided by the object content category division strategy set.

[0111] Specifically, the execution entity of the method provided in this embodiment can compare the target sub-component set with each object content category classification strategy in the pre-built object content category classification strategy set in turn, determine the object content category classification strategy that the target sub-component set conforms to, obtain the object content category to which the target sub-component set belongs, and then determine the second root component set corresponding to the object content category.

[0112] b33) Determine the target root component set from the first root component set and the second root component set, and update the target sub-component set to the target root component set.

[0113] In this embodiment, there are several possible scenarios for the target root component set to which the target sub-component set ultimately belongs: the first scenario is that the first root component set and the second root component set are the same root component set; the second scenario is that the first root component set and the second root component set are different root component sets, but the second root component set has not yet appeared in the navigation tree view; and the third scenario is that the first root component set and the second root component set are different root component sets, and the second root component set has not yet appeared in the navigation tree view.

[0114] The methods for determining the target root component set and updating the target child component set to their respective target root component set differ depending on the different scenarios described above. For example, in the first scenario, the target root component set is the first root component set. In this case, there is no need to change the root component set to which the target child component set belongs; it can remain in the first root component set.

[0115] In the second case described above, the target root component set should be the second root component set. In this case, since the second root component set does not exist in the navigation tree view, it is necessary to first construct the second root component set and add it to the navigation tree view, and then move the target sub-component set from the first root component set to the target root component set.

[0116] In the third case described above, the target root component set is also the second root component set. Since the second root component set already exists in the navigation tree view, there is no need to construct the second root component set in the navigation tree view. The target sub-component set can be directly moved from the first root component set to the target root component set.

[0117] The above technical solution in this embodiment provides a specific implementation for updating the target sub-component set to the determined target root component set, and clarifies the conditional restrictions on the updating of the target sub-component set to its corresponding target root component set. This better achieves the automatic division of the sub-component set into its corresponding object content category, while ensuring the accuracy of the navigation tree view and improving the correctness of subsequent operations.

[0118] Based on this third optional embodiment, the step of determining the second root component set to which the updated target sub-component set belongs, according to the object content category division strategy set, may specifically include the following steps:

[0119] b321) Obtain the object content category classification strategies contained in the object content category classification strategy set, where each object content category classification strategy corresponds to an object content category.

[0120] It is important to know that, in order to avoid coupling between different object content categories, which could result in a single target subcomponent set corresponding to multiple object content categories when dividing the object content categories, the object content category division strategy must ensure that there are no overlapping items between the different object content category division strategies, so that each object content category division strategy corresponds to only one object content category.

[0121] Specifically, the processor can sequentially obtain the object content category classification strategies from the object content category classification strategy set, with each object content category classification strategy corresponding to an object content category.

[0122] b322) Determine the parameter information to be judged for the target sub-component set based on the component tag information included in the updated target sub-component set.

[0123] In this embodiment, the updated target sub-component set may contain one or more component tag information. Each component tag information is associated with a component data. In this embodiment, the target sub-component set needs to be formed by using all the component tag information it contains as the parameter information to be determined.

[0124] It should be noted that each component data corresponds to relevant component attribute parameters. In this embodiment, the information to be judged can be formed using the component attribute parameters of the component data associated with each component tag information. The component attribute parameters can be understood as parameters used to characterize the features of the target sub-component set. The information to be judged can be understood as parameter information used for classifying object content categories.

[0125] It is known that each object content category classification strategy can include multiple judgment conditions. Each judgment condition may have different parameter types. The parameter types correspond to the component data and component attribute parameters included in the target sub-component set. For example, the judgment condition in object content category classification strategy A is: brightness between a1 and a5, and width between cd.

[0126] Specifically, the execution entity of the method provided in this embodiment can obtain the component data and component attribute parameters contained in the target sub-component set, divide the parameters corresponding to all division conditions in the object content category division strategy set, and determine the parameter information to be determined for the target sub-component set through the component data and component attribute parameters.

[0127] b323) Based on the parameter information to be determined and the object content category classification strategy, determine the target object content category to which the target sub-component set belongs after the update, and record the root component set corresponding to the target object content category as the second root component set.

[0128] In this embodiment, the target object content category can be understood as the object content category corresponding to the target sub-component set after division.

[0129] Specifically, the target object content category to which the target sub-component set belongs can be determined by comparing the parameter information to be judged with the corresponding parameter conditions in the content category classification strategy of each object, and the root component set corresponding to the target object content category can be recorded as the target root component set.

[0130] For example, when the original target component data is brightness value a1, the set of sub-components to which it belongs is A. The brightness value range in the object content category classification strategy to which the sub-component set A belongs is a1-a3. However, the brightness value in the changed target component data becomes a12. The brightness value range in the corresponding object content category classification strategy D2 is a10-a12. Then, D is taken as the target object content category, and the corresponding root component set D2 is taken as the target root component set.

[0131] The above technical solution in this embodiment provides a specific implementation method for determining the target root component set through the object content category division strategy set, which is equivalent to providing underlying technical support for the navigation tree view update in this embodiment.

[0132] Based on this third optional embodiment, the step of determining the target root component set from the first root component set and the second root component set, and updating the target sub-component set to the target root component set, may specifically include the following steps:

[0133] b331) If the first root component set and the second root component set are the same root component set, then the first root component set is determined as the target root component set, and the target sub-component set remains unchanged within the first root component set.

[0134] b332) If the first root component set and the second root component set are different root component sets, then the second root component set is determined as the target root component set.

[0135] b333) Determine whether the target root component set exists in the navigation tree view. If yes, proceed to step b334; otherwise, proceed to step b335.

[0136] (b334) Move the target sub-component set from the first root component set to the target root component set.

[0137] b335) Construct the target root component set and add it to the navigation tree view, then return to step b334.

[0138] The above technical solution in this embodiment provides a specific implementation method for updating the target sub-component set to the target root component set. By judging whether the first root component set and the second component set are the same, the position of the component to be updated in the navigation tree view is determined, thereby realizing the accuracy and automation of navigation tree view management and providing the logic for determining the position of component set for encapsulation.

[0139] To facilitate understanding of this solution, specific examples are provided. Figure 2 A flowchart illustrating a method for managing a navigation tree view according to an embodiment of this disclosure is provided, as follows: Figure 2 As shown, the left side illustrates several interactive operations that satisfy the set partitioning update conditions. The implementation steps can be as follows:

[0140] S1. Receive interactive operations and determine their corresponding operation types. The operation types may include, for example, adding data, deleting data, and modifying data.

[0141] S2. Determine the set of child components associated with the interaction, use the set of child components as the target set of child components, and update the target set of child components.

[0142] S3. Based on the pre-built object content category, divide the strategy set and determine the second root component set to which the target sub-component set belongs.

[0143] S4. Get the first root component set to which the target sub-component set belongs before the update.

[0144] S5. Determine whether the first root component set and the second root component set are the same. If yes, proceed to step S9; otherwise, proceed to step S6.

[0145] S6. Take the second root component set as the target root component set, and determine whether the target root component set already exists in the navigation tree view. If yes, proceed to step S7; otherwise, proceed to step S8.

[0146] S7. Move the target sub-component set from the first root component set to the second target root component set, and execute S10.

[0147] S8. Build the target root component collection and add it to the navigation tree view, then return to continue executing S7.

[0148] S9. Keep the target sub-component set under the first root component set, which is the target root component set, and execute S10.

[0149] S10. Display the updated navigation tree view of the root component set to which the child component set belongs.

[0150] Figure 3 This is a schematic diagram of the structure of a navigation tree view management device provided in an embodiment of the present disclosure, as shown below. Figure 3 As shown, the device includes: an interface display module 31, an operation receiving module 32, and a view display module 33, wherein,

[0151] The interface display module 31 is used to display the object creation interface of the target object creation tool. The object creation interface includes a navigation tree view. The root component set displayed in the navigation tree view represents the object content category of the target object, and the sub-component set under the root component set belongs to the object content category.

[0152] The operation receiving module 32 is used to receive interactive operations performed on the object creation interface.

[0153] The view display module 33 is used to update the target sub-component set associated with the interactive operation when the interactive operation satisfies the set partitioning update condition in the navigation tree view, and / or update the root component set to which the target sub-component set belongs, and display it on the navigation tree view.

[0154] This disclosure provides a navigation tree view management device, which essentially offers a management method for navigation tree views. Specifically, it adjusts the representation of the root component set presented in the navigation tree view, differing from existing methods that select a root component set from multiple component sets and manually classify and assign component data to objects of the same category. This technical solution directly adds root component sets representing different object content categories, and the sub-component sets contained under each root component set can be considered to belong to the represented object content category. Simultaneously, this management device automatically adjusts the object content category to which a component set belongs. Unlike existing methods that manually adjust the category of a component set, this management device can automatically determine and update the target sub-component set associated with the received interactive operation when the interactive operation meets the update conditions for component set division under the navigation tree view. It can also update the root component set to which the target sub-component set belongs and display it on the navigation tree view. This management device solves the problem of inaccurate component classification caused by manually dividing component sets in existing navigation tree views. It achieves accurate classification of component sets, effectively reducing the learning cost for designers, while ensuring the accuracy of the navigation tree view and improving the correctness of subsequent operation.

[0155] Furthermore, the device may also include an interaction determination module, which may specifically be used for:

[0156] Analyze the interaction operation to determine the corresponding operation behavior event;

[0157] If the operation behavior event exists in the pre-built navigation tree operation behavior set, then the operation type to which the operation behavior event belongs is determined;

[0158] If the operation type belongs to the set operation type, then the interaction operation is determined to satisfy the set partitioning update condition in the navigation tree view.

[0159] Furthermore, the device can optimize the inclusion of component tag information in the sub-component sets under the root component set, with each component tag information associated with a component data; correspondingly, the device may also include:

[0160] The first determining module is used to determine the component data involved in the interaction operation after the response as the target component data before updating the target sub-component set associated with the interaction operation and / or updating the root component set to which the target sub-component set belongs;

[0161] The second determining module is used to obtain the target component tag information corresponding to the target component data, and determine the set of sub-components containing the target component tag information as the target sub-component set.

[0162] Furthermore, the view display module 33 may specifically include:

[0163] The first update unit is used to update the target component tag information contained in the target sub-component set, wherein the target component tag information is associated with the target component data involved after the interaction operation response;

[0164] And / or,

[0165] The second update unit is used to update the target sub-component set to the determined target root component set according to the pre-built object content category division strategy set.

[0166] Furthermore, the second update unit may specifically include:

[0167] Get sub-unit, used to obtain the first root component set to which the target sub-component set belongs before the update;

[0168] Determine the sub-unit, which is used to divide the strategy set according to the content category of the object and determine the second root component set to which the target sub-component set belongs after the update;

[0169] The root component update subunit is used to determine the target root component set from the first root component set and the second root component set, and update the target subcomponent set to the target root component set.

[0170] Furthermore, the determining subunit can specifically be used for:

[0171] Obtain the object content category classification strategies contained in the object content category classification strategy set, where each object content category classification strategy corresponds to an object content category;

[0172] Based on the updated component tag information of the target sub-component set, determine the parameter information to be judged for the target sub-component set;

[0173] Based on the parameter information to be determined and the object content category classification strategy, the target object content category to which the target sub-component set belongs after the update is determined, and the root component set corresponding to the target object content category is recorded as the second root component set.

[0174] Furthermore, the root component update subunit can specifically be used for:

[0175] If the first root component set and the second root component set are the same root component set, then the first root component set is determined as the target root component set, and the target sub-component set remains within the first root component set.

[0176] If the first root component set and the second root component set are different root component sets, then the second root component set is determined as the target root component set, and it is determined whether the target root component set exists in the navigation tree view;

[0177] If so, the target sub-component set is moved from the first root component set to the target root component set;

[0178] If not, then construct the target root component set and add it to the navigation tree view, and move the target sub-component set from the first root component set to the target root component set.

[0179] The navigation tree view management device provided in this disclosure can execute the navigation tree view management method provided in any embodiment of this disclosure, and has the corresponding functional modules and beneficial effects of the execution method.

[0180] It is worth noting that the various units and modules included in the above-mentioned device are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the protection scope of the embodiments of this disclosure.

[0181] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. Reference is made below. Figure 4 It illustrates an electronic device suitable for implementing embodiments of the present disclosure (e.g., Figure 4 The diagram below shows the structure of the terminal device or server 400. The terminal device in this embodiment may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), and vehicle terminals (e.g., vehicle navigation terminals), as well as fixed terminals such as digital TVs and desktop computers. Figure 4 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0182] like Figure 4As shown, electronic device 400 may include a processing unit (e.g., central processing unit, graphics processor, etc.) 401, which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 402 or a program loaded from storage device 408 into random access memory (RAM) 403. RAM 403 also stores various programs and data required for the operation of electronic device 400. Processing unit 401, ROM 402, and RAM 403 are interconnected via bus 404. Edit / output (I / O) interface 405 is also connected to bus 404.

[0183] Typically, the following devices can be connected to I / O interface 405: input devices 406 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 407 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 408 including, for example, magnetic tapes, hard disks, etc.; and communication devices 409. Communication device 409 allows electronic device 400 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 3 An electronic device 400 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0184] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 409, or installed from a storage device 408, or installed from a ROM 402. When the computer program is executed by the processing device 401, it performs the functions defined in the methods of embodiments of this disclosure.

[0185] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0186] The electronic device provided in this embodiment and the navigation tree view management method provided in the above embodiments belong to the same inventive concept. Technical details not described in detail in this embodiment can be found in the above embodiments, and this embodiment has the same beneficial effects as the above embodiments.

[0187] This disclosure provides a computer storage medium storing a computer program that, when executed by a processor, implements the navigation tree view management method provided in the above embodiments.

[0188] It should be noted that the computer-readable medium described in this disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this disclosure, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0189] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol, such as HTTP (Hypertext Transfer Protocol), and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0190] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0191] The aforementioned computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to: perform material parsing processing on the original material of the business object to obtain the target graphic material of the business object; generate target poster description information based on the target graphic material and the poster generation configuration information of the business object; and generate and display the target poster image of the business object by rendering the target poster description information.

[0192] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0193] 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 code containing one or more executable instructions for implementing a specified logical function. It should also be noted that 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 consecutively indicated 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, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0194] The units described in the embodiments of this disclosure can be implemented in software or in hardware. The name of a unit does not necessarily limit the unit itself; for example, the first acquisition unit can also be described as "a unit that acquires at least two Internet Protocol addresses".

[0195] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0196] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0197] According to one or more embodiments of this disclosure, [Example 1] provides a method for managing a navigation tree view. The method includes: displaying an object creation interface of a target object creation tool, the object creation interface including a navigation tree view, wherein a root component set displayed in the navigation tree view represents the object content category of the target object, and a set of sub-components under the root component set belongs to the object content category; receiving an interactive operation performed on the object creation interface; when the interactive operation satisfies the set partitioning update condition in the navigation tree view, updating the target sub-component set associated with the interactive operation, and / or updating the root component set to which the target sub-component set belongs, and displaying it on the navigation tree view.

[0198] According to one or more embodiments of this disclosure, [Example 2] provides a method for managing a navigation tree view. This method optimizes the determination step of whether an interactive operation satisfies the set partitioning update condition in the navigation tree view. Specifically, it may include: parsing the interactive operation and determining the operation behavior event corresponding to the interactive operation; if the operation behavior event exists in a pre-built navigation tree operation behavior set, then determining the operation type to which the operation behavior event belongs; if the operation type belongs to a set operation type, then determining that the interactive operation satisfies the set partitioning update condition in the navigation tree view.

[0199] According to one or more embodiments of this disclosure, [Example 3] provides a method for managing a navigation tree view, which optimizes the sub-component set under the root component set to include component label information, with each component label information associated with a component data;

[0200] Accordingly, before updating the target sub-component set associated with the interactive operation and / or updating the root component set to which the target sub-component set belongs, the method may further include: determining the component data involved in the interactive operation after the response as target component data; obtaining the target component tag information corresponding to the target component data, and determining the sub-component set containing the target component tag information as the target sub-component set.

[0201] According to one or more embodiments of this disclosure, [Example 4] provides a method for managing a navigation tree view. This method optimizes and updates the target sub-component set associated with the interactive operation, and / or updates the root component set to which the target sub-component set belongs. Specifically, it may include:

[0202] The target component tag information contained in the target sub-component set is updated, and the target component tag information is associated with the target component data involved after the interaction operation response;

[0203] And / or, based on a pre-built set of object content category partitioning strategies, update the target sub-component set to the determined target root component set.

[0204] According to one or more embodiments of this disclosure, [Example 5] provides a method for managing a navigation tree view. This method optimizes updating the target sub-component set to a determined target root component set based on a pre-built object content category partitioning strategy set. Specifically, it may include: obtaining a first root component set to which the target sub-component set belongs before the update; determining a second root component set to which the target sub-component set belongs after the update based on the object content category partitioning strategy set; determining a target root component set from the first root component set and the second component set; and updating the target sub-component set to the target root component set.

[0205] According to one or more embodiments of this disclosure, [Example Six] provides a method for managing a navigation tree view. This method optimizes the division of a strategy set based on the object content category to determine the second root component set to which the updated target sub-component set belongs. Specifically, it may include:

[0206] Obtain the object content category classification strategies contained in the object content category classification strategy set, where each object content category classification strategy corresponds to an object content category;

[0207] Based on the updated component tag information of the target sub-component set, determine the parameter information to be judged for the target sub-component set;

[0208] Based on the parameter information to be determined and the object content category classification strategy, the target object content category to which the target sub-component set belongs after the update is determined, and the root component set corresponding to the target object content category is recorded as the second root component set.

[0209] According to one or more embodiments of this disclosure, [Example Seven] provides a method for managing a navigation tree view. This method optimizes the process of determining a target root component set from a first root component set and a second root component set, and updating the target sub-component set to the target root component set. Specifically, it may include:

[0210] If the first root component set and the second root component set are the same root component set, then the first root component set is determined as the target root component set, and the target sub-component set remains within the first root component set.

[0211] If the first root component set and the second root component set are different root component sets, then the second root component set is determined as the target root component set, and it is determined whether the target root component set exists in the navigation tree view;

[0212] If so, the target sub-component set is moved from the first root component set to the target root component set;

[0213] If not, then construct the target root component set and add it to the navigation tree view, and move the target sub-component set from the first root component set to the target root component set.

[0214] According to one or more embodiments of this disclosure, [Example Eight] provides a management device for a navigation tree view, the device comprising:

[0215] The interface display module is used to display the object creation interface of the target object creation tool. The object creation interface includes a navigation tree view. The root component set displayed in the navigation tree view represents the object content category of the target object, and the sub-component set under the root component set belongs to the object content category.

[0216] An operation receiving module is used to receive interactive operations performed on the object creation interface.

[0217] The view display module is used to update the target sub-component set associated with the interactive operation when the interactive operation satisfies the set partitioning update condition in the navigation tree view, and / or update the root component set to which the target sub-component set belongs, and display it on the navigation tree view.

[0218] According to one or more embodiments of this disclosure, [Example Nine] provides an electronic device including one or more processors; and a storage device for storing one or more programs, which, when executed by the one or more processors, cause the one or more processors to implement a navigation tree view management method as described in any of Examples One to Seven above.

[0219] According to one or more embodiments of this disclosure, [Example 10] provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform a method for managing a navigation tree view as described in any of Examples 1 to 7.

[0220] The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features disclosed in this disclosure that have similar functions.

[0221] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain environments, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0222] Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims.

Claims

1. A method for managing a navigation tree view, characterized in that, include: The object creation interface of the target object creation tool is displayed. The object creation interface includes a navigation tree view. The root component set displayed in the navigation tree view represents the object content category of the target object. The sub-component set under the root component set belongs to the object content category. Receive interactive operations performed on the object creation interface; When the operation type corresponding to the interactive operation satisfies the set partitioning update condition in the navigation tree view, the target sub-component set associated with the interactive operation is updated, and / or the root component set to which the target sub-component set belongs is updated and displayed on the navigation tree view. The interactive operation includes adding, deleting or modifying component data within the target sub-component set. Updating the root component set to which the target sub-component set belongs includes: updating the target sub-component set to its original root component set, or updating the target sub-component set to a new root component set according to a preset root component set partitioning strategy.

2. The method according to claim 1, characterized in that, The steps for determining whether the interactive operation satisfies the set partitioning update condition in the navigation tree view include: Analyze the interaction operation to determine the corresponding operation behavior event; If the operation behavior event exists in the pre-built navigation tree operation behavior set, then the operation type to which the operation behavior event belongs is determined; If the operation type belongs to the set operation type, then the interaction operation is determined to satisfy the set partitioning update condition in the navigation tree view.

3. The method according to claim 1, characterized in that, The set of sub-components under the root component set includes component tag information, and each component tag information is associated with a component data; Before updating the target sub-component set associated with the interactive operation, and / or updating the root component set to which the target sub-component set belongs, the method further includes: The component data involved in the interaction operation after the response is determined as the target component data; Obtain the target component tag information corresponding to the target component data, and determine the set of subcomponents containing the target component tag information as the target subcomponent set.

4. The method according to claim 1, characterized in that, The updating of the target sub-component set associated with the interactive operation, and / or updating the root component set to which the target sub-component set belongs, includes: The target component tag information contained in the target sub-component set is updated, and the target component tag information is associated with the target component data involved after the interaction operation response; And / or, Based on the pre-built object content category classification strategy set, the target sub-component set is updated to the determined target root component set.

5. The method according to claim 4, characterized in that, The step of updating the target sub-component set to the determined target root component set based on the pre-built object content category partitioning strategy set includes: Obtain the first root component set to which the target sub-component set belongs before the update; Based on the object content category classification strategy set, determine the second root component set to which the target sub-component set belongs after the update; Determine the target root component set from the first root component set and the second root component set, and update the target sub-component set to the target root component set.

6. The method according to claim 5, characterized in that, Based on the object content category partitioning strategy set, determine the second root component set to which the updated target sub-component set belongs, including: Obtain the object content category classification strategies contained in the object content category classification strategy set, where each object content category classification strategy corresponds to an object content category; Based on the updated component tag information of the target sub-component set, determine the parameter information to be judged for the target sub-component set; Based on the parameter information to be determined and the object content category classification strategy, the target object content category to which the target sub-component set belongs after the update is determined, and the root component set corresponding to the target object content category is recorded as the second root component set.

7. The method according to claim 5, characterized in that, The step of determining the target root component set from the first root component set and the second root component set, and updating the target sub-component set to the target root component set, includes: If the first root component set and the second root component set are the same root component set, then the first root component set is determined as the target root component set, and the target sub-component set remains within the first root component set. If the first root component set and the second root component set are different root component sets, then the second root component set is determined as the target root component set, and it is determined whether the target root component set exists in the navigation tree view; If so, the target sub-component set is moved from the first root component set to the target root component set; If not, then construct the target root component set and add it to the navigation tree view, and move the target sub-component set from the first root component set to the target root component set.

8. A management device for a navigation tree view, characterized in that, include: The interface display module is used to display the object creation interface of the target object creation tool. The object creation interface includes a navigation tree view. The root component set displayed in the navigation tree view represents the object content category of the target object, and the sub-component set under the root component set belongs to the object content category. An operation receiving module is used to receive interactive operations performed on the object creation interface. The view display module is used to update the target sub-component set associated with the interactive operation when the operation type corresponding to the interactive operation meets the set partitioning update condition in the navigation tree view, and / or update the root component set to which the target sub-component set belongs, and display it on the navigation tree view. The interactive operation includes adding, deleting or modifying component data in the target sub-component set. Updating the root component set to which the target sub-component set belongs includes: updating the target sub-component set to its original root component set, or updating the target sub-component set to a new root component set according to a preset root component set partitioning strategy.

9. An electronic device, characterized in that, include: One or more processors; Storage device for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-7.

Images