CN108399086B - Widget management method, server and computer readable storage medium - Google Patents
Widget management method, server and computer readable storage medium Download PDFInfo
- Publication number
- CN108399086B CN108399086B CN201810199371.5A CN201810199371A CN108399086B CN 108399086 B CN108399086 B CN 108399086B CN 201810199371 A CN201810199371 A CN 201810199371A CN 108399086 B CN108399086 B CN 108399086B
- Authority
- CN
- China
- Prior art keywords
- widget
- file
- webpage
- management method
- dom object
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
Abstract
The application discloses a widget management method, a server and a computer-readable storage medium. The method loads at least one widget into the webpage according to the instruction of the user, so that the user can dynamically load the widget according to the requirement, and the user-defined webpage is realized. And the development of the application system is carried out by adopting the widgets, so that all the functional modules are low in coupling, and the development efficiency and the usability of the application system are improved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a widget management method, a server, and a computer-readable storage medium.
Background
With the continuous expansion of the application range of the internet, more and more enterprises transfer the business to the online, and the application programs for realizing the business logic are increasingly large and complex.
Currently, in project development, the development range of developers is divided according to business functions. As shown in fig. 1, each developer is responsible for the development of multiple pages, maintains a set of single projects together, and performs jump management and parameter transmission through a uniform route. Because the coupling degree of each service function module is higher in a single project, a user can only load a page according to fixed setting, cannot realize user-defined web pages, and lacks the flexibility of page loading.
Under the condition that a single project is larger and more developers are more, the project can have the problems of unclear division among business function modules, high coupling degree among the business function modules and the like. Since all the service function module codes are written in one project, when testing a certain service function module, the whole project needs to be compiled and run. Therefore, each change of the business function module may cause modification of the whole project logic, and a developer needs to compile and run the complete project every time compiling and debugging are performed, so that the time consumption is too long, and the development efficiency is affected.
Disclosure of Invention
In view of this, the present application discloses a widget management method, a server, and a computer-readable storage medium, so that a user can dynamically load widgets according to a requirement, thereby implementing user-defined web pages and improving the development efficiency of an application system.
In a first aspect, a method for managing widgets is provided, including:
acquiring the identification of at least one widget in response to a first instruction of a user;
traversing a webpage service unit according to the identification of the widget to inquire a dom object of the widget, wherein the dom object is registered in the webpage service unit in advance by the widget;
and loading the widget into a webpage according to the dom object of the widget.
Further, the method further comprises:
and responding to a second instruction of the user to store the widget combination loaded in the current webpage as a widget template in the local storage.
Further, retrieving an identification of at least one widget in response to the user instruction comprises:
responding to a user instruction to load the corresponding widget template from a local storage to acquire an identifier of at least one widget; or
And acquiring the identification of at least one widget from a widget identification list in response to a user instruction, wherein the widget identification list comprises the identifications of all registered widgets.
Further, the method further comprises:
and different widgets communicate with each other through the communication module.
Further, the communication between different widgets through the communication module comprises:
acquiring a trigger instruction of a first function of the first widget;
traversing in the communication module according to the communication identifier in the first function to obtain a second function of a second widget corresponding to the communication identifier;
controlling the transmission of parameters contained in the trigger instruction from the first widget to the second widget;
callback the second function based on the parameter;
wherein the communication identifier is pre-registered in the communication module by the second widget.
Further, loading the widget into a webpage according to the dom object of the widget comprises:
reading a dom object of the widget in the webpage service unit and loading the dom object to a webpage;
reading an xml configuration file of an application system to load a js file and a css file of the widget to a webpage;
wherein the xml configuration file of the application system comprises the file names and paths of the js file and the css file of the widget.
Further, the method further comprises:
a new widget is added.
Further, adding a new widget includes:
registering a dom object of the new widget in the web service unit;
adding the new widget identifier to the widget identifier list;
and adding the file names and paths of the js file and the css file of the new widget in the xml configuration file of the application system.
In a second aspect, a server is provided, which comprises a memory and a processor, wherein the memory is used for storing one or more computer instructions, and the one or more computer instructions are executed by the processor to realize the method.
In a third aspect, a computer-readable storage medium is provided, on which computer program instructions are stored, which computer program instructions, when executed by a processor, implement the method described above.
According to the method and the device, at least one widget is loaded into the webpage according to the instruction of the user, so that the user can dynamically load the widget according to the requirement, and the user-defined webpage is realized. And the web page is developed by adopting the widget, so that the functional modules are coupled in a low way, and the development efficiency and the usability of the application system are improved.
Drawings
The above and other objects, features and advantages of the present application will become more apparent from the following description of embodiments thereof with reference to the accompanying drawings, in which:
FIG. 1 is a schematic diagram of a prior art application system development architecture;
FIG. 2 is a schematic structural diagram of application system development according to an embodiment of the present application;
FIG. 3 is a flow chart of a method for managing widgets according to an embodiment of the present application;
FIG. 4 is a flowchart of a widget loading method according to an embodiment of the present application;
FIG. 5 is a schematic diagram of a structure of a dom object of an embodiment of the present application;
FIG. 6 is a flow chart of a widget communication method of an embodiment of the present application;
FIG. 7 is a schematic structural diagram of a widget communication process according to an embodiment of the present application;
FIG. 8 is a schematic diagram of a widget development process according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of a server according to an embodiment of the present application.
Detailed Description
The present application is described below based on examples, but the present application is not limited to only these examples. In the following detailed description of the present application, certain specific details are set forth in detail. It will be apparent to one skilled in the art that the present application may be practiced without these specific details. Well-known methods, procedures, components and circuits have not been described in detail so as not to obscure the present application.
Further, those of ordinary skill in the art will appreciate that the drawings provided herein are for illustrative purposes and are not necessarily drawn to scale.
Unless the context clearly requires otherwise, throughout the description and the claims, the words "comprise", "comprising", and the like are to be construed in an inclusive sense as opposed to an exclusive or exhaustive sense; that is, what is meant is "including, but not limited to".
In the description of the present application, it is to be understood that the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. In addition, in the description of the present application, "a plurality" means two or more unless otherwise specified.
Fig. 2 is a schematic structural diagram of application system development according to an embodiment of the present application. As shown in fig. 2, the application system 2 includes N widgets (N is 1 or more). Widgets (Web widgets, widgets for short) are mainly used as the front end of Web2.0 services or internet contents. The widget may execute independently on the HTML-based web.
When an application system is developed, a development project is divided into different modules according to business functions, and each functional module is realized by one or more widgets. Therefore, when the application system is developed, all the functional modules are coupled in a low mode, and the development efficiency of the application system is improved.
Fig. 3 is a flowchart of a widget management method according to an embodiment of the present application. As shown in fig. 3, in step S100, an identification of at least one widget is obtained in response to a first instruction of a user. Specifically, after a user loads a webpage, the widget to be loaded is marked in the widget identification list according to own requirements, and the application system acquires the identification of the marked widget according to a first instruction of the user.
In the embodiment of the application, the user marks different widgets in the widget identification list to load the different widgets to the webpage, so that the user can define the webpage by himself.
In step S200, the web service unit is traversed to query the dom object of the widget according to the acquired identifier of the widget. Wherein the dom object of the widget is pre-registered in the web service unit by the widget. That is, when a new widget is added, the widget is registered in the web service unit in the form of a dom object, and the js file of the widget and the file name and path of the css widget are added to the xml configuration file of the application system. The html file of the widget comprises the content of the widget and determines the structure of a dom object of the widget, the js file of the widget determines the interactive logic of the widget, and the css file of the widget determines the rendering style of the widget.
The structure of the dom object determined by the html file of the widget is shown in fig. 5, and the dom object reconstructs the html file in the form of a file tree. Wherein, the whole html file is a file node (i.e. the root node of the file tree). Each html tag is an element node. The text contained in the html element is a text node. Each html attribute is an attribute node. The annotations belong to annotation nodes. The nodes all have a hierarchical relationship with each other. All nodes in the Html file constitute a file tree (or node tree). Each element, attribute, text, etc. in the Html file represents a node in the tree. The tree starts at the file node and continues to extend branches therefrom until all text nodes at the lowest level of the tree.
For example the following html document:
all the nodes have a relationship with each other. For example, the parent nodes of < head > and < body > are all < html > nodes, and the text node "Hello world! The parent node of is the < p > node.
Items on a page can be added, removed, changed, or rearranged conveniently through the dom object structure tree.
In step S300, the widget is loaded into the web page according to the dom object of the widget.
Wherein, step S300 further comprises steps S310-S320. As shown in fig. 4, in step S310, a dom object of the widget is read in the application service unit and loaded to the web page. Wherein the dom object of the widget is pre-registered in the web service unit by the widget.
In step S320, an xml configuration file of the application system is read to load the js file and the css file of the widget to the web page. The xml configuration file of the application system includes the file names and paths of js files and css files of the widget.
The widget management method according to the embodiment of the application further includes step S400, and in step S400, the application system responds to the second instruction of the user to store the widget combination loaded in the current webpage as the widget template in the local storage. That is, the user can store the widget combinations frequently browsed as widget templates in the local storage, and when the widgets are loaded later, the widgets do not need to be marked in the widget identification list one by one, and only the widget templates in the local storage need to be loaded. The widget template comprises the identification of each widget in the widget combination and the like.
In summary, according to the embodiment of the application, at least one widget is loaded into the webpage according to the instruction of the user, so that the user can dynamically load the widget according to the requirement, and the webpage is customized by the user. And the development of the application system is carried out by adopting the widgets, so that all the functional modules are low in coupling, and the development efficiency and the usability of the application system are improved.
Fig. 6 is a flowchart of a widget communication method according to an embodiment of the present application. Fig. 7 is a schematic structural diagram of a widget communication process according to an embodiment of the present application. The widget management method according to the embodiment of the application further includes step S500, and in step S500, different widgets communicate with each other through a communication module.
Wherein, step S500 includes steps S510-S540. As shown in fig. 6, in step S510, a trigger instruction for a first function of a first widget is acquired. The trigger instruction includes a parameter for executing a second function of the corresponding second widget.
In step S520, the communication identifier in the first function is traversed in the communication module to obtain a second function of the second widget corresponding to the communication identifier. Wherein the communication identifier is pre-registered in the communication module by the second widget. The communication module manages all communication identifiers in a unified manner.
In step S530, control transfers the parameters included in the trigger command from the first widget to the second widget.
In step S540, a second function is called back based on the parameters included in the trigger instruction.
It should be understood that the first function and the second function are a pair of callback functions. Callback functions in the computer domain refer to references to a piece of executable code that are passed to other code through function parameters. As shown in fig. 7, the on function and the send function are a pair of callback functions. In the application system, the widget 73 registers the communication identification key1 in the communication module 72 by an on function. When a matching on-function is called back, the communication identification key1 specifies that the widget 73 performs a preconfigured activity function 1. It should be understood that the communication identities correspond one-to-one to the specified activities. Similarly, the widget 74 registers the communication identifiers key2 and key5 with the communication module 72 through an on function. When a matching on-function is called back, the communication identification keys 2 and key5 specify that the widget 74 perform the preconfigured activity functions 2 and 5, respectively. It should be understood that the send function and the on function are matched by the communication identifier. When the send function in the widget 71 is triggered by receiving the trigger instruction, the communication identifier key1 is traversed in the communication module 72 according to the communication identifier key1 in the send function to obtain the on function in the widget (widget 73 in fig. 7) corresponding to the communication identifier key 1. The application system control widget 71 transmits the parameters in the trigger instruction to the widget 73. The widget 73 callbacks the activity function1 in the execution on function according to the received parameters. The communication between the widget 71 and the widget 73 is completed, so that the interaction between the widget 71 and the widget 73 is realized under the condition that the coupling degree is low.
For example, in the foreign exchange application system, a "market situation" widget, a "trend graph" widget, and the like are included. Wherein, the 'trend graph' widget can query the corresponding transaction trend graph according to different currency pairs, products and period combinations. The trend graph widget registers the communication identifier corresponding to the trend graph query activity in the communication module in advance through an on method. When a send function in the 'market situation' widget receives a trigger instruction, the communication module searches the communication identifier matched with the communication identifier in the send function in a traversing mode to obtain the on function of the corresponding widget. If the corresponding widget is a "trend graph" widget, the "market situation" widget transmits data such as a corresponding currency pair, product and term combination to the "trend graph" widget. And (3) calling back the on function in the trend chart widget to execute a trend chart query activity according to the corresponding data such as currency pairs, product and term combinations and the like, and displaying the trend chart to be queried in a webpage.
In the embodiment of the application, the callback function is adopted, so that the interaction between the widgets can be conveniently and quickly carried out in the low coupling process.
The widget management method according to the embodiment of the application further includes step S600, and in step S600, a new widget is added. Specifically, a dom object of a new widget is registered in the web service unit. And adding the identification of the new widget in the widget identification list. And adding the file names and paths of the js file and the css file of the new widget in the xml configuration file of the application system.
Fig. 8 is a schematic diagram of a widget development process according to an embodiment of the present application. As shown in fig. 8, a developer downloads a widget development template in the unified application system npm repository, npm is a package management tool for storing different package packages and performing version management. The widget development template comprises a packaging tool, a test operation environment, framework dependency configuration and the like. The packaging tool can uniformly package various files obtained by different development modes into js files and css files which can be directly identified and operated by the browser. The packaging tool may be a module packager such as a webpack. The test operation environment comprises a debugging basic file, a code checking tool and the like. The framework dependency configuration is used for reference dependency of corresponding versions of each widget when integration is needed.
And the developer writes service codes in the widget development template to realize the service function of the widgets and registers the widgets into the webpage service unit in the form of dom objects. And unit testing of the widget is carried out in the browser through a testing running environment provided by the development template. After the widget test is finished, compiling the widget through a packaging tool and the like to obtain a js file and a css file, and adding the file names and the paths of the js file and the css file to an xml configuration file of the application system. The application system loads different widgets by reading the xml configuration file in the web service unit and the application system.
In the embodiment of the application, different widgets are developed by adopting the development template, and the development of the widgets is subjected to normative constraint, so that developers only need to concentrate on the development of application logic. Developers do not interfere with each other and do not depend on each other when developing different widgets, and can test a single widget, so that the development efficiency is improved. Meanwhile, the application system is provided to carry out unified management and maintenance on all the widgets, the integrity of the application system is kept, the addition of new widgets has no influence on the original widgets, and the usability of the application system is improved.
Fig. 9 is a schematic structural diagram of a server according to an embodiment of the present application. The server shown in fig. 9 is a general-purpose data processing device comprising a general-purpose computer hardware structure including at least a processor 91 and a memory 92. The processor 91 and the memory 92 are connected by a bus 93. The memory 92 is adapted to store instructions or programs executable by the processor 91. The processor 91 may be a stand-alone microprocessor or may be a collection of one or more microprocessors. Thus, the processor 91 implements processing of data and control of other devices by executing instructions stored by the memory 92 to perform the method flows of the embodiments of the present application as described above. The bus 93 connects the above components together, and also connects the above components to a display controller 94 and a display device and an input/output (I/O) device 95. Input/output (I/O) devices 95 may be a mouse, keyboard, modem, network interface, touch input device, printer, and other devices known in the art. Typically, the input/output devices 95 are coupled to the system through an input/output (I/O) controller 96.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, apparatus (device) or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may employ a computer program product embodied on one or more computer-readable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations of methods, apparatus (devices) and computer program products according to embodiments of the application. It will be understood that each flow in the flow diagrams can be implemented by computer program instructions.
These computer program instructions may be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows.
These computer program instructions may also be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows.
The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (9)
1. A widget management method, comprising:
acquiring the identification of at least one widget in response to a first instruction of a user;
traversing a webpage service unit according to the identification of the widget to inquire a dom object of the widget, wherein the dom object is registered in the webpage service unit in advance by the widget;
loading the widget into a webpage according to the dom object of the widget;
loading the widget into a webpage according to the dom object of the widget comprises:
reading a dom object of the widget in the webpage service unit and loading the dom object to a webpage;
reading an xml configuration file of an application system to load a js file and a css file of the widget to a webpage;
wherein the xml configuration file of the application system comprises the file names and paths of the js file and the css file of the widget.
2. The widget management method according to claim 1, characterized in that the method further comprises:
and responding to a second instruction of the user to store the widget combination loaded in the current webpage as a widget template in the local storage.
3. The widget management method according to claim 2, wherein obtaining an identification of at least one widget in response to a user instruction comprises:
responding to a user instruction to load the corresponding widget template from a local storage to acquire an identifier of at least one widget; or
And acquiring the identification of at least one widget from a widget identification list in response to a user instruction, wherein the widget identification list comprises the identifications of all registered widgets.
4. The widget management method according to claim 1, characterized in that the method further comprises:
and different widgets communicate with each other through the communication module.
5. The widget management method according to claim 4, wherein the communication between different widgets through the communication module comprises:
acquiring a trigger instruction of a first function of a first widget;
traversing in the communication module according to the communication identifier in the first function to obtain a second function of a second widget corresponding to the communication identifier;
controlling the transmission of parameters contained in the trigger instruction from the first widget to the second widget;
callback the second function based on the parameter;
wherein the communication identifier is pre-registered in the communication module by the second widget.
6. The widget management method according to claim 1, characterized in that the method further comprises:
a new widget is added.
7. The widget management method according to claim 6, wherein adding a new widget includes:
registering a dom object of the new widget in the web service unit;
adding the new widget identifier to the widget identifier list;
and adding the file names and paths of the js file and the css file of the new widget in the xml configuration file of the application system.
8. A server comprising a memory and a processor, wherein the memory is configured to store one or more computer instructions that are executed by the processor to implement the method of any one of claims 1-7.
9. A computer-readable storage medium on which computer program instructions are stored, which, when executed by a processor, implement the method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810199371.5A CN108399086B (en) | 2018-03-12 | 2018-03-12 | Widget management method, server and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810199371.5A CN108399086B (en) | 2018-03-12 | 2018-03-12 | Widget management method, server and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108399086A CN108399086A (en) | 2018-08-14 |
| CN108399086B true CN108399086B (en) | 2021-07-09 |
Family
ID=63092727
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810199371.5A Active CN108399086B (en) | 2018-03-12 | 2018-03-12 | Widget management method, server and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108399086B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111176620B (en) * | 2019-12-26 | 2023-08-22 | 上海杰狮信息技术有限公司 | Map application rapid construction method and system based on data driving |
| CN111782248B (en) * | 2020-07-10 | 2023-09-19 | 上海淇毓信息科技有限公司 | Updating method and device of terminal application and electronic equipment |
| CN112287255B (en) * | 2020-07-13 | 2024-02-09 | 上海柯林布瑞信息技术有限公司 | Page construction method and device, computing equipment and computer readable storage medium |
| CN114090100A (en) * | 2020-08-04 | 2022-02-25 | 北京珠穆朗玛移动通信有限公司 | Method for dynamically loading widget content and related device |
| CN113127091A (en) * | 2021-03-17 | 2021-07-16 | 北京达佳互联信息技术有限公司 | Widget display method, device, equipment, storage medium and program product |
| CN114780164B (en) * | 2022-02-28 | 2023-04-25 | 深圳开源互联网安全技术有限公司 | Method and system for screening webpage information based on browser plug-in |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102253946A (en) * | 2010-05-20 | 2011-11-23 | 腾讯科技（北京）有限公司 | Lua script interactive information-based method, Web engine and embedded terminal |
| CN102339282A (en) * | 2010-07-16 | 2012-02-01 | 阿里巴巴集团控股有限公司 | Method and device for controlling web widget display |
| WO2012083006A1 (en) * | 2010-12-16 | 2012-06-21 | Rovi Solutions Corporation | Browser integration for a content system |
| CN103853812A (en) * | 2012-11-30 | 2014-06-11 | 国际商业机器公司 | Method and system for providing web page |
| CN104881355A (en) * | 2014-02-27 | 2015-09-02 | 国际商业机器公司 | Method and system for testing test coverage |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110047449A1 (en) * | 2009-08-23 | 2011-02-24 | Bank Of America Corporation | Widget Framework |
| CN105207989B (en) * | 2015-08-12 | 2018-10-09 | 中国南方电网有限责任公司 | A kind of work system and its control method of various dimensions user |
| CN106909366A (en) * | 2017-01-04 | 2017-06-30 | 乐视控股（北京）有限公司 | The method and device that a kind of widget shows |
| CN106886435A (en) * | 2017-01-04 | 2017-06-23 | 乐视控股（北京）有限公司 | The loading method and device of widget |
-
2018
- 2018-03-12 CN CN201810199371.5A patent/CN108399086B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102253946A (en) * | 2010-05-20 | 2011-11-23 | 腾讯科技（北京）有限公司 | Lua script interactive information-based method, Web engine and embedded terminal |
| CN102339282A (en) * | 2010-07-16 | 2012-02-01 | 阿里巴巴集团控股有限公司 | Method and device for controlling web widget display |
| WO2012083006A1 (en) * | 2010-12-16 | 2012-06-21 | Rovi Solutions Corporation | Browser integration for a content system |
| CN103853812A (en) * | 2012-11-30 | 2014-06-11 | 国际商业机器公司 | Method and system for providing web page |
| CN104881355A (en) * | 2014-02-27 | 2015-09-02 | 国际商业机器公司 | Method and system for testing test coverage |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108399086A (en) | 2018-08-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108399086B (en) | Widget management method, server and computer readable storage medium | |
| US10162738B2 (en) | System, method, and computer readable medium for universal software testing | |
| CA2675332C (en) | Framework for automatically merging customizations to structured code that has been refactored | |
| Pautasso et al. | The JOpera visual composition language | |
| US20200349236A1 (en) | Generation of dynamic design flows for integrated circuits | |
| CN106293675B (en) | System static resource loading method and device | |
| US20080250394A1 (en) | Synchronizing external documentation with code development | |
| KR20120076334A (en) | Data-driven actions for network forms | |
| JP2012513648A (en) | Debug pipeline | |
| Mallet et al. | MARTE for CPS and CPSoS: present and future, methodology and tools | |
| US20160275126A1 (en) | Accessing and editing virtually-indexed message flows using structured query langauge (sql) | |
| Clem et al. | Static analysis at github: An experience report | |
| Queirós | Kaang: a restful api generator for the modern web | |
| US20160283291A1 (en) | Facilitating communication between software components that use middleware | |
| Aroraa | Building Microservices with. NET Core 2.0: Transitioning monolithic architectures using microservices with. NET Core 2.0 using C# 7.0 | |
| Eng | Combining static and dynamic data in code visualization | |
| Hasanagić et al. | Formalising and Validating the Interface Description in the FMI standard | |
| Clem et al. | Static analysis at GitHub | |
| Aragón Serrano et al. | Applying model-driven paradigm for the improvement of web requirement validation | |
| JP2005250770A (en) | Application-data base linking method | |
| Northwood et al. | Javascript | |
| Telang | MicroProfile Framework–Part 2 | |
| Copei et al. | Improving the Implementation of Microservice-Based Systems with Static Code Analysis | |
| Zhang et al. | Test Case Generation of Composite Web Services Based on Semantic Matching and Condition Recognition | |
| Manta et al. | Description and consistency checking of distributed algorithms in UML models using composite structure and state machine diagrams |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |