Text style unified management method and device based on configuration sharing and electronic equipment

Abstract

This invention belongs to the field of computer software technology, specifically relating to a method, apparatus, and electronic device for unified management of text styles based on configuration sharing in graphical user interface (GUI) development. The method includes the following steps: S10, creating text style configurations and generating a unique identifier for each text style configuration, wherein the text style configuration contains multiple text style attributes; S20, applying the text style configurations to text components to achieve batch setting of style attributes; S30, synchronizing text style configurations among multiple text style managers, performing configuration identification and synchronization based on the unique identifier; S40, providing a visual interface for managing text style configurations; S50, automatically applying text style configurations when the text style manager component is enabled.

Description

Technical Field

[0001] This invention belongs to the field of computer software technology, and specifically relates to a method, device, and electronic device for unified management of text styles based on configuration sharing. Background Technology

[0002] In graphical user interface (GUI) development, especially in game and interactive application development, managing and maintaining the consistency of a large number of UI text styles is a common and tedious task. The existing common methods and their main problems include: (1) Manually setting each one: setting the font, size, color, spacing and other attributes one by one each time. The problem is that it is extremely inefficient. Modifying a style (such as the title font) requires repeated operation on dozens or even hundreds of components, which is prone to errors and difficult to guarantee global consistency. (2) Template / resource reuse: creating a text template or resource file with a specific style and instantiating it when needed. The problem is that it is inflexible. Once instantiated, it will break the association with the template if different modifications are needed. It is difficult to manage text across different templates in a unified manner and cannot effectively manage dynamically generated text. (3) Hard-coding in scripts: setting styles in C# scripts by code such as textComponent.fontSize=36. The problem is that styles are coupled with logic, and debugging and modification require recompilation; it lacks intuitiveness and is difficult for designers to participate. (4) Simple static configuration class: Create a TextStyle class to store some style properties and reference it in the code. The problem is that the functionality is incomplete (usually only including basic properties such as color and size); it lacks two-way interaction between runtime and editor; there is no automatic change propagation mechanism, and the configuration still needs to be manually applied to each component. Summary of the Invention

[0003] In view of the above-mentioned problems, the present invention provides a unified text style management method, device and electronic device based on configuration sharing, which provides centralized, shareable and real-time synchronized text style management.

[0004] To solve the above-mentioned technical problems, the present invention adopts the following technical solution: The first aspect of this invention provides a method for unified management of text styles based on configuration sharing, comprising the following steps: S10, Create a text style configuration and generate a unique identifier for each text style configuration, wherein the text style configuration contains multiple text style attributes; S20 applies text style configuration to text components, enabling batch setting of style attributes; S30, synchronize text style configurations among multiple text style managers, and perform configuration identification and synchronization based on the unique identifier; S40 provides a visual interface for managing text style configurations; S50 automatically applies text style configurations when the text style manager component is enabled.

[0005] In one possible implementation, creating a text style configuration in S10 includes: receiving a new configuration name input by the user; initializing the new configuration based on the style attributes of the current text component; generating a globally unique identifier for the new configuration; and adding the new configuration to the configuration list.

[0006] In one possible implementation, the text style configuration includes at least one of the following attributes: font resources, font material, font size, font color, font style, text alignment, automatic size adjustment, minimum font size, maximum font size, whether to enable line breaks, character spacing, word spacing, line spacing, and paragraph spacing.

[0007] In one possible implementation, the synchronized text style configuration in S30 includes: maintaining a static manager list to record all active text style managers; when a configuration is modified in a text style manager, finding the corresponding configuration in other text style managers using the unique identifier; updating the attribute values ​​of the found configuration; and applying the updated style to all text components using the configuration.

[0008] In one possible implementation, it further includes: S60, configuration update: receiving a configuration update instruction from the user; saving the style attributes of the current text component to a specified configuration; Notify all text components using this configuration to update their display.

[0009] In one possible implementation, the unique identifier adopts the GUID format to ensure the uniqueness of the configuration across scenarios and projects.

[0010] A second aspect of the present invention provides a unified text style management device based on configuration sharing, comprising: The configuration management layer is used to create and manage text style configurations. Each text style configuration contains multiple text style attributes and has a unique identifier. A synchronization engine layer is used to synchronize text style configurations across multiple text style managers. The shared synchronization layer identifies and synchronizes configurations based on the unique identifier. The editor extension layer provides a visual interface within the editor to support the creation, application, updating, and deletion of text style configurations. The application layer is used to automatically apply specified text style configurations when the text style manager component is enabled.

[0011] In one possible implementation, the text style configuration includes at least one of the following attributes: font resources, font material, font size, font color, font style, text alignment, automatic size adjustment, minimum font size, maximum font size, whether to enable line breaks, character spacing, word spacing, line spacing, and paragraph spacing.

[0012] In one possible implementation, the synchronization engine layer further includes: The GUID index table is used to store the mapping relationship between globally maintained configuration identifiers and content; A static manager list is used to maintain all active text style manager instances; The synchronization controller is used to synchronize changes to other text style managers when a change in text style configuration is detected.

[0013] In one possible implementation, when synchronizing configurations, the synchronization controller uses the unique identifier to find the corresponding configuration in other text style managers and updates the properties of that configuration.

[0014] In one possible implementation, the editor extension layer further includes: The configuration creation unit supports creating new configurations via interface input; Configure the application unit to support applying configurations via drop-down menus or buttons; The configuration update unit is used to support saving the current text style to a specified configuration. The configuration deletion unit is used to support the deletion of configurations that are no longer needed.

[0015] A third aspect of the present invention provides an electronic device comprising one or more processing units and one or more storage units, wherein the one or more storage units store at least one piece of program code, the at least one piece of program code being loaded and executed by the one or more processing units to perform the operations performed by the text style unified management method based on configuration sharing as described above.

[0016] The present invention has the following beneficial effects: (1) Reduce batch style modification from hours of manual operation to a few seconds of configuration update.

[0017] (2) The mechanism eliminates the possibility of inconsistent styles and facilitates the achievement of consistency.

[0018] (3) It provides the team with a unified style source and modification specifications, and new members can quickly understand the project UI system through the configuration list in the editor of this invention.

[0019] (4) The style logic is centrally managed, the scope of the impact of modifications is clear, and it is convenient to switch global themes or iterate styles.

[0020] (5) Smooth learning curve: The intuitive editor interface allows planners and artists to easily participate in style management. Attached Figure Description

[0021] Figure 1 This is a flowchart illustrating the steps of a unified text style management method based on configuration sharing, according to an embodiment of the present invention. Figure 2 This is a schematic diagram of a text style unified management device based on configuration sharing, according to another embodiment of the present invention. Figure 3 This is a schematic diagram of the data flow under the system architecture of unified text style management based on configuration sharing in a specific application example; Figure 4 A schematic diagram illustrating the working principle of configuring a synchronization mechanism in a specific application example; Figure 5 A flowchart illustrating the process of creating a text configuration in a specific application example; Figure 6 This is a flowchart illustrating the process of selecting a configuration from a created text configuration and applying it in a specific application example. Figure 7 This is a flowchart illustrating the process of updating and synchronizing configurations in a specific application instance. Figure 8 is a flowchart illustrating the process of deleting text configuration in a specific application example. Figure 9 This is a schematic diagram of the editor interface in a specific application example. Figure 10 This is a schematic block diagram of an electronic device according to an embodiment of the present invention. Detailed Implementation

[0022] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0023] See Figure 1 The diagram shows a flowchart of a text style unified management method based on configuration sharing according to an embodiment of the present invention, including the following steps: S10, Create text style configurations and generate a unique identifier for each text style configuration. Each text style configuration contains multiple text style attributes. S20 applies text style configuration to text components, enabling batch setting of style attributes; S30 synchronizes text style configurations across multiple text style managers, using unique identifiers for configuration identification and synchronization. The unique identifiers use GUID format to ensure the uniqueness of configurations across scenarios and projects.

[0024] S40 provides a visual interface for managing text style configurations; S50 automatically applies text style configurations when the text style manager component is enabled.

[0025] In a specific application example, creating a text style configuration in S10 includes: receiving a new configuration name input by the user; initializing the new configuration based on the style attributes of the current text component; generating a globally unique identifier for the new configuration; and adding the new configuration to the configuration list.

[0026] Specifically, text style configuration includes at least one of the following attributes: font resources, font material, font size, font color, font style, text alignment, automatic resizing, minimum font size, maximum font size, whether to enable line breaks, character spacing, word spacing, line spacing, and paragraph spacing.

[0027] In a specific application example, the synchronized text style configuration in S30 includes: maintaining a static manager list to record all active text style managers; when a configuration is modified in a text style manager, finding the corresponding configuration in other text style managers using the unique identifier; updating the attribute values ​​of the found configuration; and applying the updated style to all text components using the configuration.

[0028] Based on S10 to S50, see continue. Figure 1 Another embodiment of the present invention provides a unified text style management method based on configuration sharing, which further includes: S60, configuration update: receiving a user's configuration update instruction; saving the style attributes of the current text component to a specified configuration; Notify all text components using this configuration to update their display.

[0029] The above-described unified text style management method based on configuration sharing uses the same management system in both editing and running modes to support unified management during runtime and editing.

[0030] The above-described text style unified management method based on configuration sharing operates on a text style unified management device based on configuration sharing, according to another embodiment of the present invention. Figure 2As shown, the system architecture of this device is mainly divided into four core layers: configuration management layer, synchronization engine layer, application layer, and editor extension layer. The configuration management layer is used to create and manage text style configurations. Each text style configuration contains multiple text style attributes and has a unique identifier. A synchronization engine layer is used to synchronize text style configurations across multiple text style managers. The shared synchronization layer identifies and synchronizes configurations based on the unique identifier. The editor extension layer provides a visual interface within the editor to support the creation, application, updating, and deletion of text style configurations. The application layer is used to automatically apply specified text style configurations when the text style manager component is enabled.

[0031] Furthermore, the configuration management layer includes a local configuration database that stores all text style configuration objects. Each configuration object (such as Config A, Config B) contains complete style attributes, including all attributes supported by the text rendering component, such as font resources, font material, font size, font color, font style, text alignment, automatic size adjustment, minimum font size, maximum font size, whether to enable line breaks, character spacing, word spacing, line spacing, paragraph spacing, and more than a dozen other items. Each configuration has a unique GUID identifier (such as xxx, yyy).

[0032] The synchronization engine layer includes a GUID index table to store the mapping between globally maintained configuration identifiers and content; a static manager list to maintain all active text style manager instances (such as TextStyleManager); and a synchronization controller to synchronize changes to other text style managers when a change in text style configuration is detected. When synchronizing configurations, the synchronization controller uses the unique identifier to find the corresponding configuration in other text style managers and updates the properties of that configuration.

[0033] The application layer includes multiple text components. After the developer selects a configuration in the TextStyleManager, each text UI component connects to the configuration system through its associated TextStyleManager.

[0034] The editor extension layer provides a visual operation interface, bridging user operations and core system functions, significantly reducing the barrier to entry for this invention. During development, non-programmers such as artists and planners can also edit and manage text styles.

[0035] In a specific application example, the editor extension layer further includes: a configuration creation unit, which supports creating new configurations through interface input; a configuration application unit, which supports applying configurations through drop-down menus or buttons; a configuration update unit, which supports saving the current text style to a specified configuration; and a configuration deletion unit, which supports deleting configurations that are no longer needed.

[0036] Figure 3 To determine the data flow under the system architecture based on the above devices, firstly, the data of the configuration object is associated with the GUID and the global index table. The static manager list data stores all manager instances. Each manager instance is linked to the GUID through the configured application. Therefore, each manager corresponds to the data of a configuration object. The synchronization controller listens for configuration changes and notifies the relevant components.

[0037] Figure 4 The diagram illustrates the working principle of the configuration synchronization mechanism in a specific application example. The left side shows change detection; for example, if the font size of ConfigX in Manager A is changed from 36 to 42, the system will detect the change in configuration attributes, set a change flag, and prepare for synchronization. The middle section shows synchronization propagation; after receiving the change notification, the global synchronization controller searches for the configuration in the global index using the GUID, accesses the static manager list to obtain all manager instances corresponding to the applied configuration, and finally broadcasts the change information to all relevant managers. The right side shows the update execution process; relevant managers find the configuration with the same GUID locally, update the relevant font attributes, and each manager applies the new style to other management text components in parallel. Shared synchronization supports both automatic and manual synchronization modes, allowing users to choose the appropriate method. Two synchronization modes can be set: automatic synchronization, triggered in real-time after configuration modification, with conditions including configuration modification, actual attribute change, and automatic synchronization being enabled; and manual synchronization, triggered when the user actively clicks the synchronization button, suitable for batch update scenarios. In a specific application example, developers need to create text configurations. Figure 5 The diagram shows the main process for creating a text configuration, which includes: S401. In the configuration name input box of the visual properties panel (or style manager panel) of the development tool, enter the name of the configuration, such as Body 1, Heading 2, etc. S402, the developer triggers the creation operation through the create button in the editor interface. The created text configuration will automatically generate a unique identifier GUID, which will be the unique identifier to distinguish the configuration. S403: After creating the GUID, record the current style attributes of the text component on the corresponding UI node, including the values ​​of more than ten attributes such as font, size, color, and spacing. Bind it to the GUID and create a configuration object, such as Config{name:"NewTitle" guid:"a1b2..."fontSize:36 ...}; S404, Add the created configuration object to the configuration list, such as [ConfigA, ConfigB, Body 1]; S405 synchronizes the latest configuration list to other managers. First, it finds the managers that have enabled the sharing function, and then sends the latest configuration list data to all the found managers.

[0038] In a specific application example, the developer needs to select a configuration from the created text configuration to apply, see... Figure 6 ,include: S501 During development, if you need to manage the style of a text element, you can add or associate a "TextStyleManager" component on its UI node. S502: During the editing process in the manager, drop down the configuration list, select a configuration to apply, or select a configuration in the configuration list and click the corresponding apply button to apply the selected configuration attribute value to the text component of the corresponding node. At this time, the text component and font component in the node will apply the attribute value of the selected configuration.

[0039] S503, after applying the configuration attributes, register the relationship between the GUID and the manager, and update the manager list of the GUID. In the subsequent update and synchronization of configuration, this invention needs to find the manager that needs to be updated through the registered manager list.

[0040] In a specific application example, if the developer wants to update the configuration after the application is configured, see... Figure 7 The specific process for updating and synchronizing the configuration includes: S601: Select a configuration UI node that you want to adjust, and adjust the text style properties of the text component, including the values ​​of more than a dozen properties such as font, size, color, and spacing, all of which can be adjusted and updated; S602 offers two ways to update the configuration: first, click the "Synchronize Configuration" button in the current configuration section; second, find the configuration you want to update in the list of all configurations and click the corresponding "Update" button. S603, record the captured text style attributes of the current text component, and update the text attributes configured for the corresponding GUID; S604 synchronizes the latest configuration list to other managers. First, it finds the managers that have enabled the sharing function, and then sends the latest configuration list data to all the found managers. S605, for each manager node that has applied the updated GUID configuration, apply the updated GUID configuration's text style attribute.

[0041] In a specific application example, when a developer wants to delete a text configuration, see... Figure 8 The specific operating procedure is as follows: S701: In the configuration list of the manager, find the configuration you want to delete, and click the corresponding delete button. The manager will then delete the corresponding configuration from the configuration list. The S702 synchronizes the latest configuration list to other managers by first finding the managers that have enabled the sharing function, and then sending the latest configuration list data to all the found managers. Figure 9 The visual operation interface of the text style manager provided by this invention is demonstrated. This interface mainly includes: a shared control area, providing a master switch for shared configuration to control whether to participate in the global configuration synchronization network; and an automatic synchronization change sub-switch, controlling whether configuration modifications are automatically synchronized.

[0042] Configuration operation area: Provides a drop-down menu for the configuration list, and buttons for creating, applying, updating, and deleting, for centralized management of configurations.

[0043] The synchronization operation area features a single, prominent button that provides manual synchronization functionality. Clicking this button scans all managers and unifies their configurations, addressing the need for forced synchronization when configurations are inconsistent.

[0044] The current configuration area includes a drop-down menu that displays all available configurations and provides a clear view of the current selection. The update button saves the current text style to the selected configuration, and the configuration data is synchronized in real time to other managers that have selected the same configuration, reflecting the configuration status in real time and supporting quick switching.

[0045] In the configuration list area, there is a creation form. Enter the new configuration name and click the create button to create the configuration. By default, three configurations can be displayed, which can be expanded or collapsed. At the same time, each configuration displays a name and three operation buttons: the apply button applies this configuration to the current text, the update button updates this configuration with the current text style, and the delete button deletes this configuration.

[0046] The automatic application switch controls the automatic behavior during OnEnable, ensuring that text styles are correctly restored when the scene loads.

[0047] In traditional development, developers need to find each text node in the object list and modify them one by one in the property panel; however, with the method of this invention, only the configuration needs to be modified once in the management interface.

[0048] The above-described method for unified text style management based on configuration sharing has at least the following beneficial effects: (1) Unified standardization: Plan the font styles required for interface development, use the editor to edit the configuration list, abstract the styles from specific components and turn them into reusable assets. Developers can first achieve a high degree of unity between design and engine implementation by synchronizing the extracted style configuration with the text specifications in the interface specifications, thus solving the problem of difficulty in ensuring consistency.

[0049] (2) Interface development through a visual management interface: During the interface development process, an editor is added to the text component. The text style required during the development process is selected through GUID and static list, and a communication channel is established between the manager of the scene and the interface, so that configuration changes can be intelligently propagated.

[0050] (3) Adjust or update configuration through visual management interface: During the interface development process, there is a need to adjust the font style in a timely manner. In order to greatly improve the update efficiency, through the sharing and synchronization engine, you only need to adjust the corresponding font style through the unique GUID and use the editor to quickly complete the adjustment.

[0051] (4) Selective synchronization and sharing: The shareConfigurations and autoSyncChanges switches are available. Developers can use these two switches to allow projects to set the synchronization granularity as needed. In normal projects, there are always special font styles outside the unified specifications, leaving special functions for the overall process.

[0052] (5) Smooth learning curve: The visual management interface provided by this invention is intuitive and easy to use, enabling non-programmers such as planners and artists to easily participate in the design and management of styles, thereby improving team collaboration efficiency.

[0053] (6) Engine / Platform Universality: The configuration management, unique identifier synchronization, and manager architecture proposed in this embodiment of the invention are based on core ideas and do not depend on a specific game engine or development tool. This solution can be implemented in various game engines such as Unity, Unreal Engine, and Cocos2d-x, or in any application that supports a custom UI framework, and has good portability and wide applicability.

[0054] Reference Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Figure 8The electronic device 300 shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments of the present invention. The electronic device 300 is manifested as a general-purpose computing device. Components of the electronic device 300 may include, but are not limited to: at least one processing unit 310, a bus connecting different device components (including a storage unit 320 and the processing unit 310), an I / O interface 330, a display unit 340, etc. The storage unit stores program code, which can be executed by the processing unit 310, causing the processing unit 310 to perform the steps described in the method section of the above-described text style unified management method based on configuration sharing, according to various exemplary embodiments of the present invention. For example, the processing unit 310 may perform the following steps: S10, Create text style configurations and generate a unique identifier for each text style configuration. Each text style configuration contains multiple text style attributes. S20 applies text style configuration to text components, enabling batch setting of style attributes; S30 synchronizes text style configurations across multiple text style managers, using unique identifiers for configuration identification and synchronization. The unique identifiers use GUID format to ensure the uniqueness of configurations across scenarios and projects.

[0055] S40 provides a visual interface for managing text style configurations; S50 automatically applies text style configurations when the text style manager component is enabled.

[0056] The storage unit 320 may include a readable medium in the form of a volatile storage unit, such as a random access memory (RAM) unit 3201 and / or a cache memory unit 3202, and may further include a read-only memory unit (ROM) unit 3203. The storage unit 320 may also include a program / utility having a set (at least one) of program modules, including but not limited to: operating devices, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.

[0057] A bus can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus that uses any of the various bus structures.

[0058] Electronic device 300 can also communicate with one or more external devices 400 (e.g., keyboard, pointing device, Bluetooth device, etc.), and with one or more devices that enable a user to interact with electronic device 300, and / or with any device that enables electronic device 300 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via an input / output (I / O) interface. Furthermore, electronic device 300 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public network (Internet)) via network adapter 350. Network adapter 350 can communicate with other modules of electronic device 300 via a bus. Electronic device 300 displays the required information via display unit 340. It should be understood that, although... Figure 10 As not shown, other hardware and / or software modules may be used in conjunction with electronic device 300, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID devices, tape drives, and data backup storage devices.

[0059] It should be understood that the exemplary embodiments described herein are illustrative and not restrictive. Although one or more embodiments of the invention have been described in conjunction with the accompanying drawings, those skilled in the art will understand that various changes in form and detail may be made without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A method for unified management of text styles based on configuration sharing, characterized in that, Includes the following steps: S10, Create a text style configuration and generate a unique identifier for each text style configuration, wherein the text style configuration contains multiple text style attributes; S20 applies text style configuration to text components, enabling batch setting of style attributes; S30, synchronize text style configurations among multiple text style managers, and perform configuration identification and synchronization based on the unique identifier; S40 provides a visual interface for managing text style configurations; S50 automatically applies text style configurations when the text style manager component is enabled.

2. The text style unified management method based on configuration sharing as described in claim 1, characterized in that, The creation of text style configuration described in S10 includes: receiving a new configuration name input by the user; initializing the new configuration based on the style attributes of the current text component; generating a globally unique identifier for the new configuration; and adding the new configuration to the configuration list.

3. The text style unified management method based on configuration sharing as described in claim 1, characterized in that, The text style configuration includes at least one of the following attributes: font resources, font material, font size, font color, font style, text alignment, automatic size adjustment, minimum font size, maximum font size, whether to enable line breaks, character spacing, word spacing, line spacing, and paragraph spacing.

4. The text style unified management method based on configuration sharing as described in claim 1, characterized in that, The synchronized text style configuration described in S30 includes: maintaining a static manager list to record all active text style managers; when a configuration is modified in a text style manager, finding the corresponding configuration in other text style managers using the unique identifier; updating the attribute values ​​of the found configuration; and applying the updated style to all text components using that configuration.

5. The text style unified management method based on configuration sharing as described in claim 1, characterized in that, Further includes: S60, Configuration Update: Receives the user's configuration update command; saves the style attributes of the current text component to the specified configuration; Notify all text components using this configuration to update their display.

6. The text style unified management method based on configuration sharing as described in claim 1, characterized in that, The unique identifier adopts the GUID format to ensure the uniqueness of the configuration across scenarios and projects.

7. A unified text style management device based on configuration sharing, characterized in that, include: The configuration management layer is used to create and manage text style configurations. Each text style configuration contains multiple text style attributes and has a unique identifier. A synchronization engine layer is used to synchronize text style configurations across multiple text style managers. The shared synchronization layer identifies and synchronizes configurations based on the unique identifier. The editor extension layer provides a visual interface within the editor to support the creation, application, updating, and deletion of text style configurations. The application layer is used to automatically apply specified text style configurations when the text style manager component is enabled.

8. The text style unified management device based on configuration sharing as described in claim 7, characterized in that, The text style configuration includes at least one of the following attributes: font resources, font material, font size, font color, font style, text alignment, automatic size adjustment, minimum font size, maximum font size, whether to enable line breaks, character spacing, word spacing, line spacing, and paragraph spacing.

9. The text style unified management device based on configuration sharing as described in claim 7, characterized in that, The synchronization engine layer further includes: The GUID index table is used to store the mapping relationship between globally maintained configuration identifiers and content; A static manager list is used to maintain all active text style manager instances; The synchronization controller is used to synchronize changes to other text style managers when a change in text style configuration is detected.

10. The text style unified management device based on configuration sharing as described in claim 7, characterized in that, When synchronizing configurations, the synchronization controller uses the unique identifier to find the corresponding configuration in other text style managers and updates the properties of that configuration.

11. The text style unified management device based on configuration sharing according to claim 7, characterized in that, The editor extension layer further includes: The configuration creation unit supports creating new configurations via interface input; Configure the application unit to support applying configurations via drop-down menus or buttons; The configuration update unit is used to support saving the current text style to a specified configuration. The configuration deletion unit is used to support the deletion of configurations that are no longer needed.

12. An electronic device, characterized in that, The electronic device includes one or more processing units and one or more storage units, wherein the one or more storage units store at least one piece of program code, which is loaded and executed by the one or more processing units to perform the operations performed by the text style unified management method based on configuration sharing as described in any one of claims 1 to 6.

Images