# US 10,120,660 B2 · Systems and methods for producing launchers for a mobile terminal > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,120,660 B2 - Document ID: US10120660B2 - Status: Granted - Kind: B2 - Application number: 15/506,697 - Filed: 2016-09-02 - Published: 2018-08-09 - Granted: 2018-11-06 - Earliest claimed: 2015-10-20 - Assignees: Huizhou Tcl Mobile Communication Co., Ltd. - Applicants: Huizhou TCL Mobile Communication Co., Ltd - Inventors: Julan Chen; Qiujuan Xie; Fan Yang; Jiaqiong Feng; Qian Zhou - Web page: https://patentgrep.com/patent/US10120660B2 ## CPC - G06F 8/38: for implementing user interfaces - G06F 8/35: model driven - G06F 8/41: Compilation - G06F 8/423: {Preprocessors} - G06F 8/61: Installation - G06F 8/76: Adapting program code to run in a different environment; Porting - G06F 9/445: Program loading or initiating (bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57) - G06F 9/44505: {Configuring for program initiating, e.g. using registry, configuration files} - G06F 9/451: Execution arrangements for user interfaces - G06F 9/453: {Help systems} - G06F 40/143: Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD] - G06F 40/117: Tagging; Marking up (details of markup languages G06F40/143); Designating a block; Setting of attributes (style sheets, e.g. eXtensible Stylesheet Language Transformation [XSLT], G06F40/154) - G06F 40/205: Parsing - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A method of producing launchers for a mobile terminal is disclosed. The method includes: obtaining launcher main code having an architecture of at least two launchers; extracting form the launcher main code a corresponding first parsed XML file and first macro definition .inc file of each of the at least two launchers, and generating a second XML file using the attribute information of all applications in the launcher main code; customizing the first XML file and first .inc file of each launcher and the second XML file to obtain a corresponding second .inc file of the launcher; generating a corresponding third XML file of each of the at least two launchers using the corresponding second .inc file and first XML file of the launcher; and compiling the corresponding third XML file to obtain the at least two launchers. A system for producing launchers for the mobile terminal is disclosed. ## Claims ### Claim 1 A method of producing launchers for a mobile terminal, the method comprising: obtaining launcher main code having an architecture of at least two launchers; extracting from the launcher main code a corresponding first parsed XML file and first macro definition .inc file of each of the at least two launchers, and generating a second XML file using attribute information of all applications in the launcher main code; reading information of the first and second XML files of each of the at least two launchers using a hypertext preprocessor (PHP), and displaying layouts of the at least two launchers as windows by PHP programming; and customizing the at least two launchers to obtain a corresponding second .inc file of each of the at least two launchers, the customized contents being written into the second .inc file by way of an array; generating a corresponding third XML file of each of the at least two launchers using the corresponding second .inc file and first XML of the launcher; saving the third XML file of each of the at least two launchers in ZIP format; decompressing and compiling the third XML file saved in the ZIP format and the launcher main code, the third XML file being used to generate a corresponding client-customized graphics package file for each of the at least two launchers; downloading a file compiled from the launcher main code and the client-customized graphics package file of each of the at least two launchers to the mobile terminal; and installing, by the mobile terminal, the at least two launchers. ### Claim 2 (depends on 1) The method according to claim 1, wherein the layout information of the at least two launchers comprises a number of screens, screen layout, and applications, of each launcher. ### Claim 3 (depends on 1) The method according to claim 1, wherein types customized for the at least two launchers comprise applications, folders, navigation bars, application widgets, or favorites. ### Claim 4 (depends on 3) The method according to claim 3, wherein customization for the applications is performed through one of the folders, navigation bars, and application widgets, or performed on a customization interface. ### Claim 5 (depends on 1) The method according to claim 1, wherein the third XML file is written into the launcher main code concurrently when decompressing and compiling the third XML file saved in the ZIP format. ### Claim 6 (depends on 1) The method according to claim 1, wherein the first XML files and the first .inc files of the at least two launchers and the second XML file are stored in a same data directory of a desired customized version. ### Claim 7 (depends on 1) The method according to claim 1, wherein the respective first .inc files of the at least two launchers are the same file. ### Claim 8 (depends on 1) The method according to claim 1, wherein the windows are browsers. ### Claim 9 (depends on 1) The method according to claim 1, wherein the corresponding first parsed XML files of the at least two launchers are the same, and the corresponding first macro definition .inc files of the at least two launchers are the same. ### Claim 10 (depends on 1) The method according to claim 1, wherein the corresponding first parsed XML files of the at least two launchers are different, and the corresponding first macro definition .inc files of the at least two launchers are the same. ### Claim 11 A method of producing launchers for a mobile terminal, the method comprising: obtaining launcher main code having an architecture of at least two launchers; extracting from the launcher main code a corresponding first parsed XML file and first macro definition .inc file of each of the at least two launchers, and generating a second XML file using attribute information of all applications in the launcher main code; customizing the first XML file and the first .inc file of each of the at least two launchers and the second XML file to obtain a corresponding second .inc file of the launcher; generating a corresponding third XML file of each of the at least two launchers using the corresponding second .inc file and first XML file of the launcher; and compiling the third XML file of each of the at least two launchers to obtain the at least two launchers. ### Claim 12 (depends on 11) The method according to claim 11, wherein customizing the first XML file and the first .inc file of each of the at least two launchers and the second XML file to obtain the corresponding second .inc file of the launcher comprises: reading information of the first and second XML files of each of the at least two launchers using a hypertext preprocessor (PHP), and displaying layouts of the at least two launchers as windows by PHP programming; and customizing the at least two launchers to obtain a corresponding second .inc file of each of the at least two launchers, the customized contents being written into the second .inc file by way of an array. ### Claim 13 (depends on 12) The method according to claim 12, wherein the layout information of the at least two launchers comprises a number of screens, screen layout, and applications, of each launcher. ### Claim 14 (depends on 12) The method according to claim 12, wherein types customized for the at least two launchers comprise applications, folders, navigation bars, application widgets, or favorites. ### Claim 15 (depends on 14) The method according to claim 14, wherein customization for the applications is performed through one of the folders, navigation bars, and application widgets, or performed on a customization interface. ### Claim 16 (depends on 11) The method according to claim 11, wherein compiling the third XML file of each of the at least two launchers to obtain the at least two launchers comprises: saving the third XML file of each of the at least two launchers in ZIP format; decompressing and compiling the third XML file of each launcher that is saved in the ZIP format and the launcher main code, the third XML file being used to generate a corresponding client-customized graphics package file for the launcher; and downloading a file compiled from the launcher main code and the client-customized graphics package file of each launcher to the mobile terminal; and installing, by the mobile terminal, the at least two launchers. ### Claim 17 (depends on 16) The method according to claim 16, wherein the third XML file is written into the launcher main code concurrently when decompressing and compiling the third XML file saved in the ZIP format. ### Claim 18 (depends on 11) The method according to claim 11, wherein the first XML files and the first .inc files of the at least two launchers and the second XML file are stored in a same data directory of the desired customized version. ### Claim 19 (depends on 11) The method according to claim 11, wherein the respective first inc files of the at least two launchers are the same file. ### Claim 20 A system for producing launchers for a mobile terminal, the system comprising one or more processors and a non-transitory program storage medium containing program code executable by the one or more processors, the program code comprising: a production module configured to: extract from launcher main code a corresponding first parsed XML file and first macro definition .inc file of each of the at least two launchers, and generate a second XML file using attribute information of all applications in the launcher main code; customize the first XML file and the first .inc file of each launcher and the second XML file to obtain a corresponding second .inc file of the launcher; and generate a corresponding third XML file of each of the at least two launchers using the corresponding second .inc file and first XML file of the launcher; and a compilation module configured to compile the third XML file of each of the at least two launchers to obtain the at least two launchers.