CN117215558A

CN117215558A - Visual software development method, device, equipment and medium for android

Info

Publication number: CN117215558A
Application number: CN202311258882.7A
Authority: CN
Inventors: 杨自成; 王宁; 廖丹; 陈强
Original assignee: China Construction Bank Corp; CCB Finetech Co Ltd
Current assignee: China Construction Bank Corp; CCB Finetech Co Ltd
Priority date: 2023-09-26
Filing date: 2023-09-26
Publication date: 2023-12-12

Abstract

The application provides a visual software development method, device, equipment and medium based on android. Relates to the technical field of computers. The method comprises the following steps: carrying out integrated processing on a plurality of preset components to obtain an integrated plug-in; responding to the triggering operation of the integrated plug-in, and displaying a visual interface of the assembly; determining a target component based on selection operation of a preset component in a visual interface of the component, and acquiring a component code corresponding to the target component; and developing software based on the component code corresponding to the target component. The method reduces manual operation in the software development process, ensures that the software development is more automatic and intelligent, and improves the software development efficiency.

Description

Visual software development method, device, equipment and medium for android

Technical Field

The application relates to the technical field of computers, in particular to a visual software development method, device, equipment and medium based on android.

Background

With the continuous expansion of business involved in companies/enterprises, the need to develop new projects is also increasing. In daily development of android, various dependency libraries are usually accessed to develop software, so that the development process is quickened.

Currently, to access the dependency libraries during development, a developer is typically required to manually operate to add each dependency library that needs to be accessed to the software development code. This way of relying on library access, the comparison relies on manual operations, resulting in inefficient development. Meanwhile, under the condition that the manual operation is in error, a large amount of time is required to be consumed for troubleshooting the error, and time cost and labor cost are increased.

In addition, when a plurality of developers are required to complete the new project in a coordinated manner, each dependent library is configured through manual operation, unified development standards are lacking, and development confusion phenomenon and compatibility of accessed dependent libraries are easy to occur.

Disclosure of Invention

The application provides a visual software development method, device, equipment and medium based on android, which are used for solving the problems of low development efficiency, time cost waste and labor cost caused by manual operation access to a dependency library in the prior art.

In a first aspect, the present application provides a visual software development method for android, including:

carrying out integrated processing on a plurality of preset components to obtain an integrated plug-in; the preset component characterizes a dependency library of software development; the integrated plug-in characterizes plug-ins installed in a build tool for performing software development;

Responding to the triggering operation of the integrated plug-in, and displaying a visual interface of the assembly; the visual interface of the component characterizes an interface for selecting a preset component;

determining a target component based on selection operation of a preset component in a visual interface of the component, and acquiring a component code corresponding to the target component; wherein the selecting operation includes selecting a code acquisition location; the code acquisition position corresponds to a code acquisition mode;

and developing software based on the component code corresponding to the target component.

In one possible design, the determining the target component based on the selection operation of the preset component in the visual interface of the component includes:

acquiring component version information; wherein, the component version information characterizes a component version number input in a visual interface of the component; the component version number represents the updating times of a preset component in the integrated plug-in;

determining a first component matched with the component version information from the plurality of preset components, and displaying the first component in a visual interface of the component;

the target component is determined in response to a selection operation of the first component.

In one possible design, the obtaining the component code corresponding to the target component includes:

if the code selected by the selecting operation obtains a position representation network library, obtaining the component code of the target component from a preset first warehouse; the first warehouse characterizes a database which needs to be accessed in a networking way;

if the code selected by the selecting operation obtains a position representation local library, obtaining a component code of the target component from a second warehouse corresponding to the construction tool; wherein the second repository characterizes a database that does not require networking access.

In one possible design, the selecting operation includes selecting a project name; the software development is performed based on the component code corresponding to the target component, and the software development method comprises the following steps:

and carrying out software development on the project corresponding to the project name based on the component code corresponding to the target component.

In one possible design, the number of target components is a plurality; the software development is performed based on the component code corresponding to the target component, and the software development method comprises the following steps:

determining the splicing sequence of each target assembly;

based on the splicing sequence, splicing the component codes of the target components to obtain spliced component codes;

And performing software development based on the spliced component codes.

In one possible design, the software development based on the spliced component code includes:

adding the spliced component codes to a project configuration file; the project configuration file characterizes a file for initializing and configuring a project needing to be subjected to software development;

and carrying out software development based on the project configuration file.

In one possible design, the visual interface of the display assembly in response to a triggering operation on the integrated plug-in includes:

and responding to the triggering operation of the integrated plug-in, calling a visualization tool package, and displaying a visualization interface of the component based on the visualization tool package.

In one possible design, the integrating processing is performed on the plurality of preset components to obtain an integrated plug-in, including:

carrying out security verification on each preset component to obtain preset components after security verification;

and carrying out integration processing on the preset assembly after the security verification to obtain the integrated plug-in.

In one possible design, after integrating the plurality of preset components to obtain an integrated package, the method further includes:

Acquiring component update information; wherein the component update information characterizes the update information of the preset component;

and updating each preset component in the integrated plugin based on the component updating information.

In one possible design, the plurality of preset components characterize at least the following dependency libraries: third party library, tool class, SDK package, JDK package, general resource library, network library, software development template, functional module and safety tool library.

In a second aspect, the present application provides an android-based visualization software development apparatus, including:

the integrated unit is used for carrying out integrated processing on a plurality of preset components to obtain an integrated plug-in; the preset component characterizes a dependency library of software development; the integrated plug-in characterizes plug-ins installed in a build tool for performing software development;

the display unit is used for responding to the triggering operation of the integrated plug-in, and displaying a visual interface of the assembly; the visual interface of the component characterizes an interface for selecting a preset component;

the selection unit is used for determining a target component based on the selection operation of a preset component in the visual interface of the component and acquiring a component code corresponding to the target component; wherein the selecting operation includes selecting a code acquisition location; the code acquisition position corresponds to a code acquisition mode;

And the development unit is used for carrying out software development based on the component code corresponding to the target component.

In one possible design, the selection unit includes:

a determining unit, configured to obtain component version information; wherein, the component version information characterizes a component version number input in a visual interface of the component; the component version number represents the updating times of a preset component in the integrated plug-in;

In one possible design, the selection unit includes:

the acquisition unit is used for acquiring the component codes of the target component from a preset first warehouse if the codes selected by the selection operation acquire the position representation network library; the first warehouse characterizes a database which needs to be accessed in a networking way;

In one possible design, a development unit includes:

and the software development unit is used for carrying out software development on the project corresponding to the project name based on the component code corresponding to the target component when the selection operation comprises the selection of the project name.

In one possible design, a development unit includes:

a splicing unit, configured to determine a splicing order of each target component when the number of target components is plural;

and performing software development based on the spliced component codes.

In one possible design, the splice unit is for:

and carrying out software development based on the project configuration file.

In one possible design, the display unit is configured to:

In one possible design, the integrated unit is for:

In one possible design, the apparatus further comprises:

an updating unit configured to: after integrating a plurality of preset components to obtain an integrated plug-in, acquiring component update information; wherein the component update information characterizes the update information of the preset component;

In a third aspect, an embodiment of the present application provides a computer apparatus, including: at least one processor and memory; the memory stores computer-executable instructions; the at least one processor executes the computer-executable instructions stored by the memory, causing the at least one processor to perform the method of visual-based software development of android as described above in the first aspect and the various possible designs of the first aspect.

In a fourth aspect, embodiments of the present application provide a computer readable storage medium, where computer executable instructions are stored, when executed by a processor, to implement the android visualization-based software development method according to the first aspect and the various possible designs of the first aspect.

In a fifth aspect, embodiments of the present application provide a computer program product comprising a computer program which, when executed by a processor, implements the android-based visualization software development method according to the first aspect and the various possible designs of the first aspect.

The android-based visual software development method, device, equipment and medium provided by the application can be used for firstly componentizing a dependency library which needs to be accessed in software development to obtain a plurality of preset components. And then, a plurality of preset components can be integrated to obtain an integrated plug-in, so that a developer can be prevented from searching the dependency library and reloading the dependency library, the time is saved, the potential safety hazard problem of the dependency library is avoided, and the safety and reliability of accessing the dependency library are improved. At this time, after the integrated plug-in is installed in the build tool for performing software development, the visual interface of the component may be displayed in response to a trigger operation on the integrated plug-in, and the target component may be determined based on a selection operation on a preset component in the visual interface of the component, and then a component code corresponding to the target component may be acquired to perform software development based on the component code corresponding to the target component. The software development mode can avoid manual code writing by a developer and access of the dependency library, thereby not only avoiding manual errors, but also improving the software development efficiency. Meanwhile, the code writing rule of each component is unified through the visualized integrated plug-in, so that the development process or the initialization process of the software can be more unified and standardized.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.

FIG. 1 is a schematic diagram of a prior art software development process;

fig. 2 is a flowchart of a visual software development method based on android provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of a plug-in management interface in a build tool according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a triggering operation of an integrated plug-in according to an embodiment of the present application;

FIG. 5 is a flowchart of another method for developing android visualization-based software provided by an embodiment of the present application;

FIG. 6 is a schematic diagram of a visual interface of a component according to an embodiment of the present application;

fig. 7 is an overall flow diagram of a visual software development method based on android provided by the embodiment of the application;

fig. 8 is a schematic structural diagram of a visual software development device based on android provided by the embodiment of the application;

fig. 9 is a schematic structural diagram of another android visual-based software development device according to an embodiment of the present application;

Fig. 10 is a schematic structural diagram of a computer device according to an embodiment of the present application.

Specific embodiments of the present application have been shown by way of the above drawings and will be described in more detail below. The drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but rather to illustrate the inventive concepts to those skilled in the art by reference to the specific embodiments.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.

In the technical scheme of the application, the related processes of collecting, storing, using, processing, transmitting, providing, disclosing and the like of the information such as financial data or user data are in accordance with the regulations of related laws and regulations, and the public welfare is not violated. The user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or sufficiently authorized by each party, and the collection, use and processing of related data is required to comply with related laws and regulations and standards, and is provided with corresponding operation entries for the user to select authorization or rejection.

The term "and/or" is used herein to describe only one relationship, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist together, and B exists alone. In addition, the term "at least one" herein means any one of a plurality or any combination of at least two of a plurality, for example, including at least one of A, B, C, and may mean including any one or more elements selected from the group consisting of A, B and C.

Term interpretation:

and (3) groupwise: an efficient software design model that splits a large application into multiple independent modules, each of which may form a separate component.

These components can be independently developed, tested and deployed, thereby improving the efficiency and flexibility of software development. At the same time, componentization may also improve code reusability and maintainability because each component is independent and can be modified and updated without affecting the other components. Through the dependence, collaboration and communication of the components, a complete application program can be constructed, and a more flexible, extensible and maintainable software development mode is realized.

And (3) visualization: a mode of expressing data through visual elements is that a user can complete corresponding operation simply, accurately and efficiently through a visual page.

Item initialization: refers to creating an infrastructure of items so that code can be written and applications built later on successfully.

In software development, project initialization is a very important step, and code can be written smoothly only if project initialization is completed correctly.

Code template: refers to a pre-designed code structure and function, which can be used as a reusable code to help developers quickly construct new application programs.

At this time, development efficiency, code quality and maintainability can be improved through the code template, and reuse and standardization of codes are realized.

Gradle: a modern build tool for automated project build, test and deployment. It is widely used for Java and Android application development, but also supports other languages and technologies. Using Gradle, project build tasks, compile source code, run unit testing, package applications can be defined, and build processes can be customized as needed. It supports modular construction and allows easy management of multiple sub-items and their dependencies.

Gradle has a flexible dependency management system, and can easily manage the dependency relationship between the third party library and the plugin. The required libraries and plug-ins can be specified in the build script and Gradle will automatically download and install them.

Gradle has a strong incremental build capability. It will track changes to the file and reconstruct only the affected parts, thereby improving the speed and efficiency of construction. In addition, gradle also supports parallel construction, can simultaneously execute a plurality of tasks, and quickens the overall construction time.

Fig. 1 is a schematic diagram of a software development process in the prior art. As shown in fig. 1, in the prior art, in the case of receiving a software development request, a software dependent package corresponding to the software development request may be determined. Then, the developer can write codes manually, load corresponding software dependent packages, and develop software based on the loaded software dependent packages.

When a developer develops a new project, the process of creating the new project is very complicated due to the fact that a software dependent package is required to be manually introduced, and development efficiency is affected.

Meanwhile, because the dependency package updating iteration speed is high, a developer is required to select an adaptive dependency package from a plurality of dependency packages to integrate, and non-compliance references can cause security problems, compatibility problems and the like, so that the development work of projects is easily influenced.

Meanwhile, through a large number of manual operations, the following problems are liable to occur in the process of creating an item and initializing the created item:

1) Code structure confusion: since developers usually create projects according to own writing habits and initialize the projects, the method easily causes disordered code file distribution, loose code organization, unclear relation among code structures, no compliance with coding standards and the like.

2) The environment configuration is chaotic: in the process of initializing projects, the configuration of the environment is critical, and in the case that the configuration of the environment is inconsistent after manual operation by different staff, the later maintenance is difficult. For example, in the case where software is configured with different versions of SDKs (Software Development Kit, software development kits), compatibility problems are easily caused.

3) Lack of uniform standardization: because of the lack of unified standards during project initialization, it is difficult to follow related technical specifications and development standards during subsequent function implementation, and further it is difficult to ensure the functional stability, reliability and safety of the application program.

4) Lack of unified project planning: because a unified initialization mode is not adopted, a development team does not have unified planning in the early stage of creation, so that development difficulty of projects in the later stage is increased, and development time and cost are increased.

5) Causing a safety risk: in the project development process, a dependency library and a framework are required to be used for realizing specific functions or accelerating the development process, and if unified project initialization is not adopted, the used dependency library and framework are difficult to follow the best practice and license requirements, and then the security problem and the compatibility problem of the dependency library are easy to occur.

6) Causing writing errors: without unified specification and management, a developer may cause writing errors while writing, resulting in a series of project problems.

7) Unreasonable project structure: without unified specifications, it is difficult for a developer to perform unified and reasonable project structure planning when creating a project, for example, the contents of project structure planning may include creation of a project folder, basic building configuration, necessary resources, and corresponding directory structures.

Aiming at the technical problems, the application provides the following technical conception: and the integrated plug-in is obtained through integrating the dependency library, and the integrated spread is installed in a construction tool, so that the standard is unified for each component, and the problem of disordered coding is avoided. And then, a user can select the dependency library through a visual display interface, the dependency library is loaded, and a corresponding code template is automatically generated so as to initialize the project, so that the initialization efficiency and the software development efficiency of the project are improved, and the time cost and the labor cost are saved. Meanwhile, the step that a developer writes codes manually to load the dependent libraries is avoided, and manual errors are avoided.

The following describes the technical scheme of the present application and how the technical scheme of the present application solves the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.

Fig. 2 is a flowchart of a visual software development method based on android provided by an embodiment of the application. As shown in fig. 2, the android-based visualization software development method includes:

s201, integrating a plurality of preset components to obtain an integrated plug-in.

The method comprises the steps that a dependency library for software development is characterized by a preset component; the integrated plug-in characterizes the plug-in installed in the build tool that performs the software development.

In one example, the preset component may be understood as an independent module that may be used in the software development process, for example, the preset component may be a third party library, a functional module, a universal resource, or the like.

In one example, multiple preset components may be integrated to obtain an integrated plug-in.

Thereafter, the integrated plug-in may be installed into the build tool for software development and the build tool for software development restarted to view the integrated plug-in the management of the plug-in the build tool for software development. The construction tool for developing the software can be the Gradle tool.

In one example, fig. 3 is a schematic diagram of a plug-in management interface in a build tool according to an embodiment of the present application. As shown in fig. 3, the plug-ins installed by the build tool may be presented in a plug-in management interface, and corresponding plug-in profile information, e.g., plug-in 1, plug-in 2, and plug-in 3 as shown in fig. 3. Assuming that the plug-in 2 is an integrated plug-in, and after detecting a triggering operation on the integrated plug-in, plug-in detail information of the integrated plug-in is displayed in the plug-in management interface.

In one example, the plug-in details of the integrated plug-in may include: plug-in icon information (such as the icon shown in fig. 3), plug-in name (such as plug-in 2 shown in fig. 3), company website to which the plug-in belongs (such as the official website shown in fig. 3), plug-in version number (such as the version number shown in fig. 3), plug-in address (such as the plug-in address shown in fig. 3), plug-in function description (such as the plug-in description shown in fig. 3), plug-in version change condition (such as the plug-in version change shown in fig. 3), and the like.

In one example, after installing the integration plugin into the build tool that performs the software development and restarting the build tool, the integration success identification may be presented at the top of the build tool so that the software development may be performed by triggering the integration success identification.

S202, responding to triggering operation of the integrated plug-in, and displaying a visual interface of the assembly.

The visual interface of the component characterizes an interface for selecting a preset component.

In one example, fig. 4 is a schematic diagram of a triggering operation of an integrated plug-in according to an embodiment of the present application. As shown in fig. 4, it is assumed that the integration success flag is "APPS" as shown in fig. 4, at this time, the componentized integration button may be displayed by triggering the integration success flag "APPS", and after detecting a triggering operation of the componentized integration button, a visual interface of the component is displayed, so that a preset component may be selected, and the selected preset component may be integrated into an item.

At this point, the visual interface of the component may be presented in response to a triggering operation on the integrated plug-in. In the visual interface of the components, each preset component which can be selected can be displayed.

In another example, after detecting the triggering operation of the project groupware integration button, the visual interface of the groupware is displayed, so that the preset groupware can be selected and integrated into the project. At this point, new components may be added to the existing project.

In one example, after triggering the integration success identification "APPS," a help document button, an introduction document button, a related button, etc. may be presented in addition to the componentized integration button, such that a developer knows about the relevant information of the integrated component through the help document button, or the introduction document button, or the related button.

In one example, as shown in FIG. 4, items that have been integrated may also be viewed by triggering an item button in the integrated success flag "APPS".

In one example, all preset components in the component plug-in may be displayed first in the visual interface of the components, part of the preset components which are most commonly used may be displayed first, or the preset components may not be displayed first. Thereafter, the preset components matched with the search operation can be displayed in the visual interface of the components through the search operation.

S203, determining a target component based on selection operation of a preset component in a visual interface of the component, and acquiring a component code corresponding to the target component.

Wherein the selecting operation includes selecting a code acquisition location; the code acquisition position corresponds to the code acquisition mode.

In one example, in the case that a preset component is displayed in the visual interface of the component, a target component may be obtained by selecting from the displayed preset components; and under the condition that the preset component is not displayed in the visual interface of the component, selecting the preset component matched with the search operation from the integrated plugin as a target component.

In one example, the selection operation of the preset component may be performed once or multiple times, and after the selection is completed, the target component is obtained. Based on this, the number of target components may be one or a plurality.

In one example, after determining the target component, the component code corresponding to the target component may be acquired from the code acquisition location according to the selected code acquisition location by a corresponding code acquisition manner.

In one example, the code acquisition manner may include: a manner of acquiring through a network and a manner of acquiring not through a network (i.e., a local acquisition manner).

S204, performing software development based on the component codes corresponding to the target components.

In one example, component code corresponding to the target component may be added to the created software development project, so that software development may be performed based on the component code.

As can be seen from the above description, according to the embodiment of the present application, the dependency library that needs to be accessed by software development can be modularized to obtain a plurality of preset components. And then, a plurality of preset components can be integrated to obtain an integrated plug-in, so that a developer can be prevented from searching the dependency library and reloading the dependency library, the time is saved, the potential safety hazard problem of the dependency library is avoided, and the safety and reliability of accessing the dependency library are improved. At this time, after the integrated plug-in is installed in the build tool for performing software development, the visual interface of the component may be displayed in response to a trigger operation on the integrated plug-in, and the target component may be determined based on a selection operation on a preset component in the visual interface of the component, and then a component code corresponding to the target component may be acquired to perform software development based on the component code corresponding to the target component. The software development mode can avoid manual code writing by a developer and access of the dependency library, thereby not only avoiding manual errors, but also improving the software development efficiency. Meanwhile, the code writing rule of each component is unified through the visualized integrated plug-in, so that the development process or the initialization process of the software can be more unified and standardized.

Fig. 5 is a flowchart of another method for developing android-based visualization software according to an embodiment of the present application. As shown in fig. 5, the method for developing the android visual software includes:

s501, carrying out security verification on each preset component to obtain preset components after security verification.

In one example, the preset component characterizes a dependency library of software development.

In one example, the preset component may characterize at least the following dependency library: third party libraries, tool classes, SDK packages, JDK packages (Java Development Kit, java language software development kit), general resource libraries, network libraries, software development templates, functional modules, and security tool libraries.

The tool class can be understood as a static method, and represents a common method in the general and non-business fields.

The universal resource library characterizes a universal resource used in a software development process, for example, the universal resource can be a picture resource, an audio resource and the like.

The network library characterizes the network communication resources required by the software, e.g., the network library may include a request header, a request body, etc.

The software development template characterizes a project structure for performing software development, a code template for performing software development, an environment variable for performing software development, and the like, wherein the content of the project structure can comprise: code directory structure, files contained under each code directory, class files, etc.

The function template characterizes the functions of software development, and at this time, the functions can be reused by modularizing the developed functions.

The secure tool library characterizes the tool library for security detection or security encryption.

In the embodiment, the dependency library needed in the software development process can be modularized to obtain each preset component, so that the time for searching the dependency library is saved, and the reusability and maintainability of the dependency library can be realized.

In one example, the security verification performed on the preset components is used for determining whether the preset components have potential risks or vulnerabilities, and at this time, the preset components after the security verification can be obtained by performing security detection on each preset component and after the security detection of the preset components passes, so that the security and reliability of the preset components in use can be ensured.

In another example, the security verification performed on the preset component may be understood as a process of performing security encryption on the preset component, for example, the function module may be encrypted, and after the function module is securely encrypted, the function module after the security verification may be obtained, so that the security of the function developed by the user may be ensured.

Based on the above, according to the embodiment of the application, the security detection and/or the security encryption can be performed on each preset component according to the actual needs, so as to obtain the preset component after the security verification.

S502, carrying out integration processing on the preset assembly after security verification to obtain an integrated plug-in.

In one example, after the preset components after security verification are integrated, component update information of each preset component in the integrated plug-in can be paid attention to at any time after the integrated plug-in is obtained, after the preset component update is detected, the component update information is timely obtained, and each preset component in the integrated plug-in is updated based on the component update information.

According to the embodiment, each preset component in the integrated plug-in can be updated in time, so that the software development requirement can be better met, and the influence on the software development progress due to untimely updating of the components is avoided.

In one example, after the integrated plug-ins are obtained (or after the updates to the preset components in the integrated plug-ins are completed), the obtained integrated plug-ins may be installed in a build tool that performs software development. At this point, the integrated success flag "APPS" as shown in fig. 4 may be presented in the build tool.

S503, responding to the triggering operation of the integrated plug-in, calling a visualization tool package, and displaying a visualization interface of the component based on the visualization tool package.

In one example, the triggering operation of the integrated plug-in may be understood as the triggering operation of the componentized integrated button as shown in fig. 4.

In one example, a visualization toolkit may be understood as a GUI (Graphical User Interface ) toolkit.

In one example, the visual interface of the component can be displayed by calling the visual package in response to the triggering operation of the integrated plug-in, so that the visual interface of the component can be displayed flexibly and quickly through the GUI package to select a preset component required in the software development process in the visual interface of the component.

S504, determining a target component based on selection operation of a preset component in a visual interface of the component.

Fig. 6 is a schematic diagram of a visual interface of a component according to an embodiment of the present application.

In one example, as shown in FIG. 6, selection component version information may be included in the visual interface of the component. The method comprises the steps that component version information characterizes a component version number input in a visual interface of a component; the component version number characterizes the number of updates of a preset component in the integrated plug-in.

For example, in the case where the integration processing is performed on a plurality of preset components for the first time to obtain an integrated plug-in, the component version information may be determined to be "1.0.1".

In one example, the component version information may further include information characterizing a function/type corresponding to the preset component, for example, in a case where the preset component is a SNAPSHOT function component, the component version information may be "snap shot".

Based on the above, in the case that the component version information may be "1.0.1-snappshot", the first integrated preset component with the SNAPSHOT function is characterized.

At this time, the first component matched with the component version information can be determined from a plurality of preset components of the integrated plug-in by acquiring the component version information input by the developer, and the first component is displayed in a visual interface of the component.

Thereafter, the target component may be determined in response to a selection operation of the first component.

For example, assuming that the component version information is "1.0.4-ABCD" as shown in fig. 6, and that the first components determined to be matched with the component version information "1.0.4-ABCD" from among the plurality of preset components of the integrated package are "preset component 1", "preset component 2", "preset component 3", "preset component 4", "preset component 5", "preset component 6", "preset component 7" as shown in fig. 6, the selection may be performed by selecting each of the first components, and assuming that the selection operation indicates the selection of "preset component 1", "preset component 2", "preset component 3" and "preset component 7", the target components are "preset component 1", "preset component 2", "preset component 3" and "preset component 7".

According to the embodiment, the first component can be quickly found out from the massive preset components contained in the integrated plug-in through the component version information, so that the speed of determining the target component is increased, and the efficiency is improved.

In one example, after obtaining the target component, the steps described below in S505 may be performed.

S505, acquiring the component codes corresponding to the target components.

In one example, as shown in FIG. 6, a selection code acquisition location may also be included in the visual interface of the component. Wherein the code acquisition position corresponds to the code acquisition mode.

In one example, the code acquisition manner may be divided into the following two types: a mode of acquiring through a network and a mode of acquiring not through the network. The method comprises the steps of obtaining component codes from a network library through a representation obtained through a network, and obtaining the component codes from a local library without the representation obtained through the network.

In one example, if the code selected by the selecting operation obtains the location characterization network library, the component code of the target component is obtained from a preset first warehouse.

Wherein the first repository characterizes a database requiring networked access. For example, the first warehouse may be a maven warehouse, a jcenter warehouse, or the like.

At this time, the code acquisition position may be "network library" as shown in fig. 6.

In one example, if the code acquisition location selected by the selection operation characterizes the local library, the component code of the target component is acquired from a second repository corresponding to the build tool.

Wherein the second repository characterizes a database that does not require networking access.

At this time, the code acquisition position may be "local library" as shown in fig. 6.

In one example, the second repository may include all preset components in the integrated plugin, or may include only some preset components in the integrated plugin, which is not specifically limited herein.

In the embodiment, the component codes corresponding to the preset components can be stored in a local storage mode and a remote storage mode, so that a developer can develop software under the condition of having a network or not, and delay of the software development progress due to the network is avoided.

In one example, as shown in fig. 6, all preset components in the visual interface of the components may be selected as target components through a "full selection" operation, and the code acquisition position of the target component may be determined by selecting the code acquisition position corresponding to the "full selection".

In one example, after the target component is selected and the code acquisition position corresponding to the target component is selected, the confirm button shown in fig. 6 may be clicked to acquire the component code of the target component, or the cancel button shown in fig. 6 may be clicked to cancel the selection operation.

In one example, after the component code of the target component is obtained, the component code may be downloaded and installed into a build tool for software development, and the steps described below in S506 may be performed based on the build tool.

S506, performing software development based on the component codes corresponding to the target components.

In one example, the component's visual interface may also include a select item name, e.g., "please enter item name" as shown in fig. 6, at which point the item name may be "app" as shown in fig. 6. Wherein the item name characterizes the item name of the item to which the target component belongs.

At this time, the software development may be performed on the project corresponding to the project name based on the component code corresponding to the target component.

In one example, the selected project name may be the project name of the existing project, and at this time, a component may be newly added to the existing project through the selected target component, so that the development requirement may be better satisfied. Alternatively, the selected item name may be the item name of the new item, at this time, an item corresponding to the item name may be newly created based on the selected target component, so that creation and initialization of the new item may be completed faster and better.

In one example, when the number of the obtained target components is a plurality of, the splicing order of the target components may be determined first, and then, based on the splicing order, the component codes of the target components are subjected to splicing processing, so as to obtain spliced component codes. Then, software development can be performed based on the spliced component codes.

In one example, the splice order of the target components may be determined by any of the following.

Mode one: and determining the splicing sequence of each target component according to the selection sequence of the corresponding selection operation of each target component.

Mode two: and determining the splicing sequence of each target component according to the preset splicing sequence of the component types of each target component. The splicing order of the target components under the same component type may correspond to the selection order of the target components.

Mode three: and determining the splicing sequence of each target component according to the determined arrangement sequence of the target components by drag operation of each target component in the visual interface of the components.

The splicing order of the target components is not particularly limited herein so as to be able to be realized.

In the above embodiment, the component codes of each target component can be spliced by determining the splicing sequence of each target component under the condition that the number of the target components is multiple, so that the loading of the components is more intelligent and orderly, the development efficiency is improved, and the use experience is also improved.

In one example, after the spliced component code is obtained, the spliced component code may be added to a project configuration file and software development may be performed based on the project configuration file.

The project configuration file characterizes a file for initializing and configuring a project needing to be subjected to software development.

At the moment, the spliced component codes can be automatically loaded into the project configuration file to realize the component codes of the target component, and the component codes are automatically loaded into the project, so that the degree of automation of software development is improved, manual operation is reduced, and the software development efficiency is improved. Meanwhile, manual errors are avoided, and software development is more unified and standardized.

Fig. 7 is an overall flow diagram of a visual software development method based on android provided by the embodiment of the application. As shown in fig. 7, in the embodiment of the present application, component codes of each preset component may be pre-embedded first, so as to obtain an integrated plug-in. At this time, the integration content (i.e., the target component) may be selected through a visual interface corresponding to the integration plug-in, and added to the project engineering (i.e., the project) for software development.

The preset components may be a third party library, a common component (e.g., a tool class, a universal resource library, a network library, a functional module, a secure tool library, etc.), an SDK version, a JDK version, a software development template (e.g., a project structure, a code template, an environment variable), etc. as shown in fig. 7.

Fig. 8 is a schematic structural diagram of a visual software development device based on android, which is provided by an embodiment of the present application, as shown in fig. 8, the visual software development device 800 based on android includes:

an integration unit 801, configured to perform integrated processing on a plurality of preset components to obtain an integrated plug-in; the method comprises the steps that a dependency library for software development is characterized by a preset component; the integrated plug-in characterizes the plug-in installed in the build tool that performs the software development.

A display unit 802, configured to display a visual interface of the component in response to a triggering operation on the integrated plug-in; the visual interface of the component characterizes an interface for selecting a preset component.

A selecting unit 803, configured to determine a target component based on a selection operation of a preset component in a visual interface of the component, and obtain a component code corresponding to the target component; wherein the selecting operation includes selecting a code acquisition location; the code acquisition position corresponds to the code acquisition mode.

The development unit 804 is configured to perform software development based on the component code corresponding to the target component.

Fig. 9 is a schematic structural diagram of another android visualization-based software development device according to an embodiment of the present application, and as shown in fig. 9, the android visualization-based software development device 900 includes:

The integration unit 901 is used for performing integrated processing on a plurality of preset components to obtain an integrated plug-in; the method comprises the steps that a dependency library for software development is characterized by a preset component; the integrated plug-in characterizes the plug-in installed in the build tool that performs the software development.

A display unit 902, configured to display a visual interface of the component in response to a triggering operation on the integrated plug-in; the visual interface of the component characterizes an interface for selecting a preset component.

A selecting unit 903, configured to determine a target component based on a selection operation of a preset component in a visual interface of the component, and obtain a component code corresponding to the target component; wherein the selecting operation includes selecting a code acquisition location; the code acquisition position corresponds to the code acquisition mode.

And the development unit 904 is used for performing software development based on the component code corresponding to the target component.

In one possible design, the selection unit 903 includes:

a determining unit 9031 for acquiring component version information; the method comprises the steps that component version information characterizes a component version number input in a visual interface of a component; the component version number represents the update times of a preset component in the integrated plug-in;

determining a first component matched with the component version information from a plurality of preset components, and displaying the first component in a visual interface of the component;

In response to a selection operation of the first component, a target component is determined.

In one possible design, the selection unit 903 includes:

an obtaining unit 9032, configured to obtain, if the code selected by the selecting operation obtains the location representation network library, a component code of the target component from a first repository set in advance; the first warehouse characterizes a database which needs to be accessed by networking;

if the code acquisition position selected by the selection operation represents a local library, acquiring a component code of a target component from a second warehouse corresponding to the construction tool; wherein the second repository characterizes a database that does not require networking access.

In one possible design, the development unit 904 includes:

the software development unit 9041 is configured to, in a case where the selection operation includes selecting a project name, perform software development on a project corresponding to the project name based on the component code corresponding to the target component.

In one possible design, the development unit 904 includes:

a splicing unit 9042 for determining a splicing order of each target component in the case where the number of target components is plural;

based on the splicing sequence, splicing the component codes of all the target components to obtain spliced component codes;

And performing software development based on the spliced component codes.

In one possible design, the stitching unit 9042 is configured to:

adding the spliced component codes into a project configuration file; the project configuration file characterizes a file for initializing and configuring a project needing to be subjected to software development;

based on the project configuration files, software development is performed.

In one possible design, the display unit 902 is configured to:

and responding to the triggering operation of the integrated plug-in, calling the visualization tool package, and displaying the visualization interface of the component based on the visualization tool package.

In one possible design, the integrated unit 901 is used for:

and carrying out integration processing on the preset assembly after the security verification to obtain an integrated plug-in.

In one possible design, the apparatus further comprises:

an updating unit 905 for: after integrating a plurality of preset components to obtain an integrated plug-in, acquiring component update information; the component update information characterizes the update information of a preset component;

based on the component update information, each preset component in the integrated plug-in is updated.

In one possible design, the plurality of preset components characterizes at least the following dependency library: third party library, tool class, SDK package, JDK package, general resource library, network library, software development template, functional module and safety tool library.

It should be noted that, it should be understood that the division of the modules of the above apparatus is merely a division of a logic function, and may be fully or partially integrated into a physical entity or may be physically separated. And these modules may all be implemented in software in the form of calls by the processing element; or can be realized in hardware; the method can also be realized in a form of calling software by a processing element, and the method can be realized in a form of hardware by a part of modules. The modules may be processing elements that are individually set up, may be implemented as integrated in a chip of the above-described apparatus, or may be stored in a memory of the above-described apparatus in the form of program codes, and the functions of the above-described modules may be called and executed by a processing element of the above-described apparatus. In addition, all or part of the modules can be integrated together or can be independently implemented. The processing element here may be an integrated circuit with signal processing capabilities. In implementation, each step of the above method or each module above may be implemented by an integrated logic circuit of hardware in a processor element or an instruction in a software form.

Fig. 10 is a schematic structural diagram of a computer device according to an embodiment of the present application. As shown in fig. 10, the computer device 100 may include: a transceiver 101, a processor 102, a memory 103.

Processor 102 executes the computer-executable instructions stored in the memory, causing processor 102 to perform the aspects of the embodiments described above. The processor 102 may be a general purpose processor including a central processing unit CPU, a network processor (network processor, NP), etc.; but may also be a digital signal processor DSP, an application specific integrated circuit ASIC, a field programmable gate array FPGA or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component.

The memory 103 is coupled to the processor 102 via a system bus and communicates with each other, and the memory 103 is adapted to store computer program instructions.

The transceiver 101 may be used to obtain a task to be run and configuration information of the task to be run.

The system bus may be a peripheral component interconnect standard (peripheral component interconnect, PCI) bus or an extended industry standard architecture (extended industry standard architecture, EISA) bus, among others. The system bus may be classified into an address bus, a data bus, a control bus, and the like. For ease of illustration, the figures are shown with only one bold line, but not with only one bus or one type of bus. The transceiver is used to enable communication between the database access device and other computers (e.g., clients, read-write libraries, and read-only libraries). The memory may include random access memory (random access memory, RAM) and may also include non-volatile memory (non-volatile memory).

The computer device provided by the embodiment of the present application may be the terminal device of the above embodiment.

The embodiment of the application also provides a chip for running the instruction, which is used for executing the technical scheme of the visual-based software development method of android in the embodiment.

The embodiment of the application also provides a computer readable storage medium, wherein the computer readable storage medium stores computer instructions, and when the computer instructions run on a computer, the computer is enabled to execute the technical scheme of the software development method based on the visualization of the android in the embodiment.

The embodiment of the application also provides a computer program product, which comprises a computer program stored in a computer readable storage medium, wherein at least one processor can read the computer program from the computer readable storage medium, and the technical scheme of the android-based visual software development method in the embodiment can be realized when the at least one processor executes the computer program.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, e.g., the division of modules is merely a logical function division, and there may be additional divisions of actual implementation, e.g., multiple modules may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or modules, which may be in electrical, mechanical, or other forms.

The modules illustrated as separate components may or may not be physically separate, and components shown as modules may or may not be physical units, may be located in one place, or may be distributed over multiple network units. Some or all of the modules may be selected according to actual needs to implement the solution of this embodiment.

In addition, each functional module in the embodiments of the present application may be integrated in one processing unit, or each module may exist alone physically, or two or more modules may be integrated in one unit. The units formed by the modules can be realized in a form of hardware or a form of hardware and software functional units.

The integrated modules, which are implemented in the form of software functional modules, may be stored in a computer readable storage medium. The software functional modules described above are stored in a storage medium and include instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or processor to perform some of the steps of the methods of the various embodiments of the application.

It should be understood that the above processor may be a central processing unit (Central Processing Unit, abbreviated as CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, abbreviated as DSP), application specific integrated circuits (Application Specific Integrated Circuit, abbreviated as ASIC), etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in a processor for execution.

The memory may comprise a high-speed RAM memory, and may further comprise a non-volatile memory NVM, such as at least one magnetic disk memory, and may also be a U-disk, a removable hard disk, a read-only memory, a magnetic disk or optical disk, etc.

The bus may be an industry standard architecture (Industry Standard Architecture, ISA) bus, an external device interconnect (Peripheral Component Interconnect, PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, among others. The buses may be divided into address buses, data buses, control buses, etc. For ease of illustration, the buses in the drawings of the present application are not limited to only one bus or to one type of bus.

The storage medium may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an application specific integrated circuit (Application Specific Integrated Circuits, ASIC for short). Of course, the processor and the storage medium may reside as discrete components in an electronic control unit or master control device.

Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the method embodiments described above may be performed by hardware associated with program instructions. The foregoing program may be stored in a computer readable storage medium. The program, when executed, performs steps including the method embodiments described above; and the aforementioned storage medium includes: various media that can store program code, such as ROM, RAM, magnetic or optical disks.

Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the application.

Claims

1. The visualized software development method based on android is characterized by comprising the following steps of:

2. The method of claim 1, wherein the determining the target component based on the selection of the preset component in the visual interface of the component comprises:

3. The method according to claim 1, wherein the obtaining the component code corresponding to the target component includes:

4. The method of claim 1, wherein the selecting operation comprises selecting a project name; the software development is performed based on the component code corresponding to the target component, and the software development method comprises the following steps:

5. The method of claim 1, wherein the number of target components is a plurality; the software development is performed based on the component code corresponding to the target component, and the software development method comprises the following steps:

determining the splicing sequence of each target assembly;

and performing software development based on the spliced component codes.

6. The method of claim 5, wherein the software development based on the spliced component code comprises:

and carrying out software development based on the project configuration file.

7. The method of claim 1, wherein the exposing a visual interface of a component in response to a triggering operation of the integration plug-in comprises:

8. The method according to claim 1, wherein the integrating the plurality of preset components to obtain an integrated plug-in unit includes:

9. The method of claim 1, wherein after integrating the plurality of preset components to obtain an integrated package, the method further comprises:

10. The method according to any one of claims 1-9, wherein the plurality of preset components characterize at least the following dependency library: third party library, tool class, SDK package, JDK package, general resource library, network library, software development template, functional module and safety tool library.

11. An android-based visualization software development device, comprising:

12. A computer device, comprising: a processor, and a memory communicatively coupled to the processor;

the memory stores computer-executable instructions;

the processor executes computer-executable instructions stored by the memory to implement the android-based visualization software development method of any one of claims 1 to 10.

13. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are for implementing the visualization-based software development method of android according to any one of claims 1 to 10.

14. A computer program product comprising a computer program which, when executed by a processor, implements the android-based software development method of any one of claims 1 to 10.