CN110865827A

CN110865827A - Data updating method, device and system

Info

Publication number: CN110865827A
Application number: CN201810982508.4A
Authority: CN
Inventors: 张斌
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Singapore Holdings Pte Ltd
Priority date: 2018-08-27
Filing date: 2018-08-27
Publication date: 2020-03-06
Anticipated expiration: 2038-08-27
Also published as: CN110865827B

Abstract

The embodiment of the application provides a data updating method, equipment and a system, wherein the method comprises the following steps: in response to an update triggering event, determining a key identifier of a design unit needing to be updated as a target key identifier; acquiring a design unit to be updated corresponding to the target key identification from a design unit library; determining at least one design file to be updated corresponding to the target key identification according to the key identification of each design unit contained in at least one design file; and updating the design unit to be updated into at least one design file to be updated. In the embodiment of the application, batch updating of a plurality of design files can be realized, so that the updating efficiency of the design files is effectively improved, and the updating accuracy and comprehensiveness can be ensured.

Description

Data updating method, device and system

Technical Field

The present application relates to the field of data processing technologies, and in particular, to a data updating method, device, and system.

Background

When a technician develops a project, the technician uses design software to generate a design file, for example, a mobile phone interface can be used as a design file. Design files include design elements such as paperwork, common design components, and the like. Design files may be updated very frequently for various reasons, such as project upgrades.

Current design file update schemes typically involve manual modification of the design elements of a single design file that require updating by the design software. The number of design files involved is huge for each project, which results in that the work of updating the design files needs to consume a large amount of manpower and material resources, and mistakes and omissions are easy to occur. Especially for large projects, the required updating costs and workload are huge.

Therefore, a more efficient and less costly design file update scheme is needed.

Disclosure of Invention

Aspects of the present application provide a data updating method, device and system to provide a new, more efficient and less costly design file updating scheme.

The embodiment of the present application provides a data updating method, including:

in response to an update triggering event, determining a key identifier of a design unit needing to be updated as a target key identifier;

acquiring a design unit to be updated corresponding to the target key identification from a design unit library;

determining at least one design file to be updated corresponding to the target key identification according to the key identification of each design unit contained in at least one design file;

and updating the design unit to be updated into the at least one design file to be updated.

The embodiment of the present application further provides a data updating method, including:

responding to an operation interface access request, and displaying an operation interface which comprises an updating triggering control;

responding to the trigger operation of the updating trigger control, and displaying an information input interface;

and responding to the information input operation on the information input interface, and acquiring a key identifier of the design unit needing to be updated as a target key identifier, wherein the target key identifier is used for determining at least one design file to be updated.

The embodiment of the application also provides a server, which comprises a memory and a processor;

the memory to store one or more computer instructions;

the processor, coupled to the memory, to execute one or more computer instructions to:

The embodiment of the application also provides a client, which comprises a memory, a processor, a display and a communication component;

the memory to store one or more computer instructions;

responding to an operation interface access request, displaying an operation interface through the display, wherein the operation interface comprises an updating triggering control;

responding to the trigger operation of updating the trigger control, and displaying an information input interface through the display;

An embodiment of the present application further provides a data updating system, including: the system comprises a client, a server and a design unit library;

the client is used for sending an updating request to the server, wherein the updating request carries a target key identifier, and the target key identifier is a key identifier of a design unit needing to be updated;

the design unit library is used for storing the respective key identifiers of at least one design unit and at least one design unit;

the server is used for acquiring a design unit to be updated corresponding to the target key identification from the design unit library according to the update request sent by the client; and determining at least one design file to be updated corresponding to the target key identification according to the key identification of each design unit contained in at least one design file, and updating the design unit to be updated into the at least one design file to be updated.

In the embodiment of the present application, an association relationship between each design unit included in at least one design file and each design unit in the design unit library is formed based on the key identifier of each design unit. When an update triggering event occurs, the needed design units to be updated can be obtained from the design unit library according to the key identifiers of the design units to be updated, at least one design file to be updated is determined according to the key identifiers of the design units to be updated, and the design units to be updated are updated to the at least one design file to be updated in batches. Therefore, in the embodiment of the application, batch updating of a plurality of design files can be realized, the updating efficiency of the design files is effectively improved, and the updating accuracy and comprehensiveness can be ensured.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1 is a schematic structural diagram of a data updating system according to an embodiment of the present application;

fig. 1a is a schematic diagram of an interactive interface of a client according to an embodiment of the present application;

fig. 2 is a schematic structural diagram of another data updating system according to an embodiment of the present application

Fig. 3 is a schematic flow chart of a data updating method according to another embodiment of the present application;

fig. 4 is a schematic flowchart of another data updating method according to another embodiment of the present application;

fig. 5 is a schematic flow chart of a data updating method according to another embodiment of the present application;

FIG. 6 is a schematic flow chart diagram illustrating another data updating method according to another embodiment of the present application;

fig. 7 is a schematic structural diagram of a server according to another embodiment of the present application;

fig. 8 is a schematic structural diagram of a client according to yet another embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

In the prior art, a design file updating scheme is generally that design units needing to be updated in a single design file are manually modified through design software. The number of design files involved is huge for each project, which results in that the work of updating the design files needs to consume a large amount of manpower and material resources, and mistakes and omissions are easy to occur. Especially for large projects, the required updating costs and workload are huge. In some embodiments of the present application, an association relationship between each design unit included in at least one design file and each design unit in the design unit library is formed based on a key identifier of each design unit. When an update triggering event occurs, the needed design units to be updated can be obtained from the design unit library according to the key identifiers of the design units to be updated, at least one design file to be updated is determined according to the key identifiers of the design units to be updated, and the design units to be updated are updated to the at least one design file to be updated in batches. Therefore, in the embodiment of the application, batch updating of a plurality of design files can be realized, the updating efficiency of the design files is effectively improved, and the updating accuracy and comprehensiveness can be ensured.

The technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.

Fig. 1 is a schematic structural diagram of a data updating system according to an embodiment of the present application. As shown in fig. 1, the data update system includes: a client 11, a server 12 and a design unit library 13.

The client 11, the server 12 and the design unit library 13 are connected in communication with each other. The client 11, the server 12 and the design unit library 13 may be connected via a wireless or wired network. In this embodiment, if the three devices are communicatively connected through a mobile network, the network format of the mobile network may be any one of 2G (gsm), 2.5G (gprs), 3G (WCDMA, TD-SCDMA, CDMA2000, UTMS), 4G (LTE), 4G + (LTE +), WiMax, and even a new network format that will appear in the future.

In physical implementation, the client 11 may be a terminal device such as a personal computer, a smart phone, a tablet computer, etc., the server 12 may be a server device such as a conventional server, a cloud host, a virtual center, etc., and the design unit library 13 may be a storage device such as a local storage, a cloud storage, a network hard disk, etc. The server device mainly includes a processor, a hard disk, a memory, a system bus, and the like, and is similar to a general computer architecture.

In the present embodiment, the design unit library 13 is used for storing the design units and the key identifiers of the design units. The design cell library 13 may provide a data interface for external use, and different technicians may store a plurality of design cells involved in different projects into the design cell library 13. Also, a technician or project administrator can modify a plurality of design units in the design unit library 13, and therefore, each design unit in the design unit library 13 can maintain high freshness. In one implementation scenario, the latest design units may be stored in the design unit library 13.

The design files 17 may be generated by a technician using design software when developing a project. There may be a plurality of design files 17 corresponding to a project, and each design file 17 may contain a number of design elements, such as documentation, common design elements, and the like. After the design file 17 is completed, the design file 17 may be stored in a local storage location corresponding to a technician, or may be stored in a common storage location, for example, different technicians may store the design files 17 related to different projects in the same material library, for example, the technicians may store the design files 17 related to the same project in a local computer used by the technicians, which is not limited in this embodiment. No matter where the design file 17 is stored, when the design file 17 needs to be updated in batch, the data updating method provided by the present embodiment can be adopted. That is, at least one design file 17 determined according to other storage locations, other storage quantities, or other storage rules may be the object of performing the batch update according to the embodiment of the present application.

In the present embodiment, the client 11 is used to provide a user interaction function and may notify the server 12 of a user demand. The client 11 may have applications or program code, etc. installed thereon, and execution of these applications or program code, etc. by the client 11 may provide a user interface and generate an update request.

Fig. 1a is a schematic diagram of an interaction interface of a client according to an embodiment of the present disclosure. As shown in fig. 1a, the client 11 may display an operation interface (the left view in fig. 1 a) in response to the operation interface access request, where the operation interface includes an update trigger control. According to the usage requirement, there may be a plurality of update trigger controls, for example, 2 update trigger controls in fig. 1a, which are a document synchronization control 111 and a general design component synchronization control 112 respectively. In other scenarios, the number of the update trigger controls may also be 1, for example, the update trigger control may be a design unit synchronization control. Of course, the update trigger control may be set to other numbers, which is not limited in this embodiment.

Next, the client 11 may respond to the trigger operation of the update trigger control, and display an information input interface (the right view in fig. 1 a), where the information input interface includes an information input control 113; and acquiring the key identification of the design unit to be updated in response to the information input operation on the information input interface. The information input interface may provide an information entry area or an information list that may be selected by a technician, and may also provide other input forms, which is not limited in this embodiment. The technician may type or click information on the design unit to be updated in the information input interface, for example, directly type a key identifier of the design unit to be updated, or by typing information such as a content keyword of the design unit to be updated, retrieve a list of information and finally select the design unit to be updated, and so on. According to the information input operation of the technician, the client 11 can acquire the key identifier of the design unit that needs to be updated. For convenience of description, hereinafter, the key identification of the design unit that needs to be updated is described as the target key identification.

It should be noted that fig. 1a only illustrates an interactive interface of the client 11, and should not be taken as a specific limitation to the interactive interface of the client 11 in this embodiment. According to different use requirements, the interactive interface of the client 11 may be changed, the display layout of the update trigger control in the interactive interface may be adjusted according to the use requirements, the display order of the information input interface and the operation interface may also be adjusted, and the layout or display order of other elements in the interactive interface may also be adjusted according to the use requirements.

After obtaining the target key identifier according to the information input operation of the technician, the client 11 may send the server 12 the target key identifier carried in the update request.

For the server 12, when receiving an update request sent by the client 11, the design unit to be updated corresponding to the target key identifier may be obtained from the design unit library 13 according to the target key identifier carried in the update request; and determining at least one design file to be updated corresponding to the target key identifier according to the key identifiers of the design units contained in the at least one design file 17, and updating the design units to be updated into the at least one design file to be updated.

As previously described, at least one design file 17 may be stored in the material library 14, or may be stored in another storage location. Hereinafter, the technical solution of the present embodiment will be described by taking the material library 14 as an example. It should be understood that the storage location of the at least one design file 17 in the present embodiment is not limited to the material library 14.

Fig. 2 is a schematic structural diagram of another data updating system according to an embodiment of the present application. In fig. 2, a schematic diagram of a structure of the data update system is shown, taking as an example that at least one design file 17 is stored in the material library 14. Accordingly, the server 12 will communicate with the client 11, the design unit library 13, and the material library 14, respectively.

After the server 12 receives the update request sent by the client 11, on one hand, the design unit to be updated corresponding to the target key identifier in the design unit library 13 can be searched according to the target key identifier carried in the update request, and the design unit to be updated corresponding to the target key identifier is obtained from the design unit library 13. On the other hand, the server 12 may update the unit to be updated acquired from the unit to be designed library 13 to at least one file to be updated in the material library 14 in a batch manner.

The server 12 may determine a design unit corresponding to the target key identifier according to the target key identifier and the key identifier of each design unit included in each design file 17 in the material library 14, and determine the design file 17 including the design unit corresponding to the target key identifier as a design file to be updated, where the number of the design files to be updated may be multiple.

In the process that the server 12 updates the design units to be updated to at least one design file to be updated in batch, the design units to be updated may be written into the design file to be updated by the server 12, or a plug-in may be set in a storage location of the design file to be updated or the file to be updated may be loaded in the design software, and the server 12 triggers the plug-in or the design software to perform an operation of writing the design units to be updated into the design file to be updated. This embodiment is not limited to this.

In the embodiment of the present application, based on the key identifier of each design unit, an association relationship between each design unit included in at least one design file and each design unit in the design unit library may be formed. When an update triggering event occurs, the needed design units to be updated can be obtained from the design unit library according to the key identifiers of the design units to be updated, at least one design file to be updated is determined according to the key identifiers of the design units to be updated, and the design units to be updated are updated to the at least one design file to be updated in batches. Therefore, in the embodiment of the application, batch updating of a plurality of design files can be realized, the updating efficiency of the design files is effectively improved, and the updating accuracy and comprehensiveness can be ensured.

In the above or below embodiments, for each design file to be updated, the server 12 may determine, according to the location identifier of each design unit included in the design file to be updated, a location of the design unit corresponding to the target key identifier in the design file to be updated as a location of the design unit to be updated in the design file to be updated; and updating the design unit to be updated into the design file to be updated according to the position of the design unit to be updated in the design file to be updated.

In this embodiment, each design unit in the design file to be updated has a key identifier and a location identifier. The design unit corresponding to the target key identifier in the design file to be updated can be used as the design unit to be updated according to the key identifier of each design unit in the design file to be updated, the position of each design unit in the design file to be updated can be determined according to the position identifier of each design unit contained in the design file to be updated, and the position of the design unit to be updated can be used as the position of the design unit to be updated in the design file to be updated. Accordingly, when performing the update of the design file to be updated, the server 12 can directly update the design unit to be updated to the position of the design unit to be updated according to the position of the design unit to be updated in the design file to be updated.

For the server 12, after determining each design file to be updated, the position of the design unit to be updated in each design file to be updated can be quickly determined based on the position identifier of each design unit in each design file to be updated, and according to the position of the design unit to be updated in each design file to be updated, each design file to be updated can be accurately updated in batch, so that the updating efficiency is effectively improved.

It should be noted that the server 12 may also update each design file to be updated in other manners. For example, each design unit in the design file to be updated may be traversed according to the target key identifier, and when traversing to a design file corresponding to the target key identifier in the design file to be updated, the operation of updating the design unit to be updated to the design file to be updated may be performed. This embodiment is not limited to this.

In the above or below embodiments, in order to facilitate the server 12 to determine the position of the design unit needing to be updated in the at least one design file to be updated and the at least one design file to be updated corresponding to the target key identifier, the server 12 may initialize the identifier of the at least one design file 17 in the material library 14.

In this embodiment, the server 12 may add a key identifier to each design unit included in each design file 17 based on the key identifier of each design unit in the design unit library 13, and may also add a position identifier to each design unit according to the position of each design unit included in each design file 17. Where the key identifies the content of the design element and the location identification identifies the location of the design element in the design file 17.

As described above, the design unit library 13 stores at least one design unit and a key identifier of the design unit, and the server 12 may add the key identifier to each design unit included in each design file 17 in the material library 14 based on the key identifier of each design unit in the design unit library 13, so that the key identifier of each design unit included in each design file 17 in the material library 14 is consistent with the key identifier of each design unit in the design unit library 13. Accordingly, on the one hand, the server 12 can quickly locate the design unit to be updated in the design unit library 13 corresponding to the target key identifier according to the target key identifier, and on the other hand, the server 12 can determine the design unit corresponding to the target key identifier according to the target key identifier and the key identifier of each design unit included in each design file 17 in the material library 14, and determine the design file 17 including the design unit corresponding to the target key identifier as the design file to be updated.

Based on the file structure of the design files 17, the server 12 may add location identifiers to the design units according to the locations of the design units included in each design file 17. For example, when the design file 17 is a sketch file, due to a layering file structure of the sketch file, a corresponding relationship exists between a design unit and a layer, for example, when a design unit a included in a sketch file X is located on a layer 1, the server 12 may add a position identifier "add-layer 1" to the design unit a according to the layer where the design unit a is located. Of course, the design files 17 may also adopt other file structures, and the server 12 may add location identifiers to the design units according to the locations of the design units included in each design file 17 in different file structures.

In the present embodiment, by performing the identification initialization on at least one design file 17 in the material library 14, the correspondence between at least one design file 17 in the material library 14 and each design unit in the design unit library 13 can be formed based on the key identification and the position identification of each design unit. The server 12 may obtain the to-be-updated design unit corresponding to the target key identifier according to the invisible correspondence, determine at least one to-be-updated design file corresponding to the target key identifier in the material library 14, and locate a position of the to-be-updated design unit in the at least one to-be-updated design file. Thereby enabling a synchronized update of at least one design file to be updated.

In the above or below embodiment, the server 12 may further add a group identification to each design file 17 according to the group to which each design file 17 belongs when initializing the identification of at least one design file 17 in the material library 14. Wherein the design files 17 can be grouped according to the dimensions of the business, the project, etc. One design file 17 may be affiliated with different groups, i.e. each design file 17 may carry a plurality of group identifications. For example, when grouping is performed according to service dimensions, the design file A belongs to a service 1 group; in the range of the service 1 group, when grouping is performed according to the item dimension, the design file a is used for the item 2 group, and meanwhile, the design file 17A is also used for the item 3 group, at this time, the grouping identifiers carried by the design file a can be 3, which are respectively a "service 1 group", a "service 1-item 2 group", and a "service 1-item 3 group"; when grouping is carried out according to the service dimension, the design file B belongs to the service 1 group; in the scope of the service 1 group, when grouping is performed according to the item dimension, the design file B is used for the item 1 group, and meanwhile, the design file B is also used for the item 2 group, at this time, the grouping identifiers carried by the design file a can be 3, which are respectively the "service 1 group", the "service 1-item 1 group", and the "service 1-item 2 group"

Accordingly, the server 12 can determine the design file group corresponding to the group identifier according to the group identifier corresponding to the target key identifier, wherein the group identifier corresponding to the target key identifier can be carried in the update request sent by the client 11. Bearing the above example, when the group identifier corresponding to the target key identifier is "service 1-item 2 group", it may be determined that the design file group formed by all the design files 17 carrying the group identifier is present, where the design file a and the design file B in the above example both belong to the design file group.

After determining the design file group corresponding to the grouping identifier, the server 12 may determine the design file to be updated from the design file group according to the target key identifier. That is, the server 12 selects at least one design file to be updated corresponding to the target key identifier from the design file group.

In the embodiment, the design files belonging to different groups are isolated through the group identifiers, and when the design files are updated, the updating range can be flexibly selected according to different updating requirements, so that the updating efficiency of the design files can be further improved. Especially for the update scene requiring only updating the design units in the specific group, the update method provided by the embodiment can effectively meet the update requirement, and avoid unnecessary updating of the design files outside the specific group.

In the above or below embodiments, the design unit may include a literature and/or a general design component. The document refers to a text portion in the design document 17. The common design component refers to some common design elements in the design document 17, such as colors, fonts, font sizes, and the like. Each design file 17 may include at least one copy and/or at least one generic design component. For management, as shown in fig. 2, the design unit library 13 may include a document library 15 and a component library 16, wherein the document library 15 is used for storing at least one document and a key identifier of the document, and the component library 16 is used for storing at least one general design component and a key identifier of the general design component.

In this embodiment, the server 12 may obtain the document to be updated corresponding to the target key identifier from the document library 15; and/or, obtaining the universal design component to be updated corresponding to the target key identifier from the component library 16. In some update scenarios, only a certain document/documents need to be updated, and in such scenarios, the server 12 may only interact with the document library 15 and obtain the document to be updated corresponding to the target key identifier. In other update scenarios, the server 12 may interact with the component library 16 only, or may interact with both the document library 15 and the component library 16.

In some update scenarios, there may be multiple language versions corresponding to each case. Accordingly, the document library 15 stores documents corresponding to the key identifier of the document, at least one language value associated with the key identifier of the document, and at least one language value associated with the key identifier of the document. For example, for the case a, which corresponds to three language versions of chinese, english and french, the key identifier of the case a is associated with three language values, which correspond to three languages of chinese, english and french, respectively, and accordingly, the case library 15 stores the cases a of the three language versions, i.e., the case a of chinese, english and french, which correspond to the three language values associated with the key identifier of the case a, respectively.

For such an update scenario, the server 12 may obtain, from the document library 15, documents to be updated corresponding to at least one language value associated with the target key identifier according to the at least one language value associated with the target key identifier. Accordingly, for the target key identifier, the server 12 may obtain the documents to be updated of the plurality of language versions corresponding to the documents to be updated from the document library 15. In the above example, when the target key identifier is the key identifier of the case a, the server 12 may obtain the case to be updated in the three language versions of the chinese case a, the english case a, and the french case a from the case.

For example, the length of the documents in different languages may be different, and the length of the documents converted according to the currency exchange rate for the same amount of money in different languages may be different, which may cause different visual effects of the documents in different languages in the design file 17, and may cause problems such as line changing, line cutting, page breaking, or empty skylight.

In an alternative implementation manner, to improve the influence of the style difference between the documents of different language versions on the visual effect of the design file 17, the server 12 may determine whether the at least one language value associated with the target key identifier includes a preset language value before updating the design unit to be updated into the at least one design file to be updated according to the position of the design unit to be updated in the at least one design file to be updated. The preset language value can be one or more, and the preset language value can be modified according to different updating scenes. The server 12 may perform different operations according to different determination results.

When the at least one language value associated with the target key identifier does not include the predetermined language value, the server 12 may perform an operation of updating the document to be updated into the at least one design file to be updated according to the position of the design unit to be updated in the at least one design file to be updated.

When at least one language value associated with the target key identifier contains a preset language value, the server 12 may send the to-be-updated document corresponding to the preset language value to the client 11, aiming at the to-be-updated document corresponding to the preset language value; for the to-be-updated document corresponding to the non-predetermined language value, the server 12 may perform an operation of updating the to-be-updated document corresponding to the non-predetermined language value into at least one design file to be updated.

In addition, in this implementation manner, regardless of whether the at least one language value associated with the target key identifier includes the preset language value, the server may perform an operation of updating the to-be-updated general design component into the at least one to-be-updated design file.

In this implementation manner, for the client 11, the to-be-updated document corresponding to the preset language value associated with the target key identifier and sent by the server 12 may be received; displaying the file to be updated through a preview interface; and responding to the modification operation of the file to be updated, and updating the modified file to be updated into at least one design file to be updated corresponding to the target key identification.

For the to-be-updated document corresponding to each preset language value associated with the target key identifier, when the client 11 displays the to-be-updated document through a preview interface, the to-be-updated document may be displayed in the effect diagram of the to-be-updated design file corresponding to the target key identifier. The client 11 can adjust the language variable value of the document corresponding to the target key identifier in the design file to be updated to be displayed to be consistent with the preset language value according to the preset language value corresponding to the document to be updated. Accordingly, when the client 11 displays the effect graph of the design file to be updated through the preview interface, the document to be updated corresponding to the language variable value can be retrieved according to the adjusted language variable value of the relevant document in the design file to be updated, that is, the document to be updated corresponding to the preset language value can be retrieved, and the document to be updated is displayed in the effect graph of the design file to be updated.

The designer can modify the to-be-updated document in the preview interface to meet the design effect requirement, and the client 11 can store the modified to-be-updated document and update the modified to-be-updated document into the corresponding to-be-updated file.

It should be noted that the to-be-updated document corresponding to each preset language value associated with the target key identifier may correspond to at least one to-be-updated design file, and when there are a plurality of to-be-updated design files, the client 11 may display the plurality of to-be-updated design files in sequence through the preview interface. In one display mode, after the designer finishes modifying the to-be-updated document corresponding to the preset language type value in the currently displayed to-be-updated document, the next to-be-displayed to-be-updated document can be continuously displayed. In another way, the client 11 may also display a plurality of design files to be updated at the same time. Of course, the client 11 also adopts other sequences or other rules to display a plurality of design files to be updated, which is not limited in this embodiment.

In this implementation manner, for the to-be-updated documents corresponding to the non-preset language value, the server 12 may still perform batch update operations on the related to-be-updated documents, and for the to-be-updated documents corresponding to the preset language value, the client 11 may preview and modify the to-be-updated documents corresponding to the preset language value, and individually update at least one to-be-updated design document related to the to-be-updated documents corresponding to the preset language value, so as to solve the problems of line changing, truncation, page breaking, or empty skylight caused by the pattern difference between the documents of different language versions, and effectively improve the display effect of the documents of various language versions in the design document 17.

In the above or below embodiments, the implementation manner in which the server 12 determines the key identifier of the design unit that needs to be updated as the target key identifier may be implemented in addition to the implementation manner in which the client 11 generates the update request in the foregoing embodiments and the server 12 obtains the key identifier of the design unit that needs to be updated from the update request as the target key identifier.

In an alternative implementation manner, the server 12 may receive an update notification sent by the design unit library 13, and obtain the key identifier of the design unit where the update occurs from the update notification as the target key identifier.

In the present implementation, the design unit library 13 may generate an update notification according to the update condition of the design unit stored thereon. Due to various reasons such as upgrading of the project, a designer or a user such as a project supervisor who has authority to access the design unit library may modify the design units in the design unit library, which may result in updating the design units in the design unit library. When the design units stored in the design unit library are updated, the design unit library 13 may carry the key identifier corresponding to the updated design unit in an update notification and send the update notification to the server 12, and the server 12 may obtain the key identifier of the updated design unit from the update notification sent by the design unit library 13 as the target key identifier. And the server 12 may obtain the design unit to be updated corresponding to the target key identifier from the design unit library according to the trigger of the update notification, and update the design unit to be updated to at least one design file to be updated corresponding to the target key identifier.

In another alternative implementation manner, the server 12 may also periodically compare the version information of each design unit contained in each design file 17 with the version information of the design unit contained in the design unit library 13, and obtain the key identifier of the design unit with inconsistent version information as the target key identifier.

In this implementation, the server 12 may add version information to each design unit included in each design file 17 during initialization, and when each design file 17 is updated, the server 12 may update each design unit added version information included in each design file 17. Each design unit in the design unit library 13 also carries version information. The version information of each design unit included in each design file 17 is in accordance with the definition rule of the version information of each design unit in the design unit library 13. Thus, the version information may reflect the similarities and differences between each design unit in each design file 17 and each design unit in the design unit library. Accordingly, the server can judge whether each design unit in each design file needs to be updated according to the version information.

In order to automatically determine whether or not each design element in each design file needs to be updated, the server 12 may periodically compare the version information of each design element included in each design file 17 with the version information of each design element included in the design element library 13, and if the comparison result indicates that the version information does not match for the same design element, specify that the design element included in each design file 17 is a design element that needs to be updated. The server 12 may use the key identifier of the design unit as a target key identifier, then obtain a design unit to be updated corresponding to the target key identifier from the design unit library, and update the design unit to be updated into at least one design file to be updated corresponding to the target key identifier. In this way, the server may automatically update the at least one design file 17 without the need for a designer to manually trigger the update.

In the present embodiment, by implementing a manner in which the design unit library 13 transmits an update notification or the server 12 periodically polls the version information of the design units in the design unit library 13, batch automatic update of the design files 17 can be realized. So that the freshness of each design file 17 can be effectively ensured.

It should be noted that the above-mentioned several implementations of determining, by the server 12, the key identifier of the design unit that needs to be updated as the target key identifier may be implemented individually or in combination. For example, the server 12 may initiate a periodic polling implementation to determine the key identifier of the design unit that needs to be updated as the target key identifier when the interval duration of the last update request sent by the client 11 reaches a predetermined duration, but of course, other possible combination implementations may also be adopted, and are not exhaustive here.

Fig. 3 is a flowchart illustrating a data updating method according to another embodiment of the present application. The method is suitable for a server in a data updating system, and as shown in fig. 3, the method comprises the following steps:

300. in response to an update triggering event, determining a key identifier of a design unit needing to be updated as a target key identifier;

301. acquiring a design unit to be updated corresponding to the target key identification from a design unit library;

302. determining at least one design file to be updated corresponding to the target key identification according to the key identification of each design unit contained in at least one design file;

303. and updating the design unit to be updated into at least one design file to be updated.

In this embodiment, the design unit that needs to be updated may be determined according to the update triggering event, and the key identifier of the design unit that needs to be updated may be used as the target key identifier. The method comprises the following steps that a key identifier of a design unit needing to be updated is determined to serve as a target key identifier, in one optional implementation mode, an updating request sent by a client can be received, the key identifier of the design unit needing to be updated is obtained from the updating request to serve as the target key identifier, in the other optional implementation mode, an updating notice sent by a design unit library can be received, and the key identifier of the design unit needing to be updated is obtained from the updating notice to serve as the target key identifier; in another alternative implementation manner, the version information of each design unit included in each design file may be periodically compared with the version information of each design unit included in the design unit library, and the key identifier of the design unit with inconsistent version information is obtained as the target key identifier.

It should be noted that several implementations of determining the key identifier of the design unit needing to be updated as the target key identifier may be implemented individually or in combination. For example, when the interval duration from the last update request sent by the client reaches a predetermined duration, a regular polling implementation may be initiated to determine the key identifier of the design unit that needs to be updated as the target key identifier.

Based on the determined target key identification, the design unit to be updated corresponding to the target key identification can be obtained from the design unit library. The design unit library is used for storing the design units and the key identifications of the design units. The design unit library can provide a data interface for external use, and different technicians can store a plurality of design units related to different projects into the design unit library. Moreover, a technician or project administrator can modify a plurality of design units in the design unit library, and thus each design unit in the design unit library can maintain a high degree of freshness. In one implementation scenario, the latest design units may be stored in the library of design units.

After the design unit to be updated corresponding to the target key identifier is obtained, the design unit corresponding to the target key identifier can be determined according to the target key identifier and the key identifier of each design unit contained in each design file in the material library, the design file containing the design unit corresponding to the target key identifier is determined as the design file to be updated, and the number of the design files to be updated can be multiple.

In the above or the following embodiments, step 303 includes: for each design file to be updated, determining the position of the design unit corresponding to the target key identifier in the design file to be updated as the position of the design unit to be updated in the design file to be updated according to the position identifier of each design unit contained in the design file to be updated; and updating the design unit to be updated into the design file to be updated according to the position of the design unit to be updated in the design file to be updated.

In this embodiment, each design unit in the design file to be updated has a key identifier and a location identifier. The design unit corresponding to the target key identifier in the design file to be updated can be used as the design unit to be updated according to the key identifier of each design unit in the design file to be updated, the position of each design unit in the design file to be updated can be determined according to the position identifier of each design unit contained in the design file to be updated, and the position of the design unit to be updated can be used as the position of the design unit to be updated in the design file to be updated. Therefore, when the design file to be updated is updated, the design unit to be updated can be updated to the position directly according to the position of the design unit to be updated in the design file to be updated. The design files to be updated can be accurately updated in batches, and the updating efficiency is effectively improved.

It should be noted that, other methods may also be used to update each design file to be updated. For example, each design unit in the design file to be updated may be traversed according to the target key identifier, and when traversing to a design file corresponding to the target key identifier in the design file to be updated, the operation of updating the design unit to be updated to the design file to be updated may be performed. This embodiment is not limited to this.

In the above or the following embodiments, before the step 302, the method further includes:

based on the key identification of each design unit in the design unit library, adding the key identification to each design unit contained in each design file, and respectively adding the position identification to each design unit according to the position of each design unit contained in each design file.

In this embodiment, a key identifier may be added to each design unit included in each design file based on the key identifier of each design unit in the design unit library, and a location identifier may be added to each design unit according to the location of each design unit included in each design file. Wherein the key identifier is used to identify the content of the design element and the location identifier is used to identify the location of the design element in the design file.

As described above, the design unit library stores at least one design unit and a key identifier of the design unit, and in this embodiment, the key identifier may be added to each design unit included in each design file in the material library based on the key identifier of each design unit in the design unit library, so that the key identifier of each design unit included in each design file in the material library is consistent with the key identifier of each design unit in the design unit library. Therefore, on one hand, the design unit to be updated corresponding to the target key identification in the design unit library can be quickly positioned according to the target key identification, on the other hand, the design unit corresponding to the target key identification can be determined according to the target key identification and the key identification of each design unit contained in each design file in the material library, and the design file containing the design unit corresponding to the target key identification is determined as the design file to be updated.

Based on the file structure of the design file, position marks can be added to the design units according to the positions of the design units contained in each design file. For example, when the design file is a sketch file, due to a layering file structure of the sketch file, a corresponding relationship exists between the design unit and the layer, for example, when the design unit a included in the sketch file X is located on the layer 1, the position identifier "add-layer 1" may be added to the design unit a according to the layer where the design unit a is located. Of course, the design file may also adopt other file structures, and the position identifier may be added to each design unit according to the position of each design unit included in each design file in different file structures.

In this embodiment, by initializing the identifier of at least one design file in the material library, the correspondence between the at least one design file in the material library and each design unit in the design unit library can be formed based on the key identifier and the position identifier of each design unit. According to the invisible corresponding relation, the design unit to be updated corresponding to the target key identification can be obtained, at least one design file to be updated corresponding to the target key identification is determined in the material library, and the position of the design unit to be updated in the at least one design file to be updated is located. Thereby enabling a synchronized update of at least one design file to be updated.

In the above or the following embodiments, step 302 may include:

determining a design file group corresponding to the grouping identification according to the grouping identification corresponding to the target key identification;

and determining at least one design file to be updated corresponding to the target key identification from the design file group according to the target key identification and the key identification of each design unit in the design file group.

In this embodiment, when initializing the identifier of at least one design file, a group identifier may be added to each design file according to the group to which each design file belongs. The design files can be grouped according to the dimensions of services, projects and the like. One design file may be affiliated with different groups, i.e., each design file may carry multiple group identifications. For example, when grouping is performed according to service dimensions, the design file A belongs to a service 1 group; in the range of a service 1 group, when grouping is performed according to project dimensions, a design file A is used for a project 2 group, and simultaneously, the design file A is also used for a project 3 group, at the moment, the grouping identifiers carried by the design file A can be 3, namely, a service 1 group, a service 1-project 2 group and a service 1-project 3 group; when grouping is carried out according to the service dimension, the design file B belongs to the service 1 group; in the scope of the service 1 group, when grouping is performed according to the item dimension, the design file B is used for the item 1 group, and meanwhile, the design file B is also used for the item 2 group, at this time, the grouping identifiers carried by the design file a can be 3, which are respectively the "service 1 group", the "service 1-item 1 group", and the "service 1-item 2 group"

Accordingly, the design file group corresponding to the grouping identifier can be determined according to the grouping identifier corresponding to the target key identifier, wherein the grouping identifier corresponding to the target key identifier can be carried in the updating request sent by the client. Bearing the above example, when the group identifier corresponding to the target key identifier is "service 1-item 2 group", it may be determined that the design file group formed by all the design files carrying the group identifier is formed, where the design file a and the design file B in the above example both belong to the design file group.

After the design file group corresponding to the grouping identification is determined, the design file to be updated can be determined from the design file group according to the target key identification and the key identification of each design unit in the design file group. That is, at least one design file to be updated corresponding to the target key identifier may be selected from the design file group.

In the above or below embodiments, the design unit may include a literature and/or a general design component. The text refers to the text portion of the design document. The common design component refers to some common design elements in the design document, such as color, font size, and the like. Each design file may include at least one copy and/or at least one generic design component. For management, as shown in fig. 2, the design unit library may include a document library and a component library, wherein the document library stores at least one document and a key identifier of the document, and the component library is used for at least one general design component and a key identifier of the general design component.

In this embodiment, step 301 may include:

the file to be updated corresponding to the target key identification can be obtained from the file library; and/or acquiring the universal design component to be updated corresponding to the target key identification from the component library.

The steps in the above embodiments are further described below by taking the design units that need to be updated as examples.

In some update scenarios, each document may correspond to multiple language versions, and the styles of the documents will be different in different languages, for example, the lengths of the documents in different languages may be different, and the lengths of the documents converted from the currency exchange rate in different languages for the same amount of money may be different, which will cause different visual effects of the documents in different languages in the design file. For example, problems such as line feed, truncation, page breakage, or empty skylights may occur.

Fig. 4 is a schematic flowchart of another data updating method according to another embodiment of the present application. Wherein, for the convenience of description, each step in fig. 4 only relates to the updating process of the file. It should be understood that the update process of the general design component can be implemented as described in the foregoing embodiment for the update process of the design unit. As shown in fig. 4, the method includes:

400. in response to an update triggering event, determining a key identifier of a file needing to be updated as a target key identifier;

401. acquiring a to-be-updated file corresponding to at least one language value associated with the target key identifier from a file library according to the at least one language value associated with the target key identifier;

402. determining at least one design file to be updated corresponding to the target key identification according to the key identification of each file contained in at least one design file;

403. judging whether at least one language value associated with the target key identifier contains a preset language value, if not, executing a step 404; if so, go to step 405;

404. updating the file to be updated into at least one design file to be updated;

405. judging whether the current file to be updated is the file to be updated corresponding to the preset language value, if so, executing step 406; if not, go to step 407;

406. sending the current to-be-updated file to the client so that a designer can modify the current to-be-updated file through the client, and updating at least one to-be-updated design file corresponding to the target key identification of the modified to-be-updated file through the client;

407. and updating the current file to be updated to the at least one design file to be updated according to the position of the design unit to be updated in the at least one design file to be updated.

In step 400-402, reference may be made to the description in the foregoing embodiments, and details are not repeated herein.

In this embodiment, a step of determining whether at least one language value associated with the target key identifier includes a preset language value is added to screen out a file to be updated corresponding to the preset language value. The preset language value can be one or more, and the preset language value can be modified according to different updating scenes. And according to different judgment results, the server can execute different operations.

In this embodiment, for the to-be-updated document corresponding to the non-predetermined language value, the batch update operation may still be directly performed on the related to-be-updated file, and for the to-be-updated document corresponding to the predetermined language value, the preview and modification of the to-be-updated document corresponding to the predetermined language value may be performed through the client, and the personalized update may be performed on at least one to-be-updated design file related to the to-be-updated document corresponding to the predetermined language value, so as to solve the problems of line change, line truncation, page breakage, or empty skylight and the like caused by the pattern difference between the documents of different language versions, and effectively improve the display effect of the documents of various language versions in the design file.

Fig. 5 is a flowchart illustrating a data updating method according to another embodiment of the present application. The method is applied to a client in a data updating system, and as shown in fig. 5, the method includes:

500. responding to an operation interface access request, and displaying an operation interface which comprises an updating triggering control;

501. responding to the trigger operation of the updating trigger control, and displaying an information input interface;

502. and responding to the information input operation on the information input interface, and acquiring a key identifier of the design unit needing to be updated as a target key identifier, wherein the target key identifier is used for determining at least one design file to be updated.

In this embodiment, an operation interface may be displayed in response to an operation interface access request, where the operation interface includes an update trigger control. According to the use requirement, there may be a plurality of update trigger controls, for example, 2 update trigger controls in fig. 2, which are a document synchronization control and a general design component synchronization control, respectively. In other scenarios, the number of the update trigger controls may also be 1, for example, the update trigger control may be a design unit synchronization control. Of course, the update trigger control may be set to other numbers, which is not limited in this embodiment.

Next, an information input interface can be displayed in response to the trigger operation of the updating trigger control; and acquiring the key identification of the design unit to be updated in response to the information input operation on the information input interface. The information input interface may provide an information entry area or an information list that may be selected by a technician, and may also provide other input forms, which is not limited in this embodiment. The technician may type or click information on the design unit to be updated in the information input interface, for example, directly type a key identifier of the design unit to be updated, or by typing information such as a content keyword of the design unit to be updated, retrieve a list of information and finally select the design unit to be updated, and so on. According to the information input operation of the technician, the key identifier of the design unit to be updated can be acquired. For convenience of description, hereinafter, the key identification of the design unit that needs to be updated is described as the target key identification.

It should be noted that fig. 2 only illustrates an interactive interface of the client, and should not be taken as a specific limitation to the interactive interface of the client in this embodiment. According to different use requirements, the interactive interface in the embodiment may be changed, the display layout of the update triggering control in the interactive interface may be adjusted according to the use requirements, the display order of the information input interface and the operation interface may also be adjusted, and the layout or the display order of other elements in the interactive interface may also be adjusted according to the use requirements.

After the target key identifier is obtained according to the information input operation of the technician, the target key identifier can be carried in the update request and sent to the server.

Fig. 6 is a flowchart illustrating another data updating method according to another embodiment of the present application. As shown in fig. 6, the method includes:

600. responding to an operation interface access request, and displaying an operation interface which comprises an updating triggering control;

601. responding to the trigger operation of the updating trigger control, and displaying an information input interface;

602. responding to information input operation on an information input interface, acquiring a key identifier of a design unit needing to be updated as a target key identifier, carrying the target key identifier in an update request, and sending the update request to a server so that the server can update a corresponding design unit in at least one design file to be updated, wherein the design file comprises the target key identifier;

603. receiving a to-be-updated file corresponding to a preset language value associated with the target key identifier and sent by the server;

604. displaying the file to be updated through a preview interface;

605. and responding to the modification operation of the file to be updated, and updating the modified file to be updated into at least one design file to be updated corresponding to the target key identification.

In step 600-602, reference may be made to the description in the foregoing embodiments, and details are not repeated herein.

In this embodiment, when the design unit to be updated includes the document corresponding to the predetermined language value, the document to be updated corresponding to the predetermined language may be displayed through a preview interface. Optionally, the to-be-updated file is displayed in an effect drawing of the to-be-updated design file corresponding to the target key identifier. The language variable value of the document corresponding to the target key identifier in the design file to be updated to be displayed can be adjusted to be consistent with the preset language value according to the preset language value corresponding to the document to be updated. Therefore, when the effect graph of the design file to be updated is displayed through the preview interface, the file to be updated corresponding to the language variable value can be called according to the adjusted language variable value of the related file in the design file to be updated, namely, the file to be updated corresponding to the preset language value can be called, and the file to be updated is displayed in the effect graph of the design file to be updated.

The designer can modify the file to be updated in the preview interface to meet the design effect requirement. In this embodiment, the modified to-be-updated document can be saved, and the modified to-be-updated document is updated to the corresponding to-be-updated file.

It should be noted that the to-be-updated document corresponding to each preset language value associated with the target key identifier may correspond to at least one to-be-updated design file, and when there are a plurality of to-be-updated design files, the plurality of to-be-updated design files may be sequentially displayed through the preview interface. In one display mode, after the designer finishes modifying the to-be-updated document corresponding to the preset language type value in the currently displayed to-be-updated document, the next to-be-displayed to-be-updated document can be continuously displayed. In another presentation mode, the client may also present a plurality of design files to be updated at the same time. Of course, other sequences or other rules are also adopted to display the plurality of design files to be updated, which is not limited in this embodiment.

In this implementation manner, for the to-be-updated documents corresponding to the non-predetermined language value, the server may still perform batch update operations on the related to-be-updated documents, and for the to-be-updated documents corresponding to the predetermined language value, the technical solution provided in this embodiment may perform preview and modification on the to-be-updated documents corresponding to the predetermined language value, and perform personalized update on at least one to-be-updated design document related to the to-be-updated documents corresponding to the predetermined language value, so as to solve the problems of line change, truncation, page breakage, empty skylight, and the like caused by the pattern difference between the documents of different language versions, and effectively improve the display effect of the documents of various language versions in the design documents.

Fig. 7 is a schematic structural diagram of a server according to another embodiment of the present application. As shown in fig. 7, the server includes: a memory 70 and a processor 71.

The memory 70 is used to store computer programs and may be configured to store various other data to support operations on the master node. Examples of such data include instructions for any application or method operating on the master node, contact data, phonebook data, messages, pictures, videos, and the like.

The memory 70 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.

A processor 71, coupled to the memory 70, for executing computer programs in the memory 70 for:

and updating the design unit to be updated into at least one design file to be updated.

In an alternative embodiment, the processor 71, when updating the design unit to be updated into the at least one design file to be updated, is configured to:

for each design file to be updated, determining the position of the design unit corresponding to the target key identifier in the design file to be updated as the position of the design unit to be updated in the design file to be updated according to the position identifier of each design unit contained in the design file to be updated;

and updating the design unit to be updated into the design file to be updated according to the position of the design unit to be updated in the design file to be updated.

In an optional embodiment, before determining, according to the location identifier of each design unit included in the design file to be updated, the location of the design unit corresponding to the target key identifier in the design file to be updated as the location of the design unit needing to be updated in the design file to be updated, the processor 71 is further configured to:

and respectively adding position marks for the design units according to the positions of the design units contained in each design file.

In an alternative embodiment, before determining at least one design file to be updated corresponding to the target key identifier according to the key identifier of each design unit contained in at least one design file, the processor 71 is further configured to:

and adding key identifications to each design unit contained in each design file based on the key identifications of each design unit in the design unit library.

In an alternative embodiment, the processor 71, when determining at least one design file to be updated corresponding to the target key identifier according to the key identifier of each design unit contained in at least one design file, is configured to:

In an alternative embodiment, the processor 71, when obtaining the design unit to be updated corresponding to the target key identifier from the design unit library, is configured to:

acquiring a to-be-updated file corresponding to the target key identification from a file library; and/or the presence of a gas in the gas,

and acquiring the universal design component to be updated corresponding to the target key identification from the component library.

In an alternative embodiment, the processor 71, when obtaining the document to be updated corresponding to the target key identifier from the document library, is further configured to:

and acquiring the to-be-updated file corresponding to the at least one language value associated with the target key identifier from the file library according to the at least one language value associated with the target key identifier.

In an optional embodiment, the processor 71, before updating the design unit to be updated into the at least one design file to be updated according to the position of the design unit to be updated in the at least one design file to be updated, is further configured to:

judging whether at least one language value associated with the target key identifier contains a preset language value or not;

and when the at least one language value associated with the target key identifier does not contain the preset language value, executing the operation of updating the file to be updated into the at least one design file to be updated according to the position of the design unit to be updated in the at least one design file to be updated.

In an alternative embodiment, processor 71 is further configured to:

when at least one language value associated with the target key identifier contains a preset language value, aiming at a to-be-updated case corresponding to the preset language value, sending the to-be-updated case corresponding to the preset language value to a client, so that a designer can modify the to-be-updated case corresponding to the preset language value through the client and update at least one to-be-updated design file corresponding to the target key identifier on the to-be-updated case corresponding to the modified preset language value through the client;

and aiming at the to-be-updated file corresponding to the non-preset language value, executing the operation of updating the to-be-updated file corresponding to the non-preset language value into the at least one to-be-updated design file according to the position of the design unit needing to be updated in the at least one to-be-updated design file.

In an optional embodiment, the server further comprises: the communication component 72 is primarily responsible for communication between the server and other devices. Based on this, the processor 71, when determining that the key identifier of the design unit that needs to be updated is the target key identifier in response to the update triggering event, is configured to:

receiving an update request sent by a client through the communication component 72, and acquiring a key identifier of a design unit needing to be updated from the update request as a target key identifier; or

Receiving an update notification sent by the design unit library through the communication component 72, and acquiring a key identifier of the design unit where the update occurs from the update notification as a target key identifier; or

And regularly comparing the version information of each design unit contained in each design file with the version information of each design unit contained in the design unit library, and acquiring the key identifier of the design unit with inconsistent version information as the target key identifier.

Further, as shown in fig. 7, the server may further include: power supply components 73, and the like. Only some of the components are schematically shown in fig. 7, and it is not meant that the server includes only the components shown in fig. 7.

Accordingly, the present application further provides a computer-readable storage medium storing a computer program, where the computer program can implement the steps that can be executed by the server in the foregoing method embodiments when executed.

Fig. 8 is a schematic structural diagram of a client according to yet another embodiment of the present application. The client comprises: memory 80, processor 81, display 82, and communication component 83.

The memory 80 is used to store computer programs and may be configured to store other various data to support operations on the management device. Examples of such data include instructions for any application or method operating on the master node, contact data, phonebook data, messages, pictures, videos, and the like.

The memory 80 may be implemented by any type or combination of volatile or non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.

A processor 81, coupled to the memory 80, for executing the computer program in the memory 80 for:

responding to an operation interface access request, displaying an operation interface through the display 82, wherein the operation interface comprises an updating triggering control;

in response to the trigger operation of updating the trigger control, an information input interface is displayed through the display 82;

In an optional embodiment, the design unit to be updated includes a pattern corresponding to a predetermined language value; processor 81 is also configured to:

receiving a to-be-updated file corresponding to the preset language value associated with the target key identifier sent by the server through the communication component 83;

displaying the file to be updated through a preview interface;

and responding to the modification operation of the file to be updated, and updating the modified file to be updated into at least one design file to be updated corresponding to the target key identification.

Further, as shown in fig. 8, the client may further include: power components 84, audio components 85, and the like. Only some of the components are schematically shown in fig. 8, and the client is not meant to include only the components shown in fig. 8.

Accordingly, the present application further provides a computer-readable storage medium storing a computer program, where the computer program is capable of implementing the steps that can be executed by the client in the foregoing method embodiments when executed.

The communication components of fig. 7 and 8, among other things, may be configured to facilitate wired or wireless communication between the device in which the communication component is located and other devices. The device in which the communication component is located may access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In one embodiment, the communication component receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In one embodiment, the communication component further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

The display in fig. 8 includes a screen, and the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

The power supply components of fig. 7 and 8, among other things, provide power to the various components of the device in which the power supply components are located. The power components may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device in which the power component is located.

The audio component in fig. 8 may be configured to output and/or input an audio signal. For example, the audio component includes a Microphone (MIC) configured to receive an external audio signal when the device in which the audio component is located is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may further be stored in a memory or transmitted via a communication component. In some embodiments, the audio assembly further comprises a speaker for outputting audio signals.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in the process, method, article, or apparatus that comprises the element.

The above are merely examples of the present application and are not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A method for updating data, comprising:

2. The method according to claim 1, wherein the updating the design unit to be updated into the at least one design file to be updated comprises:

3. The method according to claim 2, before determining, for each design file to be updated, a position of the design unit corresponding to the target key identifier in the design file to be updated as a position of the design unit in the design file to be updated, which needs to be updated, according to the position identifier of each design unit included in the design file to be updated, further comprising:

4. The method according to claim 1, before determining at least one design file to be updated corresponding to the target key identifier according to the key identifiers of the design units contained in at least one design file, further comprising:

5. The method according to claim 1, wherein the determining at least one design file to be updated corresponding to the target key identifier according to the key identifier of each design unit contained in at least one design file comprises:

determining a design file group corresponding to a grouping identifier according to the grouping identifier corresponding to the target key identifier;

6. The method of claim 1, wherein the obtaining the design unit to be updated corresponding to the target key identifier from the design unit library comprises:

and acquiring the universal design component to be updated corresponding to the target key identification from a component library.

7. The method of claim 6, wherein the retrieving the document to be updated corresponding to the target key identifier from the document library further comprises:

8. The method of claim 7, wherein before updating the design unit to be updated into the at least one design file to be updated, further comprising:

and when the at least one language value associated with the target key identifier does not contain a preset language value, executing the operation of updating the design unit to be updated into at least one design file to be updated.

9. The method of claim 8, further comprising:

when at least one language value associated with the target key identifier contains a preset language value, aiming at a to-be-updated case corresponding to the preset language value, sending the to-be-updated case corresponding to the preset language value to a client, so that a designer can modify the to-be-updated case corresponding to the preset language value through the client and update the to-be-updated case corresponding to the modified preset language value to at least one to-be-updated design file corresponding to the target key identifier through the client;

and aiming at the to-be-updated file corresponding to the non-preset language value, executing the operation of updating the to-be-updated file corresponding to the non-preset language value into the at least one to-be-updated design file.

10. The method of claim 1, wherein determining the key identifier of the design unit that needs to be updated as the target key identifier in response to the update triggering event comprises:

receiving an updating request sent by a client, and acquiring a key identifier of a design unit needing to be updated from the updating request as a target key identifier; or

Receiving an update notification sent by the design unit library, and acquiring a key identifier of the design unit subjected to update from the update notification as a target key identifier; or

11. A method for updating data, comprising:

12. The method of claim 11, wherein the design unit to be updated includes a document corresponding to a predetermined language value; the method further comprises the following steps:

receiving a to-be-updated file corresponding to the preset language value associated with the target key identifier and sent by the server;

displaying the file to be updated through a preview interface;

and responding to the modification operation of the file to be updated, and updating the modified file to be updated into the at least one design file to be updated corresponding to the target key identifier.

13. A server, comprising a memory and a processor;

the memory to store one or more computer instructions;

14. A client comprising a memory, a processor, a display, and a communications component;

the memory to store one or more computer instructions;

15. A data update system, comprising: the system comprises a client, a server and a design unit library;

the server is used for acquiring a design unit to be updated corresponding to the target key identification from the design unit library according to an update request sent by the client; and determining at least one design file to be updated corresponding to the target key identification according to the key identification of each design unit contained in at least one design file, and updating the design unit to be updated into the at least one design file to be updated.

16. A computer-readable storage medium storing computer instructions, which when executed by one or more processors, cause the one or more processors to perform the data update method of any one of claims 1 to 10.

17. A computer-readable storage medium storing computer instructions, which when executed by one or more processors, cause the one or more processors to perform the data update method of any one of claims 11 to 12.