CN112256522A - Component information acquisition method and device, electronic equipment and storage medium - Google Patents

Component information acquisition method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN112256522A
CN112256522A CN202011011786.9A CN202011011786A CN112256522A CN 112256522 A CN112256522 A CN 112256522A CN 202011011786 A CN202011011786 A CN 202011011786A CN 112256522 A CN112256522 A CN 112256522A
Authority
CN
China
Prior art keywords
information
component
description information
control
interactive interface
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202011011786.9A
Other languages
Chinese (zh)
Inventor
张赛
吴贯亮
董利明
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Dajia Internet Information Technology Co Ltd
Original Assignee
Beijing Dajia Internet Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Dajia Internet Information Technology Co Ltd filed Critical Beijing Dajia Internet Information Technology Co Ltd
Priority to CN202011011786.9A priority Critical patent/CN112256522A/en
Publication of CN112256522A publication Critical patent/CN112256522A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/3003Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/302Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/32Monitoring with visual or acoustical indication of the functioning of the machine
    • G06F11/323Visualisation of programs or trace data

Abstract

The disclosure relates to a method and a device for acquiring component information, an electronic device and a storage medium, and relates to the technical field of software application, engineering management and data processing application, wherein the method comprises the following steps: monitoring a first control on the interactive interface; receiving key information of a target component input on an interactive interface; when the first control is operated, generating a first command for acquiring component information according to the key information and the first control and executing the first command to acquire description information of the target component, wherein the description information comprises the key information and basic information of the target component; and acquiring the description information, and displaying the description information on the interactive interface. The information of the component is visualized by simplifying the acquisition of the component information and displaying the description information on the interactive interface.

Description

Component information acquisition method and device, electronic equipment and storage medium
Technical Field
The present disclosure relates to the field of software application, engineering management, and data processing application technologies, and in particular, to a method and an apparatus for acquiring component information, an electronic device, and a storage medium.
Background
With the rapid development of mobile terminal technology, Application programs (APP for short) with various functions are in operation. The super APP of the large-scale internet enterprise is more and more concerned due to the characteristics of strong function, high integration level, capability of covering multiple services and multiple contents and the like.
However, since the super APP of the large internet enterprise can cover a plurality of modules such as production, consumption, social contact, live broadcast and the like, the components of part of the super APPs with rich functions are even hundreds, and thus the super APPs need to be maintained by a super team. In this case, since the technical form is complex, there are many components and many software development kits, finding the description file through the website and then checking the component information through the description file or checking the component information through the command line can cause the problems of extremely poor engineering management effectiveness, extremely low development efficiency and the like because only the information of one component can be checked at a time. Therefore, how to improve the engineering management efficiency by ensuring the effectiveness and reliability in the component information acquisition process becomes an urgent problem to be solved.
Disclosure of Invention
The present disclosure provides a component information acquisition method, device, electronic device, and storage medium, to at least solve the problem in the related art that the effectiveness and reliability of the component information acquisition process cannot be ensured, resulting in extremely low engineering management efficiency. The technical scheme of the disclosure is as follows:
according to a first aspect of the embodiments of the present disclosure, there is provided a component information acquisition method, which is applied to a component management application, the component information acquisition method including: monitoring a first control on an interactive interface, wherein the first control is used for acquiring component information; receiving key information of a target component input on the interactive interface; when the first control is operated, generating a first command for acquiring component information according to the key information and the first control and executing the first command to acquire description information of the target component, wherein the description information comprises the key information and basic information of the target component; and acquiring the description information and displaying the description information on the interactive interface.
According to one embodiment of the present disclosure, the application includes a visualization front end and a data processing end.
According to an embodiment of the present disclosure, the obtaining the description information further includes: the visual front end acquires a first storage position of a first storage file of the target assembly, reads the first storage file according to the first storage position, and acquires the description information from the first storage file.
According to an embodiment of the present disclosure, if the target component is a remote component, the executing the first command includes: the data processing end sends a request for acquiring the data packet to a remote server according to the first command; and the data processing end receives the data packet sent by the remote server and extracts the description information from the data packet.
According to an embodiment of the present disclosure, after the extracting the description information from the data packet, the method further includes: and the data processing terminal generates a first storage file corresponding to the target component according to the description information and feeds the first storage position back to the visual front end.
According to an embodiment of the present disclosure, if the target component is a local component, the obtaining the description information includes: and the visual front end receives the storage position of the description information fed back by the data processing end, and reads the description information according to the storage position, wherein the description information is stored in a first storage file of the target component, and the storage address of the description information is the first storage position of the first storage file.
According to one embodiment of the disclosure, the interactive interface comprises a display area for displaying the description information, the display area comprises a plurality of display positions, and interactive controls are arranged on part of the display positions.
According to an embodiment of the present disclosure, the presenting the description information on the interactive interface includes: and the visual front end extracts information items from the description information and loads the information items to display positions corresponding to the information items in the display area.
According to an embodiment of the present disclosure, after the presenting the description information on the interactive interface, the method further includes: the visual front end monitors the interactive control; the visualization front end sends the identifier of the operated first interactive control to the data processing end; and the data processing terminal generates a second command according to the identifier of the first interactive control, executes the second command, acquires feedback information matched with the second command and feeds the feedback information back to the visual front end for display.
According to an embodiment of the present disclosure, after the presenting the description information on the interactive interface, the method further includes: the visual front end monitors the interactive control; and the visual front end calls a communication tool according to the operated second interactive control, and displays a dialog box of the communication tool on the interactive interface.
According to an embodiment of the present disclosure, before monitoring the first control on the interactive interface, the method further includes: the visual front end loads the project to which the target component belongs, and displays first project data of the project on the interactive interface; the visual front end receives second engineering data of the engineering fed back by the data processing end; and the visual front end compares the first engineering data with the second engineering data, and if the first engineering data and the second engineering data are not consistent, reminding information is displayed on the interactive interface.
According to an embodiment of the present disclosure, the method further comprises: when the visual front end starts or creates a project for the first time, the project information of the project is read from the second storage file of the project in the data processing end and displayed on the interactive interface.
According to a second aspect of the embodiments of the present disclosure, there is provided a component information acquisition apparatus adapted to a component management application, the apparatus including: the monitoring unit is configured to monitor a first control on an execution interactive interface, wherein the first control is used for acquiring component information; a receiving unit configured to perform receiving key information of a target component input on the interactive interface; an obtaining unit, configured to execute, when the first control is operated, a first command for obtaining component information according to the key information and the first control, and execute the first command to obtain description information of the target component, where the description information includes the key information and basic information of the target component; and the display unit is configured to acquire the description information and display the description information on the interactive interface.
According to one embodiment of the present disclosure, the application includes a visualization front end and a data processing end.
According to an embodiment of the present disclosure, the obtaining unit further includes: the acquisition subunit is configured to execute the visualization front end to acquire a first storage location of a first storage file of the target component, read the first storage file according to the first storage location, and acquire the description information from the first storage file.
According to an embodiment of the present disclosure, the component information acquiring apparatus further includes: the second sending unit is configured to execute the data processing terminal to send a request for acquiring the data packet to a remote server according to the first command; and the extraction unit is configured to execute the data processing terminal to receive the data packet sent by the remote server and extract the description information from the data packet.
According to an embodiment of the present disclosure, the component information acquiring apparatus further includes: and the feedback unit is configured to execute the data processing terminal to generate a first storage file corresponding to the target component according to the description information, and feed back the first storage position to the visualization front end.
According to an embodiment of the present disclosure, the component information acquiring apparatus further includes: the reading unit is configured to execute a storage location where the visualization front end receives the description information fed back by the data processing end, and read the description information according to the storage location, wherein the description information is stored in a first storage file of the target component, and a storage address of the description information is a first storage location of the first storage file.
According to an embodiment of the present disclosure, the generating unit includes: the interactive interface comprises a display area used for displaying the description information, the display area comprises a plurality of display positions, and interactive controls are distributed on part of the display positions.
According to an embodiment of the present disclosure, the display unit includes: and the loading subunit is configured to execute the visualization front end to extract an information item from the description information and load the information item to a display position corresponding to the information item in the display area.
According to an embodiment of the present disclosure, the display unit further includes: the first monitoring subunit is configured to execute the visualization front end to monitor the interaction control; the sending subunit is configured to execute the visualization front end to send the identifier of the operated first interactive control to the data processing end; and the first display subunit is configured to execute the data processing end to generate a second command according to the identifier of the first interactive control, execute the second command, acquire feedback information matched with the second command, and feed the feedback information back to the visualization front end for display.
According to an embodiment of the present disclosure, the display unit further includes: the second monitoring subunit is configured to execute the visualization front end to monitor the interaction control; and the second display subunit is configured to execute the visualization front end, call a communication tool according to the operated second interactive control, and display a dialog box of the communication tool on the interactive interface.
According to an embodiment of the present disclosure, the monitoring unit further includes: the third display subunit is configured to execute the project to which the target component belongs loaded by the visual front end, and display first project data of the project on the interactive interface; the receiving subunit is configured to execute that the visualization front end receives second engineering data of the engineering fed back by the data processing end; and the fourth display subunit is configured to execute the visual front end to compare the first engineering data with the second engineering data, and if the first engineering data and the second engineering data are not consistent, display reminding information on the interactive interface.
According to an embodiment of the present disclosure, the generating unit includes: the monitoring unit further comprises: and the fifth display subunit is configured to, when the visual front end is started for the first time or a project is created, read the project information of the project from the second storage file of the project in the data processing end and display the project information on the interactive interface.
According to a third aspect of the embodiments of the present disclosure, there is provided an electronic apparatus including: a processor; a memory for storing the processor-executable instructions; wherein the processor is configured to execute the instructions to implement the component information obtaining method provided by the embodiment of the first aspect of the disclosure.
According to a fourth aspect of the embodiments of the present disclosure, there is provided a storage medium, where instructions, when executed by a processor of an electronic device, enable the electronic device to perform the component information obtaining method provided in the embodiments of the first aspect of the present disclosure.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:
according to the method and the device, the key information of the target component is received, and the description information of the target component is pulled according to the key information and the first control, so that the description information can be displayed on an interactive interface. Therefore, the information of the component is visualized by simplifying the acquisition of the component information and showing the description information on the interactive interface.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure and are not to be construed as limiting the disclosure.
Fig. 1 is a flowchart illustrating a component information acquisition method according to an exemplary embodiment.
FIG. 2 is a schematic diagram illustrating an interactive interface and control, according to an exemplary embodiment.
FIG. 3 is a schematic diagram illustrating another interactive interface and control, according to an exemplary embodiment.
FIG. 4 is a schematic diagram illustrating another interactive interface and control, according to an exemplary embodiment.
FIG. 5 is a schematic diagram illustrating an engineering management platform, according to an example embodiment.
Fig. 6 is a flowchart illustrating another component information acquisition method according to an example embodiment.
Fig. 7 is a flowchart illustrating another component information acquisition method according to an example embodiment.
Fig. 8 is a flowchart illustrating another component information acquisition method according to an example embodiment.
Fig. 9 is a flowchart illustrating another component information acquisition method according to an example embodiment.
FIG. 10 is a diagram illustrating dependency information for a component in accordance with an illustrative embodiment.
Fig. 11 is a flowchart illustrating another component information acquisition method according to an example embodiment.
Fig. 12 is a flowchart illustrating another component information acquisition method according to an example embodiment.
FIG. 13 is a diagram illustrating an interaction control, according to an exemplary embodiment.
Fig. 14 is a diagram illustrating a feedback information presentation, according to an example embodiment.
Fig. 15 is a flowchart illustrating another component information acquisition method according to an example embodiment.
Fig. 16 is a flowchart illustrating another component information acquisition method according to an example embodiment.
Fig. 17 is a block diagram illustrating a component information acquisition apparatus according to an exemplary embodiment.
Fig. 18 is a block diagram illustrating another component information acquisition apparatus according to an example embodiment.
FIG. 19 is a block diagram illustrating an electronic device in accordance with an example embodiment.
Detailed Description
In order to make the technical solutions of the present disclosure better understood by those of ordinary skill in the art, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
Fig. 1 is a flowchart illustrating a component information acquisition method according to an exemplary embodiment. It should be noted that the main execution body of the component information acquisition method of the present disclosure is a component information acquisition apparatus. The component information acquiring method according to the embodiment of the present disclosure may be executed by the component information acquiring apparatus according to the embodiment of the present disclosure, and the component information acquiring apparatus may specifically be a hardware device, or software in the hardware device, or the like. The hardware devices are, for example, terminal devices, servers, and the like. As shown in fig. 1, the method for acquiring component information according to this embodiment includes the following steps:
in step 101, a first control on an interactive interface is monitored, where the first control is a control for acquiring component information.
In the embodiment of the disclosure, the interactive interface is provided with a plurality of controls, and by triggering different controls, for example, controls such as a component query control, a component acquisition control, a component deletion control, a component addition control, and the like, various functions can be realized. Accordingly, the operation object can perform various operations on the interactive interface, such as operations of querying the component, obtaining the component, deleting the component, adding the component newly and the like, so as to realize various requirements. For a developer, when trying to acquire component information, the component information acquisition can be realized by triggering a control of the acquisition component.
It should be noted that, for the same control, different functions may be triggered by different operations of the operation object. Therefore, in the embodiment of the disclosure, the target operation can be set for the interactive interface in advance, and the control on the interactive interface can be monitored by identifying the target operation.
Optionally, a first control on the interactive interface may be configured specifically in advance, a specific operation of the first control is defined as a target operation, and a non-specific operation of the first control is defined as a non-target operation; optionally, certain operations of the interactive interface may be specifically configured, defined as target operations, and other operations of the interactive interface may be defined as non-target operations. The first control is used for acquiring component information; the target operation and the non-target operation trigger different functions respectively. In order to enrich the functions of the controls on the interactive interface, the functions which can be triggered by the non-target operation can be further preset.
For example, as shown in fig. 2, the interactive interface 21 is provided with a plurality of controls 22-1 to 22-4 with multiple functions, where the control 22-1 is a control for querying a component, the control 22-2 is a control (i.e., a first control) for a user to acquire a component, the control 22-3 is a control for deleting a component, and the control 22-4 is a control for adding a component; the developer can perform various operations in the interactive interface 21, wherein double-clicking the first control 22 is a target operation, and the other operations are non-target operations, wherein triple-clicking the first control 22 is an operation of updating the component. If the operation of the developer on the first control 22 is monitored to be double-click, and the operation of the developer is indicated as a target operation, the monitoring that the first control is operated can be determined; if the operation of the card sender on the first control 22 is monitored to be a three-click, which indicates that the operation of the developer is a non-target operation, and the operation of the update component is monitored, it may be determined that the first control is not monitored to be operated, but the update control is operated.
It should be noted that, before attempting to monitor the first control on the interactive interface, the operation object may issue a control instruction through a control terminal (such as a remote controller). Accordingly, when the operation object issues an instruction, the instruction can be received and the control can be loaded.
In step 102, key information of a target component input on an interactive interface is received.
The target component can be any component involved in a project. For example, the engineering armor has 10 components 1-10, and in this case, any one of the components 1-10 can be selected as the target component.
The operation object can be any user participating in the development process, such as a developer.
The key information may be information of the determined target component grasped by the operation object, such as a name, an address, and the like of the target component.
In an embodiment of the present disclosure, a developer may input key information of a target component at a specific position on an interactive interface, and accordingly, may receive the key information of the target component.
For example, as shown in FIG. 3, the developer may enter the name "A" of the target component at location 24 and the address "111.101.110" of the target component at location 25 on the interactive interface 21.
It should be noted that, in order to further simplify the interaction process and improve the experience of the developer, in the present disclosure, the manner of the key information of the target component input by the developer may be optimized.
For example, as shown in fig. 4, unlike the input method shown in fig. 3, when the developer attempts to input the address "111.101.110" of the target component on the interactive interface 21, instead of the text box 25 that can be input (supporting the input word by word), a dropdown list box 25-2 (supporting the selection candidate type) as shown in fig. 4 may be provided to select the address "111.101.110" matching the target component among the addresses provided on the interactive interface.
In step 103, when the first control is operated, a first command for acquiring component information is generated according to the key information and the first control and is executed to acquire description information of the target component, wherein the description information includes the key information and basic information of the target component.
In the embodiment of the disclosure, after the first control is monitored to be operated and the key information of the target component is received, the key information of the target component and the identifier of the first control can be sent.
It should be noted that, the present disclosure does not limit the specific manner for sending the key information and the identifier, and may be selected according to the actual situation. For example, the key information And the identifier of the first control may be encapsulated by a JavaScript Object Notation (JSON for short) through Asynchronous JavaScript And XML or HTML (Asynchronous JavaScript And XML, Ajax for short), And then the JSON may be transmitted through Ajax; for another example, the key information and the identifier of the first control may be filled in a JavaScript variable declaration by JavaScript assignment, or sent by Smarty (back-end template engine); for another example, the key information and the identifier of the first control may be sent by a method of requesting a background in an Action (service agent).
It should be noted that, in order to improve the adaptability and reliability of the component information obtaining method, the transmission method may be selected according to actual requirements. Optionally, when trying to send the key information and the identifier of the first control, if the key information and the identifier of the first control need to be checked before being transmitted, a method for requesting a background in an Action may be selected, a JavaScript method is called for checking an On Submit (an event for verification when a Form is submitted) in a Form (which forms a part of an application user interface), and the Action is triggered when a return value of the JavaScript is True (correct); when the returned value of JavaScript is False, no Action is triggered.
For example, when it is monitored that the first control is operated, the address "111.1019.110" (the address format of the target component is wrong) of the target component input by the developer, and the remaining key information and the identification of the first control can be sent. At the moment, checking the address of the target component by calling a JavaScript method through the On Submit in the Form, and identifying that the return value of the JavaScript is False, not triggering the Action and reminding the developer to re-input the address of the target component.
In the embodiment of the disclosure, after the key information and the identifier of the first control are sent, the key information and the identifier of the first control are stored in a specific format. Further, a first command for obtaining component information may be generated and executed to obtain description information of the target component from the storage location.
The description information at least includes key information, and may also include some basic information of the component, for example, the attribute information may include an introduction manner of the component, a brief description of a function, a belonging service line, whether there is a new version, information of a person in charge, dependency information, and the like.
In step 104, the description information is obtained, and the description information is displayed on the interactive interface.
In the embodiment of the disclosure, after the description information of the target component is obtained, the description information can be obtained, and the description information is displayed in the information window on the interactive interface according to the description information and the information window corresponding to the description information.
According to the method and the device, the key information of the target component is received, and the description information of the target component is pulled according to the key information and the first control, so that the description information can be displayed on an interactive interface. Therefore, the information of the component is visualized by simplifying the acquisition of the component information and showing the description information on the interactive interface.
It should be noted that, in the present disclosure, the component information obtaining method is applicable to a component management application, where the application includes a visualization front end and a data processing end. On the basis of the above embodiment, steps S101 to S103 may be executed by the visualization front end; step S104 may be executed by the data processing side.
It should be noted that the visualization front end 1, the data processing end 2, and the application Server (APP Server)3 proposed in the present disclosure can constitute an engineering management platform as shown in fig. 5. Wherein, the data processing terminal 2 is established based on CocoaPods and Homebrew.
CocoaPods, comprising: xcodeprox (a configuration file in the project name. xcodeprox package), CocoaPods-Core (Core file), and CocoaPods-download (download file) for component management.
And Homebrew for environment configuration. Alternatively, the environment configuration function of App is used when trying to install the component management application proposed in the present disclosure on a brand-new computer environment. The data processing end can install Ruby (object-oriented programming scripting language) of a specified version and a standard environment of CocoaPods for the current computer environment through Homebrew. It should be noted that, for part of apps with special requirements, a specific environment may be installed by configuring parameters. For example, the App nail of the business nail needs to be provided with some command line tools, and the data processing end can achieve the purpose by means of Homebrew.
To sum up, the visual front end can display the engineering information, especially the component information, and meanwhile, the engineering information is managed by the data processing end, that is, in the present disclosure, the acquisition of the component information can be realized through the cooperation of the visual front end and the data processing end.
In the present disclosure, in order to further unify the development environment and ensure standardized management of component information, the description information may be stored in a specific format and a specific storage location, so that the visualization front end can obtain the description information.
As a possible implementation manner, as shown in fig. 6, on the basis of the foregoing embodiment, the process of acquiring description information by the visualization front end specifically includes the following steps:
in step 201, the visualization front end obtains a first storage location of a first storage file of the target component.
In embodiments of the present disclosure, the description information may be stored in a particular format to form a first storage file, and the first storage file is stored in a first storage location. The first storage files of the target assembly correspond to the first storage positions one by one. For example, the description information may be stored in YML format to form a first storage file and stored in a first storage location.
It should be noted that, in order to improve the adaptability in the component acquisition process, the specific content of the description information may be expanded according to the actual situation, for example, p.xx in the YML file may be added to expand the description information.
It should be noted that the description information may be stored in YML format to form the first storage file, or may be stored in other formats, for example, TXT, DOCX, and the like to form the first storage file.
In step 202, the first storage file is read according to the first storage location, and the description information is obtained from the first storage file.
In the embodiment of the disclosure, after the visualization front end acquires the first storage location of the first storage file of the target component, the first storage file may be pulled from the first storage location, and then the description information is acquired from the first storage file.
According to the component information acquisition method provided by the embodiment of the disclosure, the first storage position of the first storage file of the target component can be acquired through the visual front end, and the first storage file is read according to the first storage position, so that the description information is acquired from the first storage file. Therefore, the description information can be stored in a specific format and a specific storage position, the Podfile (the specification file for describing at least one project target dependent item) file in CocoaPods can be directly operated by an operation object such as a developer, and the technical problem that the Podfile file is modified randomly by the operation object such as the developer to cause extremely high code risk is solved. Furthermore, the description information is uniformly stored in a YML format to form a first storage file, so that the accuracy and reliability in the component information acquisition process can be improved, the introduction of components is standardized, the development environment can be further uniformly developed, and the standardized management of the component information can be ensured.
It should be noted that, in practical applications, the target component may be a remote component or a local component. The following explains the component information acquisition method proposed by the present disclosure, respectively for the target component being a remote component and a local component.
As a possible implementation manner for the target component being a remote component, as shown in fig. 7, on the basis of the foregoing embodiment, the process of the data processing end executing the first command specifically includes the following steps:
in step 301, the data processing side sends a request for acquiring a data packet to a remote server according to a first command.
Wherein, the data Packet (Packet) refers to a combined data unit of the code information and the description file of the target component; the description file refers to a file for describing component information, such as a component name, an address, and a dependency case.
The dependency condition may be a dependency condition between the service component and the platform component version. For example, business A relies on the current version of the platform component; as another example, business B depends on a previous version of the platform component.
In the embodiment of the disclosure, after the data processing end generates the first command for acquiring the component information, a request for acquiring the data packet may be sent to the remote server according to the first command. Accordingly, the remote server can respond to the request for acquiring the data packet and send the data packet to the data processing terminal.
In step 302, the data processing side receives a data packet sent by the remote server, and extracts the description information from the data packet.
In the present disclosure, the specific manner of extracting the description information from the data packet is not limited, and may be set according to actual situations. For example, the description information may be extracted from the data packet by network packet analysis software such as Wireshark (ethernet).
Further, after the description information is extracted from the data packet, the data processing terminal may generate a first storage file corresponding to the target component according to the description information, and feed back the first storage location to the visualization front end.
For example, after the description information is extracted from the data packet, the data processing end may store the description information in a YML format to generate a first storage file corresponding to the target component, and feed back the first storage location stored in the first storage file to the visualization front end, so that the visualization front end can obtain the first storage location, and read the first storage file according to the first storage location to obtain the description information.
Further, after the data processing side receives the data packet sent by the remote server, the data processing side may manage the code information of the target component.
As a possible implementation manner, as shown in fig. 8, on the basis of the foregoing embodiment, the process of managing, by the data processing end, the code information of the target component in the step S302 specifically includes the following steps:
in step 401, the data processing side extracts the code information of the target component from the data packet.
In the embodiment of the disclosure, the data packet includes the code information of the target component, so that after the data processing end receives the data packet sent by the remote server, the data processing end can extract the code information of the target component from the data packet.
In step 402, the data processing end obtains the description information of the project to which the target component belongs, and determines the storage path of the target component according to the description information of the project.
It should be noted that, in the present disclosure, a mapping relationship between the description information of the project described in the target component and the storage path of the target component is preset. Optionally, after obtaining the description information of the project to which the target component belongs, the storage path of the target component may be determined by querying the mapping relationship. And the project to which the target component belongs corresponds to the storage path of the target component one by one through the description information.
For example, after the data processing end extracts the code information of the target component, the description information 1 of the project 1 to which the target component 1 belongs may be acquired, and then the storage path 1 of the target component 1 may be determined by querying the mapping relationship.
In step 403, the data processing side stores the code information according to the storage path.
Alternatively, when attempting to store code information in accordance with a storage path, the code information may be stored in YML format in accordance with the storage path.
As a possible implementation manner for the target component being a local component, as shown in fig. 9, on the basis of the foregoing embodiment, the process of the data processing side executing the first command specifically includes the following steps:
in step 501, the storage location of the description information fed back by the data processing end is visualized.
It should be noted that, if the target component is a local component, the visualization front end may obtain the storage location of the description information by performing data interaction with the data processing end. Optionally, the visualization front end receives a storage location of the description information fed back by the data processing end.
In step 502, according to the storage location, the description information is read, wherein the description information is stored in a first storage file of the target component, and the storage address of the description information is the first storage location of the first storage file.
It should be noted that, if the target component is a local component, the description information stored in the storage location is also stored in a specific and unified format, such as a YML format.
It should be noted that after acquiring the address of the remote server or the path of the component (essentially, the address information of the component), the data processing side may perform an Install operation using the CocoaPods tool, where the Install operation essentially places the code under a specified folder, and specifies the code path of the component in the configuration file of the project, so as to facilitate the search and compilation by the compiler.
According to the component information acquisition method provided by the embodiment of the disclosure, a matched mode for acquiring the description information by the visual front end can be determined for the target component being a remote component or a local component, so that the visual front end can smoothly acquire the description information. Optionally, if the target component is a remote component, the data processing end may receive a data packet sent by a remote server, so as to extract description information from the data packet, store the description information in a specific format, generate a first storage file, and feed back a first storage location of the first storage file to the visualization front end; if the target component is a local component, the visualization front end can receive the storage position of the description information fed back by the data processing end, and the description information is read according to the storage position. Furthermore, the method does not rely on obtaining the component information in a mode of a command line and the like, the data processing end obtains the component information in advance, or the remote server issues the component information, and then the component information is directly displayed at the visual front end, so that the development efficiency is greatly improved.
Further, after the description information is acquired by the visualization front end, the description information can be displayed on the interactive interface. In the embodiment of the disclosure, the interactive interface comprises a display area for displaying the description information, the display area comprises a plurality of display positions, and interactive controls are arranged on part of the display positions.
For example, as shown in FIG. 10, the interactive interface 21 includes a display area 91 for displaying the description information, and the display area includes a plurality of display positions 91-1 to 91-6, which are 6 display positions. Wherein interaction controls 92-1, 92-5 and 92-6 are laid out on the part of the display positions 91-1, 91-5 and 91-6 related to the subsequent operation.
And whether new version information exists or not can be displayed at a display position 91-5 in the visual front-end interactive interface. Whether the new version information exists or not can be inquired about the latest version information of a current remote component (Software Development Kit, SDK for short) by the data processing end through a CocoaPods command, and the latest version information is transmitted back to the visualization front end for displaying. Therefore, the information displayed on the display position 91-5 can prompt developers and other operation objects to upgrade the SDK in time so as to use the more stable SDK. Meanwhile, the visual front end can display the updating information of the new version of the SDK on the interface, so that operation objects such as developers and the like can clearly and visually observe the updating content of the SDK.
Further, in order to simplify the interaction process and reduce the learning cost of the operation object, different settings may be performed on the interaction control in advance in the present disclosure. Optionally, the responsible person of the SDK can be displayed on the interactive interface at the visualization front end, the visualization front end is closely associated with the chat window and the chat tool, and when an operation object such as a developer encounters a problem, the information of the responsible person is clicked, so that the chat window of the responsible person of the SDK can be opened for fast communication.
For example, as shown in the interactive interface 21 shown in fig. 10, a "responsible person (click name private chat TA)" button is an interactive control 91-6, and if a click operation within a layout position of the interactive control 91-6 is monitored, a chat window and a chat software call instruction may be generated according to a name of a responsible person selected by an operation object, for example, lee, so that the operation object may communicate with the selected responsible person.
In summary, when an operation object such as a developer tries to check the word stock dependency condition of a certain SDK at the visualization front end, only the space on the interactive interface needs to be clicked, at this time, the data processing end retrieves the Podspec file corresponding to the SDK, returns the Denpency information in the Podspec file to the visualization front end, and displays the Denpency information in the interaction interface of the visualization front end. The Podspec file is a support file in CocoaPods for component management.
Therefore, the component information acquisition method provided by the disclosure can provide reliable help for developers unfamiliar with SDK dependency information or operation objects such as engineering management to quickly check the SDK dependency condition through the cooperation of the visual front end and the data processing end, can effectively avoid the problem of SDK sub-library version conflict, and is beneficial to the reduction of unnecessary SDK dependency of the developers.
It should be noted that, in the process of presenting the description information on the interactive interface, for a Project, such as an Xcode Project, whether newly created or already existing on a disk, when being read by the visualization front end for the first time, Project data about the Project is generated, and the Project data, current information of the Project, and a series of configuration information generated subsequently are associated.
As a possible implementation manner, as shown in fig. 11, on the basis of the foregoing embodiment, the process of displaying the description information on the interactive interface specifically includes the following steps:
in step 601, the visualization front end extracts information items from the description information.
The information item may be any information in the description information of the target component. Such as name, address, dependency, etc.
In step 602, the visualization front end loads the information item to a display position corresponding to the information item in the display area.
It should be noted that, in the present disclosure, a mapping relationship between the information item and the display position is preset, and after the information item is extracted from the description information at the visualization front end, the display position corresponding to the information item can be determined by querying the mapping relationship. Further, the information item may be loaded to the display position corresponding to the information item in the display area according to the display position. Wherein, the information items and the display positions are in one-to-one correspondence.
Furthermore, after the description information is displayed on the interactive interface, the operation performed by the operation object on the interactive control can be monitored, and the matched display operation can be performed according to the operation of the operation object. The following explains a case of whether data interaction with the data processing terminal is required when the visualization front end monitors that the control is operated.
As a possible implementation manner for the situation that the visualization front end monitors that data interaction is required to be performed with the data processing end when the control is operated, as shown in fig. 12, on the basis of the above embodiment, the process of displaying the feedback information by the visualization front end specifically includes the following steps:
in step 701, the visualization front end monitors the interactive control.
For example, as shown in fig. 13, the visualization front end may monitor whether a control that the operation of the engineering manager stops is an interactive control 131 to 133, and if the control that the operation of the engineering manager stops is identified as the interactive control 131, and the operation of the engineering manager is identified as a specific operation, which indicates that the operation of the engineering manager is a target operation, it may be determined that the visualization front end monitors that the interactive control 131 is operated.
In step 702, the visualization front end sends the identifier of the operated first interactive control to the data processing end.
The first interactive control refers to any one of the interactive controls monitored and operated by the visualization front end for obtaining feedback information, for example, the interactive control 131 shown in fig. 13.
In the embodiment of the disclosure, after the first interactive control monitored by the visualization front end is operated, the identifier of the first interactive control can be acquired and sent to the data processing end. Accordingly, the data processing end can receive the identification of the first interaction control sent by the visualization front end.
In step 703, the data processing end generates a second command according to the identifier of the first interactive control, executes the second command, obtains feedback information matched with the second command, and feeds the feedback information back to the visualization front end for display.
Wherein the feedback information includes: version information of the target component and dependency of the target component.
Wherein, the second command refers to a command for acquiring feedback information.
In the embodiment of the disclosure, after the data processing end receives the identifier of the first interactive control sent by the visual front end, it is indicated that the first interactive control is triggered, and then a second command may be generated and executed according to the identifier of the first interactive control, so as to obtain feedback information matched with the second command and feed the feedback information back to the visual front end for display.
For example, as shown in fig. 14, after the data processing end receives the identifier 131 of the first interactive control sent by the visualization front end, a second command may be generated and executed according to the identifier of the first interactive control, so as to obtain the version information 141 of the target component and the dependency condition 142 of the target component, and feed back the version information and dependency condition to the visualization front end, and then display the version information and dependency condition on the interactive interface.
It should be noted that, in the present disclosure, specific display positions of the feedback information displayed on the interactive interface are not limited, and may be limited according to actual situations. For example, the version information 141 of the target component and the dependency condition 142 of the target component may be presented in a vertical direction in a manner as presented in fig. 14; for another example, the version information 141 of the target component and the dependency condition 142 of the target component may be presented in a horizontal direction.
As a possible implementation manner for the situation that the visualization front end monitors that data interaction with the data processing end is not required when the control is operated, as shown in fig. 15, on the basis of the above embodiment, the process of displaying the dialog box of the tool by the visualization front end specifically includes the following steps:
in step 801, a visualization front end monitors an interactive control.
It should be noted that step S801 is the same as step S701, and is not described again here.
In step 802, the visualization front end invokes the communication tool according to the operated second interactive control, and displays a dialog box of the communication tool on the interactive interface.
Wherein, the second interactive control refers to an interactive control operated by the visualization front end for obtaining a dialog box of the communication tool, such as the interactive control 132 shown in fig. 13.
In the embodiment of the disclosure, after the second interactive control monitored by the visualization front end is operated, the communication tool can be called according to the operated second interactive control, and the dialog box of the communication tool is displayed on the interactive interface.
According to the component information acquisition method provided by the embodiment of the disclosure, the visual front end can monitor the interactive control, and after the first interactive control and the second interactive control are monitored to be operated, the corresponding contents can be respectively displayed on the interactive interface, so that the adaptability of the component information acquisition method provided by the disclosure is improved, the operation object can be ensured to acquire the required information through the interactive operation on the interactive interface, and the user experience is improved.
It should be noted that, in practical application, the operation object may use an application program to manage the project, or may not use the application program to manage the project; or whether to use the application program to manage the project can be selected at any stage in the project management process. For example, the management of the project by the operation object can be divided into the following three stages: in the first stage, an operation object manages the project to which the target component belongs through an application program; in the second stage, the operation object closes the application program and modifies the project to which the target component belongs in other ways; in the third phase, the operation object starts the application program again, and the project to which the target component belongs is managed through the application program.
Thus, there is a possibility that component information is deleted or modified during the switching process of whether or not to manage a project using an application. Therefore, in the disclosure, before the visualization front end monitors the first control on the interactive interface, the engineering data can be identified.
As a possible implementation manner, as shown in fig. 16, on the basis of the foregoing embodiment, a process of identifying engineering data by a visualization front end specifically includes the following steps:
in step 901, the visual front end loads the project to which the target component belongs, and displays first project data of the project on an interactive interface.
The first engineering data refers to engineering data of an engineering to which the visual front-end loading target component belongs when the engineering belongs, that is, the first engineering data is updated engineering data of the visual front-end.
In step 902, the visualization front end receives second engineering data of the engineering fed back by the data processing end.
The second engineering data refers to engineering data of the engineering to which the visual front-end loading target component belongs when the engineering belongs, that is, the second engineering data is the engineering data updated by the data processing end.
In step 903, the visual front end compares the first engineering data with the second engineering data, and if the first engineering data and the second engineering data are not consistent, the reminding information is displayed on the interactive interface.
In the embodiment of the disclosure, the visualization front end may compare the first engineering data with the second engineering data to identify whether the updated engineering data of the visualization front end and the data processing end are synchronous. If the first engineering data and the second engineering data are consistent, the updated engineering data of the visual front end and the updated engineering data of the data processing end are synchronous, and the information currently displayed by the visual front end can be maintained; if the first engineering data and the second engineering data are not consistent, the updated engineering data of the visual front end and the updated engineering data of the data processing end are not synchronous, and reminding information can be displayed on the interactive interface to remind an operation object to ensure that the updated engineering data of the visual front end and the updated engineering data of the data processing end can be synchronous through updating operation.
It should be noted that, when the visual front end starts or creates a project for the first time, the project of the target component does not carry the first project data, and at this time, the project information of the project can be read from the second storage file of the project in the data processing end and displayed on the interactive interface. Wherein the second storage file may be in YML format.
According to the component information acquisition method provided by the embodiment of the disclosure, the engineering data can be identified by the visual front end before the first control on the interactive interface is monitored, so as to judge whether the updated engineering data of the visual front end and the data processing end are synchronous, and when the updated engineering data of the visual front end and the data processing end are not synchronous, the reminding information is displayed on the interactive interface so as to remind an operation object to ensure that the updated engineering data of the visual front end and the data processing end can be synchronous through updating operation, so that the effectiveness and the reliability of the component acquisition process are improved.
Fig. 17 to 18 are block diagrams illustrating a component information acquisition apparatus according to an exemplary embodiment.
As shown in fig. 17, the device 1000 for acquiring component information is suitable for a component management application, and the device 1000 includes a monitoring unit 121, a receiving unit 122, an acquiring unit 123 and a presenting unit 124.
The monitoring unit 121 is configured to perform monitoring on a first control on an interactive interface, where the first control is a control for acquiring component information;
the receiving unit 122 is configured to perform receiving key information of the target component input on the interactive interface;
the obtaining unit 123 is configured to execute, when a first control is operated, a first command for obtaining component information according to the key information and the first control, and execute the first command to obtain description information of the target component, where the description information includes the key information and basic information of the target component;
the presentation unit 124 is configured to obtain the description information by the execution end, and present the description information on the interactive interface.
In an embodiment of the present disclosure, the application includes a visualization front end and a data processing end.
In the embodiment of the present disclosure, as shown in fig. 18, the obtaining unit 123 in fig. 17 further includes: an obtaining subunit 1231, configured to execute the visualization front end to obtain a first storage location of a first storage file of the target component, read the first storage file according to the first storage location, and obtain the description information from the first storage file.
In an embodiment of the present disclosure, as shown in fig. 18, the component information acquiring apparatus 1000 in fig. 17 further includes: a second sending unit 125, configured to execute the data processing end to send, according to the first command, a request for obtaining the data packet to a remote server; an extracting unit 126, configured to execute the data processing end to receive the data packet sent by the remote server, and extract the description information from the data packet.
In an embodiment of the present disclosure, as shown in fig. 18, the component information acquiring apparatus 1000 in fig. 17 further includes: the feedback unit 127 is configured to execute the data processing end to generate a first storage file corresponding to the target component according to the description information, and feed back the first storage location to the visualization front end.
In an embodiment of the present disclosure, as shown in fig. 18, the component information acquiring apparatus 1000 in fig. 17 further includes: a reading unit 128, configured to execute a storage location where the visualization front end receives the description information fed back by the data processing end, and read the description information according to the storage location, where the description information is stored in a first storage file of the target component, and a storage address of the description information is a first storage location of the first storage file.
In an embodiment of the present disclosure, the interactive interface includes a display area for displaying the description information, the display area includes a plurality of display positions, and an interactive control is laid out on some of the display positions.
In an embodiment of the present disclosure, as shown in fig. 18, the display unit 124 in fig. 17 further includes: a loading subunit 1251 configured to execute the visualization front end to extract an information item from the description information, and load the information item to a display position corresponding to the information item in the display area.
In an embodiment of the present disclosure, as shown in fig. 18, the display unit 124 in fig. 17 further includes: a first monitoring subunit 1242, configured to execute the visualization front end to monitor the interaction control; a sending subunit 1243, configured to execute the visualization front end to send the identifier of the operated first interaction control to the data processing end; a first display subunit 1244, configured to execute the data processing end to generate a second command according to the identifier of the first interactive control, execute the second command, obtain feedback information matched with the second command, and feed the feedback information back to the visualization front end for display.
In an embodiment of the present disclosure, as shown in fig. 18, the display unit 124 in fig. 17 further includes: a second monitoring subunit 1245 configured to execute the visualization front end to monitor the interaction control; a second display subunit 1246, configured to execute the visualization front end to invoke the communication tool according to the operated second interactive control, and display a dialog box of the communication tool on the interactive interface.
In the embodiment of the present disclosure, as shown in fig. 18, the monitoring unit 121 in fig. 17 further includes: a third display subunit 1211, configured to execute the visual front-end loading of the project to which the target component belongs, and display first project data of the project on the interactive interface; a receiving subunit 1212, configured to execute the visualization front end to receive second engineering data of the engineering fed back by the data processing end; a fourth display subunit 1213, configured to execute the visual front-end comparison of the first engineering data and the second engineering data, and if the first engineering data and the second engineering data are not consistent, display a reminder message on the interactive interface.
In the embodiment of the present disclosure, as shown in fig. 18, the monitoring unit 121 in fig. 17 further includes: a fifth display subunit 1214, configured to, when the visualization front end is started for the first time or a project is created, read the project information of the project from the second storage file of the project in the data processing end, and display the project information on the interactive interface.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
The method comprises the steps of receiving key information of a target component through a visual front end, sending the key information and an identifier of a first control to a data processing end, and pulling description information of the target component through the data processing end so that the visual front end can display the description information on an interactive interface. Therefore, the visual front end simplifies the acquisition of the component information through the cooperation between the visual front end and the data processing end, and displays the description information on the interactive interface, so that the information of the component is visualized.
In order to implement the above embodiments, the present disclosure also provides an electronic device, as shown in fig. 19, where the electronic device 8000 includes: a processor 801; one or more memories 802 for storing instructions executable by the processor 801; wherein the processor 801 is configured to execute the component information acquiring method according to the above embodiment. The processor 801 and the memory 802 are connected by a communication bus.
To implement the above embodiments, the present disclosure also provides a storage medium comprising instructions, such as the memory 802 comprising instructions, executable by the processor 801 of the apparatus 1000 to perform the above method. Alternatively, the storage medium may be a non-transitory computer readable storage medium, which may be, for example, a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (10)

1. A component information acquisition method, adapted to a component management application, the component information acquisition method comprising:
monitoring a first control on an interactive interface, wherein the first control is used for acquiring component information;
receiving key information of a target component input on the interactive interface;
when the first control is operated, generating a first command for acquiring component information according to the key information and the first control and executing the first command to acquire description information of the target component, wherein the description information comprises the key information and basic information of the target component; and
and acquiring the description information, and displaying the description information on the interactive interface.
2. The component information acquisition method according to claim 1, wherein the application program includes a visualization front end and a data processing end.
3. The component information acquisition method according to claim 2, wherein the acquiring the description information further includes:
the visual front end acquires a first storage position of a first storage file of the target assembly, reads the first storage file according to the first storage position, and acquires the description information from the first storage file.
4. The component information acquiring method according to claim 2 or 3, wherein if the target component is a remote component, the executing the first command includes:
the data processing end sends a request for acquiring the data packet to a remote server according to the first command; and
and the data processing end receives the data packet sent by the remote server and extracts the description information from the data packet.
5. The method according to claim 2, wherein if the target component is a local component, the acquiring the description information includes:
and the visual front end receives the storage position of the description information fed back by the data processing end, and reads the description information according to the storage position, wherein the description information is stored in a first storage file of the target component, and the storage address of the description information is the first storage position of the first storage file.
6. The component information acquisition method according to claim 2, wherein the presenting the description information on the interactive interface includes:
and the visual front end extracts information items from the description information and loads the information items to display positions corresponding to the information items in the display area.
7. The component information acquisition method according to claim 6, further comprising, after the presenting the description information on the interactive interface:
the visual front end monitors the interactive control;
the visualization front end sends the identifier of the operated first interactive control to the data processing end;
and the data processing terminal generates a second command according to the identifier of the first interactive control, executes the second command, acquires feedback information matched with the second command and feeds the feedback information back to the visual front end for display.
8. A component information acquisition apparatus adapted to a component management application, the apparatus comprising:
the monitoring unit is configured to monitor a first control on an interactive interface, wherein the first control is used for acquiring component information;
a receiving unit configured to perform receiving key information of a target component input on the interactive interface;
an obtaining unit, configured to execute, when the first control is operated, a first command for obtaining component information according to the key information and the first control, and execute the first command to obtain description information of the target component, where the description information includes the key information and basic information of the target component; and
and the display unit is configured to acquire the description information and display the description information on the interactive interface.
9. An electronic device, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the component information acquisition method according to any one of claims 1 to 7.
10. A storage medium in which instructions are executed by a processor of an electronic device, so that the electronic device can perform the component information acquisition method according to any one of claims 1 to 7.
CN202011011786.9A 2020-09-23 2020-09-23 Component information acquisition method and device, electronic equipment and storage medium Pending CN112256522A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011011786.9A CN112256522A (en) 2020-09-23 2020-09-23 Component information acquisition method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011011786.9A CN112256522A (en) 2020-09-23 2020-09-23 Component information acquisition method and device, electronic equipment and storage medium

Publications (1)

Publication Number Publication Date
CN112256522A true CN112256522A (en) 2021-01-22

Family

ID=74231958

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011011786.9A Pending CN112256522A (en) 2020-09-23 2020-09-23 Component information acquisition method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN112256522A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113391867A (en) * 2021-06-16 2021-09-14 杨永飞 Big data service processing method and service server based on digitization and visualization

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101493750A (en) * 2008-11-28 2009-07-29 深圳华为通信技术有限公司 Application program control input method and device based on touch screen input
US20100153977A1 (en) * 2008-12-11 2010-06-17 Sap Ag Creating Step Descriptions for Application Program Interfaces
CN105974804A (en) * 2016-05-09 2016-09-28 北京小米移动软件有限公司 Method and device for controlling equipment
CN107515702A (en) * 2016-06-16 2017-12-26 苏宁云商集团股份有限公司 A kind of page interaction and device
CN109118178A (en) * 2018-08-27 2019-01-01 深圳市商汤科技有限公司 Data processing method and device, electronic equipment and computer storage medium
CN110430558A (en) * 2019-06-26 2019-11-08 深圳绿米联创科技有限公司 Apparatus control method, device, electronic equipment and storage medium
CN110716714A (en) * 2019-09-30 2020-01-21 奇安信科技集团股份有限公司 Component creation method, device, computer system, and computer-readable storage medium
CN110807536A (en) * 2019-09-30 2020-02-18 北京三快在线科技有限公司 Account information association method and device, electronic equipment and storage medium

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101493750A (en) * 2008-11-28 2009-07-29 深圳华为通信技术有限公司 Application program control input method and device based on touch screen input
US20100153977A1 (en) * 2008-12-11 2010-06-17 Sap Ag Creating Step Descriptions for Application Program Interfaces
CN105974804A (en) * 2016-05-09 2016-09-28 北京小米移动软件有限公司 Method and device for controlling equipment
CN107515702A (en) * 2016-06-16 2017-12-26 苏宁云商集团股份有限公司 A kind of page interaction and device
CN109118178A (en) * 2018-08-27 2019-01-01 深圳市商汤科技有限公司 Data processing method and device, electronic equipment and computer storage medium
CN110430558A (en) * 2019-06-26 2019-11-08 深圳绿米联创科技有限公司 Apparatus control method, device, electronic equipment and storage medium
CN110716714A (en) * 2019-09-30 2020-01-21 奇安信科技集团股份有限公司 Component creation method, device, computer system, and computer-readable storage medium
CN110807536A (en) * 2019-09-30 2020-02-18 北京三快在线科技有限公司 Account information association method and device, electronic equipment and storage medium

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113391867A (en) * 2021-06-16 2021-09-14 杨永飞 Big data service processing method and service server based on digitization and visualization
CN113391867B (en) * 2021-06-16 2022-07-01 刘叶 Big data service processing method and service server based on digitization and visualization

Similar Documents

Publication Publication Date Title
CN108108297B (en) Method and device for automatic testing
CN109542412A (en) Interface message generation method, device, computer equipment and storage medium
EP1906305B1 (en) Method and system for data preparation and communication between software applications
CN109271157B (en) Software development method, device and computer readable storage medium
CN111695827B (en) Business process management method and device, electronic equipment and storage medium
CN112256522A (en) Component information acquisition method and device, electronic equipment and storage medium
CN112905441A (en) Test case generation method, test method, device and equipment
CN113934832A (en) Interactive processing method, device, equipment, medium and program product based on session
CN113364515B (en) Satellite remote control method, device, equipment and storage medium based on Xstate
CN112486797A (en) Interface test method and device
CN113407288A (en) Data processing method and device and electronic equipment
CN111125205A (en) Signboard data display method, terminal and storage medium
CN114610446B (en) Method, device and system for automatically injecting probe
CN114443294B (en) Big data service component deployment method, system, terminal and storage medium
CN111488286B (en) Method and device for independently developing Android modules
CN114936152A (en) Application testing method and device
CN110727457A (en) Component management method, device, storage medium and electronic equipment
CN117112654B (en) City data display method, device, computer equipment and storage medium
CN115080152B (en) Broker configuration method and device of message middleware, computer equipment and medium
CN113010189B (en) Database installation method, device, equipment and storage medium
CN114995836A (en) Cloud platform management method, device, equipment and medium
CN115185565A (en) Constraint-based article construction method, apparatus, device, medium, and program product
CN112698885A (en) Operating method and device
US20090171940A1 (en) Method and system for central data querying
CN116820414A (en) Front-end custom delivery method, device, equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination