Cross-platform interface conversion method and device, equipment, medium and product

Abstract

The invention discloses a cross-platform interface conversion method and device, equipment, a medium and a product. The method comprises the following steps: acquiring an instance object corresponding to a first component used when a first interface is generated on a first media production platform; wherein the instance object comprises a component type and a resource path of a second component corresponding to the first component in the second media production platform; and determining interface structured information of the first interface, and converting the first interface into a second interface adaptive to the second media production platform based on the interface structured information and the instance object. According to the technical scheme provided by the invention, efficient cross-platform interface conversion is realized, the conversion result is ensured to conform to the design specification of the second media production platform, and the conversion result is kept consistent with the original interface in structural layout and visual performance.

Description

Technical Field

[0001] This invention relates to the field of computer processing technology, and in particular to a cross-platform interface conversion method, apparatus, device, medium, and product. Background Technology

[0002] In current game development, the requirements for user interfaces are becoming increasingly complex and numerous. When creating interfaces, it is usually necessary to rely on multiple tools to work together to complete the interface design and implementation.

[0003] Currently, the common approach to creating cross-tool interfaces is as follows: after completing the interface design in one design tool, the interface is exported as an image; then, the user recreates the components one by one in another design tool based on these design images.

[0004] This method of rebuilding the interface across tools relies on manual export, visual comparison, and manual configuration. It not only suffers from low interface conversion efficiency, but is also prone to inconsistencies between the interface appearance and the original design due to human error. Summary of the Invention

[0005] This invention provides a cross-platform interface conversion method, apparatus, device, medium, and product to achieve efficient cross-platform interface conversion while ensuring that the conversion result conforms to the design specifications of the second media production platform and maintains consistency with the original interface in terms of structural layout and visual presentation.

[0006] According to one aspect of the present invention, a cross-platform interface conversion method is provided, the method comprising:

[0007] Obtain the instance object corresponding to the first component used when generating the first interface on the first media production platform; wherein, the instance object includes the component type and resource path of the second component corresponding to the first component in the second media production platform;

[0008] The interface structure information of the first interface is determined, and based on the interface structure information and the instance object, the first interface is converted into a second interface adapted to the second media production platform.

[0009] According to another aspect of the present invention, a cross-platform interface conversion device is provided, the device comprising:

[0010] The instance object acquisition module is used to acquire the instance object corresponding to the first component used when generating the first interface on the first media production platform; wherein, the instance object includes the component type and resource path of the second component corresponding to the first component in the second media production platform;

[0011] The interface conversion module is used to determine the interface structure information of the first interface, and based on the interface structure information and the instance object, convert the first interface into a second interface adapted to the second media production platform.

[0012] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0013] At least one processor; and a memory communicatively connected to said at least one processor; wherein,

[0014] The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the cross-platform interface conversion method according to any embodiment of the present invention.

[0015] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the cross-platform interface conversion method according to any embodiment of the present invention.

[0016] According to another aspect of the present invention, a computer program product is provided, comprising a computer program that, when executed by a processor, implements the cross-platform interface conversion method as described in any embodiment of the present invention.

[0017] The technical solution of this invention obtains the instance object corresponding to the first component used when generating the first interface on the first media production platform; the instance object includes the component type and resource path of the second component corresponding to the first component in the second media production platform; determines the interface structure information of the first interface; and converts the first interface into a second interface adapted to the second media production platform based on the interface structure information and the instance object. This solves the problems of low efficiency and inconsistent interface performance with the original design caused by relying on manual cross-tool interface reconstruction in the prior art. It realizes the accurate and efficient generation of a second interface that conforms to the design specifications of the second media production platform by parsing the interface structure information of the first interface and integrating the instance object of the first component used when generating the first interface on the first media production platform, as well as the interface structure information. While achieving efficient cross-platform conversion, it ensures that the conversion result maintains a high degree of consistency with the original interface in terms of structural layout and visual performance.

[0018] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 This is a flowchart of a cross-platform interface conversion method provided according to an embodiment of the present invention;

[0021] Figure 2 This is a schematic diagram for representing a first page according to an embodiment of the present invention;

[0022] Figure 3 This is a flowchart of a cross-platform interface conversion method provided according to an embodiment of the present invention;

[0023] Figure 4 This is a flowchart of a cross-platform interface conversion method provided according to an embodiment of the present invention;

[0024] Figure 5 This is a flowchart provided according to an embodiment of the present invention for characterizing the validity of resource paths in a runtime format file;

[0025] Figure 6 This is a flowchart of a cross-platform interface conversion method provided according to an embodiment of the present invention;

[0026] Figure 7 This is a schematic diagram of the structure of a cross-platform interface conversion device provided according to an embodiment of the present invention;

[0027] Figure 8 This is a schematic diagram of the structure of an electronic device that implements the cross-platform interface conversion method of this invention. Detailed Implementation

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

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

[0030] It should be noted that the collection, gathering, updating, analysis, processing, use, transmission, and storage of user personal information involved in the technical solution disclosed herein all comply with relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken to prevent unauthorized access to user personal information data and to maintain user personal information security and network security. It should also be noted that the collection, gathering, updating, analysis, processing, use, transmission, and storage of user personal information involved in the technical solution disclosed herein are all conducted with the user's knowledge and consent, and comply with relevant privacy protection regulations.

[0031] Before introducing the technical solutions provided in the embodiments of this disclosure, the application scenarios can be illustrated by example.

[0032] Currently, to meet the increasingly diverse needs of interface creation, various types of interface design platforms are typically developed, allowing users to create interfaces efficiently and flexibly. For example, game development involves numerous complex interface requirements, necessitating the creation of various UI interfaces, including main menus, inventory systems, and combat HUDs. In this process, UI (User Interface) design often involves collaboration between multiple design platforms. These platforms include, but are not limited to, Figma, Photoshop, and all UI editors (such as XGUI). Figma, in particular, is a cloud-based UI / UX (User Experience) design and collaboration tool that supports cross-platform interface design and real-time collaboration. XGUI is a dedicated user interface editing tool for game engines, used to generate in-game UI panels.

[0033] However, due to differences in data formats, component models, and resource management mechanisms among different tools, existing technical workflows often require designers to first complete visual designs in a design tool (such as Figma or Photoshop), and then manually export them as static mockups or secondary optimized mockups. Engineers then need to manually rebuild UI components one by one in another development tool (such as XGUI) based on these mockups, and repeatedly adjust their positions, sizes, hierarchical relationships, style attributes, and interaction logic to ensure that the final implementation meets development specifications and visual requirements. This repetitive cross-tool production method, relying on manual export, visual comparison, and manual configuration, is not only inefficient but also prone to human error leading to inconsistencies between the final result and the original design, thus affecting the overall interface quality, extending the development cycle, and increasing design and development costs.

[0034] To address the aforementioned issues, this disclosure provides a cross-platform interface conversion method that efficiently and accurately converts an interface created on one platform (such as Figma or Photoshop) into an interface adapted to another platform (such as XGUI), thereby improving interface conversion efficiency and ensuring the accuracy and consistency of the conversion result with the original design. This improves overall interface production efficiency and reduces labor costs and error risks.

[0035] Figure 1 This is a flowchart of a cross-platform interface conversion method according to an embodiment of the present invention. This embodiment is applicable to any situation requiring cross-platform interface conversion. The method can be executed by a cross-platform interface conversion device, which can be implemented in hardware and / or software and can be configured in a computing device. Figure 1 As shown, the method includes:

[0036] S110. Obtain the instance object corresponding to the first component used when generating the first interface on the first media production platform.

[0037] The first media production platform refers to the media content creation tool or system used to create user interfaces (such as UI design drafts or interactive prototypes), such as Figma and Photoshop. The first interface refers to the specific user interface built by the designer within the first media production platform, composed of multiple layers and components. The first component refers to the component that constitutes the first interface, containing specific structures, styles, behaviors, and interaction logic. These include, but are not limited to: images, buttons, checkboxes, sliders, progress bars, WordArt, input boxes, text boxes, scrollable containers, combo controls, cards, navigation bars, status bars, icons, menus, lists, pop-ups, tabs, placeholders, dividers, title bars, and various other components.

[0038] The instance object contains the component type and resource path of the second component corresponding to the first component in the second media production platform. The second media production platform refers to a different media content generation or runtime environment than the first media production platform. Different media production platforms differ in their component systems and resource management mechanisms. For example, when a design completed on platform A needs to be converted into a runnable interface adapted to platform B (such as XGUI, React, Flutter, or other UI editors), platform A is the first media production platform; platform B is the second media production platform. The second component refers to the specific implementation component in the second media production platform that corresponds to the first component in terms of function or visual appearance. The component type describes the category identifier of the second component in the second media production platform (such as "Button" or "ImageCard"). The resource path refers to the location address of the component resources (such as icons, images, style files, etc.) that the second component depends on in the project resource library of the second media production platform.

[0039] An instance object is a concrete reference or copy of a first component created through the Component-Instance mechanism. The first component is defined in the first media production platform, and its corresponding instance object inherits its mapping information (i.e., the component type and resource path of the second component) from the second media production platform. This allows the instance object to know which target second component to replace and which resources to use during the conversion process. When this mapping information associated with the first component (e.g., the resource path corresponding to the second component) is updated, its instance object can be updated synchronously, thus maintaining cross-platform consistency.

[0040] For example, in the first media production platform, a user can define a button E (i.e., the first component) as a Component on the panel, and create one or more Instances (i.e., instance objects) based on this Component. The instance object is then associated with the button E (e.g., an association based on a unique identifier, an association based on a memory pointer or object reference, or an association based on declarative dependencies), inheriting the cross-platform mapping information associated with the button E (e.g., the component type and resource path of the corresponding component H (i.e., the second component) in the second media production platform), thereby achieving efficient reuse and accurate adaptation during subsequent conversions. Alternatively, a globally unique identifier can be pre-assigned to each first component in the first media production platform. When the user creates an instance object for this component, this identifier can be stored within the instance. During interface conversion, the first media production platform can locate the first component based on this identifier and inject its mapping information into the instance object.

[0041] In practical implementation, the instance objects of each component in the first media production platform can be pre-configured. When the first interface is completed in the first media production platform and needs to be converted into an interface adapted for the second media production platform, the instance objects corresponding to one or more first components used in building the first interface can be obtained from the object configuration library. Alternatively, a mapping configuration table can be pre-maintained, which contains the unique identifier of each component in the first media production platform (such as componentKey in Figma), as well as the component type and resource path of the second component matched by each component in the second media production platform. When performing interface conversion, the mapping configuration table can be queried according to the identifier of the first component actually used in the first interface to obtain its corresponding component type and resource path, and the corresponding instance object can be dynamically generated.

[0042] In addition, semantic analysis algorithms can be used to analyze the attributes of the first component (such as size, text content, layer structure, interactive behavior, etc.) and extract the functional semantics of the first component; compare the functional semantics with the available components in the second media production platform to infer the second component that best matches the first component, and associate the corresponding component type and resource path in the resource library to generate the corresponding instance object.

[0043] The above methods can be used individually or in combination to improve the automation and flexibility of cross-platform interface conversion while ensuring conversion accuracy.

[0044] To improve the visualization, controllability, and operational efficiency of cross-platform interface conversion, an interface export page, including at least the first interface, can be displayed during the process of obtaining the instance object corresponding to the first component used when generating the first interface on the first media production platform; in response to the conversion operation for the first interface, the instance object corresponding to the first component used when generating the first interface can be obtained.

[0045] The interface export page refers to a page developed within the first media production platform used to display or export the created primary interface; it may contain one or more display areas. The conversion operation refers to an instruction initiated by a user or system to convert the primary interface into an interface compatible with another platform.

[0046] In this embodiment, when a user triggers the interface display control on the first media production platform, shares the first interface to the display module of the first media production platform, clicks the interface check control before the cross-platform conversion operation, performs an interface preview or publishing operation, opens the project page containing the first interface, or calls the interface export and synchronization function, the displayed page serves as the interface export page, and the first interface to be converted is displayed on the interface export page. Users can perform conversion operations on the first interface on the interface export page, such as clicking the export control, clicking the link or card to synchronize to another platform, or entering a shortcut key. When a user triggers a conversion operation on the first interface, all layer nodes of the first interface can be traversed, all first components can be identified, and the instance object corresponding to each first component can be obtained.

[0047] The interface export page can also synchronously display interface attribute information, such as interface name, interface development stage, interface identifier, interface type (e.g., frame / canvas), visibility status, size, specific coordinates in its parent container or canvas coordinate system, and component information (e.g., number of child nodes, nesting level). The corresponding program logic (the component type of the second component corresponding to the first component) is encapsulated within a script, achieving the goal of presenting as little obscure information as possible while retaining the content needed by the design user. The advantages of this setup are: users can intuitively understand the design details and structural features of the currently selected interface, avoiding misjudgments or misoperations due to incomplete information; and before performing interface conversion, developers or conversion tools can judge the layout rationality and resource dependencies based on attributes such as coordinates, size, and visibility, improving conversion accuracy. Furthermore, when the interface displays abnormally or the conversion fails, it is easy to quickly locate the root cause of the problem based on the interface attribute information (e.g., coordinate overflow, hidden state, missing child components), thereby improving the overall efficiency and reliability of interface creation, conversion, and maintenance.

[0048] For example, see Figure 2 The exported interface page displays the first interface and its attribute information. The name of the first interface is A; the type is FRAME; the position is (-566.0, 1430.0); the size is 806×608; the ID is 1354:838; the visibility is yes; and the number of child nodes is 22.

[0049] The technical solution provided in this embodiment, by visually presenting the exported interface page and its contained first interface before conversion, enables designers or developers to clearly confirm the scope and structure of the interface content to be converted, avoiding misoperation or omission of key components. Simultaneously, by associating the conversion operation with the process of obtaining instance objects, it ensures that the extracted instance objects accurately correspond to the components actually used on the current converted interface, rather than redundant components not referenced in the entire project, thus ensuring the generation of a high-fidelity, structurally consistent second interface.

[0050] In order to pre-map and instantiate components in the first media production platform that are not directly involved in the construction of the current first interface but may be referenced in subsequent expansion, reuse or dynamic loading scenarios, for at least one third component in the first media production platform, a fourth component corresponding to the third component in the second media production platform can be determined, and based on the component type and resource path of the fourth component, an instance object corresponding to the third component can be determined.

[0051] The third component refers to any component defined or used in the first media production platform. The fourth component refers to the specific implementation component in the second media production platform that corresponds to the third component in terms of function, appearance, or semantics.

[0052] In this embodiment, a component library can be created in the first media production platform. This library labels the component type and resource path of the corresponding fourth component in the second media production platform for all third components in the first platform. For example, the third component may include basic controls (buttons, images) and composite controls (reusable UI components). Each third component is bound to at least two attributes of the fourth component: component type _ctlType (e.g., CCButton) and resource path _resPath (e.g., res / button / confirm.png).

[0053] To improve the ease of labeling component types and resource paths and reduce manual searching and settings, generative intelligent tools (such as the generative intelligent image search software AISlim) can be integrated into the plugins of the first media production platform to assist in adding component types and resource paths. Specifically, through the interactive interface, scanning the fourth component in the panel can automatically recommend a resource path _resPath for unnamed fourth components and add a component type _ctlType. For example, when the generative intelligent tool recognizes the "Confirm Button" image (i.e., the fourth component), it can recommend _ctlType=CCButton and retrieve _resPath=res / button / confirm.png from the project repository of the second media production platform through image matching.

[0054] The third component in the component library is treated as a language class, and the two properties of the fourth component it is bound to are used as instances of that class, thus achieving property inheritance. For example, the third component in Figma (the first media production platform) is defined as a Component, and a text property is created to store the _ctlType and _resPath attributes. By simply creating an instance of the Component, the created instance can inherit all the properties of the Component, just like an object of a class in a programming language, achieving the effect of "annotate once, use forever." In other words, each instance of the third component is pre-generated and associated with the property information of the corresponding fourth component in the second media production platform (such as a UI editor).

[0055] The technical solution provided in this embodiment, by pre-generating instance objects for the third component (including the component type and resource path of the corresponding fourth component), can dynamically configure cross-platform component mapping data. When the third component is dynamically inserted into the first interface through scripts or logic, if its instance objects have been pre-defined, all instance objects corresponding to the first interface can be quickly and conveniently obtained, and the first interface can be automatically converted into the interface required by the second media production platform. At the same time, it ensures that the rendering effect of the second interface in the second media production platform matches the design intent. Figure 1 This improves the accuracy and efficiency of cross-platform interface conversion.

[0056] S120. Determine the interface structure information of the first interface, and based on the interface structure information and instance objects, convert the first interface into a second interface adapted to the second media production platform.

[0057] The structured information of the interface refers to the data with clear semantics and organizational relationships obtained after parsing the first interface, including but not limited to: component hierarchy, layout, referenced component identifiers, relative positions of each component in the interface, component size information, visibility status, interactive attributes (such as whether it is clickable or disabled), style features (such as color, font, rounded corners), component type identifiers, resource reference relationships, layout constraint rules, parent-child nesting relationships, etc. The second interface refers to the interface that is adapted to the resources of the second media production platform and is structurally and functionally aligned with the original first interface.

[0058] In this embodiment, image recognition algorithms (such as object detection models, optical character recognition, UI element segmentation, etc.) can be used to identify the structural elements and layout relationships of the first interface, obtaining the interface's structured information. Alternatively, code analysis tools can be used to analyze the front-end implementation code of the first interface to identify its structured information. Furthermore, by recording user actions on the first interface (such as clicking, swiping, and dwell time), the functional partitions and structural logic of the first interface can be inferred, yielding the interface's structured information. Further, based on the interface's structured information, the corresponding component types and resource paths in the instance objects can be mapped to the corresponding component types and resources in the second interface. Alternatively, the interface's structured information and the component types and resource paths in the instance objects can be injected into a predefined second media production platform template, and a second interface conforming to the syntax and structural specifications of the second media production platform can be generated through template engine rendering.

[0059] For example, after a component library is created in the first media production platform and an instance of the third component in the component library is generated in the specific interface panel, when it is necessary to transform the first interface of the first media production platform into the second interface (xprefab) required by the second media production platform, the instance of the first component in the first interface can be mapped to the component type and corresponding resources in xprefab according to the interface structure information based on the cross-platform export plugin.

[0060] For example, see Figure 3 The pre-built component library includes fourth components such as widget 1, widget n, UI component 1, and UI component n. Component properties (including component type and resource path) can be created for each fourth component. For example, if it's a widget, the component type is named XGUI component type; if it's a UI component, the component type is named XPrefab. The instance object of the third component is determined based on the component properties of the fourth component corresponding to the third component. When the first UI needs to be transformed, the instance object is obtained and automatically transformed into the second UI.

[0061] In order to accurately understand, reproduce, or automate the transformation of the functions and layout of the first interface, the interface structure information can be obtained by parsing the first interface during the process of determining the interface structure information of the first interface.

[0062] The interface structure information includes at least: component hierarchy information, hierarchy identifiers for at least one level, interface layout information, relative position information of at least one first component in the first interface, and style attributes of the corresponding second component in the second media production platform. Component hierarchy information describes the nesting and parent-child relationships between all first components in the first interface and can be expressed as a tree structure, reflecting the logical organization of the interface. Hierarchy identifiers uniquely or semantically identify labels or attributes of a specific level in the first interface; for example, layer names, node IDs, semantic roles, etc., can be used to represent hierarchy identifiers. Interface layout information refers to the overall or partial arrangement rules of the first interface, including container type (such as flexible layout, grid layout), alignment, spacing constraints, etc., used to restore the spatial organization logic of the interface. Relative position information refers to the position offset of the first component in its parent container or the entire first interface coordinate system (such as top-left corner coordinates, center offset, etc.), used to accurately restore the visual layout.

[0063] Style attributes are used to describe the visual or behavioral characteristics of the second component when it is presented in the second media production platform, including but not limited to: whether it is interactive (e.g., whether a button responds to a click), initial visibility state (e.g., default display or hiding), color, font bolding (whether bold is used), and font size (text size) of at least one of these.

[0064] In practical implementation, the screenshot or interface tools in the first media production platform can be used to capture a snapshot of the first interface. Using object detection models (such as YOLO or Mask R-CNN), the nesting relationships between components are extracted to form component hierarchy information. Hierarchical identifiers for each level are retained or generated, interface layout information is parsed, and the coordinates of each first component relative to its parent container are calculated as relative position information. Simultaneously, predefined component mapping rules can be used to dynamically query the corresponding second component in the second media production platform associated with each first component, and determine the style attributes of that second component (such as interactivity, initial visibility state, etc.), ultimately integrating them into complete interface structure information. Alternatively, the original JSON data of the first interface design file can be obtained based on the API (interface) provided by the first media production platform (Figma). This data contains a complete node tree structure; by recursively traversing the node tree, the parent-child nesting relationships of each component are identified, obtaining the component hierarchy information. During the traversal, the hierarchical path (e.g., page→frame→group→button), the coordinate offset relative to the parent container, and the layout constraints (e.g., automatic layout direction and spacing) are recorded. The style attributes of the second component corresponding to the first component in the second media production platform are obtained, and the component hierarchical structure tree with hierarchical identifiers, layout rules, and relative position information is output as the interface structure information of the first interface.

[0065] The above method generates structured interface information by parsing the first interface and integrating the style attributes of the cross-platform second component. This improves the compatibility of the converted second interface with the second media production platform during interface conversion, and ensures consistency of interface structure with the first interface, thereby improving the accuracy of interface conversion.

[0066] The technical solution provided in this embodiment obtains the instance object corresponding to the first component used when generating the first interface on the first media production platform; the instance object includes the component type and resource path of the second component corresponding to the first component in the second media production platform; determines the interface structure information of the first interface; and converts the first interface into a second interface adapted to the second media production platform based on the interface structure information and the instance object. This solves the problems of low efficiency and inconsistent interface performance with the original design caused by relying on manual cross-tool interface reconstruction in the prior art. It realizes the accurate and efficient generation of a second interface that conforms to the design specifications of the second media production platform by parsing the interface structure information of the first interface and integrating the instance object of the first component used when generating the first interface on the first media production platform, as well as the interface structure information. While achieving efficient cross-platform conversion, it ensures that the conversion result maintains a high degree of consistency with the original interface in terms of structural layout and visual performance.

[0067] Figure 4 This is a flowchart of a cross-platform interface conversion method provided by an embodiment of the present invention. Based on the foregoing embodiments, step "S120" is further refined. Specific implementation details can be found in the technical solution of this embodiment. Technical terms that are the same as or corresponding to those in the above embodiments will not be repeated here.

[0068] like Figure 4 As shown, the method specifically includes the following steps:

[0069] S210. Obtain the instance object corresponding to the first component used when generating the first interface on the first media production platform.

[0070] S220. Determine the interface structure information of the first interface.

[0071] S230. Serialize the interface structure information, component types and resource paths in the instance objects to generate a structured text-formatted interface description file.

[0072] The interface description file can be understood as a structured description or data model of the interface; for example, the structured text format can be JSON.

[0073] In this embodiment, the interface structure information and all acquired instance objects can be integrated into an intermediate data model. This intermediate data model is organized in a tree structure, with each node containing the layout and hierarchy information of the first interface, and also embedding the component type and resource path of the corresponding second component. A standard serializer (such as a JSON serialization engine) is called to output the intermediate data model as a well-structured and readable interface description file according to predefined field naming conventions and nesting rules. Alternatively, a structured text template (such as a JSON Schema conforming to low-code engine specifications) can be predefined. During serialization, the interface structure information and instance objects are mapped item by item to the corresponding fields of the structured text template, and the interface description file is output. For example, the component type is filled in the "componentType" field, the resource path is filled in the "assetPath" field, and the relative position and style attributes are written into the layout and style blocks according to the agreed format.

[0074] The interface description file can include the component hierarchy, layout information, relative positions, style attributes, and the component type and resource path of the second component corresponding to each first component. The advantage of converting it to a structured text format is that it can fully express the visual elements, layout relationships, style attributes, interaction information, and cross-platform component attribute information in the first interface in a machine-readable form.

[0075] S240. Based on the interface description file, convert and generate a runtime format file that can be parsed by the second media production platform, load the runtime format file based on the second media production platform, and render and display the second interface.

[0076] The runtime format file is a binary prefab file. Binary prefab files are prefab format files (such as XPrefab) defined in a second media production platform (such as XGUI), storing data in binary encoding; their format is typically not user-readable. The runtime format file encapsulates the interface structure, component types, and resource paths of the second interface, and can be instantiated and rendered at runtime.

[0077] In this embodiment, the interface description file can be read, its structured information and component mapping data can be parsed, and the text content in the interface description file can be converted into a binary prefab format natively supported by the second media production platform according to the prefab specifications (such as node type, serialization protocol, and resource reference mechanism) to obtain a runtime format file. The runtime format file can be imported into the second media production platform, where efficient loading and parsing of the file can be completed to render the second interface.

[0078] For example, a plugin can be pre-developed in the first media production platform. Based on the plugin, the attribute information (including interface structure information and instance objects) required in the first interface panel is exported to a JSON file (i.e., the interface description file). This JSON file contains the information needed to be converted into xprefab (i.e., the runtime file). The information required by xprefab includes the component type and the resource path pointed to by the component. The component type, resource path, and interface structure information can be extracted from the instance objects in the JSON file. The component type _ctlType is mapped to the control type specified by the second media production platform, and the resource path _resPath (format can be res / ) is embedded in the runtime format file, thereby converting it into a runtime format file that XGUI can recognize. The runtime format file contains a complete interface structure and resource links, which can be directly used by the users corresponding to the second media production platform.

[0079] For example, a command-line tool (a binary executable file) takes a compliant interface description file as input. The command-line tool then converts (or compiles) the interface description file into a runtime format file required by a second media production platform (such as the XGUI UI engine). The XGUI engine directly loads this runtime format file at runtime.

[0080] When the XGUI engine loads and parses this runtime format file, it can create corresponding component objects (such as Button and Image); set the position, size, text, and images of the components; establish parent-child hierarchical relationships; and finally render an interactive second interface on the screen.

[0081] To ensure the integrity of the interface when the second media production platform loads runtime format files, it can also verify, based on the second media production platform, whether the resource file pointed to by at least one resource path in the runtime format file exists in the local resource library. When a resource file corresponding to at least one resource path is detected to be missing, the placeholder area corresponding to the second component of the missing resource file is displayed in the editing canvas of the second media production platform according to a preset format, and a jump control is displayed. In response to the trigger event of the jump control, the resource path of the missing resource file is located.

[0082] The local resource library refers to the collection of resources imported into and directly accessible in the current project or workspace of the second media production platform, which can be stored in its local file system or a database managed by the platform. A placeholder area is a temporary visual replacement area displayed on the editing canvas in a preset format when a resource file dependent on a second component is missing, used to identify the location of the missing component. A jump control, when triggered, navigates to the expected path of the missing resource in the project or the resource management panel. The jump control can be an interactive element embedded in the placeholder area (such as a "Locate Resource" button or link). A trigger event is an operation performed on the jump control (such as a click or double-click), used to initiate the resource path location process.

[0083] In this embodiment, when the second media production platform loads the runtime format file, it can traverse all resource paths and compare them one by one with the resources already stored in the local resource library. If it finds that the resource file corresponding to a certain resource path is missing, it can determine the placeholder area of ​​the second component based on the position of the second component corresponding to the missing resource in the editing canvas, and display the placeholder area in a preset form. For example, the preset form includes, but is not limited to: a gray square, a gray dashed frame, an icon placeholder, a text prompt, or one or more combinations of pop-ups. At the same time, a jump control can be embedded in the placeholder area. After the user clicks the jump control, the second media production platform can automatically open the resource manager and highlight the directory where the missing path is located (even if the directory is empty), guiding the user to supplement or correct the resource.

[0084] To avoid the loading process being blocked due to resource verification, a background task can be started to verify the validity of each resource path after the runtime format file has been loaded. Once a missing resource is detected, a semi-transparent placeholder area and a jump control are overlaid on the corresponding second component of the editing canvas, without affecting the overall rendering and interaction of the interface. Users can quickly locate the expected path of the missing resource at any time through the jump control.

[0085] For example, see Figure 5 It can load runtime format files, extract all resource paths (_resPath), check the existence of resource files under the resource paths to verify the validity of each resource path (_resPath), locate missing resources, and when a resource is missing, prompt the user and support one-click jump to repair. Finally, it can also generate an inspection report.

[0086] The advantage of this setup is that by validating the resource path when loading the runtime format file, and providing visual feedback and precise navigation through placeholder areas and jump controls when resources are missing, it guides users to complete resource repair. This makes it easier for users to quickly identify, replace, or relink valid resources, reducing the risk of interface abnormalities caused by resource missing resources and shortening the cost of troubleshooting and repairing problems.

[0087] To enable real-time visual editing and dynamic configuration of the second interface, and to improve the user's interactive flexibility and efficiency during the design process, the system can also receive attribute adjustment operations for the second component in the second interface after rendering and displaying the second interface, determine the attribute adjustment parameters associated with the attribute adjustment operations, and update the second interface based on the attribute adjustment parameters so that it reflects the adjustment results in real time.

[0088] Attribute adjustment operations refer to modifications performed by users on second components within the editing environment of the second media production platform. Examples include dragging to adjust size, changing color, size, animation parameters, data binding relationships, toggling visibility, and modifying text content in the attribute panel. Attribute adjustment parameters are the specific data describing the attribute adjustment operation, including but not limited to: the name of the modified attribute, the new size value, color value, animation parameter value, text content, and the identifier of the target second component, used to precisely guide interface updates.

[0089] Specifically, when a user performs attribute adjustment operations on a second component in the second media production platform, the system can identify the attribute adjustment operation and extract the corresponding attribute adjustment parameters. Based on these parameters, a partial re-rendering of the second interface is triggered, instantly displaying the updated second interface on the canvas. This allows for real-time modification of the corresponding second component's appearance within the second interface, showcasing the latest changes.

[0090] For example, users import XPrefab files into the second media production platform XGUI and use visualization tools to adjust the position and animation effects of components in the second interface.

[0091] The technical solution provided in this embodiment improves the flexibility and freedom of developers or designers in optimizing interface details in the platform environment by receiving attribute adjustment operations for the second component in the second interface, extracting attribute adjustment parameters and updating the interface accordingly, ensuring the efficiency and controllability of interface adjustment, improving the convenience of interface design, and thus enhancing the user experience.

[0092] It should be noted that current technical solutions for rebuilding interfaces across design tools are prone to inconsistencies in component naming, size specifications, and resource paths during the migration process. Furthermore, the target design platform may not accurately reproduce certain key attributes from the source design. Therefore, users typically need to manually compare the original design with the interface panel generated by the target tool and correct component naming, location, and resource references.

[0093] To ensure the uniqueness and standardization of component naming, components using Chinese names in the first interface can be automatically converted to camelCase, a naming convention consistent with the development practices of the second media production platform (e.g., converting "Confirm Button" to BtnConfirm). Furthermore, it can detect components with duplicate names and automatically add a unique suffix (e.g., BtnConfirm_1, BtnConfirm_2) to conflicting entries, thus guaranteeing global naming uniqueness. This standardized naming strategy not only avoids naming conflicts but also makes UI components more aligned with the development specifications of the second media production platform, improving the accuracy and efficiency of interface transitions.

[0094] The technical solution provided in this embodiment generates a standardized structured text-formatted interface description file by sequentially and systematically processing the structured information of the interface and the component types and resource paths in the instance object. This effectively reduces human translation errors and improves consistency and delivery efficiency across multiple platforms. Furthermore, by converting the structured interface description file into a binary prefab file that can be directly loaded by the second media production platform, the runtime format file is loaded on the second media production platform, enabling efficient and accurate rendering of the second interface. This achieves efficient cross-platform interface conversion while ensuring the accuracy and consistency of the interface conversion results.

[0095] As an optional embodiment of the above embodiments, specific application scenario examples are provided to enable those skilled in the art to further understand the technical solutions of the embodiments of the present invention. Specifically, please refer to the following detailed content.

[0096] See Figure 6 The system loads the first interface, initializes the converter, and supports various UI component types, including images, text, buttons, checkboxes, sliders, etc. Each component has a corresponding Actor class (role object) and Component class (component object). It recursively traverses the first interface, creates a root node, processes the components in the first interface, and identifies the component type of the first component. When the component type is a control instance, a user interface component is created; when the component type is text, a text component is created; when the component type is a container, a panel container is created. After recursively processing complex nested interface structures, it automatically performs coordinate system transformations (such as converting the top-left coordinate system of Figma to the bottom-left coordinate system of xprefab), font mapping, etc., to obtain the interface structure information and all instance objects of the first component. After traversing all components in the first interface, it constructs an interface description file based on the interface structure information and instance objects. The interface description file is output as a runtime format file. The runtime format file is loaded based on the second media production platform to render and display the second interface. It can also perform validity checks on resource paths in the runtime format file based on a resource inspector and a set of general utility functions.

[0097] The technical solution of this embodiment analyzes the interface structure information of the first interface and integrates the instance objects of the first component used when the first interface is generated by the first media production platform, as well as the interface structure information, to accurately and efficiently generate a second interface that conforms to the design specifications of the second media production platform. While achieving efficient cross-platform conversion, it ensures that the conversion result is highly consistent with the original interface in terms of structural layout and visual presentation.

[0098] Figure 7 This is a schematic diagram of a cross-platform interface conversion device provided according to an embodiment of the present invention. Figure 7 As shown, the device includes an instance object acquisition module 310 and an interface conversion module 320.

[0099] The instance object acquisition module 310 is used to acquire the instance object corresponding to the first component used when generating the first interface on the first media production platform; wherein the instance object includes the component type and resource path of the second component corresponding to the first component in the second media production platform; the interface conversion module 320 is used to determine the interface structure information of the first interface, and based on the interface structure information and the instance object, convert the first interface into a second interface adapted to the second media production platform.

[0100] The technical solution of this embodiment obtains the instance object corresponding to the first component used when generating the first interface on the first media production platform; the instance object includes the component type and resource path of the second component corresponding to the first component in the second media production platform; determines the interface structure information of the first interface; and converts the first interface into a second interface adapted to the second media production platform based on the interface structure information and the instance object. This solves the problems of low efficiency and inconsistent interface performance with the original design caused by relying on manual cross-tool interface reconstruction in the prior art. It realizes the accurate and efficient generation of a second interface that conforms to the design specifications of the second media production platform by parsing the interface structure information of the first interface and integrating the instance object of the first component used when generating the first interface on the first media production platform, as well as the interface structure information. While achieving efficient cross-platform conversion, it ensures that the conversion result maintains a high degree of consistency with the original interface in terms of structural layout and visual performance.

[0101] Optionally, based on the above-described device, the instance object acquisition module 310 includes:

[0102] The interface export page display unit is used to display the interface export page, which includes at least the first interface.

[0103] The instance object acquisition unit is used to acquire the instance object corresponding to the first component used when generating the first interface in response to the transformation operation for the first interface.

[0104] Based on the above-mentioned device, optionally, an interface conversion module 320 is used to obtain interface structure information by parsing the first interface;

[0105] The interface structure information includes at least: component hierarchy information, at least one hierarchy identifier, interface layout information, at least one relative position information of the first component in the first interface, and style attributes of the second component corresponding to the first component in the second media production platform; the style attributes include at least one of whether it is interactive, initial display / hidden state, color, bold font identifier, and font size.

[0106] Based on the above-mentioned device, optionally, the interface conversion module 320 includes:

[0107] The interface description file determination unit is used to serialize the interface structured information, the component types and resource paths in the instance object, and generate an interface description file in structured text format.

[0108] The runtime format file determination unit is used to convert and generate a runtime format file that can be parsed by the second media production platform based on the interface description file, so as to load the runtime format file based on the second media production platform and render and display the second interface;

[0109] The runtime format file is a binary prefab file.

[0110] Optionally, based on the above-described apparatus, the apparatus may further include:

[0111] The verification unit is used to verify, based on the second media production platform, whether the resource file pointed to by at least one resource path in the runtime format file exists in the local resource library.

[0112] The placeholder area determination unit is used to, when at least one resource file corresponding to the resource path is detected to be missing, display the placeholder area corresponding to the second component of the missing resource file in the editing canvas of the second media production platform according to a preset format, and display a jump control.

[0113] The positioning unit is used to locate the resource path of the missing resource file in response to a trigger event of the jump control.

[0114] Optionally, based on the above-described apparatus, the apparatus may further include:

[0115] An attribute adjustment parameter determination unit is used to receive an attribute adjustment operation for a second component in the second interface and determine the attribute adjustment parameters associated with the attribute adjustment operation.

[0116] The interface update unit is used to adjust parameters based on the attributes and update the second interface.

[0117] Optionally, based on the above-described apparatus, the apparatus may further include:

[0118] The instance object determination unit is used to determine, for at least one third component in the first media production platform, a fourth component corresponding to the third component in the second media production platform, and to determine the instance object corresponding to the third component based on the component type and resource path of the fourth component.

[0119] The cross-platform interface conversion device provided in this embodiment of the invention can execute the cross-platform interface conversion method provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the method execution.

[0120] Figure 8 This is a schematic diagram of the structure of an electronic device implementing the cross-platform interface conversion method of this invention. The electronic device is intended to represent various forms of digital computers, such as laptops, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframes, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0121] like Figure 8 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory 12 or a random access memory 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the read-only memory 12 or a computer program loaded from storage unit 18 into the random access memory 13. The random access memory 13 can also store various programs and data required for the operation of the electronic device 10. The processor 11, read-only memory 12, and random access memory 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0122] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0123] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as cross-platform interface conversion methods.

[0124] In some embodiments, the cross-platform interface conversion method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 10 via read-only memory 12 and / or communication unit 19. When the computer program is loaded into random access memory 13 and executed by processor 11, one or more steps of the cross-platform interface conversion method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the cross-platform interface conversion method by any other suitable means (e.g., by means of firmware).

[0125] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0126] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0127] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory, read-only memory, erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0128] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0129] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0130] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0131] In particular, according to embodiments of the present invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of the present invention include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication unit 19, or installed from storage unit 18, or installed from read-only memory 12. When the computer program is executed by processor 11, it performs the functions defined in the methods of the embodiments of the present invention.

[0132] This invention also provides a computer program product, including a computer program that, when executed by a processor, implements the cross-platform interface conversion method provided in any embodiment of this invention.

[0133] In implementing the computer program product, computer program code for performing the operations of this invention can be written in one or more programming languages ​​or a combination thereof. Programming languages ​​include object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0134] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0135] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A cross-platform interface conversion method, characterized in that, include: Obtain the instance object corresponding to the first component used when generating the first interface on the first media production platform; wherein, the instance object includes the component type and resource path of the second component corresponding to the first component in the second media production platform; The interface structure information of the first interface is determined, and based on the interface structure information and the instance object, the first interface is converted into a second interface adapted to the second media production platform.

2. The method according to claim 1, characterized in that, The step of obtaining the instance object corresponding to the first component used when generating the first interface on the first media production platform includes: The output page should display at least the first interface. In response to the transformation operation for the first interface, obtain the instance object corresponding to the first component used when generating the first interface.

3. The method according to claim 1, characterized in that, The step of determining the interface structure information of the first interface includes: By parsing the first interface, the interface structure information is obtained; The interface structure information includes at least: component hierarchy information, at least one hierarchy identifier, interface layout information, at least one relative position information of the first component in the first interface, and style attributes of the second component corresponding to the first component in the second media production platform; the style attributes include at least one of whether it is interactive, initial display / hidden state, color, bold font identifier, and font size.

4. The method according to claim 1, characterized in that, The step of converting the first interface into a second interface adapted to the second media production platform based on the interface structure information and the instance object includes: The interface structure information, component types and resource paths in the instance object are serialized to generate an interface description file in structured text format; Based on the interface description file, a runtime format file that can be parsed by the second media production platform is generated, and the runtime format file is loaded by the second media production platform to render and display the second interface; The runtime format file is a binary prefab file.

5. The method according to claim 4, characterized in that, When loading the runtime format file based on the second media production platform, the method further includes: For at least one resource path in the runtime format file, based on the second media production platform, it is verified whether the resource file pointed to by the resource path exists in the local resource library; When at least one resource file corresponding to the resource path is detected to be missing, the placeholder area corresponding to the second component of the missing resource file is displayed in the editing canvas of the second media production platform in a preset format, and a jump control is displayed. In response to the trigger event of the jump control, the resource path of the missing resource file is located.

6. The method according to claim 4, characterized in that, After rendering and displaying the second interface, the method further includes: Receive an attribute adjustment operation for a second component in the second interface, and determine the attribute adjustment parameters associated with the attribute adjustment operation; Adjust the parameters based on the attributes and update the second interface.

7. The method according to claim 1, characterized in that, The method further includes: For at least one third component in the first media production platform, determine the fourth component corresponding to the third component in the second media production platform, and determine the instance object corresponding to the third component based on the component type and resource path of the fourth component.

8. A cross-platform interface conversion device, characterized in that, include: The instance object acquisition module is used to acquire the instance object corresponding to the first component used when generating the first interface on the first media production platform; wherein, the instance object includes the component type and resource path of the second component corresponding to the first component in the second media production platform; The interface conversion module is used to determine the interface structure information of the first interface, and based on the interface structure information and the instance object, convert the first interface into a second interface adapted to the second media production platform.

9. An electronic device, characterized in that, The electronic device includes: At least one processor; and a memory communicatively connected to said at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the cross-platform interface conversion method according to any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the cross-platform interface conversion method according to any one of claims 1-7.

11. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the cross-platform interface conversion method as described in any one of claims 1-7.

Images