Editing service platform, interface style preview method, medium and computing device

Abstract

The embodiments disclosed in the specification provide a style preview method of an editing service platform, an interface, a medium and a computing device. The platform comprises: a communication service module, which, in response to a style editing request of a target interface generated by an editing end, creates a session identifier corresponding to the target interface and returns the session identifier to the editing end generating the corresponding style editing request; an editing service module, which generates style data and style data events of the target interface based on at least the style editing data of the target interface generated by the editing end; and a data service module, which, when a style data event of the target interface is listened to, sends the style data corresponding to the target interface to a target preview end, and the target preview end establishes a connection with the platform through the session identifier corresponding to the target interface.

Description

Technical Field

[0001] This specification relates to the field of interface display technology in several embodiments, and in particular to an editing service platform, an interface style preview method, a medium, and a computing device. Background Technology

[0002] In practical applications, software needs to be installed on different types of devices. Therefore, it is necessary to develop a version of the software that is adapted to different types of devices. The adaptation process usually involves editing the interface style of the software's front-end interface, that is, editing the interface style that is suitable for the characteristics of different types of devices (such as mobile devices or in-vehicle devices).

[0003] In existing technologies, developers typically edit the interface style of the front-end interface on a development device (such as a computer), and then display the corresponding front-end interface according to the edited interface style to determine whether the visual effect of the front-end interface meets expectations. Therefore, how to efficiently verify the visual effect of the front-end interface during the adaptation development process is a problem that needs to be solved by those skilled in the art. Summary of the Invention

[0004] A first aspect of several embodiments of this specification provides an editing service platform, wherein the platform includes:

[0005] The communication service module, in response to the style editing request of the target interface generated by the editing terminal, creates a session identifier corresponding to the target interface and returns the session identifier to the editing terminal that generated the corresponding style editing request;

[0006] The editing service module generates style data and style data events for the target interface, based at least on the style editing data of the target interface generated by the editing client.

[0007] When the data service module detects a style data event of the target interface, it sends the style data corresponding to the target interface to the target preview terminal. The target preview terminal establishes a connection with the platform through the session identifier corresponding to the target interface.

[0008] According to a second aspect of several embodiments of this specification, a method for previewing the style of an interface is proposed, applied to an editing service platform, the method comprising:

[0009] In response to a style editing request for the target interface generated by the editing end, a session identifier corresponding to the target interface is created and returned to the editing end that generated the style editing request, so that the target preview end can obtain the session identifier corresponding to the target interface from the editing end, and then the target preview end can establish a connection with the platform through the session identifier;

[0010] Based at least on the style editing data of the target interface generated by the editing end, generate style data and style data events for the target interface;

[0011] When a style data event of the target interface is detected, the style data corresponding to the target interface is sent to the target preview terminal.

[0012] According to a third aspect of several embodiments of this specification, an interface editing system is proposed, comprising: an editing service platform, an editing terminal, and a target preview terminal;

[0013] On the editing end, a style editing request for the target interface is sent to the editing service platform;

[0014] The editing service platform, in response to the style editing request of the target interface generated by the editing terminal, creates a session identifier corresponding to the target interface and returns the session identifier to the editing terminal that generated the corresponding style editing request; at least based on the style editing data of the target interface generated by the editing terminal, it generates style data and style data events for the target interface, and when it listens for the style data event of the target interface, it sends the style data corresponding to the target interface to the target preview terminal;

[0015] The target preview end obtains the session identifier corresponding to the target interface from the editing end, and establishes a connection with the platform through the session identifier.

[0016] According to a fourth aspect of several embodiments of this specification, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the functions of the editing service platform, editing terminal, or target preview terminal in the first aspect embodiment.

[0017] Through the above technical solution, during the adaptation development process, the style editing data of the target interface generated by the developers on the editing end will be uploaded to the editing service platform. The editing service platform will generate the latest style data of the target interface based on the style editing data, and then send the latest style data to the target preview end, so that the developers can use the target preview end to efficiently verify the visual effect of the front-end interface. Attached Figure Description

[0018] Figure 1 An exemplary schematic diagram of the software architecture of an interface editing system is provided.

[0019] Figure 2 This is a schematic diagram of the architecture of an editing service platform provided in this public disclosure.

[0020] Figure 3 This is a flowchart illustrating a method for previewing the style of an interface provided in this publication.

[0021] Figure 4This is a schematic diagram of the structure of a computing device provided in this disclosure.

[0022] In the accompanying drawings, identical or corresponding reference numerals denote identical or corresponding parts. Any number of elements in the drawings is for illustrative purposes only and not for limitation, and any naming is for distinction only and has no limiting meaning. Detailed Implementation

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

[0024] It should be noted that the steps of the corresponding methods are not necessarily performed in the order shown and described in this specification in other embodiments. In some other embodiments, the methods may include more or fewer steps than described in this specification. Furthermore, a single step described in this specification may be broken down into multiple steps in other embodiments; and multiple steps described in this specification may be combined into a single step in other embodiments.

[0025] In this disclosure, the front-end interface refers to the visual interface displayed on the device screen during software runtime. The front-end interface is simply referred to as the interface. For example, the interface can specifically be a graphical user interface (GUI), or it can be an interface including a map (which may be called a map interface). The style of the interface may include, but is not limited to, the styles of interface elements and the layout styles within the interface.

[0026] For example, the interface elements in electronic map service software can include background surfaces, road lines, text labels, etc. The distribution effect of these interface elements in the interface is the interface layout style, and the design effect of each interface element is the interface element style. Specifically, the style of the background surface can be the color and texture of the surface, the style of the road lines can be the width and color of the lines, and the style of the text labels can be the font and font size.

[0027] The development of software interfaces involves editing interface styles. Developers typically edit these styles on devices that facilitate editing (such as PCs), but the types of devices the software needs to support (such as mobile devices and in-vehicle systems) often differ from the devices used by the developers. It should be noted that mobile devices here can include smartphones and tablets, while in-vehicle systems specifically refer to the central control devices in vehicles.

[0028] It's easy to understand that different types of devices often have different screen specifications (screen size, screen resolution, etc.). Therefore, the interface style that developers edit on a specific type of device may not look good on other types of devices. As a result, developers need to preview the visual effects of the edited interface style on other types of devices frequently during the editing process, so as to optimize and adjust the interface style based on the previewed visual effects.

[0029] For ease of description, this document refers to the device used for editing the interface style (i.e., the specific type of device mentioned above) as the editing device; and the device used for actually installing the developed software as the preview device. Editing devices and preview devices are usually different types of devices, and this disclosure can classify the different types of devices according to their screen specifications.

[0030] One feasible technical solution is to install a simulator for the preview device on the editing device, and edit the interface style within the interface displayed in the simulator. The aim is to create an interface style adapted to the preview device and with good visual effects on the editing device without needing to preview element styles on the preview device itself. However, since the editing device and the preview device are different types of devices, although the environment of the preview device can be simulated on the editing device to display the front-end interface, the simulated visual effect of the front-end interface in the simulated environment differs significantly from the real visual effect in the actual environment of the preview device.

[0031] Another feasible technical solution is for developers to copy the interface style data to be previewed from the editing device and then transfer it to the preview device. This allows them to see the visual effect of the edited interface style on the preview device. However, copying and transferring the interface style data is cumbersome for developers and significantly impacts editing efficiency.

[0032] Therefore, in one or more embodiments provided in this disclosure, a software architecture for an interface editing system is provided, such as... Figure 1As shown, the system includes an editing service platform (which can be deployed on one or more servers), at least one editing client (deployed on an editing client device), and at least one target preview client (deployed on a preview client device). In embodiments with at least two editing clients and / or at least two target preview clients, any two editing clients can be deployed on the same or different editing client devices. These editing client devices can be of the same type, such as a PC platform. Any two target preview clients are typically deployed on different preview client devices. These different preview client devices can be of the same type or different types (to preview the visual effect of the same interface style on different types of preview client devices), such as different models of mobile phones or different models of in-vehicle infotainment systems.

[0033] It should be noted that the editing terminal is the software used by developers to edit the style of the interface. Different developers can operate different editing terminals, or multiple developers can operate a single editing terminal.

[0034] A target preview client is a piece of software that displays the visual effects of the interface styles edited by developers. Target preview clients are deployed on preview client devices, and different target preview clients typically need to be deployed on different preview client devices.

[0035] For example, the preview device can include at least one model of mobile device or at least one model of in-vehicle infotainment platform. It's easy to understand that, taking a mobile platform device as an example (the principle of an in-vehicle infotainment platform is similar), two different mobile device models often mean different screen specifications. The same interface style may have different visual effects on these two mobile devices. Therefore, it is often necessary to preview the interface style separately on mobile devices of different specifications.

[0036] The editing service platform can communicate with both the editing end and the target preview end via network.

[0037] In summary, Figure 1 In the system shown:

[0038] On the editing end, a style editing request for the target interface is sent to the editing service platform;

[0039] The editing service platform, in response to the style editing request of the target interface generated by the editing terminal, creates a session identifier corresponding to the target interface and returns the session identifier to the editing terminal that generated the corresponding style editing request; at least based on the style editing data of the target interface generated by the editing terminal, it generates style data and style data events for the target interface, and when it listens for the style data event of the target interface, it sends the style data corresponding to the target interface to the target preview terminal;

[0040] The target preview end obtains the session identifier corresponding to the target interface from the editing end, and establishes a connection with the platform through the session identifier corresponding to the target interface.

[0041] based on Figure 1 The system shown can support at least one developer to edit the interface style of at least one interface using at least one editing terminal, and preview the interface style of at least one interface on at least one target preview terminal. The number of developers, interfaces, editing terminals, and target preview terminals can be set according to actual needs; there can be one or more.

[0042] Specifically, taking a single editing client and a single target preview client as an example, the editing service platform can respond to the editing client's style editing request for the target interface by creating a unique session identifier corresponding to the target interface (different interfaces have different and unique session identifiers; a single interface can correspond to multiple session identifiers). This session identifier is then returned to the editing client, which can provide it to the target preview client so that the target preview client can establish a connection with the editing service platform through this session identifier. In this way, for the editing and previewing of the target interface, the editing service platform establishes a relationship between the target interface and the target preview client using the session identifier. The editing client can upload the generated style editing data of the target interface to the editing service platform. The editing service platform determines the style data of the target interface based on the style editing data and also determines the corresponding session identifier based on the target interface, thus determining which target preview client the style data of the target interface needs to be sent to.

[0043] The target preview client can render the visual effects of the target interface style based on the received target interface style data, so that developers can view it.

[0044] With the technical solution provided in this disclosure, during the adaptation development process, the style editing data of the target interface generated by the developers on the editing end will be uploaded to the editing service platform. The editing service platform will generate the latest style data of the target interface based on the style editing data, and then send the latest style data to the target preview end, so that the developers can use the target preview end to efficiently verify the visual effect of the front-end interface.

[0045] The technical solutions provided in this disclosure will be described in more detail below.

[0046] Figure 2 This is a schematic diagram of the architecture of an editing service platform provided in this public disclosure. For example... Figure 2 As shown, the editing service platform includes a communication service module, an editing service module, and a data service module. Among them:

[0047] The communication service module, in response to the style editing request of the target interface generated by the editing terminal, creates a session identifier corresponding to the target interface and returns the session identifier to the editing terminal that generated the corresponding style editing request;

[0048] The editing service module generates style data and style data events for the target interface, based at least on the style editing data of the target interface generated by the editing client.

[0049] When the data service module detects a style data event of the target interface, it sends the style data corresponding to the target interface to the target preview terminal. The target preview terminal then establishes a connection with the platform through the session identifier corresponding to the target interface.

[0050] In practical applications, an editing service platform can provide editing and preview services for one or more interfaces. For ease of description, any interface will be referred to as the target interface. This section describes how the editing service platform provides editing and preview services for the target interface.

[0051] The number of editing endpoints participating in the editing-previewing of the target interface can be one or more, and the number of preview endpoints participating in the editing-previewing of the target interface can also be one or more. For ease of description, this is described from the perspective of a single editing endpoint. This editing endpoint sends a style editing request for the target interface to the editing service platform and obtains a session identifier corresponding to the target interface returned by the editing service platform. The editing endpoint provides the session identifier to one or more target preview endpoints used to preview the visual effects of the target interface style. The target preview endpoints establish a communication connection with the editing service platform through the obtained session identifier. It is easy to understand that this communication connection is bound to the session identifier. The editing endpoint uploads the target interface identifier and the corresponding style editing data to the editing service platform. On the one hand, the editing service platform determines the style data of the target interface based on the style editing data of the target interface. On the other hand, it can determine which communication connection to send the style data of the target interface through based on the session identifier corresponding to the target interface identifier.

[0052] Specifically, the communication service module can respond to a style editing request for the target interface generated by the editing end and generate a session identifier; it can also establish a correspondence between the session identifier and the interface identifier of the target interface carried in the request, wherein each target interface corresponds to a unique interface identifier. The data service module, upon detecting a style data event of the target interface, can retrieve the session identifier corresponding to the target interface from the correspondence based on the interface identifier carried in the style data event, and send the style data corresponding to the target interface to the target preview end that has established a connection with the platform through the session identifier.

[0053] In terms of technical effectiveness, when the style of the target interface changes on the editing end, the target preview end corresponding to the communication connection bound to the session identifier of the target interface can receive the latest style data of the target interface.

[0054] For example, the target interface's interface identifier is 001, which corresponds to session identifiers 1, 2, and 3. Preview client a establishes a connection with the editing service platform through session identifier 1, preview clients b and c establish connections through session identifier 2, and preview client d establishes a connection through session identifier 3. When the editing client generates new style editing data for the target interface, preview clients a, b, c, and d can all receive the latest style data for the target interface. Specifically, preview client a obtains the latest style data for the target interface through the connection corresponding to session identifier 1, preview clients b and c obtain the latest style data for the target interface through the connection corresponding to session identifier 2, and preview client d obtains the latest style data for the target interface through the connection corresponding to session identifier 3.

[0055] It should be noted that the editing client often edits the target interface multiple times, not just once, and these multiple edits occur frequently. This means that the editing service platform also needs to frequently send the latest style data of the target interface to the target preview client. Therefore, setting the communication connection between the target preview client and the editing service platform to a persistent connection (such as a WebSocket connection) can avoid the performance overhead caused by the editing service platform frequently establishing short connections with the target preview client, and can also improve the real-time performance of data interaction between the editing service platform and the target preview client.

[0056] It should also be noted that the connection between the editing client and the editing service platform can also be a persistent connection. This can avoid the performance overhead caused by the editing client frequently establishing short connections with the editing service platform, and can also make the data interaction between the editing client and the editing service platform more real-time.

[0057] The aforementioned style data event is generated by the editing service module. Its function is to trigger the data service module to send the latest style data of the target interface (style data generated by the editing service module based on the received style editing data of the target interface) to the target preview terminal. In some embodiments, the style editing data generated by the editing terminal can be in key-value format, where the key represents a certain interface style attribute and the value represents the value of the interface style attribute. The editing service module can parse the key-value pairs in the style editing data and then generate the style data of the target interface based on the parsing results.

[0058] In some embodiments, the editing service module can obtain the style editing data of the target interface generated by the editing terminal, and then update the historical style data of the target interface based on the style editing data to generate the style data and style data events of the target interface.

[0059] Some target interfaces have style attributes that are divided into basic style attributes and non-basic style attributes. Updating basic style attributes (such as the background of the target interface) involves a global update of the target interface's historical style data, that is, a global update of the values ​​of the basic style attributes in the historical style data. Updating non-basic style attributes (such as the font of a piece of text) involves a partial update of the target interface's historical style data, that is, a partial update of the values ​​of the non-basic style attributes in the historical style data.

[0060] In other words, for the editing service module, if the style editing data carries the modified value of the basic style attribute, then the value of the basic style attribute in the historical style data is globally updated, and a global style data update event is generated; if the style editing data carries the modified value of the non-basic style attribute, then the value of the non-basic style attribute in the historical style data is locally updated, and a local style data update event is generated.

[0061] For the target preview client, if the received style data corresponds to a global update event, the received style data can be used to completely replace the historical style data of the local target interface. If the received style data corresponds to a partial update event, the received style data can be used to partially update the non-basic attribute values ​​of the historical style data of the local target interface.

[0062] In some embodiments, the editing client can generate an identifier image based on a session identifier and display the identifier image. The target preview client can scan the identifier image to obtain the session identifier corresponding to the target interface. Then, the target preview client sends a connection request (carrying the session identifier) ​​to the editing service platform to establish a communication connection bound to the session identifier. The identifier image here can be, for example, a barcode image, a QR code image, etc.

[0063] In some embodiments, the data service module can also obtain the preview device information uploaded by the target preview client after establishing a connection with the editing service platform through the session identifier, and send the preview device information to the editing client so that the editing client can display the preview device information. In this way, developers can confirm that the current editing client and the adapted preview client are associated through the preview device information displayed on the editing client, thus ensuring that style changes to the target interface are successfully synchronized to the target preview client.

[0064] In addition, when multiple developers are collaboratively editing and previewing the interface style of the same interface, the technical solution provided in this disclosure eliminates the difficulty of collaboration among multiple developers. The target interface style update generated by each developer will be synchronized to the target preview terminal in a timely manner, allowing each developer to preview the latest results of team collaboration (i.e., the visual effect of the latest interface style of the same interface).

[0065] It should be noted here that when multiple editing clients are editing the style of the same target interface, the editing service platform may receive style editing data of the target interface uploaded by at least two editing clients within a certain time period. In this case, the editing service module of the editing service platform can generate the latest style data of the target interface at the end of this time period based on all the style editing data of the same target interface received within the same time period, and then send the latest style data of the target interface to the target preview client at the end of this time period.

[0066] Figure 3 This is a flowchart illustrating a method for previewing the style of an interface provided in this disclosure. This method, applied in an editing service platform, may include the following steps:

[0067] S300: In response to a style editing request for the target interface generated by the editing terminal, create a session identifier corresponding to the target interface and return the session identifier to the editing terminal that generated the corresponding style editing request.

[0068] In this way, the target preview client can obtain the session identifier corresponding to the target interface from the editing client, and then the target preview client can establish a connection with the editing service platform through the session identifier.

[0069] S302: Generate style data and style data events for the target interface based at least on the style editing data of the target interface generated by the editing end.

[0070] S304: When the style data event of the target interface is detected, the style data corresponding to the target interface is sent to the target preview terminal.

[0071] for Figure 3 The method flow shown can be explained in the previous text and will not be repeated here.

[0072] This disclosure also provides a computer program product that implements the methods of the embodiments of this disclosure when running.

[0073] This disclosure also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the methods of embodiments of this disclosure.

[0074] This disclosure also provides a computing device, including a memory and a processor; the memory is used to store computer instructions that can be executed on the processor, and the processor is used to implement the methods of the embodiments of this disclosure when executing the computer instructions.

[0075] Figure 4 This is a schematic diagram of the structure of a computing device provided in this disclosure. The computing device 15 may include, but is not limited to, a processor 151, a memory 152, and a bus 153 connecting different system components (including the memory 152 and the processor 151).

[0076] The memory 152 stores computer instructions that can be executed by the processor 151, enabling the processor 151 to perform the methods of any embodiment of this disclosure. The memory 152 may include a random access memory (RAM) 1521, a cache memory 1522, and / or a read-only memory (ROM) 1523. The memory 152 may also include a program tool 1525 having a set of program modules 1524, including but not limited to: an operating system, one or more application programs, other program modules, and program data. One or more combinations of these program modules may include an implementation of a network environment.

[0077] Bus 153 may include, for example, a data bus, an address bus, and a control bus. The computing device 15 can also communicate with external devices 155 via I / O interface 154, such as a keyboard or a Bluetooth device. The computing device 150 can also communicate with one or more networks via network adapter 156, such as a local area network (LAN), a wide area network (WAN), or a public network. As shown, network adapter 156 can also communicate with other modules of the computing device 15 via bus 153.

[0078] Furthermore, although the operations of the methods disclosed herein are described in a specific order in the accompanying drawings, this does not require or imply that these operations must be performed in that specific order, or that all of the operations shown must be performed to achieve the desired result. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.

[0079] While the spirit and principles of this disclosure have been described with reference to several specific embodiments, it should be understood that this disclosure is not limited to the disclosed specific embodiments, and the division of aspects does not imply that features in these aspects cannot be combined for benefit; such division is merely for convenience of expression. This disclosure is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

[0080] The methods described in the above embodiments can be implemented by a computer chip or physical entity, or by a product with a certain function. A typical implementing device is a computer. Specifically, the computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0081] For ease of description, the above devices are described in terms of function, divided into various modules. Of course, in implementing this specification, the functions of each module can be implemented in one or more software and / or hardware.

[0082] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, apparatus, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can 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, etc.) containing computer-usable program code.

[0083] Computer-readable media, including both permanent and non-permanent, removable and non-removable media, can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, 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 technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, disk storage, quantum memory, graphene-based storage media or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

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

[0085] The terminology used in the various embodiments of this specification is for the purpose of describing particular embodiments only and is not intended to limit the various embodiments of this specification. The singular forms “a,” “described,” and “the” as used in the various embodiments of this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

[0086] It should be understood that although the terms first, second, third, etc., may be used to describe various information in various embodiments of this specification, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first information may also be referred to as second information without departing from the scope of various embodiments of this specification, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0087] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on its differences from other embodiments. In particular, the method embodiments are basically similar to the method embodiments and are therefore described simply; relevant parts can be referred to the descriptions of the method embodiments. The method embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate. When implementing the embodiments of this specification, the functions of each module can be implemented in one or more software and / or hardware. Alternatively, some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0088] The above description is merely a preferred embodiment of the various embodiments of this specification and is not intended to limit the various embodiments of this specification. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the various embodiments of this specification should be included within the protection scope of the various embodiments of this specification.

Claims

1. An editing service platform, wherein, The platform includes: The communication service module, in response to a style editing request for the target interface generated by the editing terminal, generates a session identifier; establishes a correspondence between the session identifier and the interface identifier of the target interface carried in the request, and returns the session identifier to the editing terminal that generated the corresponding style editing request; wherein, one target interface corresponds to one unique interface identifier; The editing service module generates style data and style data events for the target interface, based at least on the style editing data of the target interface generated by the editing client. When the data service module detects a style data event of the target interface, it sends the style data corresponding to the target interface to the target preview terminal. The target preview terminal establishes a connection with the platform through the session identifier corresponding to the target interface. When a style data event of the target interface is detected, the style data corresponding to the target interface is sent to the target preview terminal. The target preview terminal establishes a connection with the platform through the session identifier corresponding to the target interface, including: When a style data event of the target interface is detected, the session identifier corresponding to the target interface is obtained from the correspondence based on the interface identifier carried in the style data event. The style data corresponding to the target interface is sent to the target preview terminal that has established a connection with the platform through the session identifier.

2. The platform as described in claim 1, wherein, The generation of style data and style data events for the target interface based on the style editing data of the target interface generated by the editing terminal specifically includes: Obtain the style editing data of the target interface generated by the editing terminal; Based on the style editing data, the historical style data of the target interface is updated to generate the style data and style data events of the target interface.

3. The platform as described in claim 2, wherein, The step of updating the historical style data of the target interface based on style editing data, and generating style data and style data events for the target interface, includes: If the style editing data carries the modified value of the basic style attribute, then the value of the basic style attribute in the historical style data is globally updated, and a global style data update event is generated. If the style editing data carries the modified values ​​of non-basic style attributes, then the values ​​of the non-basic style attributes in the historical style data are partially updated, and a style data partial update event is generated.

4. The platform as described in any one of claims 1-3, wherein, The editing terminal generates an identification code image based on the session identifier and displays the identification code image; The target preview terminal obtains the session identifier corresponding to the target interface from the editing terminal, including: The target preview terminal scans the identification code image displayed by the editing terminal to obtain the session identifier corresponding to the target interface.

5. The platform as described in claim 1, wherein, The target preview client establishes a connection with the platform through the session identifier corresponding to the target interface, including: The target preview client establishes a long connection with the platform through the session identifier corresponding to the target interface.

6. The platform as described in claim 1, wherein the data service module acquires the preview device information uploaded by the target preview terminal after establishing a connection with the platform through the session identifier, and sends the preview device information to the editing terminal so that the editing terminal can display the preview device information.

7. A method for previewing the style of an interface, applied to an editing service platform, the method comprising: In response to a style editing request for the target interface generated by the editing terminal, a session identifier is generated; Establish a correspondence between the session identifier and the interface identifier of the target interface carried in the request, and return the session identifier to the editing end that generated the corresponding style editing request, so that the target preview end can obtain the session identifier corresponding to the target interface from the editing end, and then the target preview end can establish a connection with the platform through the session identifier; wherein, one target interface corresponds to one unique interface identifier; Based at least on the style editing data of the target interface generated by the editing end, generate style data and style data events for the target interface; When a style data event of the target interface is detected, the session identifier corresponding to the target interface is obtained from the correspondence based on the interface identifier carried in the style data event. The style data corresponding to the target interface is sent to the target preview terminal that has established a connection with the platform through the session identifier.

8. A user interface editing system, wherein, include: Editing service platform, editing terminal, and target preview terminal; On the editing end, a style editing request for the target interface is sent to the editing service platform; The editing service platform responds to style editing requests for the target interface generated by the editing client and generates a session identifier; Establish a correspondence between the session identifier and the interface identifier of the target interface carried in the request, and return the session identifier to the editing terminal that generated the corresponding style editing request; Based at least on the style editing data of the target interface generated by the editing end, style data and style data events of the target interface are generated. When the style data event of the target interface is detected, the session identifier corresponding to the target interface is obtained from the correspondence based on the interface identifier carried in the style data event. The style data corresponding to the target interface is sent to the target preview terminal that has established a connection with the platform through the session identifier; wherein, each target interface corresponds to a unique interface identifier; The target preview end obtains the session identifier corresponding to the target interface from the editing end, and establishes a connection with the platform through the session identifier.

9. A computer-readable storage medium having a computer program stored thereon, the program being executed by a processor to perform the functions of the editing service platform, editing terminal, or target preview terminal as described in any one of claims 1-6.

Images