Automatic generation method and related devices for interface software

Abstract

This application discloses a method and related apparatus for automatically generating interface software. The method includes obtaining the interface type corresponding to the target interface software; retrieving the interface file path and interface resource file path corresponding to the interface type; and generating the target interface software based on the interface file path and interface resource file path. This application pre-configures several interface types and their corresponding interface files and interface resource files in the interface project. When different customers require interface software of different interface types, it can automatically obtain the interface file path and interface resource file path based on the required interface software type, and automatically generate the interface software based on these paths. This not only avoids software generation errors caused by human error, but also allows for the generation of different types of interface software for different customers to meet their diverse needs.

Description

Technical Field

[0001] This application relates to the field of software development and application technology, and in particular to a method and apparatus for automatically generating interface software. Background Technology

[0002] With increasing globalization, terminal devices are sold worldwide. However, customers in different countries and regions have different requirements for the interface of terminal devices, which makes management in the software code very difficult. Currently, existing software compilation methods require manual selection of UI type and UI resource paths, which, while generating interface software, can lead to software errors due to human selection.

[0003] Therefore, existing technologies still need to be improved and enhanced. Summary of the Invention

[0004] The technical problem to be solved by this application is to provide a method and related apparatus for automatically generating interface software, in order to address the shortcomings of the prior art.

[0005] To address the aforementioned technical problems, a first aspect of this application provides a method for automatically generating interface software, applied to an interface project without configured system software. The interface project includes several interface types and corresponding interface files and resource files for each interface type. The method comprises:

[0006] Obtain the interface type corresponding to the target interface software;

[0007] Retrieve the interface file path and interface resource file path corresponding to the interface type;

[0008] The target interface software is generated based on the interface file path and interface resource file path.

[0009] The automatic generation method for the interface software, wherein obtaining the interface type corresponding to the target interface software specifically involves:

[0010] The project compilation file is used to obtain the interface type corresponding to the target interface software. The project compilation file contains pre-set program code for determining the interface type.

[0011] The automatic generation method for the interface software, wherein the compilation of the project file to obtain the interface type corresponding to the target interface software specifically includes:

[0012] Compile the project files to locate the project identifier corresponding to the interface item in the program code;

[0013] When the project identifier corresponding to the interface item is found, the first line number of the project identifier in the program code is obtained;

[0014] Based on the first line number, determine the second line number of the interface type in the program code;

[0015] Read the code file corresponding to the second line number to obtain the interface type corresponding to the target interface software.

[0016] In the automatic generation method of the interface software, the difference between the number of lines of the second code and the number of lines of the first code is 2.

[0017] The automatic generation method for the interface software, wherein reading the code file corresponding to the second line number of code to obtain the interface type corresponding to the target interface software specifically includes:

[0018] Read the code file corresponding to the second line number of code, and search for the interface type in the code file;

[0019] When a suitable interface type is found, it will be used as the interface type corresponding to the target interface software.

[0020] If no interface type is found, the default interface type will be used as the interface type corresponding to the target interface software.

[0021] The automatic generation method for the interface software, wherein generating the target interface software based on the interface file path and the interface resource file path specifically includes:

[0022] The interface file corresponding to the interface type is retrieved based on the interface file path, and the interface resource file corresponding to the interface type is retrieved based on the interface resource file path.

[0023] The interface files and interface resource files are automatically compiled to generate the target interface software.

[0024] The automatic generation method for the interface software, wherein the interface resource file path is used to store interface resource files, wherein the interface resource files include one or more of strings, images, icons, and fonts.

[0025] A second aspect of this application provides an apparatus for automatically generating interface software, the apparatus comprising:

[0026] The acquisition module retrieves the interface type corresponding to the target interface software.

[0027] The retrieval module is used to retrieve the interface file path and interface resource file path corresponding to the interface type.

[0028] The generation module is used to generate the target interface software based on the interface file path and the interface resource file path.

[0029] A third aspect of this application provides a computer-readable storage medium storing one or more programs that can be executed by one or more processors to implement the steps in the automatic generation method of interface software as described above.

[0030] A fourth aspect of this application provides a terminal device, which includes: a processor, a memory, and a communication bus; the memory stores a computer-readable program that can be executed by the processor;

[0031] The communication bus enables communication between the processor and the memory;

[0032] When the processor executes the computer-readable program, it implements the steps in the automatic generation method of interface software as described above.

[0033] Beneficial Effects: Compared with the prior art, this application provides a method and related apparatus for automatically generating interface software. The method includes obtaining the interface type corresponding to the target interface software; retrieving the interface file path and interface resource file path corresponding to the interface type; and generating the target interface software based on the interface file path and interface resource file path. This application pre-configures several interface types and their corresponding interface files and interface resource files in the interface project. When different customers require interface software of different interface types, it can automatically obtain the interface file path and interface resource file path based on the required interface software type, and automatically generate the interface software based on these paths. This not only avoids software generation errors caused by human error, but also generates different types of interface software for different customers to meet their diverse needs. Attached Figure Description

[0034] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0035] Figure 1 A flowchart illustrating the automatic generation method for the interface software provided in this application.

[0036] Figure 2A flowchart illustrating the automatic generation method for the interface software provided in this application.

[0037] Figure 3 A schematic diagram of the structure of the automatic generation device for the interface software provided in this application.

[0038] Figure 4 A schematic diagram of the terminal device provided in this application. Detailed Implementation

[0039] This application provides a method and related apparatus for automatically generating interface software. To make the purpose, technical solution, and effects of this application clearer and more explicit, the following detailed description is provided with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only for explaining this application and are not intended to limit this application.

[0040] Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the term “comprising” as used in this application means the presence of the stated features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. It should be understood that when we say an element is “connected” or “coupled” to another element, it can be directly connected or coupled to the other element, or there may be intermediate elements. Furthermore, “connected” or “coupled” as used herein can include wireless connections or wireless coupling. The term “and / or” as used herein includes all or any units and all combinations of one or more associated listed items.

[0041] It will be understood by those skilled in the art that, unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. It should also be understood that terms such as those defined in general dictionaries should be understood to have the same meaning as in the context of the prior art, and should not be interpreted in an idealized or overly formal sense unless specifically defined as herein.

[0042] It should be understood that the sequence number and size of each step in this embodiment do not imply the order of execution. The execution order of each process is determined by its function and internal logic, and should not constitute any limitation on the implementation process of this application embodiment.

[0043] The inventors discovered through research that with increasing globalization, terminal devices are sold worldwide. However, customers in different countries and regions have varying interface requirements for these devices, making software code management extremely difficult. Currently, existing software compilation involves manually selecting the UI type and UI resource paths, which, while generating a user interface, introduces errors due to human selection. Furthermore, some software, to meet diverse customer needs, creates separate codebases for each requirement. This results in multiple codebases requiring maintenance. When bugs appear in the user interface, the corresponding codebases for each customer need must be modified, increasing maintenance workload and costs.

[0044] To address the aforementioned issues, in this embodiment, the method includes obtaining the interface type corresponding to the target interface software; retrieving the interface file path and interface resource file path corresponding to the interface type; and generating the target interface software based on the interface file path and interface resource file path. This application pre-configures several interface types and their corresponding interface files and resource files in the interface project. When different customers require interface software of different interface types, the application can automatically obtain the interface file path and resource file path based on the required interface software type, and automatically generate the interface software based on these paths. This not only avoids software generation errors caused by human error but also allows for the generation of different types of interface software to meet diverse customer needs. Furthermore, this application uses a single set of interface software code to generate target interface software corresponding to different interface types. When bugs occur in the interface software, only one set of software code needs to be maintained, thereby reducing the workload and cost of code maintenance.

[0045] The application content will be further explained below with reference to the accompanying drawings and the description of the embodiments.

[0046] This embodiment provides a method for automatically generating interface software. The method can be applied to electronic devices with interface display functions. The electronic device is configured with an interface project, which does not have a system program configured. This interface project contains several interface files and interface resource files required by each of these interface files. Each interface file corresponds to a different interface type, and each interface type is suitable for different users. For example, interface types include Skyworth interface and Panasonic interface. Skyworth interface software can be generated based on the interface files and interface resource files corresponding to the Skyworth interface; similarly, Panasonic interface software can be generated based on the interface files and interface resource files corresponding to the Panasonic interface. Furthermore, the electronic device can be a mobile phone, tablet computer, smart TV, or desktop computer, etc.

[0047] This embodiment provides a method for automatically generating interface software, as shown in the figure. The method includes:

[0048] S10. Obtain the interface type corresponding to the target interface software.

[0049] Specifically, the target interface software is the interface software to be generated, and the interface type is the interface type of the target interface software. The interface type can be a type determined according to customer requirements or a default interface type. In other words, before generating the target interface software, the interface type required by the customer can be known and stored. When the interface software needs to be generated, this interface type is automatically obtained through the project compilation file, facilitating the automatic generation of the interface software required by the customer.

[0050] In one implementation of this embodiment, such as Figure 2 As shown, before obtaining the interface type corresponding to the target interface software, the method may further include:

[0051] Receive input operations and extract the interface type carried by the input operations, and store the interface type in the project compilation file.

[0052] Specifically, the input operation can be performed in a preset input window or input interface, or it can be an operation formed based on control commands sent by an external device. The input operation carries the interface type of the user interface software required by the client. After extracting the interface type from the input operation, the interface type is stored in the project compilation file. This way, when the target interface software needs to be generated subsequently, the interface type can be automatically obtained by compiling the working compilation file.

[0053] In one implementation of this embodiment, the specific method for obtaining the interface type corresponding to the target interface software is as follows:

[0054] Compile the project files to obtain the interface type corresponding to the target interface software.

[0055] Specifically, the project compilation file contains pre-defined program code for determining the interface type. This program code can find the interface type carried by the input operation in the interface item and use the found interface type as the interface type of the target interface software. Therefore, when compiling the project compilation file, the interface type of the target interface software can be obtained by executing this program code.

[0056] In one specific implementation of this embodiment, the program code can be:

[0057]

[0058]

[0059] Based on the above code file, in one implementation of this embodiment, the process of obtaining the interface type corresponding to the target interface software by compiling the project file specifically includes:

[0060] Compile the project files to locate the project identifier corresponding to the interface item in the program code;

[0061] When the project identifier corresponding to the interface item is found, the first line number of the project identifier in the program code is obtained;

[0062] Based on the first line number, determine the second line number of the interface type in the program code;

[0063] Read the code file corresponding to the second line number to obtain the interface type corresponding to the target interface software.

[0064] Specifically, the project identifier is a marker for an interface project, indicating that the target interface software belongs to an interface project. When the project identifier is found, it means that the interface software can be generated through the interface project. When the project identifier is not found, it means that the interface software cannot be generated through the interface project. In this case, the operation is terminated directly without any processing.

[0065] The first line number refers to the line number of the code file carrying the project identifier in the program code, and the second line number refers to the line number of the code file used to determine the interface type in the program code. There is a preset relationship between the second line number and the first line number. After obtaining the first line number, the second line number can be determined based on this preset relationship. For example, the first and second line numbers are adjacent, or the code file corresponding to the second line number is located a preset number of lines after the code file corresponding to the first line number. In a typical implementation of this embodiment, the line number difference between the second and first line numbers is 2. That is, the code file corresponding to the second line number is located one line after the code file corresponding to the first line number. For example, the first line number is 5, and the second line number is 7.

[0066] In one implementation of this embodiment, reading the code file corresponding to the second line number to obtain the interface type corresponding to the target interface software specifically includes:

[0067] Read the code file corresponding to the second line number of code, and search for the interface type in the code file;

[0068] When a suitable interface type is found, it will be used as the interface type corresponding to the target interface software.

[0069] If no interface type is found, the default interface type will be used as the interface type corresponding to the target interface software.

[0070] Specifically, the code file corresponding to the second line of code may contain interface types, such as Skyworth, Panasonic, and Huawei. Upon obtaining the code file, the system searches for the interface type. If a type is found, it is used as the interface type for the target interface software; that is, the found interface type is used as the interface type for the client's required interface software. Conversely, if no interface type is found, it indicates that the client requires a custom interface software. In this case, a pre-set default interface type can be used as the interface type for the target interface software. This ensures that the interface software can be generated correctly even if the client does not automatically select an interface type. For example, if the default interface type is Skyworth software, then if no interface type is found, Skyworth software will be used as the interface type for the target interface software to facilitate subsequent generation of the Skyworth interface software.

[0071] S20. Retrieve the interface file path and interface resource file path corresponding to the interface type.

[0072] Specifically, the interface file path is the storage path of the interface file, and the interface resource file path is the storage path of the interface resource file. The interface file can be obtained through the interface file path, and the interface resource file path can be obtained through the interface resource file path. The interface file is used to store the code file used to edit and generate the interface software, and the interface resource file path is used to store the interface resource file. The interface resource file includes one or more of the following: strings, images, icons, and fonts.

[0073] In one implementation of this embodiment, the interface files corresponding to each interface type are stored in the same large folder, for example, in \tv-ap\dvb. Within this large folder, a subfolder is allocated for each interface type, and each subfolder can use the interface type name as its suffix. For example, if the interface type is 'oem', its corresponding subfolder name is ui2_oem. Similarly, the interface resource files corresponding to each interface type are stored in the same large folder, for example, in project\image. Within this large folder, a subfolder is allocated for each interface type, and each subfolder can use the interface type name as its suffix. For example, if the interface type is 'oem', its corresponding subfolder name is bininfo_oem.

[0074] In one implementation of this embodiment, assuming the interface types include OEM UI, Panasonic UI, Skyworth UI, and Toshiba UI, the code used to retrieve the interface file path corresponding to the interface type can be Code 1; the code used to retrieve the interface resource file path corresponding to the interface type can be Code 2.

[0075] Code 1:

[0076]

[0077]

[0078] Code 2:

[0079]

[0080]

[0081] S30. Based on the interface file path and interface resource file path, generate the target interface software.

[0082] Specifically, the target interface software is the interface software corresponding to the interface type. This interface software can be based on an interface type selected by the customer, or it can be based on a preset default interface type. Furthermore, after generating the target interface software, the interface formed based on the target interface software can be displayed on the display screen. And unless the customer modifies the interface type, the interface can be formed using this target interface software each time the interface is displayed.

[0083] In one implementation of this embodiment, generating the target interface software based on the interface file path and the interface resource file path specifically includes:

[0084] The interface file corresponding to the interface type is retrieved based on the interface file path, and the interface resource file corresponding to the interface type is retrieved based on the interface resource file path.

[0085] The interface files and interface resource files are automatically compiled to generate the target interface software.

[0086] Specifically, the interface file stores the code files used to generate the target interface software, and the interface resource file stores the resource data for generating the target interface software. When generating the target interface software based on the interface file, the resource data in the interface resource file is called. For example, images, fonts, etc., in the interface resource file are called. For example, when the interface type is OEM, the software compilation will generate OEM interface burning software; when the interface type is SKYWORTH, the software compilation will generate Skyworth interface burning software. In this way, different interface software can be generated for different interface types, and only one set of interface software is installed in the terminal device, so only one set of interface software needs to be maintained, thereby reducing code maintenance costs.

[0087] In summary, this embodiment provides an automatic method for generating interface software. The method includes obtaining the interface type corresponding to the target interface software; retrieving the interface file path and interface resource file path corresponding to the interface type; and generating the target interface software based on the interface file path and interface resource file path. This application pre-configures several interface types and their corresponding interface files and resource files in the interface project. When different customers require interface software of different interface types, it can automatically obtain the interface file path and interface resource file path based on the required interface software type, and automatically generate the interface software based on these paths. This not only avoids software generation errors caused by human error but also allows for the generation of different types of interface software to meet the needs of different customers. Furthermore, this application uses a single set of interface software code to generate target interface software corresponding to different interface types. When bugs occur in the interface software, only one set of software code needs to be maintained, thereby reducing the workload and cost of code maintenance.

[0088] Based on the above-described method for automatically generating interface software, this embodiment provides an apparatus for automatically generating interface software, such as... Figure 3 As shown, the device includes:

[0089] Get module 100 to obtain the interface type corresponding to the target interface software;

[0090] The retrieval module 200 is used to retrieve the interface file path and interface resource file path corresponding to the interface type.

[0091] The generation module 300 is used to generate the target interface software based on the interface file path and the interface resource file path.

[0092] Based on the above-described method for automatically generating interface software, this embodiment provides a computer-readable storage medium storing one or more programs that can be executed by one or more processors to implement the steps in the method for automatically generating interface software as described in the above embodiment.

[0093] Based on the above-mentioned automatic generation method for interface software, this application also provides a terminal device, such as... Figure 4 As shown, it includes at least one processor 20; a display screen 21; and a memory 22, and may also include a communications interface 23 and a bus 24. The processor 20, display screen 21, memory 22, and communications interface 23 can communicate with each other via the bus 24. The display screen 21 is configured to display a preset user guide interface in the initial setup mode. The communications interface 23 can transmit information. The processor 20 can invoke logical instructions in the memory 22 to execute the methods described in the above embodiments.

[0094] Furthermore, the logical instructions in the aforementioned memory 22 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium.

[0095] The memory 22, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, such as program instructions or modules corresponding to the methods in the embodiments of this disclosure. The processor 20 executes functional applications and data processing by running the software programs, instructions, or modules stored in the memory 22, thereby implementing the methods in the above embodiments.

[0096] The memory 22 may include a program storage area and a data storage area. The program storage area may store the operating system and application programs required for at least one function; the data storage area may store data created based on the use of the terminal device. Furthermore, the memory 22 may include high-speed random access memory (RAM) and non-volatile memory. Examples include various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, as well as transient storage media.

[0097] Furthermore, the specific process of loading and executing multiple instruction processors in the aforementioned storage medium and terminal device has been described in detail in the above method, and will not be repeated here.

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

Claims

1. A method for automatically generating user interface software, characterized in that, The method is applied to interface projects that do not have system software configured, wherein the interface project has several interface types and corresponding interface files and interface resource files for each interface type; the method includes: Obtain the interface type corresponding to the target interface software; Retrieve the interface file path and interface resource file path corresponding to the interface type; The target interface software is generated based on the interface file path and interface resource file path. Before obtaining the interface type corresponding to the target interface software, the method further includes: receiving an input operation and extracting the interface type carried by the input operation, and storing the interface type in a project compilation file; the input operation is an operation performed in a preset input window or input interface, or an operation formed based on control instructions sent by an external device, wherein the input operation carries the interface type of the interface software required by the customer; after extracting the interface type from the input operation, the interface type is stored in the project compilation file; The interface file path is the storage path for the interface file, and the interface resource file path is the storage path for the interface resource file. The interface file is obtained through the interface file path, and the interface resource file path is obtained through the interface resource file path. The interface file is used to store the code file used to compile and generate the interface software, and the interface resource file path is used to store the interface resource file. Each interface type's corresponding interface file is stored in the same large folder. Within this large folder, a subfolder is allocated for each interface type, and each subfolder uses the name of the respective interface type as its suffix.

2. The automatic generation method for interface software according to claim 1, characterized in that, The specific interface type corresponding to the target interface software is as follows: The project compilation file is used to obtain the interface type corresponding to the target interface software. The project compilation file contains pre-set program code for determining the interface type.

3. The method for automatically generating interface software according to claim 2, characterized in that, The compilation project files used to obtain the interface type corresponding to the target interface software specifically include: Compile the project files to locate the project identifier corresponding to the interface item in the program code; When the project identifier corresponding to the interface item is found, the first line number of the project identifier in the program code is obtained; Based on the first line number, determine the second line number of the interface type in the program code; Read the code file corresponding to the second line number to obtain the interface type corresponding to the target interface software.

4. The method for automatically generating interface software according to claim 3, characterized in that, The difference between the second line number and the first line number is 2.

5. The method for automatically generating interface software according to claim 3, characterized in that, The step of reading the code file corresponding to the second line number of code to obtain the interface type of the target interface software specifically includes: Read the code file corresponding to the second line number of code, and search for the interface type in the code file; When a suitable interface type is found, it will be used as the interface type corresponding to the target interface software. If no interface type is found, the default interface type will be used as the interface type corresponding to the target interface software.

6. The method for automatically generating interface software according to claim 1, characterized in that, The process of generating the target interface software based on the interface file path and the interface resource file path specifically includes: The interface file corresponding to the interface type is retrieved based on the interface file path, and the interface resource file corresponding to the interface type is retrieved based on the interface resource file path. The interface files and interface resource files are automatically compiled to generate the target interface software.

7. The method for automatically generating interface software according to claim 6, characterized in that, The interface resource file path is used to store interface resource files, wherein the interface resource files include one or more of the following: strings, images, icons, and fonts.

8. An automatic interface software generation device, characterized in that, An interface project without configured system software, wherein the interface project is configured with several interface types and corresponding interface files and interface resource files for each interface type, the device comprising: The acquisition module retrieves the interface type corresponding to the target interface software. The retrieval module is used to retrieve the interface file path and interface resource file path corresponding to the interface type. The generation module is used to generate the target interface software based on the interface file path and the interface resource file path; Before the acquisition module, the device further includes: receiving an input operation and extracting the interface type carried by the input operation, and storing the interface type in a project compilation file; the input operation is an operation performed in a preset input window or input interface, or an operation formed based on control instructions sent by an external device, wherein the input operation carries the interface type of the interface software required by the customer; after extracting the interface type in the input operation, the interface type is stored in the project compilation file; The interface file path is the storage path for the interface file, and the interface resource file path is the storage path for the interface resource file. The interface file is obtained through the interface file path, and the interface resource file path is obtained through the interface resource file path. The interface file is used to store the code file used to compile and generate the interface software, and the interface resource file path is used to store the interface resource file. Each interface type's corresponding interface file is stored in the same large folder. Within this large folder, a subfolder is allocated for each interface type, and each subfolder uses the name of the respective interface type as its suffix.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores one or more programs, which can be executed by one or more processors to implement the steps in the automatic generation method of interface software as described in any one of claims 1-7.

10. A terminal device, characterized in that, include: Processor, memory, and communication bus; the memory stores a computer-readable program that can be executed by the processor; The communication bus enables communication between the processor and the memory; When the processor executes the computer-readable program, it implements the steps in the automatic generation method of interface software as described in any one of claims 1-7.

Images