A multi-space programming method for application development

Abstract

This application relates to the field of computer technology and discloses a multi-space programming method for application development. A user inputs information in the image interface of Application A located in the desktop space; the information is encapsulated into a vimcall message and transmitted to the terminal space through network transmission; the terminal space analyzes the vimcall message to determine whether backend processing is required; when backend processing is not required, the vimcall message is processed by the front-end of Application A or in a collaborative manner between the front-end of Application A and the front-ends of other applications, and the processing result is displayed in the desktop space; otherwise, the vimcall message is processed through backend calls, and the result of the backend processing is transmitted back to the desktop space and the interface for application processing is displayed. This application realizes the calling of the front-end and backend of an application in the desktop space and the terminal space to complete the processing of system data information that needs to be processed, simplifies and standardizes the calling relationship between applications, and reduces the development difficulty for developers.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more specifically, to a multi-space programming method for application development. Background Art

[0002] In the design and development of traditional system applications, the front-end and back-end of an application have a loose call relationship, which increases flexibility. However, the call relationships between multiple applications are relatively complex, and the threshold for developers also increases. Summary of the Invention

[0003] The purpose of this application is to provide a multi-space programming method for application development to solve the technical problems mentioned in the above background.

[0004] To achieve the above purpose, this application discloses the following technical solutions: A multi-space programming method for application development, the method includes the following steps:

[0005] The user inputs information in the graphical interface of Application A located in the desktop space;

[0006] Encapsulate the information input by the user into a vimcall message;

[0007] The vimcall message is transmitted to the terminal space through network transmission;

[0008] The terminal space analyzes the vimcall message to determine whether the vimcall message requires back-end processing;

[0009] When the vimcall message does not require back-end processing, the vimcall message is processed by the front-end of Application A or in a collaborative manner between the front-end of Application A and the front-ends of other applications, and the processing result is displayed in the desktop space;

[0010] When the vimcall message requires back-end processing, the vimcall message is processed through back-end calls, and the result of the back-end processing is transmitted back to the desktop space through network transmission and the application processing interface is displayed in the desktop space; where the back-end call methods include: the back-end of Application A, the front-end and back-end of Application A, the back-end of Application A and the back-ends of other applications, the back-end of Application A and the back-ends of other applications, or the front-end and back-end of Application A and the front-ends and / or back-ends of other applications.

[0011] Preferably, the desktop space communicates with the terminal space through a WebSocket channel.

[0012] Preferably, in the method of backend call, after the front end or the backend of an application finishes processing the vimcall message, the terminal space determines the vimcall message to analyze whether subsequent processing of the vimcall message is required. When subsequent processing is required, an application other than the one application processes the vimcall message until the vimcall message is completely processed.

[0013] Preferably, an artificial intelligence algorithm for processing and analyzing the applications required to process the vimcall message is arranged in the terminal space.

[0014] Preferably, the artificial intelligence algorithm accesses the terminal space through an AI interface.

[0015] Preferably, the API of the desktop space is configured to provide calls to the application layer and calls between application levels.

[0016] Preferably, the call of the terminal space adopts the channel method of the system bottom layer, and the output of the previous application is used as the input of the next application.

[0017] Preferably, in the method of backend call, the end call between two applications is as follows: the front end of application one calls the front end of application two, and the backend of application one calls the backend of application two.

[0018] Beneficial effects: The multi-space programming method for application development in this application realizes the call of the front end and the backend of the application in the desktop space and the terminal space to complete the processing of the system data information to be processed, simplifies and standardizes the call relationship between applications, and reduces the development difficulty of developers. Description of the Drawings

[0019] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative efforts.

[0020] Figure 1 It is a flowchart of the multi-space programming method for application development provided by the embodiment of the present application;

[0021] Figure 2 It is a system block diagram of a system corresponding to the multi-space programming method for application development provided by the embodiment of the present application. Detailed Embodiments

[0022] The technical solutions in the embodiments of the present application will be clearly and completely described below. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts shall fall within the protection scope of the present application.

[0023] In this article, the term "including" is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or also includes elements inherent to such a process, method, article or device. Without further limitation, the elements defined by the statement "including..." do not exclude the existence of additional identical elements in the process, method, article or device including the said elements.

[0024] In application development and design, although the loose call relationship between the front end and the back end of an application can increase flexibility, the call relationships between multiple applications are relatively complex, which correspondingly increases the threshold for developers.

[0025] In view of this, this embodiment discloses a multi-space programming method for application development as Figure 1 shown, aiming to simplify and standardize the calls between the front end and the back end of an application. Specifically, the method includes the following steps:

[0026] The user inputs information in the graphical interface of application A located in the desktop space;

[0027] Encapsulate the information input by the user into a vimca l l message;

[0028] The vimca l l message is transmitted to the terminal space by means of network transmission;

[0029] The terminal space analyzes the vimca l l message to determine whether the vimca l l message requires back-end processing;

[0030] When the vimca l l message does not require back-end processing, the vimca l l message is processed by the front end of application A or in a collaborative manner between the front end of application A and the front ends of other applications, and the processing result is displayed in the desktop space;

[0031] When the vimcall message needs to be processed by the backend, the vimcall message is processed by means of backend call, and the result of the backend processing is transmitted back to the desktop space through network transmission and the interface of the application processing is displayed in the desktop space; wherein the means of backend call includes: the backend of Application A, the front end and the backend of Application A, the backend of Application A and the backends of other applications, the backend of Application A and the backends of other applications, or the front end and the backend of Application A and the front ends and / or backends of other applications.

[0032] In this embodiment, an artificial intelligence algorithm for processing and analyzing the vimcall message and the applications required for processing the vimcall message are arranged in the terminal space. The artificial intelligence algorithm accesses the terminal space through an AI interface, and the AI interface can be a third-party AI interface or a private AI platform interface. Among them, the applications required for analyzing and processing the vimcall message are, based on the specific data content of the vimcall message, to analyze and obtain the applications needed to process the vimcall message, and whether the front end or the backend of the corresponding applications is needed. For those of ordinary skill in the art, any one of the existing technologies can be adopted for this algorithm.

[0033] In this method, in terms of the layout of the application, the front end of the application runs in the desktop space, and the backend of the application runs in the terminal space. Moreover, in order to ensure the stability of the application call between the desktop space and the terminal space, the desktop space and the terminal space communicate through a WebSocket channel. The API of the desktop space is configured to: provide calls to the application layer and calls between application levels. And in the desktop space, the call relationship between two applications is that the front end of Application A can call the front end of Application B. The call in the terminal space adopts the channel method at the system bottom layer, and the output of the previous application is used as the input of the next application. In the terminal space, the call relationship between two applications is that the backend of Application A can call the backend of Application B. And between the desktop space and the terminal space, the front end of Application A can only call the backend of Application A and cannot call the backend of Application B. Furthermore, cross-front-end and -backend mutual calls are realized, and the direct calls between the front end and the backend are limited to within the same application.

[0034] As a preferred implementation manner of this embodiment, in the means of backend call, when the front end or the backend of an application finishes processing the vimcall message, the terminal space judges the vimcall message to analyze whether subsequent processing of the vimcall message is required. When subsequent processing is required, the vimcall message is processed by an application other than this one application until the vimcall message is completely processed.

[0035] Next, the multi-space programming method for application development disclosed in this embodiment will be further refined with a specific operating system. Among them, the operating system selected is the Codigger system, and the applications running in the Codigger system include the front end and the back end. The front end runs in the desktop space, and the back end runs in the Terminai space (terminal space). The corresponding system architecture is as Figure 2 shown.

[0036] The front end in the desktop space provides interfaces that can be called mutually (similar to a traditional operating system, there are system-level APIs provided for applications running on the desktop to access; in the desktop space hierarchy of the Codigger system, there are Desktop APIs provided for application layer calls, and there are also API calls between application levels. In the Desktop Space, the API definitions for calls between applications need to conform to the desktop space interface definition standard); in the Terminai space, communication between back ends can be carried out through other existing channels, that is, they can be called mutually (the calls in the Terminai space adopt the system's underlying channel method, and the output of the previous application is used as the input of the next application).

[0037] Based on the above, the processing process of a message is as follows:

[0038] What is received on the graphical interface of the front end is the input of user operations. After being converted into system data information, it is transmitted to the terminal space of the back end through the network. In the terminal space, the user information is processed, and some calls between multiple applications will be involved (by means of the system's underlying channels, data is transmitted between applications to achieve calls in the Terminai space). The applications in the desktop space include front-end code and back-end code, each processing relevant information. The calls between applications are as follows: The front ends of application A and application B can be called mutually. Similarly, the back ends of application A and application B can also be called mutually. However, the front end of application A cannot call the back end of user B. Similarly, the back end of application A cannot call the front end of application B. That is, applications can be called mutually within the same space, and the same application can be called across spaces. In terms of concept, this design expands the specifications of application development, provides clear call logic for developers and maintains the interconnection of multiple applications, reducing the difficulty for developers.

[0039] Furthermore, the specific call logic is as follows:

[0040] 1. The front end of Application A calls the back end of Application A through v i nca l l, such as: ["share.WidgetManager","In it ia l i se",["java-Spr ingBoot"," / home / c louder / Down loads / sjava","0",{"projectName":"sjava","projectPath":" / home / c lo uder / Down loads / sjava","package":"oc.test","gitRepos itory":"","cod igge rSett ing":{"codeSty le":{"java":[{"codeSty leName":"ide","i sDefau lt":"1","indentsMode":"useTab","tabSize":4,"indent":4}]},"fi leAndCodeTemp l ate":{"java":""}}}]]. Among them, the name of the back-end service is share.WidgetManger, the name of the function is Imit ia l i se, and the content within the [] square brackets is the parameter of the function;

[0041] 2. The back end of Application A can implement the interface to call the back end of Application B through the pipe l ine method;

[0042] 3. The front end of Application A calls the front end of Application B, such as: ["AppB","GetTit leCo lor",["parameters"]]. AppB indicates that the name of the application is B, GetTit leCo lor is the interface GetTit leCo lor provided by the front end of Application B, and ["parameters"] is the input of the interface GetTit leCo lor.

[0043] In summary, the multi-space programming method for application development provided in this embodiment realizes the call of the front end and back end of the application in the desktop space and the terminal space to complete the processing of the system data information to be processed, simplifies and standardizes the call relationship between applications, and reduces the development difficulty of developers.

[0044] In the embodiments provided in the present application, it should be understood that the embodiments described herein can be implemented in hardware, software, firmware, middleware, code, or any appropriate combination thereof. For hardware implementation, the processor can be implemented in one or more of the following units: application specific integrated circuit (ASIC), digital signal processor (DSP), digital signal processing device (DSPD), programmable logic device (PLD), field programmable gate array (FPGA), processor, controller, microcontroller, microprocessor, other electronic units designed to implement the functions described herein, or a combination thereof. For software implementation, part or all of the processes of the embodiments can be completed by a computer program instructing the relevant hardware. When implemented, the above program can be stored in a computer-readable storage medium or transmitted as one or more instructions or codes on a computer-readable storage medium. The computer-readable storage medium includes computer storage media and communication media, where the communication media includes any medium that facilitates the transmission of a computer program from one place to another. The storage media can be any available medium accessible by a computer. The computer-readable storage medium can include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer.

[0045] Finally, it should be noted that the above are only the preferred embodiments of the present application and are not intended to limit the present application. Although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing embodiments or perform equivalent replacements for some of the technical features. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. A multi-space programming method for application development, characterized in that: The method comprises the following steps: The user inputs information in the graphical interface of application A located in the desktop space; Encapsulate user input information into vimcall messages; The vimcall message is transmitted to the terminal space via network transmission; The terminal space analyzes the vimcall message to determine whether the vimcall message needs backend processing; When the vimcall message does not need to be processed by the backend, the frontend of application A or the frontend of application A in collaboration with the frontends of other applications processes the vimcall message and displays the processing result in the desktop space; When the vimcall message needs back-end processing, the vimcall message is processed by back-end calling, and the result of the back-end processing is transmitted back to the desktop space through network transmission and the interface of application processing is displayed in the desktop space; wherein the back-end calling method includes: the back-end of application A, the front-end and back-end of application A, the back-end of application A and the back-end of other applications, the back-end of application A and the back-end of other applications, or the front-end and back-end of application A and the front-end and / or back-end of other applications; in the back-end calling method, the end call between two applications is: the front-end of application one calls the front-end of application two, and the back-end of application one calls the back-end of application two.

2. The multi-space programming method for application development according to claim 1, characterized in that: The desktop space and the terminal space communicate via a WebSocket channel.

3. The multi-space programming method for application development according to claim 1, characterized in that: In the back-end calling method, when the front-end or back-end of an application completes processing the vimcall message, the terminal space judges the vimcall message and analyzes whether the vimcall message needs to be subsequently processed. When subsequent processing is required, the vimcall message is processed by an application other than the application until the vimcall message is completely processed.

4. The multi-space programming method for application development according to claim 1, characterized in that: The terminal space is provided with an artificial intelligence algorithm for processing the vimcall message and analyzing the application required for processing the vimcall message.

5. The multi-space programming method for application development according to claim 4, characterized in that: The artificial intelligence algorithm is accessed into the terminal space via an AI interface.

6. The multi-space programming method for application development according to claim 4, characterized in that: The API configuration of the desktop space is: provided to the application layer for calling, and between application layers for calling.

7. The multi-space programming method for application development according to claim 4, characterized in that: The terminal space is called using the channel mode of the system bottom layer, and the output of the previous application is used as the input of the next application.

Images