Polymorphic interface control method and device for programming application software, equipment and medium

Abstract

The invention provides a polymorphic interface control method and device for programming application software, equipment and a medium, and the method comprises the steps: obtaining functional component use data when detecting that a target user logs in the programming application software; analyzing a language file used for marking that the use permission is controlled to obtain controlled component data corresponding to the target user; based on the functional component use data and the controlled component data, performing multi-level component analysis on a language file for marking a component organization relationship to obtain interface control information of each first-level component, interface control information of a second-level component under the first-level component, and interface control information of a third-level component under the second-level component; and based on the interface control information of each first-level component, the interface control information of the second-level component below the first-level component and the interface control information of the third-level component below the second-level component, performing authority control on a function layout interface when the target user uses the programming application software. Therefore, multi-form interface control of different login users is effectively realized.

Description

Technical Field

[0001] The embodiments disclosed herein relate to the field of interface control technology, and more specifically, to a multi-form interface control method, apparatus, device, and medium suitable for a programming application software. Background Technology

[0002] In programming applications, each logged-in user has different permission roles, meaning there are many role types. Users can log in to the programming application to use the software's functional modules for visual language editing.

[0003] In related technologies, when all products and all types of users log in to the programming application software, the functional areas displayed in the software interface are the same, that is, different types of users will see the same functional area after logging in to the programming application software.

[0004] However, the existing methods result in a limited interface control and low user engagement. Summary of the Invention

[0005] The embodiments described herein provide a multi-form interface control method, apparatus, device, and medium for programming application software, overcoming the aforementioned problems.

[0006] Firstly, based on the content of this disclosure, a multi-form interface control method for programming application software is provided, including:

[0007] When a target user is detected to be logged into a programming application, the functional component usage data of the programming application corresponding to the target user is obtained. The functional component usage data includes: the logical component identifier and the component function identifier that the target user has the right to use in the programming application.

[0008] Parse the language file used to mark the controlled access permissions to obtain the controlled component data corresponding to the target user. The controlled component data includes: the identifier of the controlled component with controlled permissions relative to the programming application software for the target user;

[0009] Based on functional component usage data and controlled component data, multi-level component parsing is performed on the language file used to mark component organization relationships to obtain the target user's interface control information relative to each first-level component, the interface control information relative to the second-level components under the first-level components, and the interface control information relative to the third-level components under the second-level components.

[0010] Based on the target user's interface control information relative to each primary component, the interface control information relative to the secondary components under the primary components, and the interface control information relative to the tertiary components under the secondary components, permission control is implemented for the functional layout interface when the target user uses the programming application software.

[0011] Secondly, according to the present disclosure, a multi-form interface control device for programming application software is provided, comprising:

[0012] The acquisition module is used to acquire the functional component usage data of the programming application software corresponding to the target user when the target user is detected to be logged into the programming application software. The functional component usage data includes: the logical component identifier and the component function identifier that the target user has the right to use in the programming application software.

[0013] The first parsing module is used to parse the language file used to mark the controlled access permissions, and obtain the controlled component data corresponding to the target user. The controlled component data includes: the identifier of the controlled component with controlled permissions relative to the programming application software for the target user.

[0014] The second parsing module is used to perform multi-level component parsing on the language file used to mark the component organization relationship based on the functional component usage data and controlled component data, so as to obtain the target user's interface control information relative to each first-level component, the interface control information relative to the second-level components under the first-level components, and the interface control information relative to the third-level components under the second-level components.

[0015] The control module is used to control the access permissions of the functional layout interface of the target user when using the programming application software, based on the interface control information of the target user relative to each first-level component, the interface control information of the second-level components under the first-level components, and the interface control information of the third-level components under the second-level components.

[0016] Thirdly, a computer device is provided, including a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, it implements the steps of the multi-form interface control method for programming application software as described in any of the above embodiments.

[0017] Fourthly, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the multi-form interface control method of the programming application software as described in any of the above embodiments.

[0018] The multi-form interface control method for programming application software provided in this application embodiment, upon detecting that a target user has logged into the programming application software, acquires functional component usage data corresponding to the target user in the programming application software. This functional component usage data includes: logical component identifiers and component function identifiers for which the target user has usage permissions relative to the programming application software; parses a language file used to mark controlled usage permissions to obtain controlled component data corresponding to the target user. This controlled component data includes: controlled component identifiers for which the target user has controlled permissions relative to the programming application software; based on the functional component usage data and the controlled component data, performs multi-level component parsing on the language file used to mark component organization relationships to obtain interface control information for the target user relative to each first-level component, interface control information for second-level components under the first-level components, and interface control information for third-level components under the second-level components; and performs permission control on the functional layout interface when the target user uses the programming application software based on the interface control information for each first-level component, the second-level components under the first-level components, and the third-level components under the second-level components. In this way, language files can be parsed for logged-in users with different permissions to determine the component usage constraints for different users, and interface control information can be parsed for multi-level components to effectively realize multi-form interface control for different logged-in users and improve user stickiness.

[0019] The above description is merely an overview of the technical solutions of the embodiments of this application. In order to better understand the technical means of the embodiments of this application and to implement them in accordance with the contents of the specification, and to make the above and other objects, features and advantages of the embodiments of this application more obvious and understandable, specific implementation methods of this application are described below. Attached Figure Description

[0020] To more clearly illustrate the technical solutions of the embodiments of this disclosure, the accompanying drawings of the embodiments will be briefly described below. It should be understood that the drawings described below only relate to some embodiments of this disclosure and are not intended to limit this disclosure, wherein:

[0021] Figure 1 This is a flowchart illustrating a multi-form interface control method for a programming application software disclosed herein.

[0022] Figure 2 This is a schematic diagram of the structure of a multi-form interface control device for programming application software provided in this disclosure.

[0023] Figure 3 This is a schematic diagram of the structure of a computer device provided in this disclosure.

[0024] It should be noted that the elements in the attached diagram are schematic and not drawn to scale. Detailed Implementation

[0025] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this disclosure. All other embodiments obtained by those skilled in the art based on the described embodiments of this disclosure without creative effort are also within the scope of protection of this disclosure.

[0026] Unless otherwise defined, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which this subject matter pertains. It will be further understood that terms such as those defined in commonly used dictionaries shall be interpreted as having the meaning consistent with their meaning in the context of the specification and in the relevant art, and shall not be interpreted in an idealized or overly formal form unless otherwise explicitly defined herein. As used herein, the statement of “connecting” or “coupling” two or more parts together shall mean that these parts are directly joined together or joined through one or more intermediate components.

[0027] The term "embodiment" as used herein means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of the phrase "embodiment" in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0028] In this document, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists, A and B exist simultaneously, or B exists. Additionally, the character " / " generally indicates that the preceding and following related objects have an "or" relationship. Terms such as "first" and "second" are only used to distinguish one component (or part of a component) from another component (or another part of a component).

[0029] In the description of this application, unless otherwise stated, "multiple" means two or more (including two), and similarly, "multiple groups" means two or more (including two groups).

[0030] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.

[0031] Figure 1 This is a flowchart illustrating a multi-form interface control method for programming application software provided in this embodiment of the disclosure, such as... Figure 1 As shown, the specific process of the multi-form interface control method for programming application software includes:

[0032] S110. When it is detected that a target user has logged into the programming application software, obtain the usage data of the functional components of the programming application software corresponding to the target user.

[0033] Among them, programming application software such as PQArt can realize different functional areas in multiple forms, that is, different tab order, number, and displayed text in the functional area, different tray order, number, and displayed text under each tab, and different number, order, and displayed text of buttons under each tray.

[0034] The functional component usage data includes: logical component identifiers and component function identifiers that the target user has usage rights to relative to the programming application software. The functional component usage data can be stored in list form, which may include all module IDs (Identity Documents, unique codes) (i.e., logical component identifiers) and function IDs (i.e., component function identifiers). The functional component usage data can be represented by a set L.

[0035] All modules can include tabs, tray icons, and buttons. A tab-tray-button layout can be understood as a module containing multiple functions; a tab can include multiple tray icons, and a tray icon can include multiple buttons. In the access control logic, the priority of the interface layout display is tabs, tray icons, and buttons. That is, if a tab is unavailable, its tray icon and any buttons within it are also unavailable and will not be loaded into the functional area. If a tab is available, its tray icon will be loaded into the functional area if available, otherwise, the tray icon and any buttons within it will be unavailable and will not be loaded into the functional area. Similarly, if a tray icon is available, any buttons within it will be loaded into the functional area if available, otherwise, they will not be loaded into the functional area.

[0036] In some embodiments, obtaining usage data of functional components of the programming application software corresponding to the target user includes:

[0037] If the target user's login status in the programming application is detected as online, the system sends the target user's identity information to the server and obtains the functional component usage data of the programming application corresponding to the target user sent by the server. If the target user's login status in the programming application is detected as offline, the system reads the functional component usage data of the programming application corresponding to the target user from the dongle inserted when the target user logs in.

[0038] For example, when a target user logs in online, a web service function transmits the user's identity information (such as username, password, and login product ID) to the backend server. The backend server then returns a list string of all module IDs and function IDs available to the target user (i.e., functional component usage data). When the user uses the software offline, a dongle needs to be inserted. The dongle is provided by a third-party software provider (such as an ART provider). The third-party dongle maker obtains the list of all module IDs and function IDs available to the target user from the backend and writes the list to the hardware dongle using a dongle-making tool. When the software logs in, it detects that the login is via the hardware dongle and reads the list of module IDs and function IDs from the dongle to obtain the functional component usage data.

[0039] Therefore, by setting up two user verification methods, online and offline, the login status constraints of users logging into programming applications are reduced, and the usage data of functional components of programming applications corresponding to target users can be effectively obtained.

[0040] S120. Parse the language file used to mark the controlled usage permissions to obtain the controlled component data corresponding to the target user.

[0041] The controlled component data includes: identifiers of controlled components for which the target user has controlled permissions relative to the programming application software. The controlled component data can be represented by a set Q.

[0042] XML files, such as XML-B, are used to mark access control permissions. XML-B describes function buttons, specifying their function, icon, and whether they are controlled. During XML-B parsing, each button in the function area corresponds to a Command node in the XML-B file. Whether a button is controlled is determined by whether its Command node contains a Command node. <iscontroled> TRUE< / iscontroled> If an ID is present, it means the button is controlled, and its ID is added to the controlled component data. If no ID is present, it means the button is uncontrolled, and no addition operation is performed.

[0043] S130. Based on the functional component usage data and controlled component data, perform multi-level component parsing on the language file used to mark the component organization relationship to obtain the target user's interface control information relative to each first-level component, the interface control information relative to the second-level components under the first-level components, and the interface control information relative to the third-level components under the second-level components.

[0044] Among them, the language file used to mark the organizational relationship of components, such as xml A, is used to describe the organizational relationship of tab-tray-button, that is, how many trays are under a certain tab, and how many buttons are under each tray. Each PQArt series product has an xml A after installation. The software organizes the layout of the function area buttons by parsing xml A and performing permission processing.

[0045] Every tab, tray icon, and button in XML A can be controlled. Tabs correspond to the `RibbonTab` node in XML A, the tray icon to the `RibbonPanel` node, and buttons to the `RibbonButton` node. For tabs and the tray icon, whether they are controlled depends on whether their nodes have any... <type> Module< / type> A node, if present, indicates that the tab or tray icon is controlled.

[0046] When a user role is created, the backend account creator selects which modules and functions that user role should have, thus determining which buttons, tray icons, and tabs are available. During the development of the Art product, whenever a new function, tray icon, or tab is added, in addition to updating XML A and XML B, the matching relationship of the button, tray icon, or tab is also transmitted to the backend server.

[0047] In some embodiments, based on functional component usage data and controlled component data, multi-level component parsing is performed on the language file used to mark component organizational relationships to obtain the target user's interface control information relative to each first-level component, interface control information relative to second-level components under the first-level components, and interface control information relative to third-level components under the second-level components, including:

[0048] For each first-level component in the language file used to mark component organization relationships, if the node affiliation of the first-level component in the language file used to mark component organization relationships meets the preset affiliation strategy, then the interface control information of the target user relative to the first-level component is determined based on the functional component usage data. For second-level components under the first-level components in the language file used to mark component organization relationships, if the node affiliation of the second-level components under the first-level components in the language file used to mark component organization relationships meets the preset affiliation strategy, then the interface control information of the target user relative to the second-level components under the first-level components is determined based on the functional component usage data. For third-level components under the second-level components in the language file used to mark component organization relationships, the interface control information of the target user relative to the third-level components under the second-level components is determined based on the corresponding logical component identifier, functional component usage data, and controlled component data.

[0049] The method in this embodiment also includes:

[0050] If the node affiliation of a first-level component in the language file used to mark component organization does not meet the preset affiliation policy, then the interface control information of the target user relative to the first-level component is determined as the component loading authorization instruction; if the node affiliation of a second-level component under a first-level component in the language file used to mark component organization does not meet the preset affiliation policy, then the interface control information of the target user relative to the second-level component under the first-level component is determined as the component loading authorization instruction.

[0051] A primary component may include one or more secondary components, and a secondary component may include one or more tertiary components. Primary components include tabs as mentioned above, secondary components include tray icons as mentioned above, and tertiary components include buttons as mentioned above.

[0052] Preset attribution policies, such as those stored <type> Module< / type> Nodes. For example, if the node affiliation of a first-level component in a language file used to mark component organization is: [The first-level component has...] <type> Module< / type> If a node is identified as a first-level component in the language file used to mark component organizational relationships, then the node affiliation of that first-level component satisfies the preset affiliation strategy; otherwise, the node affiliation of that first-level component in the language file used to mark component organizational relationships is not specified. <type> Module< / type> If a node is identified as a first-level component in the language file used to mark component organization relationships, and its node affiliation does not meet the preset affiliation strategy, then the node affiliation of a second-level component under a first-level component in the language file used to mark component organization relationships is determined to be a node with a node affiliation of a second-level component under a first-level component. <type> Module< / type> In a language file used to mark component organizational relationships, the node affiliation of the second-level components under a first-level component satisfies a preset affiliation strategy; if the node affiliation of the second-level components under a first-level component in the language file used to mark component organizational relationships is such that the second-level components under the first-level component do not have a node affiliation strategy, then the node affiliation of the second-level components under a first-level component satisfies a preset affiliation strategy. <type> Module< / type> Nodes, used to mark the organizational relationships of components, indicate that the node affiliation of a second-level component under a first-level component in the language file does not meet the preset affiliation strategy.

[0053] Therefore, hierarchical analysis is performed on first-level components, second-level components, and third-level components in sequence to effectively determine the interface control information of the target user relative to different levels of components.

[0054] In some embodiments, based on functional component usage data, the interface control information of the target user relative to the primary component is determined, including:

[0055] Determine whether the logical component identifier of the first-level component is stored in the functional component usage data; if the logical component identifier of the first-level component is stored in the functional component usage data, then determine that the target user's interface control information relative to the first-level component is a component loading authorization instruction; if the logical component identifier of the first-level component is not stored in the functional component usage data, then determine that the target user's interface control information relative to the first-level component is a component loading controlled instruction.

[0056] Based on the above, we determine whether the logical component identifier of the first-level component is in set L. If it is, the interface control information of the target user relative to the first-level component is determined to be a component loading authorization indication, and we continue to determine the interface control information of its second-level and third-level components. If not, the interface control information of the target user relative to the first-level component is determined to be a component loading controlled indication, and the second-level and third-level components do not need to be determined further, as their corresponding interface control information is also a component loading controlled indication. Thus, the interface control information of the target user relative to the first-level component is effectively determined.

[0057] In some embodiments, based on functional component usage data, the interface control information of the target user relative to the second-level components under the first-level components is determined, including:

[0058] Determine whether the logical component identifier of the second-level component is stored in the functional component usage data; if the logical component identifier of the second-level component is stored in the functional component usage data, then determine that the interface control information of the target user relative to the second-level component under the first-level component is the component loading authorization instruction; if the logical component identifier of the second-level component is not stored in the functional component usage data, then determine that the interface control information of the target user relative to the second-level component under the first-level component is the component loading controlled instruction.

[0059] Based on the above, we determine whether the logical component identifier of the second-level component is in set L. If it is, we determine that the interface control information of the second-level component under the first-level component for the target user is a component loading authorization indicator, and continue to determine the interface control information of the third-level component below it. If not, we determine that the interface control information of the second-level component under the first-level component for the target user is a component loading controlled indicator, and the third-level component below it does not need to be determined again; the interface control information corresponding to the third-level component below it is a component loading controlled indicator. Thus, we can effectively determine the interface control information of the second-level component under the first-level component for the target user.

[0060] In some embodiments, for third-level components under second-level components in a language file used to mark component organization relationships, based on the corresponding logical component identifier, functional component usage data, and controlled component data, the interface control information of the target user relative to the third-level component under the second-level component is determined, including:

[0061] If the logical component identifier corresponding to the third-level component under the second-level component in the language file used to mark the component organization relationship is not stored in the controlled component data, then the interface control information of the target user relative to the third-level component under the second-level component is determined to be a component loading authorization instruction; if the logical component identifier corresponding to the third-level component under the second-level component in the language file used to mark the component organization relationship is stored in the controlled component data, then it is determined whether the component function identifier of the third-level component is stored in the function component usage data: if yes, then the interface control information of the target user relative to the third-level component under the second-level component is determined to be a component loading authorization instruction; if no, then the interface control information of the target user relative to the third-level component under the second-level component is determined to be a component loading controlled instruction.

[0062] In summary, if the logical component identifier corresponding to the third-level component under the second-level component in the language file used to mark component organization relationships is not in set Q, then the interface control information of the target user relative to the third-level component under the second-level component is determined to be a component loading authorization indicator. If the logical component identifier corresponding to the third-level component under the second-level component in the language file used to mark component organization relationships is in set Q, then it is checked whether its component function identifier is in set L. If it is, then the interface control information of the target user relative to the third-level component under the second-level component is determined to be a component loading authorization indicator; otherwise, the interface control information of the target user relative to the third-level component under the second-level component is determined to be a component loading controlled indicator. Thus, the interface control information of the target user relative to the third-level component under the second-level component is effectively determined.

[0063] S140. Based on the target user's interface control information relative to each first-level component, the interface control information relative to the second-level components under the first-level components, and the interface control information relative to the third-level components under the second-level components, the target user performs permission control on the functional layout interface when using the programming application software.

[0064] In some embodiments, based on the target user's interface control information relative to each primary component, the interface control information relative to the secondary components under the primary components, and the interface control information relative to the tertiary components under the secondary components, permission control is performed on the functional layout interface when the target user uses the programming application software, including:

[0065] If the target user's interface control information relative to a first-level component is a component loading authorization instruction, then the first-level component is loaded into the functional layout interface when the target user uses the programming application software. If the target user's interface control information relative to a first-level component is a component loading controlled instruction, then the first-level component is hidden in the functional layout interface when the target user uses the programming application software. If the target user's interface control information relative to a second-level component under a first-level component is a component loading authorization instruction, then the second-level component under the first-level component is loaded into the functional layout interface when the target user uses the programming application software. If the target user's interface control information relative to a second-level component under a first-level component is a component loading controlled instruction, then the second-level component under the first-level component is hidden in the functional layout interface when the target user uses the programming application software. If the target user's interface control information relative to a third-level component under a second-level component is a component loading authorization instruction, then the third-level component under the second-level component is loaded into the functional layout interface when the target user uses the programming application software. If the target user's interface control information relative to a third-level component under a second-level component is a component loading controlled instruction, then the third-level component under the second-level component is hidden in the functional layout interface when the target user uses the programming application software.

[0066] Thus, by loading components with authorization instructions into the functional area using interface control information and hiding components with controlled instructions using interface control information, multi-form control of the functional layout interface can be effectively achieved when the target user uses the programming application software.

[0067] It should be noted that if the target user's interface control information relative to a first-level component is a component loading controlled indication, that first-level component can also be displayed in a non-triggerable manner in the function layout interface; similarly, if the target user's interface control information relative to a second-level component under a first-level component is a component loading controlled indication, that second-level component can also be displayed in a non-triggerable manner in the function layout interface; and if the target user's interface control information relative to a third-level component under a second-level component is a component loading controlled indication, that third-level component can also be displayed in a non-triggerable manner in the function layout interface. This facilitates demonstrating the multi-functionality of the programming application software to logged-in users.

[0068] In this embodiment, when a target user is detected logging into the programming application software, the system obtains the functional component usage data corresponding to the target user. This functional component usage data includes: logical component identifiers and component function identifiers that the target user has usage rights with respect to the programming application software. The system then parses a language file used to mark controlled usage rights to obtain controlled component data corresponding to the target user. This controlled component data includes: controlled component identifiers that the target user has controlled permissions with respect to the programming application software. Based on the functional component usage data and the controlled component data, the system performs multi-level component parsing on the language file used to mark component organizational relationships to obtain the target user's interface control information relative to each first-level component, the interface control information relative to second-level components under the first-level components, and the interface control information relative to third-level components under the second-level components. Based on the target user's interface control information relative to each first-level component, the interface control information relative to second-level components under the first-level components, and the interface control information relative to third-level components under the second-level components, the system performs permission control on the functional layout interface when the target user uses the programming application software. In this way, language files can be parsed for logged-in users with different permissions to determine the component usage constraints for different users, and interface control information can be parsed for multi-level components to effectively realize multi-form interface control for different logged-in users and improve user stickiness.

[0069] Figure 2 This is a schematic diagram of the structure of a multi-form interface control device for programming application software provided in this embodiment. The multi-form interface control device for programming application software may include: an acquisition module 210, a first parsing module 220, a second parsing module 230, and a control module 240.

[0070] The acquisition module 210 is used to acquire the functional component usage data of the programming application software corresponding to the target user when the target user is detected to have logged into the programming application software. The functional component usage data includes: the logical component identifier and the component function identifier that the target user has the right to use in the programming application software.

[0071] The first parsing module 220 is used to parse the language file used to mark the controlled access permissions, and obtain the controlled component data corresponding to the target user. The controlled component data includes: the identifier of the controlled component that the target user has access control with respect to the programming application software.

[0072] The second parsing module 230 is used to perform multi-level component parsing on the language file used to mark the component organization relationship based on the functional component usage data and the controlled component data, so as to obtain the interface control information of the target user relative to each first-level component, the interface control information of the second-level component under the first-level component, and the interface control information of the third-level component under the second-level component.

[0073] The control module 240 is used to perform permission control on the functional layout interface of the target user when using the programming application software, based on the interface control information of the target user relative to each first-level component, the interface control information of the second-level components under the first-level components, and the interface control information of the third-level components under the second-level components.

[0074] In this embodiment, optionally, the second parsing module 230 includes:

[0075] The first determining unit is used to determine the interface control information of the target user relative to the first-level component based on the functional component usage data, if the node affiliation relationship of the first-level component in the language file used to mark the component organization relationship satisfies the preset affiliation strategy.

[0076] The second determining unit is used to determine the interface control information of the target user relative to the second-level component under the first-level component in the language file used to mark the component organization relationship. If the node affiliation relationship of the second-level component under the first-level component in the language file used to mark the component organization relationship meets the preset affiliation strategy, then based on the functional component usage data, the unit determines the interface control information of the target user relative to the second-level component under the first-level component.

[0077] The third determining unit is used to determine the interface control information of the target user relative to the third-level component under the second-level component in the language file used to mark the component organization relationship, based on the corresponding logical component identifier, functional component usage data and controlled component data.

[0078] The device in this embodiment also includes: a fourth determining unit.

[0079] The fourth determining unit is used to determine the interface control information of the target user relative to the first-level component as a component loading authorization instruction if the node affiliation relationship corresponding to the first-level component in the language file used to mark the component organization relationship does not meet the preset affiliation strategy; and to determine the interface control information of the target user relative to the second-level component under the first-level component as a component loading authorization instruction if the node affiliation relationship corresponding to the second-level component under the first-level component in the language file used to mark the component organization relationship does not meet the preset affiliation strategy.

[0080] In this embodiment, optionally, the first determining unit is specifically used for:

[0081] Determine whether the logical component identifier of the first-level component is stored in the functional component usage data; if the logical component identifier of the first-level component is stored in the functional component usage data, then determine that the target user's interface control information relative to the first-level component is a component loading authorization instruction; if the logical component identifier of the first-level component is not stored in the functional component usage data, then determine that the target user's interface control information relative to the first-level component is a component loading controlled instruction.

[0082] In this embodiment, optionally, the second determining unit is specifically used for:

[0083] Determine whether the logical component identifier of the second-level component is stored in the functional component usage data; if the logical component identifier of the second-level component is stored in the functional component usage data, then determine that the interface control information of the target user relative to the second-level component under the first-level component is the component loading authorization instruction; if the logical component identifier of the second-level component is not stored in the functional component usage data, then determine that the interface control information of the target user relative to the second-level component under the first-level component is the component loading controlled instruction.

[0084] In this embodiment, optionally, the third determining unit is specifically used for:

[0085] If the logical component identifier corresponding to the third-level component under the second-level component in the language file used to mark the component organization relationship is not stored in the controlled component data, then the interface control information of the target user relative to the third-level component under the second-level component is determined to be a component loading authorization instruction; if the logical component identifier corresponding to the third-level component under the second-level component in the language file used to mark the component organization relationship is stored in the controlled component data, then it is determined whether the component function identifier of the third-level component is stored in the function component usage data: if yes, then the interface control information of the target user relative to the third-level component under the second-level component is determined to be a component loading authorization instruction; if no, then the interface control information of the target user relative to the third-level component under the second-level component is determined to be a component loading controlled instruction.

[0086] In this embodiment, optionally, the control module 240 is specifically used for:

[0087] If the target user's interface control information relative to a first-level component is a component loading authorization instruction, then the first-level component is loaded into the functional layout interface when the target user uses the programming application software. If the target user's interface control information relative to a first-level component is a component loading controlled instruction, then the first-level component is hidden in the functional layout interface when the target user uses the programming application software. If the target user's interface control information relative to a second-level component under a first-level component is a component loading authorization instruction, then the second-level component under the first-level component is loaded into the functional layout interface when the target user uses the programming application software. If the target user's interface control information relative to a second-level component under a first-level component is a component loading controlled instruction, then the second-level component under the first-level component is hidden in the functional layout interface when the target user uses the programming application software. If the target user's interface control information relative to a third-level component under a second-level component is a component loading authorization instruction, then the third-level component under the second-level component is loaded into the functional layout interface when the target user uses the programming application software. If the target user's interface control information relative to a third-level component under a second-level component is a component loading controlled instruction, then the third-level component under the second-level component is hidden in the functional layout interface when the target user uses the programming application software.

[0088] In this embodiment, optionally, the acquisition module 210 is specifically used for:

[0089] If the target user's login status in the programming application is detected as online, the system sends the target user's identity information to the server and obtains the functional component usage data of the programming application corresponding to the target user sent by the server. If the target user's login status in the programming application is detected as offline, the system reads the functional component usage data of the programming application corresponding to the target user from the dongle inserted when the target user logs in.

[0090] The multi-form interface control device for programming application software provided in this disclosure can execute the above-described method embodiments. Its specific implementation principle and technical effects can be found in the above-described method embodiments, and will not be repeated here.

[0091] This application also provides a computer device. Please refer to the following for details. Figure 3 , Figure 3 This is a basic structural block diagram of the computer device in this embodiment.

[0092] The computer device includes a memory 310 and a processor 320 that are communicatively connected to each other via a system bus. It should be noted that only a computer device with memory 310 and processor 320 is shown in the figure; however, it should be understood that it is not required to implement all the components shown, and more or fewer components may be implemented alternatively. Those skilled in the art will understand that the computer device described herein is a device capable of automatically performing numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes, but is not limited to, microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), embedded devices, etc.

[0093] Computer devices can include desktop computers, laptops, handheld computers, and cloud servers. These devices allow for human-computer interaction with users through keyboards, mice, remote controls, touchpads, or voice-activated devices.

[0094] The memory 310 includes at least one type of readable storage medium, including non-volatile memory or volatile memory, such as flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. RAM may include static RAM or dynamic RAM. In some embodiments, the memory 310 may be an internal storage unit of a computer device, such as the hard disk or RAM of the computer device. In other embodiments, the memory 310 may also be an external storage device of the computer device, such as a plug-in hard drive, smart media card (SMC), secure digital (SD) card, or flash card equipped on the computer device. Of course, the memory 310 may include both internal storage units and external storage devices of the computer device. In this embodiment, the memory 310 is typically used to store the operating system and various application software installed on the computer device, such as the program code of the methods described above. Furthermore, the memory 310 may also be used to temporarily store various types of data that have been output or will be output.

[0095] Processor 320 is typically used to perform overall operations of a computer device. In this embodiment, memory 310 is used to store program code or instructions, including computer operation instructions, and processor 320 is used to execute the program code or instructions stored in memory 310 or process data, such as program code that runs the methods described above.

[0096] In this article, the bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. This bus system can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not mean that there is only one bus or one type of bus.

[0097] Another embodiment of this application also provides a computer-readable medium, which may be a computer-readable signal medium or a computer-readable medium. A processor in a computer reads computer-readable program code stored in the computer-readable medium, enabling the processor to execute the functional actions specified in each step or combination of steps in the above method; and to generate means for implementing the functional actions specified in each block or combination of blocks in the block diagram.

[0098] Computer-readable media include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared memory or semiconductor systems, devices or apparatuses, or any suitable combination thereof, wherein the memory is used to store program code or instructions, the program code including computer operation instructions, and the processor is used to execute the program code or instructions of the above-described methods stored in the memory.

[0099] The definitions of memory and processor can be found in the description of the foregoing computer device embodiments, and will not be repeated here.

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

[0101] In the various embodiments of this application, the functional units or modules can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0102] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0103] In the claims, any reference signs placed between parentheses should not be construed as limiting the claims. The word "comprising" as described in this application does not exclude the presence of elements or steps not listed in the claims. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. This application can be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In the unit claims listing several means, several units of these means may be embodied by the same item of hardware. The use of "first," "second," and "third," etc., does not indicate any order and these words should be interpreted as names. Unless otherwise specified, the steps in the above embodiments should not be construed as limiting the order of execution.

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

Claims

1. A multi-form interface control method for programming application software, characterized in that, include: When a target user is detected to have logged into the programming application software, the functional component usage data of the programming application software corresponding to the target user is obtained. The functional component usage data includes: the logical component identifier and the component function identifier that the target user has the right to use the programming application software. Parse the language file used to mark the controlled access permissions to obtain the controlled component data corresponding to the target user. The controlled component data includes: the controlled component identifier that the target user has controlled access permissions relative to the programming application software. Based on the functional component usage data and the controlled component data, multi-level component parsing is performed on the language file used to mark the component organization relationship to obtain the target user's interface control information relative to each first-level component, the interface control information relative to the second-level components under the first-level components, and the interface control information relative to the third-level components under the second-level components. Based on the target user's interface control information relative to each primary component, the interface control information relative to the secondary components under the primary components, and the interface control information relative to the tertiary components under the secondary components, permission control is performed on the functional layout interface when the target user uses the programming application software.

2. The method according to claim 1, characterized in that, The process involves performing multi-level component parsing on the language file used to mark component organizational relationships based on the functional component usage data and the controlled component data. This yields the target user's interface control information relative to each first-level component, interface control information relative to second-level components under the first-level components, and interface control information relative to third-level components under the second-level components. This includes: For each first-level component in the language file used to mark the organizational relationship of components, if the node affiliation relationship corresponding to the first-level component in the language file used to mark the organizational relationship of components satisfies the preset affiliation strategy, then based on the functional component usage data, the interface control information of the target user relative to the first-level component is determined. For a second-level component under a first-level component in a language file used to mark component organization relationships, if the node affiliation relationship of the second-level component under a first-level component in the language file used to mark component organization relationships satisfies the preset affiliation strategy, then based on the functional component usage data, the interface control information of the target user relative to the second-level component under the first-level component is determined. For a third-level component under a second-level component in a language file used to mark component organization relationships, the interface control information of the target user relative to the third-level component under the second-level component is determined based on the corresponding logical component identifier, the functional component usage data, and the controlled component data. The method further includes: If the node affiliation of a first-level component in a language file used to mark component organization does not meet the preset affiliation strategy, then the interface control information of the target user relative to the first-level component is determined to be a component loading authorization instruction; if the node affiliation of a second-level component under a first-level component in a language file used to mark component organization does not meet the preset affiliation strategy, then the interface control information of the target user relative to the second-level component under the first-level component is determined to be a component loading authorization instruction.

3. The method according to claim 2, characterized in that, The step of determining the interface control information of the target user relative to the primary component based on the functional component usage data includes: Determine whether the logical component identifier of the first-level component is stored in the functional component usage data; If the logical component identifier of the first-level component is stored in the functional component usage data, then the interface control information of the target user relative to the first-level component is determined to be a component loading authorization indication; if the logical component identifier of the first-level component is not stored in the functional component usage data, then the interface control information of the target user relative to the first-level component is determined to be a component loading controlled indication.

4. The method according to claim 3, characterized in that, The step of determining the interface control information of the target user relative to the second-level component under the first-level component based on the functional component usage data includes: Determine whether the logical component identifier of the secondary component is stored in the functional component usage data; If the logical component identifier of the secondary component is stored in the functional component usage data, then the interface control information of the target user relative to the secondary component under the primary component is determined to be a component loading authorization indication; if the logical component identifier of the secondary component is not stored in the functional component usage data, then the interface control information of the target user relative to the secondary component under the primary component is determined to be a component loading controlled indication.

5. The method according to claim 4, characterized in that, The method for determining the interface control information of the target user relative to the third-level components under the second-level components in the language file used to mark component organization relationships, based on the corresponding logical component identifier, the functional component usage data, and the controlled component data, includes: If the logical component identifier corresponding to the third-level component under the second-level component in the language file used to mark the component organization relationship is not stored in the controlled component data, then the interface control information of the target user relative to the third-level component under the second-level component is determined to be a component loading authorization instruction. If the logical component identifier corresponding to the third-level component under the second-level component in the language file used to mark the component organization relationship is stored in the controlled component data, then it is determined whether the component function identifier of the third-level component is stored in the functional component usage data: if yes, then the interface control information of the target user relative to the third-level component under the second-level component is determined to be a component loading authorization instruction; if no, then the interface control information of the target user relative to the third-level component under the second-level component is determined to be a component loading controlled instruction.

6. The method according to claim 5, characterized in that, The method of controlling access to the functional layout interface of the target user when using the programming application software, based on the target user's interface control information relative to each primary component, the interface control information relative to the secondary components under the primary components, and the interface control information relative to the tertiary components under the secondary components, includes: If the target user's interface control information relative to the primary component is a component loading authorization instruction, then the primary component is loaded into the functional layout interface when the target user uses the programming application software; if the target user's interface control information relative to the primary component is a component loading controlled instruction, then the primary component is hidden in the functional layout interface when the target user uses the programming application software. If the target user's interface control information relative to the second-level component under the first-level component is a component loading authorization instruction, then the second-level component under the first-level component is loaded into the functional layout interface when the target user uses the programming application software; if the target user's interface control information relative to the second-level component under the first-level component is a component loading controlled instruction, then the second-level component under the first-level component is hidden in the functional layout interface when the target user uses the programming application software. If the target user's interface control information relative to the third-level component under the second-level component is a component loading authorization instruction, then the third-level component under the second-level component is loaded into the functional layout interface when the target user uses the programming application software; if the target user's interface control information relative to the third-level component under the second-level component is a component loading controlled instruction, then the third-level component under the second-level component is hidden in the functional layout interface when the target user uses the programming application software.

7. The method according to claim 1, characterized in that, The step of obtaining the functional component usage data of the programming application software corresponding to the target user includes: If it is detected that the target user's login status in the programming application software is online, then the target user's identity information is sent to the server, and the functional component usage data of the programming application software corresponding to the target user is obtained from the server. If it is detected that the target user's login status in the programming application software is offline, then the functional component usage data of the programming application software corresponding to the target user is read from the dongle inserted when the target user logs in to the programming application software.

8. A multi-form interface control device for programming application software, characterized in that, include: The acquisition module is used to acquire the functional component usage data of the programming application software corresponding to the target user when it is detected that the target user has logged into the programming application software. The functional component usage data includes: the logical component identifier and the component function identifier that the target user has the right to use the programming application software. The first parsing module is used to parse the language file used to mark the controlled access permissions, and obtain the controlled component data corresponding to the target user. The controlled component data includes: the controlled component identifier that the target user has controlled access permissions relative to the programming application software; The second parsing module is used to perform multi-level component parsing on the language file used to mark the component organization relationship based on the functional component usage data and the controlled component data, so as to obtain the interface control information of the target user relative to each first-level component, the interface control information relative to the second-level component under the first-level component, and the interface control information relative to the third-level component under the second-level component. The control module is used to perform permission control on the functional layout interface of the target user when using the programming application software, based on the interface control information of the target user relative to each primary component, the interface control information relative to the secondary components under the primary components, and the interface control information relative to the tertiary components under the secondary components.

9. A computer device, characterized in that, It includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the multi-form interface control method of the programming application software as described in any one of claims 1 to 7.

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

Images