Method and device for displaying icons in application program of vehicle and electronic equipment

Abstract

The embodiment of the invention provides a method and device for displaying icons in an application program of a vehicle and electronic equipment, and the method comprises the steps that item information of icon items needed by the application program of the vehicle is obtained, the icon items come from icon platforms allowing the application program to access, and the item information is used for representing attributes and content of the icon items; attributes and contents in the item information are adjusted, adjusted item information is obtained, and the adjusted item information is used for representing the adjusted attributes and the adjusted contents; on the basis of the adjusted item information, configuration information of a to-be-displayed icon in the application program is generated, and the configuration information is used for representing at least one parameter describing the to-be-displayed icon in a preset information format; and configuring the to-be-displayed icon on the interface of the application program according to the configuration information. The technical problem of low icon maintenance efficiency is solved.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and more specifically, to a method, apparatus, and electronic device for displaying icons in a vehicle application. Background Technology

[0002] Currently, with the development of human-computer interaction in vehicles, the icons of applications displayed on vehicle display devices, which serve as a bridge for human-computer interaction services, need to be maintained periodically to ensure display quality.

[0003] In existing icon maintenance methods, icons are often stored in image format within application development tools. However, these icons are typically scattered across different development projects within the application. When adding, deleting, or modifying icons, it is necessary to manually synchronize the maintained code and resources across different development projects. This results in excessively long icon maintenance times, leading to low icon maintenance efficiency.

[0004] There is currently no good solution to the technical problem of low maintenance efficiency of the aforementioned icons. Summary of the Invention

[0005] This application provides a method, apparatus, and electronic device for displaying icons in a vehicle application, to at least solve the technical problem of low icon maintenance efficiency.

[0006] According to one aspect of the embodiments of this application, a method for displaying icons in a vehicle application is provided, comprising: obtaining project information of icon items required by the vehicle application, wherein the icon items come from an icon platform that the application is allowed to access, and the project information is used to represent the attributes and content of the icon items; adjusting the attributes and content in the project information to obtain adjusted project information, wherein the adjusted project information is used to represent the adjusted attributes and adjusted content; generating configuration information for an icon to be displayed in the application based on the adjusted project information, wherein the configuration information is used to represent at least one parameter describing the icon to be displayed through a preset information format; and configuring the icon to be displayed on the interface of the application according to the configuration information.

[0007] Furthermore, based on the adjusted project information, configuration information for the icons to be displayed in the application is generated, including: extracting address information from the adjusted project information, wherein the address information is used to indicate the address where the font file in the content is stored; downloading the font file by accessing the address corresponding to the address information; and generating configuration information based on the downloaded font file.

[0008] Furthermore, based on the downloaded font file, configuration information is generated, including: using the application's adaptation platform to determine the font file's configuration strategy, wherein the configuration strategy is used to represent the rules for configuring the font file; configuring the font file on the adaptation platform according to the configuration strategy; and generating configuration information based on the configured font file.

[0009] Furthermore, based on the configured font file, configuration information is generated, including: resolving the names of the configured font file to obtain multiple name information, wherein the name information is used to represent the names of icons in the icon project, and the icon project includes multiple icons; generating encoding information that maps to the multiple name information respectively to obtain multiple encoding information; adjusting the configured font file to obtain an adjusted font file, wherein the encoding information is used to represent the result of encoding the icons; and generating configuration information by combining the multiple encoding information, the adjusted font file, and the class information of the font file, wherein the class information is used to represent the font category to which the font file belongs.

[0010] Furthermore, the adaptation platform includes: a first adaptation platform and a second adaptation platform, wherein the first number of platforms extended to the first adaptation platform is less than the second number of platforms extended to the second adaptation platform, and the configuration strategy includes: a first configuration strategy and a second configuration strategy, wherein the first configuration strategy is used to represent the rules for configuring font files on the first adaptation platform, and the second configuration strategy is used to represent the rules for configuring font files on the second adaptation platform, wherein determining the configuration strategy for font files using the application's adaptation platform includes: determining the configuration strategy as the first configuration strategy in response to the adaptation platform being the first adaptation platform; and determining the configuration strategy as the second configuration strategy in response to the adaptation platform being the second adaptation platform.

[0011] Furthermore, on the adaptation platform, the font file is configured according to the configuration strategy, including: on the first adaptation platform, configuring the font file according to the first configuration strategy; and on the second adaptation platform, configuring the font file according to the second configuration strategy.

[0012] Furthermore, the attributes and content in the project information are adjusted to obtain the adjusted project information, including: performing structural parsing on the attributes and content to obtain the parsed attributes and parsed content; and adjusting the structure of the parsed attributes and parsed content respectively to obtain the adjusted project information.

[0013] Furthermore, the method also includes: extracting first version information from the adjusted project information and obtaining second version information from the icon platform, wherein the first version information is used to represent the version of the icon project at a first moment, and the second version information is used to represent the version of the icon project at a second moment, with the first moment being earlier than the second moment; determining the information relationship between the first version information and the second version information; updating the adjusted project information based on the information relationship; or, maintaining the adjusted project information based on the information relationship.

[0014] Furthermore, based on information relationships, the adjusted project information is updated, including: updating the adjusted project information in response to a difference between the first version information and the second version information; and maintaining the adjusted project information based on information relationships, including: maintaining the adjusted project information in response to a difference between the first version information and the second version information.

[0015] According to another aspect of the embodiments of this application, a device for displaying icons in a vehicle application is also provided, comprising: an acquisition unit, configured to acquire item information of icon items required by the vehicle application, wherein the icon items come from an icon platform accessible to the application, and the item information is used to represent the attributes and content of the icon items; a conversion unit, configured to adjust the attributes and content in the item information to obtain adjusted item information, wherein the adjusted item information is used to represent the adjusted attributes and adjusted content; a generation unit, configured to generate configuration information of an icon to be displayed in the application based on the adjusted item information, wherein the configuration information is used to represent at least one parameter describing the icon to be displayed in a preset information format; and a configuration unit, configured to configure the icon to be displayed on the interface of the application according to the configuration information.

[0016] According to another aspect of the embodiments of this application, an electronic device is also provided, including: a memory storing an executable program; and a processor for running the program, wherein the program executes the methods in various embodiments of this application when it runs.

[0017] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored executable program, wherein, when the executable program is running, it controls the device where the computer-readable storage medium is located to perform the methods of various embodiments of this application.

[0018] According to another aspect of the embodiments of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements the methods of various embodiments of this application.

[0019] According to another aspect of the embodiments of this application, a computer program product is also provided, including a non-volatile computer-readable storage medium storing a computer program that, when executed by a processor, implements the methods in various embodiments of this application.

[0020] According to another aspect of the embodiments of this application, a computer program is also provided, which, when executed by a processor, implements the methods of the various embodiments of this application.

[0021] In this embodiment, project information for the icon items required by the vehicle's application is obtained; the attributes and content in the project information are adjusted to obtain adjusted project information; based on the adjusted project information, configuration information for the icon to be displayed in the application is generated; and the icon to be displayed is configured on the application's interface according to the configuration information. In other words, in this embodiment, after obtaining the project information for the icon items required by the vehicle's application, the attributes and content in the obtained project information are adjusted to obtain adjusted project information, and configuration information describing at least one parameter of the icon to be displayed can be generated based on the adjusted project information. Finally, according to the generated configuration information, the icon to be displayed can be configured on the interface, thereby avoiding icon scaling distortion and solving the technical problem of low icon maintenance efficiency, thus achieving the technical effect of improving icon maintenance efficiency. Attached Figure Description

[0022] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0023] Figure 1 This is a flowchart of a method for displaying icons in a vehicle application according to an embodiment of this application;

[0024] Figure 2 This is a schematic diagram of a font icon integration management system according to an embodiment of this application;

[0025] Figure 3 This is a schematic diagram of an icon display device in a vehicle application according to an embodiment of this application. Detailed Implementation

[0026] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0027] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0028] According to an embodiment of this application, a method embodiment for displaying icons in a vehicle application is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0029] In this embodiment of the application, a method for displaying icons in a vehicle application is provided. Figure 1 This is a flowchart illustrating a method for displaying icons in a vehicle application according to an embodiment of this application, such as... Figure 1 As shown, the process may include the following steps.

[0030] Step S101: Obtain the project information for the icon items required by the vehicle's application.

[0031] In the technical solution provided in step S101 of this application, the icon items can come from an icon platform that allows the application to access them. Optionally, the icon platform can be a font icon library service platform, for example, a font icon library service platform can also be an Iconfont platform. The icon items can be font icon items in the font icon library service platform, for example, font icon items can be Iconfont items.

[0032] In this embodiment, the aforementioned project information is used to represent the attributes and content of the aforementioned icon project. Optionally, the aforementioned project information may include: attribute information and content information. The attribute information may be basic information about the aforementioned icon project, which may include, but is not limited to: project name, creation time, latest version number, and update time. The content information may include: icon details and font association information of the aforementioned icon project. The icon details may include, but are not limited to: icon name, Unicode encoding, icon label, and icon status. The font association information may include, but is not limited to: online download address of the font file and font family name.

[0033] In this embodiment, the project information of the icon items required by the vehicle's application is obtained. Optionally, the complete project information of the icon item can be obtained from the icon platform through the icon item's identification information. The identification information can be the icon item's identifier on the icon platform; for example, it can be a project identifier (ID) or a project online link.

[0034] For example, by entering the project ID or online link of the desired icon project in the icon platform, the icon platform can automatically search for the corresponding icon project information based on the entered project ID or online link, and provide the searched project information to the application.

[0035] Step S102: Adjust the attributes and content in the project information to obtain the adjusted project information.

[0036] In the technical solution provided by step S102 of this application, the adjusted project information can be used to represent the adjusted attributes and the adjusted content. Specifically, the adjustment can represent the process of parsing the project information and generating a file in a preset format. For example, the preset format can be a readable JavaScript Object Notation (JSON) format, and the preset format file can be an iconfont.json file.

[0037] In this embodiment, after obtaining the project information, the attributes and content in the project information are adjusted to obtain the adjusted project information. Optionally, by using a preset library file, the attributes and content in the project information are parsed into attributes and content that meet a preset data structure, and the attributes and content that meet the preset data structure are stored in a file with a preset format, thus obtaining the adjusted project information. This achieves the purpose of converting the format of the original data in the project information into a unified preset format.

[0038] For example, when the attributes and content in the project information are in Extensible Markup Language (XML) format, an XML-to-JavaScript converter (xml2js) can be used to convert the XML attributes and content into JSON format. Writing the JSON attributes and content into the iconfont.json file yields the adjusted project information.

[0039] Step S103: Based on the adjusted project information, generate configuration information for the icons to be displayed in the application.

[0040] In the technical solution provided by step S103 of this application, the configuration information can be used to represent at least one parameter describing the icon to be displayed through a preset information format. The preset information format can be Iconfont.js format.

[0041] In this embodiment, the parameters of the icon to be displayed may include attributes and styles. The attributes may include: icon name, icon size, and icon color, etc.

[0042] In this embodiment, after obtaining the adjusted project information, configuration information for the icon to be displayed in the application can be generated based on the adjusted project information. Optionally, by defining the parameters in the adjusted project information using a preset component template, the defined parameters can be obtained. Storing the defined parameters as a file in Iconfont.js format yields the configuration information, thereby achieving the goal of creating a dynamic and reusable component from the adjusted project information.

[0043] For example, first, mapping the icon names and Unicode encodings in the `iconfont.json` file yields an icon map. Then, using React Native component templates, the parameters in the `iconfont.json` file are defined, resulting in the defined parameters. For instance, the icon name attribute is defined to look up the Unicode encoding in the `iconMap`; the icon size and icon color attributes are defined to set the icon style. Storing these defined parameters as a `Conconfont.js` file provides the configuration information described above.

[0044] Step S104: Configure the icon to be displayed on the application interface according to the configuration information.

[0045] In the technical solution provided by step S104 of this application, the above configuration can be an operation to call the icon to be displayed.

[0046] In this embodiment, after obtaining the configuration information, the icon to be displayed can be configured on the application's interface according to the configuration information. Optionally, the icon to be displayed can be directly invoked using the icon name. When the icon to be displayed is invoked, the Unicode encoding corresponding to the icon name can be found in the iconMap through the icon name attribute in the configuration information. Using the Unicode encoding, the icon to be displayed can be determined. At the same time, the icon style of the determined icon to be displayed is set through the icon size and icon color in the configuration information. Then, the icon to be displayed is configured on the application's interface according to the above icon style.

[0047] In steps S101 to S104 above, project information for the icon items required by the vehicle's application is obtained; the attributes and content in the project information are adjusted to obtain adjusted project information; based on the adjusted project information, configuration information for the icon to be displayed in the application is generated; and the icon to be displayed is configured on the application interface according to the configuration information. In other words, in this embodiment, after obtaining the project information for the icon items required by the vehicle's application, the adjusted project information can be obtained by adjusting the attributes and content in the obtained project information, and configuration information describing at least one parameter of the icon to be displayed can be generated based on the adjusted project information. Finally, according to the generated at least one parameter of the icon to be displayed, the icon to be displayed can be configured on the interface, thereby avoiding icon scaling distortion, solving the technical problem of low icon maintenance efficiency, and thus achieving the technical effect of improving icon maintenance efficiency.

[0048] The method for determining the vehicle's pose in this application will be further described below.

[0049] As an optional embodiment, step S103, based on the adjusted project information, generates configuration information for the icon to be displayed in the application, including: extracting address information from the adjusted project information, wherein the address information is used to indicate the address where the font file in the content is stored; downloading the font file by accessing the address corresponding to the address information; and generating configuration information based on the downloaded font file.

[0050] In this embodiment, the address information can be used to represent the address where the font file in the above content is stored. Optionally, the address information can be used to represent the online download address of the font file; for example, the online download address of the font file can be a server address located on the Internet. The font file can be a file stored at the above address; for example, the font file can be an iconfont.ttf file.

[0051] In this embodiment, after obtaining the adjusted project information, the address information can be extracted from it. Optionally, after obtaining the adjusted project information, the adjusted project information can be traversed, and the information fragments containing the online download address of the aforementioned font file can be extracted to obtain the aforementioned address information.

[0052] In this embodiment, after extracting the address information, the font file can be downloaded by accessing the address corresponding to the address information. Optionally, accessing the address corresponding to the address information on the Internet can retrieve various information files stored at that address. Initiating download requests for these various information files can download the corresponding iconfont.ttf file, thus obtaining the aforementioned font file.

[0053] In this embodiment, after downloading the font file, configuration information can be generated based on the downloaded font file. Optionally, by using the aforementioned React Native component template, the parameters in the downloaded font file can be defined to obtain the defined parameters of the font file. Storing the defined parameters of the font file as an Iconfont.js file yields the aforementioned configuration information.

[0054] In this embodiment, by extracting the online download address of the font file from the adjusted project information, the font file can be downloaded by accessing the online download address, and configuration information can be generated based on the downloaded font file. This achieves the purpose of generating configuration information for the corresponding font file in the adjusted project information.

[0055] As an optional implementation method, generating configuration information based on the downloaded font file includes: determining a configuration strategy for the font file using the application's adaptation platform, wherein the configuration strategy is used to represent the rules for configuring the font file; configuring the font file on the adaptation platform according to the configuration strategy; and generating configuration information based on the configured font file.

[0056] In this embodiment, the configuration strategy described above can be used to represent rules for configuring the font file. For example, the configuration strategy can be used to represent the loading rules of the font file in the adapted platform. The adapted platform can be an application platform used to run the application, wherein the application platform can include different types of operating system platforms. For example, the different types of operating systems can include: Apple's operating system (iOS) and Android's operating system (Android).

[0057] In this embodiment, after the font file is downloaded, the configuration strategy for the font file is determined using the application's platform compatibility. Optionally, after downloading the font file, a configuration strategy matching the application platform is determined based on the application platform on which the application runs. For example, if the application platform is iOS, the configuration strategy can be a strategy matching the iOS platform; if the application platform is Android, the configuration strategy can be a strategy matching the Android platform.

[0058] In this embodiment, after determining the configuration strategy, the font file can be configured on the adapted platform according to the configuration strategy. Optionally, the font file can be configured on the adapted platform according to the determined configuration strategy. For example, if the configuration strategy is a configuration strategy matching the iOS platform, the font file can be configured on the iOS platform according to the configuration strategy; if the configuration strategy is a configuration strategy matching the Android platform, the font file can be configured on the Android platform according to the configuration strategy.

[0059] In this embodiment, after configuring the font file, configuration information can be generated based on the configured font file. Optionally, by using the aforementioned React Native component template, the parameters in the configured font file can be defined to obtain the defined parameters of the font file. Storing the defined parameters of the font file as an Iconfont.js file yields the configuration information.

[0060] In this embodiment, different configuration strategies for the font file can be determined according to different adaptation platforms. Based on different configuration strategies, the font file is configured in the corresponding adaptation platform to obtain the configured font file. Based on the configured font file, the above configuration information can be generated. This achieves the purpose of configuring the font file differently on different adaptation platforms and realizes the technical effect of improving the adaptability of the font file.

[0061] As an optional implementation method, based on the configured font file, configuration information is generated, including: resolving the name of the configured font file to obtain multiple name information, wherein the name information is used to represent the name of the icon in the icon project, and the icon project includes multiple icons; generating encoding information that maps to the multiple name information respectively to obtain multiple encoding information; adjusting the configured font file to obtain an adjusted font file, wherein the encoding information is used to represent the result of encoding the icon; and generating configuration information by combining the multiple encoding information, the adjusted font file, and the class information of the font file, wherein the class information is used to represent the font category to which the font file belongs.

[0062] In this embodiment, the aforementioned name information can be used to represent the names of icons in an icon project, and an icon project can include multiple icons. Optionally, the aforementioned multiple name information can be presented in the form of an array, for example, the aforementioned multiple name information can be an array of icons.

[0063] In this embodiment, the encoding information can be used to represent the result of encoding the icon. Optionally, the encoding information can be used to represent the mapping relationship between the icon name and the Unicode encoding. Multiple encoding information can be presented in the form of a mapping list; for example, the multiple encoding information can be an iconMap.

[0064] In this embodiment, the class information can be used to indicate the font category to which the font file belongs. For example, the class information can be the Font Family.

[0065] In this embodiment, after configuring the font file, name parsing is performed on the configured font file to obtain various name information. Optionally, after configuring the iconfont.ttf file, the iconfont.json file is parsed to obtain the parsed iconfont.json file. By traversing the contents of the parsed iconfont.json file, the icons array in the parsed iconfont.json file can be extracted, and the icons array can be determined as the aforementioned various name information.

[0066] In this embodiment, after obtaining multiple name information, encoding information mapping to each of the multiple name information is generated, resulting in multiple encoding information. The configured font file is then adjusted to obtain an adjusted font file. Optionally, after obtaining the `icons` array, based on the multiple icon names contained in the `icons` array and their respective Unicode encodings, the multiple icon names are mapped one-to-one to their respective Unicode encodings to obtain an `iconMap`. Simultaneously, using the aforementioned React Native component template, the parameters in the configured font file are defined, resulting in the font file with defined parameters. This font file with defined parameters is then identified as the adjusted font file.

[0067] In this embodiment, after obtaining various encoding information and the adjusted font file, configuration information is generated by combining the various encoding information, the adjusted font file, and the class information of the font file. Optionally, after obtaining the above-mentioned iconMap and the above-mentioned font file with defined parameters, the above-mentioned iconMap, the above-mentioned font file with defined parameters, and the above-mentioned FontFamily are stored as a file in Iconfont.js format to obtain the above-mentioned configuration information.

[0068] In this embodiment, by parsing the configured font file, various name information can be obtained. Furthermore, by encoding these various name information, various encoding information can be obtained. Simultaneously, by adjusting the configured font file, an adjusted font file can be obtained. Finally, based on the various encoding information, the adjusted font file, and the class information of the font file, the aforementioned configuration information can be generated, thereby achieving the goal of generating configuration information containing the mapping relationship between icon names and Unicode encodings.

[0069] As an optional embodiment, the adaptation platform includes: a first adaptation platform and a second adaptation platform. The first number of platforms extended to the first adaptation platform is less than the second number of platforms extended to the second adaptation platform. The configuration strategy includes: a first configuration strategy and a second configuration strategy. The first configuration strategy represents the rules for configuring font files on the first adaptation platform, and the second configuration strategy represents the rules for configuring font files on the second adaptation platform. Determining the font file configuration strategy using the application's adaptation platform includes: determining the configuration strategy as the first configuration strategy in response to the adaptation platform being the first adaptation platform; and determining the configuration strategy as the second configuration strategy in response to the adaptation platform being the second adaptation platform.

[0070] In this embodiment, the first compatible platform can be the iOS platform; the second compatible platform can be the Android platform. Optionally, the first quantity can be the number of platforms extended based on the first compatible platform, for example, the first quantity can be the number of platforms extended based on the iOS platform; the second quantity can be the number of platforms extended based on the second compatible platform, for example, the second quantity can be the number of platforms extended based on the Android platform. The first quantity is less than the second quantity.

[0071] In this embodiment, the first configuration strategy can be used to represent the rules for configuring font files on the first adapted platform. Optionally, the first configuration strategy can be a configuration strategy that matches the iOS platform; for example, the first configuration strategy can be the loading rules for the font files on the iOS platform.

[0072] For example, parsing the contents of the Info.plist file in an iOS project on the iOS platform, specifically within the Info.plist file... <key> UIAppFonts< / key> Add the iconfont.ttf file mentioned above to the corresponding array. If the iconfont.ttf file already exists, skip this step.

[0073] In this embodiment, the second configuration strategy described above can be used to represent the rules for configuring font files on the second adapted platform. Optionally, the second configuration strategy can be a configuration strategy that matches the Android platform; for example, the second configuration strategy can be the loading rules for the font files on the Android platform.

[0074] For example, on the Android platform, no additional configuration is required. The Android platform will automatically scan the iconfont.ttf file located in the . / android / app / src / main / assets / fonts directory to load the font file. At the same time, a log file will be generated to indicate that the font file configuration is complete.

[0075] In this embodiment, in response to the adapted platform being a first adapted platform, the configuration strategy is determined to be a first configuration strategy. Optionally, when the adapted platform is an iOS platform, the above configuration strategy is determined to be a configuration strategy that matches the iOS platform.

[0076] In this embodiment, in response to the adapted platform being a second adapted platform, the configuration strategy is determined to be the second configuration strategy. Optionally, when the adapted platform is an Android platform, the above configuration strategy is determined to be a configuration strategy that matches the Android platform.

[0077] In this embodiment, the above configuration strategy is determined to be a configuration strategy that matches the adaptation platform based on the type of the operating system of the adaptation platform, thereby achieving the purpose of determining different configuration strategies for different types of operating system platforms.

[0078] As an optional implementation method, on the adaptation platform, the font file is configured according to the configuration strategy, including: on the first adaptation platform, configuring the font file according to the first configuration strategy; on the second adaptation platform, configuring the font file according to the second configuration strategy.

[0079] In this embodiment, on the first adapted platform, the font file is configured according to the first configuration strategy. Optionally, when the adapted platform is the iOS platform, the font file can be configured on the iOS platform according to a configuration strategy that matches the iOS platform.

[0080] In this embodiment, on the second adaptation platform, the font file is configured according to the second configuration strategy. Optionally, when the adaptation platform is the Android platform, the font file can be configured on the Android platform according to a configuration strategy that matches the Android platform.

[0081] In this embodiment, font files can be configured according to different configuration strategies for different adaptation platforms, thereby achieving the goal of configuring font files differently on different adaptation platforms and realizing the technical effect of improving the adaptability of font files.

[0082] As an optional embodiment, step S102 involves adjusting the attributes and content in the project information to obtain the adjusted project information, including: performing structural parsing on the attributes and content to obtain the parsed attributes and parsed content; and performing structural adjustments on the parsed attributes and parsed content to obtain the adjusted project information.

[0083] In this embodiment, after obtaining the aforementioned project information, the attributes and content within the project information are parsed to obtain the parsed attributes and content. Optionally, a preset library file can be used to parse the original data of the attributes and content in the project information to obtain a data structure in a preset format. For example, when the original data of the attributes and content in the project information is in XML format, xml2js can be used to convert the original XML data into a JSON data structure, and the resulting JSON data structure is used as the parsed attributes and content.

[0084] In this embodiment, after obtaining the parsed attributes and parsed content, the structure of the parsed attributes and parsed content is adjusted to obtain the adjusted project information. Optionally, the parsed attributes and parsed content are used to generate a list of attributes and content for the aforementioned project information. Each element in the list of attributes and content may include the parsed attribute and the parsed content corresponding to the parsed attribute. Converting the list of attributes and content into a JSON string and writing the JSON string into the iconfont.json file yields the adjusted project information.

[0085] In this embodiment, by performing structural parsing on the attributes and content in the project information, the parsed attributes and content can be obtained. Furthermore, by adjusting the parsed attributes and content, the adjusted project information can be obtained. This achieves the goal of adjusting the original data in the project information into data that can be called.

[0086] As an optional embodiment, the method further includes: extracting first version information from the adjusted project information and obtaining second version information from the icon platform, wherein the first version information is used to represent the version of the icon project at a first moment, and the second version information is used to represent the version of the icon project at a second moment, and the first moment is earlier than the second moment; determining the information relationship between the first version information and the second version information; updating the adjusted project information based on the information relationship; or, maintaining the adjusted project information based on the information relationship.

[0087] In this embodiment, the first version information can be used to represent the version of the icon item at a first moment. Optionally, the first version information can be used to represent the first version number stored locally, such as the first version number (version) in the iconfont.json file. The second version information can be used to represent the version of the icon item at a second moment. Optionally, the second version information can be used to represent the second version number of the icon item in the Iconfont platform. The first moment can be the moment when the icon item is first obtained from the Iconfont platform; the second moment can be the moment when the Iconfont platform is accessed during an update check, and the first moment is earlier than the second moment.

[0088] In this embodiment, first version information is extracted from the adjusted project information, and second version information is obtained from the icon platform. Optionally, after obtaining the project information of the icon project from the Iconfont platform, an update check needs to be performed on the obtained project information to determine whether it needs to be updated. When performing the update check, the contents of the iconfont.json file are traversed, and the first version number stored in the version field of the iconfont.json file is read to obtain the first version information. Simultaneously, the second version number of the icon project in the Iconfont platform is obtained by accessing the Iconfont platform, thus obtaining the second version information.

[0089] In this embodiment, after obtaining the first version information and the second version information, the information relationship between the first version information and the second version information can be determined. Optionally, after obtaining the first version information and the second version information, the information relationship between the first version information and the second version information can be determined by comparing the relationship between the first version number indicated by the first version information and the second version number indicated by the second version information. The aforementioned information relationship can be either the same or different.

[0090] In this embodiment, after determining the information relationship between the first version information and the second version information, the adjusted project information can be updated or maintained according to the information relationship. Optionally, after determining the information relationship between the first version information and the second version information, the adjusted project information can be updated or maintained according to whether the first version information and the second version information are the same or different as indicated by the above information relationship.

[0091] In this embodiment, by extracting the first version information from the project information and obtaining the second version information from the icon platform, the information relationship between the first version information and the second version information can be determined, thereby achieving the purpose of determining whether to update or maintain the project information based on the information relationship.

[0092] As an optional implementation method, updating the adjusted project information based on information relationships includes: updating the adjusted project information in response to the information relationship being different between the first version information and the second version information; and maintaining the adjusted project information based on information relationships includes: maintaining the adjusted project information in response to the information relationship being the same between the first version information and the second version information.

[0093] In this embodiment, the adjusted project information is updated in response to a difference between the first version information and the second version information in terms of information relationship. Optionally, when the aforementioned information relationship indicates that the first version information and the second version information are different, the adjusted project information is updated.

[0094] For example, when the first version information differs from the second version information, it indicates that the version of the project information stored locally is inconsistent with the version of the project information in the Iconfont platform. In this case, the project information corresponding to the second version information is retrieved from the Iconfont platform, along with the project information corresponding to the first version information stored locally. Simultaneously, the update details (e.g., added icons, deleted icons, or modified icons) contained in the project information corresponding to the second version information are retrieved, and the update log corresponding to the update details is displayed.

[0095] In this embodiment, in response to the information relationship indicating that the first version information and the second version information are the same, the adjusted project information is maintained. Optionally, when the aforementioned information relationship indicates that the first version information and the second version information are the same, the adjusted project information is maintained.

[0096] For example, when the first version information is the same as the second version information, it means that the version of the project information stored locally is consistent with the version of the project information in the Iconfont platform. In this case, a prompt can be displayed that "the icon information is the latest version".

[0097] In this embodiment, when the above information relationships are different, the adjusted project information is updated; when the above information relationships are the same, the adjusted project information is maintained, thereby achieving the goal of keeping the adjusted project information as the latest version.

[0098] In this embodiment, when an icon is displayed in a vehicle application, the project information of the icon items required by the vehicle application is obtained; the attributes and content in the project information are adjusted to obtain adjusted project information; based on the adjusted project information, configuration information for the icon to be displayed in the application is generated; and the icon to be displayed is configured on the application interface according to the configuration information. In other words, in this embodiment, after obtaining the project information of the icon items required by the vehicle application, the adjusted project information can be obtained by adjusting the attributes and content in the obtained project information, and configuration information describing at least one parameter of the icon to be displayed can be generated based on the adjusted project information. Finally, according to the generated at least one parameter of the icon to be displayed, the icon to be displayed can be configured on the interface, thereby avoiding icon scaling distortion and solving the technical problem of low icon maintenance efficiency, thus achieving the technical effect of improving icon maintenance efficiency.

[0099] The above technical solutions of the embodiments of this application will be further illustrated below with reference to preferred embodiments of the present invention.

[0100] In related technologies, when maintaining icons, application development tools often store icons in image format. However, these icons are usually scattered across different development projects of the application. When adding, deleting, or modifying icons, it is necessary to manually synchronize the maintained code and resources across different development projects. This results in excessively long icon maintenance times, leading to the technical problem of low icon maintenance efficiency.

[0101] However, this application proposes a method for displaying icons in a vehicle application. The method involves obtaining project information for the icon items required by the vehicle application; adjusting the attributes and content of the project information to obtain adjusted project information; generating configuration information for the icon to be displayed in the application based on the adjusted project information; and configuring the icon to be displayed on the application interface according to the configuration information. In other words, in this application embodiment, after obtaining the project information for the icon items required by the vehicle application, the adjusted project information can be obtained by adjusting the attributes and content of the obtained project information. Based on the adjusted project information, configuration information describing at least one parameter of the icon to be displayed can be generated. Finally, according to the generated at least one parameter of the icon to be displayed, the icon can be configured on the interface, thereby avoiding icon scaling distortion and solving the technical problem of low icon maintenance efficiency, thus achieving the technical effect of improving icon maintenance efficiency.

[0102] Figure 2 This is a schematic diagram of a font icon integration management system according to an embodiment of this application; as shown Figure 2 As shown, the font icon integration management system 200 may include: an icon resource management module 201, a font file processing module 202, a code generation module 203, an icon calling module 204, and a version update module 205.

[0103] The icon resource management module 201 is used to interface with the Iconfont platform and manage project data. This module can be implemented through the following steps.

[0104] The steps for platform integration configuration are as follows: Enter the unique identifier of the Iconfont project in this module. This identifier can be: a project ID (e.g., a numeric ID assigned by the Iconfont platform) or a project online link (e.g., a server address located on the internet). This module has built-in Iconfont platform API call logic, sending verification requests to the Iconfont platform via Hypertext Transfer Protocol Secure (HTTPS). Public project information can be directly obtained through the project ID or project online link, or private projects can be accessed by configuring an Iconfont platform authentication token.

[0105] The steps for synchronizing icon library information are as follows: This module initiates a synchronization request to the Iconfont platform to obtain complete project information, including: basic information (e.g., project name, creation time, latest version number, and update time); icon details (e.g., icon name, Unicode encoding, icon label, whether it is newly added / deprecated, etc.); and font association information (e.g., online download address of font files, font family name, etc.).

[0106] The steps for local metadata storage and structured management. This module parses the synchronized information into structured data and generates an iconfont.json file, with the default storage path being the project root directory.

[0107] The font file processing module 202 is used to automatically download font files and adapt them to different platforms. This module can be implemented through the following steps.

[0108] The automatic font file download process involves the following steps: This module extracts the online URL of the font file from the icon metadata (iconfont.json), automatically initiates a download request, and obtains the iconfont.ttf file. During the download, it supports resuming interrupted downloads (for network interruption scenarios) and verifies the file's MD5 value (comparing it with the verification value returned by the platform) to ensure file integrity. The downloaded font file is temporarily stored in the . / iconfont / temp / directory for later distribution.

[0109] The steps for cross-platform resource directory distribution are as follows: For iOS: This module detects the iOS project path (e.g., . / ios / [project name] / ) and copies the iconfont.ttf file to the . / ios / [project name] / Resources / directory (automatically creating the directory if it doesn't exist). For Android: This module detects the Android project path (e.g., . / android / app / src / main / ) and copies the iconfont.ttf file to the . / android / app / src / main / assets / fonts / directory (automatically creating the assets / fonts subdirectories). This module supports custom platform resource paths (set via the configuration file iconfont.config.js, overriding the default path).

[0110] The platform relies on automatic configuration steps. For iOS configuration: This module parses the Info.plist file of the iOS project (path: . / ios / [project name] / Info.plist), in... <key> UIAppFonts< / key> Add iconfont.ttf to the corresponding array (skip if it already exists to avoid duplicate configuration) to ensure the system recognizes the font. For Android configuration: no additional configuration is required (Android will automatically scan the assets / fonts directory and load fonts). This module can generate a log message indicating "Android font configuration complete." After configuration, this module automatically backs up the original configuration file (e.g., Info.plist.bak) for easy recovery in case of errors.

[0111] Code generation module 203 is used to generate reusable icon components. This module can be implemented through the following steps.

[0112] The steps for defining a component template. This module has a built-in React Native component template, which includes the basic structure: importing a Text component (which renders font icons in React Native), defining an Iconfont functional component, and receiving properties such as name, size, and color.

[0113] The module generates mapping relationships based on metadata. By parsing the icons array in iconfont.json, it can generate an iconMap that maps icon names to Unicode characters. Embedding this mapping object into a React Native component template enables dynamic matching between icon names and Unicode characters.

[0114] Steps for supporting component properties and styles. React Native components receive and process core properties, which include the following.

[0115] name: Required, icon name (associated with the key in iconMap);

[0116] size: Optional, font size (default 16), type is number;

[0117] color: Optional, icon color (default #000), type string;

[0118] style: Optional, custom style (supports Text component styles such as fontWeight / margin).

[0119] Additionally, React Native components can retrieve the Unicode from the iconMap using the name for rendering. <text>The component is set to "fontFamily: 'iconfont'" (associated with the font file).

[0120] The module outlines the steps for component output and type definition. Following these steps, it generates the Iconfont.js file, with the default path being . / src / components / Iconfont / (custom paths are supported). It also generates a TypeScript type definition file, Iconfont.d.ts, to constrain attribute types (e.g., name must be a key from the iconMap), improving the development experience.

[0121] The icon call module 204 is used to standardize the interface and facilitate ease of use. This module can be implemented through the following steps.

[0122] The steps for importing and initializing the component are as follows: Import the generated component using a relative path: "import Iconfontfrom '.. / components / Iconfont';". This module can automatically handle platform compatibility (e.g., differences in font rendering between iOS and Android) when generating components, without requiring additional adaptation.

[0123] The module standardizes the steps for invoking icons. It can retrieve the icon to be displayed by its name. When a non-existent name is entered, the component will throw a warning in the development environment (e.g., "Icon 'invalid-name' not found in iconMap") to facilitate debugging.

[0124] Steps for global configuration support. This module can globally configure default properties (e.g., default size / color) through a predefined component (IconfontProvider) to avoid repeated settings.

[0125] Version update module 205 is used for automatic monitoring and synchronization mechanisms. This module can be implemented through the following steps.

[0126] Update the steps for monitoring triggering. This module supports the following two monitoring methods.

[0127] Manual triggering: Proactively check for updates by executing a command (e.g., npx iconfont-sync);

[0128] Automatic Trigger: This module automatically initiates a check when the project starts (e.g., react-native start) (can be turned off through configuration).

[0129] The version comparison logic steps are as follows: This module requests the latest version number of the current project from the Iconfont platform and compares it with the version in the local iconfont.json file.

[0130] When the versions are the same: this module can display "The icon library is now the latest version";

[0131] When versions are inconsistent: This module retrieves update details (e.g., added icons, deleted icons, and modified icons), and displays the update log (e.g., "added icon: user; deleted icon: old-home").

[0132] The steps for automatic synchronization and component rebuilding. After confirming the update, this module can perform the following operations.

[0133] Step 1: Resynchronize icon project information and update iconfont.json (keep a backup of historical versions).

[0134] Step 2: Download the latest iconfont.ttf again, overwrite the old font file, and distribute it to the corresponding platform directory.

[0135] Step 3: Regenerate Iconfont.js and type files based on the new metadata, and update the mapping relationships.

[0136] Step 4: If the iOS font configuration changes (e.g., the font file name is modified), update Info.plist synchronously.

[0137] In this embodiment, the icon integration management system can obtain project information for icon projects from the Iconfont platform and download the font files contained in the project information. Based on the project information and font files, reusable icon components can be generated, and by calling these icon components, the icons to be displayed can be invoked. This achieves the goal of avoiding icon scaling distortion, solves the technical problem of low icon maintenance efficiency, and realizes the technical effect of improving icon maintenance efficiency.

[0138] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0139] According to an embodiment of this application, an embodiment of a device for displaying icons in a vehicle application is provided. It should be noted that this device can be used to execute the above-described method for displaying icons in a vehicle application. Figure 3 This is a schematic diagram of an icon display device in a vehicle application according to an embodiment of this application. Figure 3 As shown, the icon display device 300 in the vehicle's application may include: an acquisition unit 301, a conversion unit 302, a generation unit 303, and a configuration unit 304.

[0140] The acquisition unit 301 is used to acquire the project information of the icon items required by the vehicle's application, wherein the icon items come from an icon platform that the application is allowed to access, and the project information is used to represent the attributes and content of the icon items.

[0141] The conversion unit 302 is used to adjust the attributes and content in the project information to obtain the adjusted project information, wherein the adjusted project information is used to represent the adjusted attributes and content.

[0142] The generation unit 303 is used to generate configuration information for an icon to be displayed in the application based on the adjusted project information, wherein the configuration information is used to represent at least one parameter describing the icon to be displayed through a preset information format.

[0143] Configuration unit 304 is used to configure the icon to be displayed on the application interface according to the configuration information.

[0144] Optionally, the generation unit 303 includes: an extraction module for extracting address information from the adjusted project information, wherein the address information is used to indicate the address where the font file in the content is stored; a download module for downloading the font file by accessing the address corresponding to the address information; and a generation module for generating configuration information based on the downloaded font file.

[0145] Optionally, the generation module includes: a determination submodule, used to determine the configuration strategy of the font file using the application's adaptation platform, wherein the configuration strategy is used to represent the rules for configuring the font file; a configuration submodule, used to configure the font file on the adaptation platform according to the configuration strategy; and a generation submodule, used to generate configuration information based on the configured font file.

[0146] Optionally, the generation submodule includes: a parsing component, used to parse the names of the configured font file to obtain various name information, wherein the name information is used to represent the names of the icons in the icon project, and the icon project includes: multiple icons; a generation and configuration component, used to generate encoding information mapped to the various name information respectively to obtain various encoding information, and to adjust the configured font file to obtain an adjusted font file, wherein the encoding information is used to represent the result of encoding the icons; and a generation component, used to generate configuration information from the various encoding information, the adjusted font file, and the class information of the font file, wherein the class information is used to represent the font category to which the font file belongs.

[0147] Optionally, the determining submodule includes: a first determining component, used to determine a configuration strategy as a first configuration strategy in response to the adaptation platform being a first adaptation platform; and a second determining component, used to determine a configuration strategy as a second configuration strategy in response to the adaptation platform being a second adaptation platform.

[0148] Optionally, the configuration submodule includes: a first configuration component, used to configure font files on a first adaptation platform according to a first configuration strategy; and a second configuration component, used to configure font files on a second adaptation platform according to a second configuration strategy.

[0149] Optionally, the conversion unit 302 includes: a first parsing module, used to perform structural parsing on the attributes and content to obtain the parsed attributes and parsed content; and a second parsing module, used to perform structural adjustments on the parsed attributes and parsed content to obtain the adjusted project information.

[0150] Optionally, the device further includes: an extraction unit, configured to extract first version information from the adjusted project information and obtain second version information from the icon platform, wherein the first version information represents the version of the icon project at a first moment, and the second version information represents the version of the icon project at a second moment, with the first moment being earlier than the second moment; a determination unit, configured to determine the information relationship between the first version information and the second version information; an update unit, configured to update the adjusted project information based on the information relationship; or, a retention unit, configured to retain the adjusted project information based on the information relationship.

[0151] Optionally, the update unit includes: an update module, used to update the adjusted project information in response to a difference between the first version information and the second version information; the retain unit includes: a retain module, used to retain the adjusted project information in response to a difference between the first version information and the second version information.

[0152] In this embodiment, project information for the icon items required by the vehicle's application is obtained; the attributes and content in the project information are adjusted to obtain adjusted project information; based on the adjusted project information, configuration information for the icon to be displayed in the application is generated; and the icon to be displayed is configured on the application's interface according to the configuration information. In other words, in this embodiment, after obtaining the project information for the icon items required by the vehicle's application, the attributes and content in the obtained project information are adjusted to obtain adjusted project information, and configuration information describing at least one parameter of the icon to be displayed can be generated based on the adjusted project information. Finally, according to the generated at least one parameter of the icon to be displayed, the icon to be displayed can be configured on the interface, thereby avoiding icon scaling distortion and solving the technical problem of low icon maintenance efficiency, thus achieving the technical effect of improving icon maintenance efficiency.

[0153] Embodiments of this application also provide an electronic device, including: a memory storing an executable program; and a processor for running the program, wherein the program executes the methods in various embodiments of this application when it runs.

[0154] Embodiments of this application also provide a computer-readable storage medium including a stored executable program, wherein, when the executable program is running, it controls the device where the computer-readable storage medium is located to perform the methods of various embodiments of this application.

[0155] Embodiments of this application also provide a computer program product, including a computer program that, when executed by a processor, implements the methods of various embodiments of this application.

[0156] Embodiments of this application also provide a computer program product, including a non-volatile computer-readable storage medium for storing a computer program that, when executed by a processor, implements the methods in various embodiments of this application.

[0157] Embodiments of this application also provide a computer program that, when executed by a processor, implements the methods described in the various embodiments of this application.

[0158] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

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

[0160] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

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

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

[0163] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.< / text>

Claims

1. A method for displaying icons in a vehicle application, characterized in that, include: Obtain the project information of the icon items required by the vehicle's application, wherein the icon items come from an icon platform that the application is allowed to access, and the project information is used to represent the attributes and content of the icon items; The attributes and content in the project information are adjusted to obtain the adjusted project information, wherein the adjusted project information is used to represent the adjusted attributes and the adjusted content; Based on the adjusted project information, configuration information for the icon to be displayed in the application is generated, wherein the configuration information is used to represent at least one parameter describing the icon to be displayed in a preset information format; Configure the icon to be displayed on the interface of the application according to the configuration information.

2. The method according to claim 1, characterized in that, Based on the adjusted project information, configuration information for the icons to be displayed in the application is generated, including: From the adjusted project information, the address information is extracted, wherein the address information is used to indicate the address where the font file in the content is stored; The font file is downloaded by accessing the address corresponding to the address information; The configuration information is generated based on the downloaded font file.

3. The method according to claim 2, characterized in that, Based on the downloaded font file, the configuration information is generated, including: Using the application's adaptation platform, a configuration strategy for the font file is determined, wherein the configuration strategy represents the rules for configuring the font file; On the adaptation platform, configure the font file according to the configuration strategy; The configuration information is generated based on the configured font file.

4. The method according to claim 3, characterized in that, Based on the configured font file, the configuration information is generated, including: The configured font file is parsed to obtain various name information, wherein the name information is used to represent the name of the icon in the icon project, and the icon project includes: multiple icons; Generate encoding information that maps to various name information respectively, obtain various encoding information, and adjust the configured font file to obtain the adjusted font file, wherein the encoding information is used to represent the result of encoding the icon; The configuration information is generated by combining various encoding information, the adjusted font file, and the class information of the font file, wherein the class information is used to indicate the font category to which the font file belongs.

5. The method according to claim 3, characterized in that, The adaptation platform includes: a first adaptation platform and a second adaptation platform. The first number of platforms extending from the first adaptation platform is less than the second number of platforms extending from the second adaptation platform. The configuration strategy includes: a first configuration strategy and a second configuration strategy. The first configuration strategy represents the rules for configuring the font file on the first adaptation platform, and the second configuration strategy represents the rules for configuring the font file on the second adaptation platform. Determining the configuration strategy for the font file using the application's adaptation platform includes: In response to the fact that the adapted platform is the first adapted platform, the configuration strategy is determined to be the first configuration strategy; In response to the fact that the adapted platform is the second adapted platform, the configuration strategy is determined to be the second configuration strategy.

6. The method according to claim 5, characterized in that, On the adaptation platform, the font file is configured according to the configuration strategy, including: On the first adaptation platform, configure the font file according to the first configuration strategy; On the second adaptation platform, the font file is configured according to the second configuration strategy.

7. The method according to any one of claims 1 to 6, characterized in that, The attributes and content in the project information are adjusted to obtain the adjusted project information, including: Perform structural parsing on the attributes and the content to obtain the parsed attributes and the parsed content; The parsed attributes and parsed content are structurally adjusted to obtain the adjusted project information.

8. A device for displaying icons in a vehicle application, characterized in that, include: The acquisition unit is used to acquire project information of the icon items required by the application of the vehicle, wherein the icon items come from an icon platform that the application is allowed to access, and the project information is used to represent the attributes and content of the icon items; A conversion unit is used to adjust the attributes and content in the project information to obtain the adjusted project information, wherein the adjusted project information is used to represent the adjusted attributes and the adjusted content; The generation unit is configured to generate configuration information for an icon to be displayed in the application based on the adjusted project information, wherein the configuration information is used to represent at least one parameter describing the icon to be displayed in a preset information format; A configuration unit is used to configure the icon to be displayed on the interface of the application according to the configuration information.

9. An electronic device, characterized in that, include: Memory, which stores executable programs; A processor for running the program, wherein the program, when running, performs the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored executable program, wherein, when the executable program is executed, it controls the device on which the storage medium is located to perform the method according to any one of claims 1 to 7.

Images