CN110968317B - Method and system for automatically generating vue page assembly through UCI/USI configuration file - Google Patents

Method and system for automatically generating vue page assembly through UCI/USI configuration file Download PDF

Info

Publication number
CN110968317B
CN110968317B CN201911212430.9A CN201911212430A CN110968317B CN 110968317 B CN110968317 B CN 110968317B CN 201911212430 A CN201911212430 A CN 201911212430A CN 110968317 B CN110968317 B CN 110968317B
Authority
CN
China
Prior art keywords
configuration file
uci
usi
vue
file
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
Application number
CN201911212430.9A
Other languages
Chinese (zh)
Other versions
CN110968317A (en
Inventor
谈宇刚
何奎
陶洋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangzhou Lubangtong IoT Co Ltd
Original Assignee
Guangzhou Lubangtong IoT Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Guangzhou Lubangtong IoT Co Ltd filed Critical Guangzhou Lubangtong IoT Co Ltd
Priority to CN201911212430.9A priority Critical patent/CN110968317B/en
Publication of CN110968317A publication Critical patent/CN110968317A/en
Application granted granted Critical
Publication of CN110968317B publication Critical patent/CN110968317B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/30Creation or generation of source code
    • G06F8/38Creation or generation of source code for implementing user interfaces
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/71Version control; Configuration management

Abstract

The invention belongs to the technical field of electronics, and discloses a method for automatically generating a vue page component through a UCI/USI configuration file, which comprises the following steps: step 1: configuring a UCI configuration file and a USI configuration file which are used for describing a presentation mode and an interaction mode of a vue page; the UCI configuration file and the USI configuration file store configuration parameters related to a display mode and an interaction mode in a plurality of xml format files; each xml format file corresponds to a vue page; step 2: analyzing a plurality of xml format files in each UCI configuration file and each USI configuration file into a plurality of JSON format data; and step 3: generating a plurality of routing configuration files according to the JSON format data; the user accesses a vue page corresponding to the vue page file according to the route configuration file; and 4, step 4: the vue page file and the routing configuration file are integrated into a vue frame, and a production version is generated through packaging and deployed to a server. The method ensures that the vue page generation, modification, deletion, addition and editing are simple and easy.

Description

Method and system for automatically generating vue page assembly through UCI/USI configuration file
Technical Field
The invention relates to the technical field of electronics, in particular to a method and a system for automatically generating vue page components through a UCI/USI configuration file.
Background
vue is a set of progressive JavaScript frames used to construct user interfaces. Unlike other large frames, vue is designed to be applied layer by layer from bottom to top. vue core library only focuses on the view layer, facilitating integration with third party libraries or existing projects.
Most of the existing vue files are written as vue.
The problems with this mode of operation are: json files related to vue pages of multiple pages have large data volume, and for program writers, the workload is large, and errors are easy to occur. In addition, parameter modification and page addition and deletion related to vue pages often bring very large workload.
Therefore, the technical problem to be solved by the present application is: how to make the generation, modification, deletion and addition of vue pages simple and easy.
Disclosure of Invention
The invention aims to provide a method for automatically generating a vue page component through a UCI/USI configuration file. The method ensures that the generation, modification, deletion, addition and editing of the vue page are simple and easy.
UCI is short for UnifiedConfigurationInterface, which is a uniform configuration interface in XML format;
the USI is the abbreviation of UnifiedserviceInterface, which is a universal service interface in XML format;
vue is one of the leading frames of the mainstream at the present stage.
The specific technical scheme of the invention is as follows:
a method for automatically generating vue page components through a UCI/USI configuration file comprises the following steps in sequence:
step 1: configuring a UCI configuration file and a USI configuration file which are used for describing a presentation mode and an interaction mode of a vue page; the UCI configuration file and the USI configuration file store configuration parameters related to a display mode and an interaction mode in a plurality of xml format files; each xml format file corresponds to a vue page;
and 2, step: analyzing a plurality of xml format files in each UCI configuration file and each USI configuration file into a plurality of JSON format data;
and 3, step 3: generating a plurality of vue page files and a routing configuration file corresponding to vue page files one by one according to the JSON format data; the user accesses a vue page corresponding to the vue page file according to the route configuration file;
and 4, step 4: the vue page file and the routing configuration file are integrated into a vue frame, and a production version is generated through packaging and deployed to a server.
In the method for automatically generating vue page components by using the UCI/USI configuration file, the UCI configuration file includes a first storage parameter, a first current parameter, and a first operating parameter; the USI configuration file comprises a second storage parameter, a second current parameter and a second operation parameter.
In the method for automatically generating vue page assemblies by using the UCI/USI configuration file, the first storage parameter and the second storage parameter are data which are stored in a plurality of xml format files and are required to be managed by the generated management page;
the first current parameter and the second current parameter are a plurality of UCI format text files and USI format files under/var/config/directory, and each UCI format text file and each USI format file correspond to different functions;
the first operating parameter and the second operating parameter are stored in the shared memory, and the first operating parameter and the second operating parameter are data parameters generated by the device during operation, such as a current mac address, a current network environment parameter, and the like, which are dynamically acquired from the device after being released.
The storage parameter is a managed object; the current parameter is a configuration item for generating a management page; the operation parameter is a parameter generated in the operation of the management system, and can influence whether a certain page element and a certain module are displayed, and a corresponding variable and a corresponding judgment logic exist in the configuration item.
In the method for automatically generating vue page components by using the UCI/USI configuration file, the UCI configuration file is used for configuring configuration information of an interactive page; the USI configuration file is used for configuring configuration information of non-interactive pages which are only used for display.
Meanwhile, the invention also discloses a system for realizing the method, which comprises the following modules:
the UCI/USI configuration file generation module comprises: the UCI configuration file and the USI configuration file are used for configuring a presentation mode and an interaction mode for describing a vue page;
an analysis module: the device comprises a module for generating a CI/USI configuration file, a module for generating the USI configuration file, a module for analyzing the UCI configuration file configured by the CI/USI configuration file and a plurality of xml format files in the USI configuration file into a plurality of JSON format data;
vue page file generation module: the JSON data processing module is used for generating vue page files and routing configuration files according to the JSON format data generated by the analysis module;
a production version generation module: the system is used for integrating the vue page file and the routing configuration file generated by the vue page file generation module into the vue framework, packaging, generating a production version and deploying the production version to a server.
Compared with the prior art, the invention has the beneficial effects that:
the invention adopts UCI configuration files and USI configuration files to configure a plurality of pages, each page is generated by a JSON file obtained by converting an xml format file, after the vue display interface is modified to the vue page, the modified configuration parameters can be updated to the xml file, and the updated data can not be lost after the next restart. If the vue pages are to be added or deleted, the corresponding UCI configuration file/USI configuration file and routing configuration file are deleted, the rendering data corresponding to all vue pages do not need to be modified, and the operation convenience is good.
Drawings
FIG. 1 is a block flow diagram of example 1 of the present invention;
FIG. 2 is a block diagram showing the structure of embodiment 3 of the present invention;
fig. 3 is a schematic view of a display interface according to embodiment 2 of the present invention.
Detailed Description
The technical solution of the present invention will be described in further detail with reference to the following embodiments, but the present invention is not limited thereto.
Example 1
As shown in fig. 1, a method for automatically generating vue page components by UCI/USI configuration files includes the following steps in sequence:
step 1: configuring a UCI configuration file and a USI configuration file which are used for describing a presentation mode and an interaction mode of a vue page; the UCI configuration file and the USI configuration file store configuration parameters related to a display mode and an interaction mode in a plurality of xml format files; each xml (extensible markup language, a subset of standard universal markup language, which is a markup language for marking electronic documents with structures) format file corresponds to a vue page;
the UCI configuration file comprises a first storage parameter, a first current parameter and a first operation parameter; the USI configuration file comprises a second storage parameter, a second current parameter and a second operation parameter;
the UCI configuration file is used for configuring configuration information of an interactive page; the USI configuration file is used for configuring configuration information of a page which cannot be interacted and is only used for displaying;
the UCI configuration file and the USI configuration file are relatively similar in file structure.
The UCI configuration file is now taken as an example for explanation:
tissue form of UCI: the UCI parameters have three different organization forms in the system, namely storage parameters, current parameters and operation parameters. The storage parameter is in an xml format, a single independent file, and specific positions are/app/config. The current parameters are a plurality of uci format text files under/var/config/directory, and different functions correspond to different files. The operating parameters are stored in the shared memory and accessed in a manner similar to the environment variables. In order to conveniently obtain the parameters through the script, the operation parameters are simultaneously stored in a/etc/uci directory in the form of a variable file. When the equipment is powered on, the xml file in the Flash is converted into a uci file, and the uci file is loaded into the shared memory. When parameters are modified, only the corresponding content in the uci file is modified, the uci file is converted into an xml format file when storage is executed, and the uci file is loaded into a memory when effective operation is executed.
UCI TAG: IP represents the IP parameter of the LAN function, and IPSec represents the mode parameter of tunnel 1 in the IPSec function. The linked list is fixed with a column member id, and a certain row in the linked list is referred by the linked list id. id is calculated starting from 1, and id may not be continuous.
Introduction of UCI API:
uci _ get: obtaining the appointed parameter value according to tag
uci _ get _ int: uci _ get variant
uci _ match: after obtaining the parameters, judging whether the parameters are matched with the specified values
uci check _ pool: similar to uci _ match, the fix matches "true"
uci _ list _ get _ max _ entry _ num: obtaining the maximum number of rows of the linked list for traversing the whole linked list, and noting that the number of rows is not the current total number of rows
uci _ list _ entry _ empty: determine if the line exists
uci _ list _ get: obtaining the value of a specified column member of a row
uci _ list _ match: after obtaining the value of a certain row of appointed column members, judging whether the value is matched with the appointed value
uci _ init: the function is called only by calling the parameter modification related interface, and the initialization operation is not needed to be executed when the parameter is read
UCI command line facility: the system also provides a command line tool program uci, so that debugging can be conveniently carried out on the shell, and part of complex operations, such as parameter storage and parameter validation, can be uniformly realized. The CLI parameter related command also directly calls the implementation of the tool.
UCI prototype file: all differentiated information is stored in an xml file, and a user does not need to be concerned about the specific implementation process of the UCI system. Each function corresponds to an independent file, so that the APP developed by the SDK can be conveniently integrated into the UCI system. When the system is started, a plurality of uci prototype files are combined into an xml file according to the equipment model and the equipment configuration information, and then a vue page file, a CLI command file, an SNMPMIB and the like are automatically generated according to the xml file.
Introduction of UCI attribute: type: the parameter type, the default type is a character string, and other types include integer, boolean, and enumeration. In addition, special character string types are supported for special checks. Such as built-in types like IP _ ADDR, MAC, etc., or regex types checked using specified regular expressions.
defaults: and generating default parameters according to the default values of the parameters. When the default value is not specified, the type of the character string is default to be null, the integer type is default to be 0, and the default value must be specified by other types.
range: and the value range of the parameter is used for representing the length range of the character string when the character string is of the type, representing the value range when the character string is of the integer type and representing all selectable items when the character string is of the integer type.
max _ entry _ num: the method is used for the linked list, the structure is represented as the linked list type, and the maximum row number is a designated value.
dynamic _ range: dynamic enumeration options are supported, here indicating from which enumeration options are available.
dynamic _ entry _ num: the maximum number of rows of the linked list may be dynamic, indicating where to obtain the maximum number of rows.
empty: under what conditions the parameter is allowed to be empty, "@ true" indicates that it may be empty under any condition. At most a combination of two conditions and not.
unique: column members of some tables have uniqueness and different rows cannot be configured the same, setting this attribute to "true" can support such checks.
edge _ only: rows of some tables cannot be added for deletion, and this property is used to support this property, referred to as cellular.
feature _ disable: when the specified conditions are met, the function fails, the related parameters cannot be configured when the function fails, and the related webpage cannot be generated.
export _ disable: the partial parameters are not derived when the specified condition is satisfied.
save _ only: the indication part is only used for saving and cannot be derived under any condition, and is mainly used for parameters of the user name and the password part.
pattern: used with type regex, represents a regular expression for parameter checking.
pattern _ help: used with type regex for help hints in CLI.
cli _ help: help hints used in CLI are a must-choice for non-leaf members. The following attributes are mostly only used for WEB, and a small part is used for CLI at the same time.
desc: parameter description, word initials capitalized.
range — desc: description of the page drop-down option, since space is used for the delimiter, please use underlining instead if space needs to be displayed.
group: grouping in a WEB page navigation bar.
group _ hide: this packet is hidden when a specified condition is satisfied.
group _ show: the packet is displayed when a specified condition is satisfied.
menu: menu names, typically one menu for each function.
menu _ weight: the order of the menu in the grouping is defined.
menu _ hide: this menu is hidden when a specified condition is satisfied.
menu _ show: this menu is displayed when a specified condition is satisfied.
tab: define a TAB page that displays parameters including all parameters between this TAB and the next TAB definition
tab _ weight: display order of TAB pages
area: the parameters of the area display, which includes all parameters between this area and the next area definition, are displayed in divided areas in the same TAB page. The order of the areas coincides with the parameter order.
area _ help: the page partition may be augmented with help information for providing general help information for certain functions.
area _ hide: this partition is hidden when a specified condition is met.
area _ show: the partition is displayed when a specified condition is satisfied.
shrink: setting to "true" indicates that this partition is in the collapsed state by default.
row _ help: here, a line indicates a line of a WEB page, and each line displays one parameter. The help information for indicating the parameter includes data unit information and the like. The value range is not suggested to be displayed, and the value range is indicated through error prompt after the configuration is in error.
row _ disable: this line grays out when the specified condition is satisfied.
row _ show: this line is displayed when the specified condition is satisfied.
row _ hide: this row is hidden when the specified condition is met.
col _ width: and is used to indicate whether or not the column members of the table are displayed in the preview table, as is the occupied width.
custom _ btn _ desc: description of page buttons for adding buttons in the status page.
custom _ btn _ script: and the script name called by the custom button comprises a path.
The USI profile is similar and not overly elaborated.
Step 2: analyzing a plurality of xml format files in each UCI configuration file and each USI configuration file into a plurality of JSON format data;
JSON formatted data (JSON Object Notation) is a lightweight data exchange format. It stores and represents data in a text format that is completely independent of the programming language, based on a subset of ECMAScript (js specification set by the european computer association). The compact and clear hierarchy makes JSON an ideal data exchange language. The method is easy for human reading and writing, and is also easy for machine analysis and generation, and the network transmission efficiency is effectively improved;
the readability of JSON and xml is similar, xml inherently has very good extensibility, JSON certainly has, and nothing is xml but JSON can be extended. However, JSON battles in the Javascript main field, can store Javascript composite objects, and has the advantage that xml is incomparable.
There are many ways for the xml data file to be parsed into JSON data, for example, converting to JSON data using the method provided by JSON-lib, or using the read (xml) method in xmlseriizer object of JSON-lib.
And step 3: generating a plurality of vue page files and a routing configuration file corresponding to vue page files one by one according to the JSON format data; the user accesses a vue page corresponding to the vue page file according to the route configuration file;
most of the routing configuration files of the vue page files are stored in one routing table, and when a user accesses the corresponding vue page, the corresponding vue page can be linked according to the corresponding routing configuration parameters in the routing table.
And 4, step 4: the vue page file and the routing configuration file are integrated into a vue frame, and a production version is generated through packaging and deployed to a server.
The user can remotely access the server, the production version can be displayed in a website or other forms, the user accesses the vue page according to the IP address, and the corresponding link of the vue page is clicked to achieve the corresponding display interface through the routing configuration parameters.
Example 2
Firewall function module is taken as an example
1. The XML file (i.e. current parameters) in UCI or USI format under system parsing/var/config/directory is as follows:
<cellular desc="firewall"group="Interface"group_weight="10"menu="firewall"
menu _ weight = "30" disable = "devcfg. Cellular _ support = = false" oid = "4"// label is module name, and the rest label parameter is used for describing information such as type, grouping and the like
< SIM desc = "SIM Settings" area = "Advanced Cellular Settings" max _ entry _ num = "2" dynamic u entry num = "status.u.sim _ num =" true "tab =" Cellular "tab _ weight ="0 "id ="1 "// tag name is the current parameter
<id type="int"range="1..2"desc="Index"
area = "General Settings" col _ width = "80" row \ disable = "@ true" oid = "2"/>/parameter id in corresponding configuration file
< card type = "enum" range = "SIM1SIM2" range _ desc = "SIM1SIM2" unique = "true" corresponds to the card parameter in the configuration file, the remaining xml tag elements are used to describe the data type, the range value range, whether unique is oid
desc="SIM Card"row_disable="@true"col_width="80"oid="3"/>
< PHONE _ Number type = "PHONE _ NUM" empty = "@ true" desc = "PHONE Number" col _ width = "140" oid = "4"/>// describe PHONE _ Number parameter, desc
</sim>
</cellular>
The devcfg, cellular _ support in the code is one of the operation parameters that need to be dynamically acquired.
2. The system traverses the analyzed JSON data, generates a corresponding vue component according to the template, and adds firewall route configuration in the router configuration file, as follows:
vue assembly:
< template lang = "jade" >/vue template lang specific template language
div, firewall (v-show = "devcfg, cellular _ support = = false")// parsing out corresponding jade syntax, devcfg, cellular _ support is a dynamically obtained operation parameter, and is used for judging whether the device supports the current module or not
el-tab(tabNam="sim"desc="SIM Settings"area="Advanced Cellular Settings"max_entry_num="2"dynamic_entry_num="status.uci.sim_num"edit_only="true"tab="Cellular"tab_weight="0"oid="1")
Tag of type// tab, the tag parameters are all used to describe the tag attributes, the tag shows the style, and the status
Figure BDA0002298502750000091
/>
Figure BDA0002298502750000101
After the packaging deployment, the interface shown in FIG. 3 can be seen.
And before page loading, requesting the device end to store data/app/config/config.xml through an interface, assigning values to corresponding configuration items, and displaying the current parameters of the device.
And simultaneously, acquiring the operating parameters of the equipment, and performing authority control on the menu and the elements.
And after the user operation is modified, submitting config.
Example 3
Referring to fig. 2, a system for implementing the method of embodiment 1 includes the following modules:
UCI/USI configuration file generation module 1: the UCI configuration file and the USI configuration file are used for configuring a presentation mode and an interaction mode for describing a vue page; the UCI configuration file and the USI configuration file store configuration parameters related to a display mode and an interaction mode in a plurality of xml format files; each xml (extensible markup language, a subset of standard universal markup language, which is a markup language for marking electronic documents with structures) format file corresponds to a vue page; the UCI configuration file comprises a first storage parameter, a first current parameter and a first operation parameter; the USI configuration file comprises a second storage parameter, a second current parameter and a second operation parameter;
the UCI configuration file is used for configuring configuration information of the interactive page; the USI configuration file is used for configuring configuration information of a page which cannot be interacted and is only used for displaying;
the UCI configuration file and the USI configuration file are relatively similar in file structure. Reference is made specifically to example 1.
An analysis module 2: the device comprises a module for generating a CI/USI configuration file, a module for generating the USI configuration file, a module for analyzing the UCI configuration file configured by the CI/USI configuration file and a plurality of xml format files in the USI configuration file into a plurality of JSON format data;
vue page file generation module 3: the JSON data processing module is used for generating vue page files and routing configuration files according to the JSON format data generated by the analysis module;
production version generation module 4: the system is used for integrating the vue page file and the routing configuration file generated by the vue page file generation module into the vue framework, packaging, generating a production version and deploying the production version to a server.
The user can remotely access the server, the production version can be displayed in a website or other forms, the user accesses the vue page according to the IP address, and the corresponding link of the vue page is clicked to achieve the corresponding display interface through the routing configuration parameters.
The above description is only a preferred embodiment of the present invention, and any modifications, equivalents, and improvements made within the spirit and scope of the present invention should be considered within the scope of the present invention.

Claims (5)

1. A method for automatically generating vue page components through a UCI/USI configuration file is characterized by comprising the following steps of:
step 1: configuring a UCI configuration file and a USI configuration file which are used for describing a display mode and an interaction mode of a vue page; the UCI configuration file and the USI configuration file store configuration parameters related to a display mode and an interaction mode in a plurality of xml format files; each xml format file corresponds to a vue page;
step 2: analyzing a plurality of xml format files in each UCI configuration file and each USI configuration file into a plurality of JSON format data;
and step 3: generating a plurality of vue page files and a routing configuration file corresponding to vue page files one by one according to the JSON format data; the user accesses a vue page corresponding to the vue page file according to the route configuration file;
and 4, step 4: the vue page file and the routing configuration file are integrated into a vue frame, and a production version is generated through packaging and deployed to a server.
2. The method of automatically generating vue page components from a UCI/USI configuration file as in claim 1, wherein the UCI configuration file comprises a first storage parameter, a first current parameter, a first operating parameter; the USI configuration file comprises a second storage parameter, a second current parameter and a second operation parameter.
3. The method for automatically generating vue page components by UCI/USI configuration file as claimed in claim 2, wherein the first and second storage parameters are data stored in multiple xml format files about management of the generated management page;
the first current parameter and the second current parameter are a plurality of UCI format text files and USI format files under/var/config/directory, and each UCI format text file and each USI format file correspond to different functions;
the first operating parameter and the second operating parameter are stored in a shared memory, and both the first operating parameter and the second operating parameter are a mac address and a current network environment parameter.
4. The method for automatically generating vue page components from a UCI/USI configuration file as claimed in claim 2, wherein the UCI configuration file is used to configure configuration information of interactable pages; the USI configuration file is used for configuring configuration information of non-interactive pages which are only used for display.
5. A system for implementing the method of any of claims 1-4, comprising the following modules:
the UCI/USI configuration file generation module comprises: the UCI configuration file and the USI configuration file are used for configuring a presentation mode and an interaction mode for describing a vue page;
an analysis module: the device comprises a UCI/USI configuration file generation module, a JSON format data analysis module and a USI configuration file generation module, wherein the UCI configuration file generation module is used for generating a UCI configuration file;
vue page file generation module: the JSON data analysis module is used for generating a vue page file and a route configuration file from a plurality of JSON format data generated by the analysis module;
a production version generation module: the system is used for integrating the vue page file and the routing configuration file generated by the vue page file generating module into the vue framework, and packaging to generate a production version to be deployed to a server.
CN201911212430.9A 2019-12-02 2019-12-02 Method and system for automatically generating vue page assembly through UCI/USI configuration file Active CN110968317B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911212430.9A CN110968317B (en) 2019-12-02 2019-12-02 Method and system for automatically generating vue page assembly through UCI/USI configuration file

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911212430.9A CN110968317B (en) 2019-12-02 2019-12-02 Method and system for automatically generating vue page assembly through UCI/USI configuration file

Publications (2)

Publication Number Publication Date
CN110968317A CN110968317A (en) 2020-04-07
CN110968317B true CN110968317B (en) 2023-04-18

Family

ID=70032502

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911212430.9A Active CN110968317B (en) 2019-12-02 2019-12-02 Method and system for automatically generating vue page assembly through UCI/USI configuration file

Country Status (1)

Country Link
CN (1) CN110968317B (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112083966B (en) * 2020-08-14 2024-02-27 杭州当虹科技股份有限公司 Method for loading remote vue component
CN113821193B (en) * 2020-11-26 2023-09-26 北京京东振世信息技术有限公司 Information generation method, device and storage medium
CN113031947A (en) * 2021-03-05 2021-06-25 苏州帝博信息技术有限公司 Configuration data management method and device used in interface design tool
CN115951882B (en) * 2023-02-16 2023-06-20 中孚安全技术有限公司 Third-party interface format conversion platform and method based on vue

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104125092A (en) * 2013-04-25 2014-10-29 杭州华三通信技术有限公司 Matching method and device of network resource
CN108683740A (en) * 2018-05-18 2018-10-19 烽火通信科技股份有限公司 A kind of method and system of the promotion configuration access speed based on UCI

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8065204B2 (en) * 2005-09-29 2011-11-22 Sony Corporation System and method for software integration and factory deployment
US7953863B2 (en) * 2007-05-08 2011-05-31 Intel Corporation Techniques for timing optimization in wireless networks that utilize a universal services interface
US8990289B2 (en) * 2009-02-27 2015-03-24 Oracle America, Inc. Server based framework for improving Ajax performance
US20130031455A1 (en) * 2011-07-28 2013-01-31 Peter Griffiths System for Linking to Documents with Associated Annotations
US20130031453A1 (en) * 2011-07-28 2013-01-31 Peter Griffiths System for Annotating Documents Served by a Document System without Functional Dependence on the Document System
US11159929B2 (en) * 2017-03-24 2021-10-26 Apple Inc. Scheduling request for further enhanced narrowband internet of things (feNB-IoT)
CN108052548A (en) * 2017-11-27 2018-05-18 深圳市前海圆舟网络科技股份有限公司 Method, system and the terminal device that a kind of webpage creates
CN108491195A (en) * 2018-01-26 2018-09-04 海尔优家智能科技(北京)有限公司 Equipment controls page generation method and system
CN110308908B (en) * 2018-03-20 2023-07-18 北京小米移动软件有限公司 Method and device for generating configuration file of application and displaying application page and storage medium
CN110502232B (en) * 2018-05-16 2023-10-10 杭州海康威视***技术有限公司 Routing address configuration method and device for page application
CN108958736B (en) * 2018-07-20 2022-04-15 北京三快在线科技有限公司 Page generation method and device, electronic equipment and computer readable medium
CN109325205A (en) * 2018-09-25 2019-02-12 中国建设银行股份有限公司 A kind of page generation method and device
CN110297636B (en) * 2019-07-03 2023-06-27 广州鲁邦通物联网科技股份有限公司 Page automatic generation and parameter management method, system and device based on page configuration file

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104125092A (en) * 2013-04-25 2014-10-29 杭州华三通信技术有限公司 Matching method and device of network resource
CN108683740A (en) * 2018-05-18 2018-10-19 烽火通信科技股份有限公司 A kind of method and system of the promotion configuration access speed based on UCI

Also Published As

Publication number Publication date
CN110968317A (en) 2020-04-07

Similar Documents

Publication Publication Date Title
CN110968317B (en) Method and system for automatically generating vue page assembly through UCI/USI configuration file
US10592319B2 (en) API notebook tool
US9589014B2 (en) Creating data in a data store using a dynamic ontology
CN100511129C (en) Multilanguage-supporting user interface realizing method and apparatus thereof
JP7316349B2 (en) Customizable enterprise automation test framework
FI118311B (en) Procedure, data processing apparatus, computer software product and arrangements for processing electronic data
CN112114807A (en) Interface display method, device, equipment and storage medium
US20150089469A1 (en) Computer-aided development of native mobile application code
US8918710B2 (en) Reducing programming complexity in applications interfacing with parsers for data elements represented according to a markup language
CN110297636A (en) A kind of automatic production of HTML page and parameter management method based on page configuration file, system and device
US7158907B1 (en) Systems and methods for configuring a test setup
US20150278190A1 (en) Web server system, dictionary system, dictionary call method, screen control display method, and demonstration application generation method
CN111596902B (en) Method, device, equipment and storage medium for building front-end and back-end development framework
CN111338637A (en) Code generation method and device
CN114036425A (en) Page access method, client, server and system
CN111158687B (en) Interface generation method and device of JAVA plugin, computer equipment and storage medium
CN114371845A (en) Form generation method and device
US20060085492A1 (en) System and method for modifying process navigation
CN103473431B (en) A kind of method of the on-line debugging PHP program of lightweight
CN113342399A (en) Application structure configuration method and device and readable storage medium
CN112199335A (en) Generation method and generation system of operation log
CN111078337A (en) Pattern adjusting method, system and computer readable storage medium
CN110311819A (en) Automatic production of HTML page and MIBs table generating method, management method, equipment end and management system based on page configuration file
CN109597845A (en) Report configuration method, device, computer equipment and storage medium
CN112732254B (en) Webpage development method, webpage development device, computer equipment and storage medium

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
CB02 Change of applicant information
CB02 Change of applicant information

Address after: 511356 Room 501, building 2, No. 63, Yong'an Avenue, Huangpu District, Guangzhou, Guangdong

Applicant after: Guangzhou lubangtong Internet of things Technology Co.,Ltd.

Address before: 510653 3rd floor, building F, kehuiyuan, 95 Daguan Road, Tianhe District, Guangzhou City, Guangdong Province

Applicant before: GUANGZHOU ROBUSTEL TECHNOLOGIES Co.,Ltd.

GR01 Patent grant
GR01 Patent grant