CN113515281A - Method for realizing user-defined interface of mobile application - Google Patents
Method for realizing user-defined interface of mobile application Download PDFInfo
- Publication number
- CN113515281A CN113515281A CN202110315222.2A CN202110315222A CN113515281A CN 113515281 A CN113515281 A CN 113515281A CN 202110315222 A CN202110315222 A CN 202110315222A CN 113515281 A CN113515281 A CN 113515281A
- Authority
- CN
- China
- Prior art keywords
- interface
- service
- custom
- user
- mobile application
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 36
- 238000011161 development Methods 0.000 claims abstract description 20
- 238000002347 injection Methods 0.000 claims abstract description 13
- 239000007924 injection Substances 0.000 claims abstract description 13
- 238000013499 data model Methods 0.000 claims description 15
- 238000012545 processing Methods 0.000 claims description 10
- 230000008520 organization Effects 0.000 claims description 4
- 230000001960 triggered effect Effects 0.000 claims description 3
- 230000000875 corresponding effect Effects 0.000 claims 6
- 238000012986 modification Methods 0.000 abstract description 4
- 230000004048 modification Effects 0.000 abstract description 4
- 230000008859 change Effects 0.000 abstract description 3
- 230000007246 mechanism Effects 0.000 description 12
- 230000000007 visual effect Effects 0.000 description 5
- 238000013461 design Methods 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000000712 assembly Effects 0.000 description 1
- 238000000429 assembly Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
-
- 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/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
-
- 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/451—Execution arrangements for user interfaces
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Human Computer Interaction (AREA)
- Data Mining & Analysis (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a method for realizing a user-defined interface of a mobile application. The method aims to solve the problems that the prior art can only change the appearance of an application interface, cannot expand a service model according to the self requirement and has poor maintainability; the invention comprises the following steps: s1: adding pre-registered service information through a mobile application custom interface designer, adjusting interface layout and generating a custom interface; s2: the enterprise number is respectively corresponding to different application server URLs through service registration, service discovery and service routing, and the request of the mobile application is routed to the corresponding application server URL to obtain data; s3: and the user individuates a user-defined interface, and self-defines and expands the service logic through self-defined script injection. Performing secondary development customization on the user interface during operation, and expanding new user-defined interface information for different organizations and different roles; by injecting the custom script, the expansion of service logic is completed, the modification is convenient, the service function is rapidly grounded, and the maintainability is improved.
Description
Technical Field
The invention relates to the field of user-defined interfaces, in particular to a user-defined interface implementation method for mobile application.
Background
The existing mobile application user interface implementation mode is generally written by a fixed source code writing mode, local information of a user interface is packaged into metadata, the metadata information of the user interface is stored in an application server database, the metadata information of the user interface is loaded from a server and is rendered on the interface when the application interface is opened, generally, the implementation mode is only limited to personalized display similar to a recommendation system, and a user-defined interface can be realized in a mobile application complex form layer (for example, interfaces with a plurality of detail forms at the head of a form and the like).
A conventional deployment mode is that one mobile application client corresponds to one software server; when the number of customers using the software is large and some users require that the server of the software is deployed on their private servers, the deployment manner of the application client and the server in one-to-one correspondence necessitates that a large number of repeated applications are deployed in the mobile application store, thereby increasing the cost of installing, upgrading and updating the mobile application in the application store.
The drawbacks of these mobile application user interface implementations are: when the service changes and the user interface needs to be adjusted, the source code must be modified, and software must be reissued and deployed, so that the maintainability is poor; when there are more clients using the mobile application and the requirements of clients with different roles on the user interface layout are inconsistent, the mobile application development team must maintain different source code branches for different clients, which increases the development and testing costs; when a client is a large enterprise with a group type or multi-organization architecture and the requirements of each service unit and organization on the user interfaces of the same service point are inconsistent, a fixed source code compiling mode is adopted to deploy a mobile application which only supports one set of user interfaces and cannot meet the service scene of the multi-group architecture; the multi-tenant SaaS software system deploys one mobile application, different tenants require to display application scenes of different user interfaces, and the implementation mode of the fixed writing source code cannot be met.
For example, a method for customizing an application interface based on an Android system disclosed in chinese patent literature, which is disclosed in publication No. CN103377051B, includes the following steps: s1, selecting an interface to be modified by a user, and enabling the interface to enter an editing mode; s2, a user self-editing interface; s3, the user determines to save the edited result, and the new layout file is saved in the xml format; and S4, restarting the interface, judging whether the user sets a user-defined interface, if not, loading the interface by using a default layout file, if so, judging whether the user-defined layout file exists, if so, using the user-defined layout file, otherwise, still using the default layout file. The scheme can only change the appearance of the application interface, cannot expand the service model according to the self requirement, and has poor maintainability because the source code must be modified, the software must be re-released and deployed when the service is changed.
Disclosure of Invention
The invention mainly solves the problems that the prior art can only change the appearance of an application interface, cannot expand a service model according to the self requirement, and has poor maintainability because source codes are modified, software is released and deployed again when the service is changed; providing a method for realizing a custom interface of a mobile application, and expanding a service model by adding a custom field during running; through a service registration mechanism, a service discovery mechanism and a service routing mechanism, the mobile application store can be provided with one mobile application, so that the mobile application store can support the connection to a plurality of application service terminals deployed at different positions, and different user-defined interface information can be obtained from the plurality of different application service terminals; and the maintainability is improved.
The technical problem of the invention is mainly solved by the following technical scheme:
a method for realizing a custom interface of a mobile application comprises the following steps:
s1: adding pre-registered service information through a mobile application custom interface designer, adjusting interface layout and generating a custom interface;
s2: the enterprise number is respectively corresponding to different application server URLs through service registration, service discovery and service routing, and the request of the mobile application is routed to the corresponding application server URL to obtain data;
s3: and the user individuates a user-defined interface, and self-defines and expands the service logic through self-defined script injection.
According to the scheme, the user interface is developed and customized secondarily during operation, the user field expansion service model is added, the user can customize the interface of the mobile application in a personalized mode, and new user-defined interface information is expanded for different organizations and different roles. By injecting the custom script, the expansion of the service logic is completed, software is released and deployed again without modifying the source code, the modification is convenient, and the maintainability is improved. Through a service registration mechanism, a service discovery mechanism and a service routing mechanism, the application service terminals connected to a plurality of different positions for deployment can be supported only by installing one mobile application in a mobile application store, different user-defined interface information is obtained from the plurality of different application service terminals, and therefore the private deployment mode of multiple enterprise users can be supported only by deploying one mobile application; the method has the advantages of quickly deploying new functions, quickly responding to user requirements, realizing agile development of applications and improving user satisfaction.
Preferably, the step S1 includes the following steps:
s11: the method comprises the following steps of defining a service model, and performing service type registration, data table information registration and field information registration in a metadata registration module;
s12: according to the service model definition content, a development interface designer in the metadata registration module automatically generates a mobile application user interface metadata model in a standard format;
s13: the mobile application user-defined interface designer loads a mobile application user interface element data model, adjusts the interface layout and then stores the interface layout to generate a user-defined interface;
s14: and establishing a relationship between the information of the user-defined interface stored by the mobile application user-defined interface designer and a service unit, an organization or a role.
The mobile application custom interface designer loads a mobile application user interface data model and custom fields, drags the custom fields to corresponding container assemblies in a visual mode, adjusts the interface layout position in the visual mode, modifies the attributes of related UI controls, obtains a new custom interface after storage, and finishes the design of the custom interface.
Preferably, the service type registration includes registering service codes and service name information and storing the service codes and the service name information into a service type data table; registering data table information, including registering the name of the data table contained in the service type into a service type containing table; and field information registration, including registering the field information of the service data table into a column information metadata table. And registering metadata to finish the preparation work in advance of the user-defined interface design.
Preferably, the field information registration further comprises custom field registration, and the custom field registration binds the custom field to the UI control of the corresponding attribute; the UI control comprises a container component and a basic control, wherein the container component comprises a form container component and a form component; the basic controls are form controls and comprise a text control, a digital control, a pull-down selection control, a date control and a basic data selection control. The custom field expansion business model can be added during running, the control attributes bound by the custom field correspond, checking is carried out during dragging, only digital controls can be bound like numerical value type fields, only date controls can be bound to date type fields, and error reporting during running caused by invalid binding is prevented.
Preferably, the step S2 includes the following steps:
s21: the service registration distributes an enterprise number for each private deployment enterprise client in a registration center database, and registers the URL address of an application server end of the enterprise private deployment;
s22: inputting an enterprise number when a terminal user logs in a mobile application, and acquiring an application server URL address corresponding to the enterprise number from a registry database through service discovery;
s23: all data requests of the mobile application are sent to the URL address through a service route; the data request comprises the user-defined interface information.
Through a service registration mechanism, a service discovery mechanism and a service routing mechanism, the application service terminals connected to a plurality of different positions for deployment can be supported only by installing one mobile application in a mobile application store, different user-defined interface information is obtained from the plurality of different application service terminals, and therefore the private deployment mode of multiple enterprise users can be supported only by deploying one mobile application; in the multi-tenant mode, different interfaces can be displayed for different tenants by only deploying one application on the shelf in a mobile application store; the method has the advantages of quickly deploying new functions, quickly responding to user requirements, realizing agile development of applications and improving user satisfaction.
Preferably, the step S3 includes the following steps:
s31: selecting pre-registered service type information, and newly generating a user-defined interface scheme; the two attributes of the custom interface information and the script information of the newly generated custom interface scheme are null;
s32: the method comprises the steps that a mobile application user interface data model and custom field information are obtained and dragged to a custom interface in a dragging mode, so that a user personalized custom interface is realized;
s33: by writing the processing function codes of the corresponding events of the control, when the control clicks or data changes, the corresponding events are triggered, the processing function codes are called, and script injection is completed.
According to the scheme, after the application deployment is put on shelf, the interface layout is adjusted during operation, and the interface can be adjusted at any time by using an agile development method, so that the efficiency of development and deployment is greatly improved, the response time of user requirements is greatly shortened, and the user satisfaction is improved. The method can avoid the overlong auditing period of the application store from one week to two weeks, can continuously release new functions more quickly and effectively, reduces the communication cost, and saves more than two times of software development and maintenance cost. The user-defined interface script injection method expands the service logic boundary of the user-defined interface and can realize the quick landing of service functions.
Preferably, the step S32 includes the following steps:
opening a custom interface scheme in a custom interface designer, and sending two requests to a server side by the custom interface designer:
the method comprises the steps that 1, a mobile application user interface element data model in a standard format is obtained from a server according to the service type;
request 2, according to the service type, the self-defined field information contained in the service type is searched out in a correlation manner from a pre-registered service type containing table and a list information metadata table;
after a mobile application user interface element data model in a standard format and a custom field are successfully obtained from a server, loading and displaying the data in nodes through a mobile application custom interface designer;
and designing an interface, selecting a certain custom field, dragging the selected field to a custom interface in a dragging mode, checking whether the table name of the custom field is consistent with the data table name bound with the currently displayed container component, and prompting that dragging is not allowed if the table name is inconsistent with the data table name bound with the currently displayed container component.
According to the scheme, after application deployment is put on shelf, the interface layout is adjusted during operation, and the interface can be adjusted at any time by using an agile development method, so that the efficiency of development and deployment is greatly improved, the response time of user requirements is greatly shortened, and the user satisfaction is improved.
Preferably, the step S33 includes the following steps:
selecting a user-defined interface scheme, and compiling script codes in a user-defined script interface;
storing the custom script code into a script information field of the custom interface scheme;
and simultaneously, generating a script file with a suffix name js under a certain folder under the individualinfo path of the server, wherein the specific path rule is as follows: individualinfo/service type code/custom interface scheme code js;
when the service interface is opened, the path of the self-defined script file is mounted on the script tag of the page according to the read path of the self-defined script file, and a javascript engine of the browser loads the self-defined script content according to the URL defined by the script tag to complete injection.
The user-defined interface script injection method expands the service logic boundary of the user-defined interface and can realize the quick landing of service functions.
The invention has the beneficial effects that:
1. by carrying out secondary development and customization on the user interface during operation and adding the user-defined field to expand the service model, the user can personally define the interface of the mobile application and expand new user-defined interface information for different organizations and different roles.
2. By injecting the custom script, the expansion of the service logic is completed, software is not required to be released and deployed again after source codes are modified, the modification is convenient, the service function is rapidly grounded, and the maintainability is improved.
3. Through a service registration mechanism, a service discovery mechanism and a service routing mechanism, the application service terminals connected to a plurality of different positions for deployment can be supported only by installing one mobile application in a mobile application store, different user-defined interface information is obtained from the plurality of different application service terminals, and therefore the private deployment mode of multiple enterprise users can be supported only by deploying one mobile application; the method has the advantages of quickly deploying new functions, quickly responding to user requirements, realizing agile development of applications and improving user satisfaction.
4. The interface layout is adjusted during operation, and the interface can be adjusted at any time by using an agile development method, so that the efficiency of development and deployment is greatly improved, the response time of user requirements is greatly shortened, and the user satisfaction is improved; the method can avoid the overlong auditing period of the application store from one week to two weeks, can continuously release new functions more quickly and effectively, reduces the communication cost, and saves more than two times of software development and maintenance cost.
Drawings
FIG. 1 is a flow chart of a method for implementing a custom interface of a mobile application according to the present invention.
Detailed Description
The technical scheme of the invention is further specifically described by the following embodiments and the accompanying drawings.
Example (b):
as shown in fig. 1, the method for implementing a custom interface of a mobile application in this embodiment includes the following steps:
s1: and adding pre-registered service information through a mobile application custom interface designer, adjusting the interface layout and generating a custom interface.
S11: and defining a service model, and performing service type registration, data table information registration and field information registration in a metadata registration module.
In this embodiment, the service type registration, specifically, the information such as the registration service code, the service name, etc. is stored in the service type data table; registering data table information, specifically registering the name of the data table of the service type into a service type containing table; and registering field information, specifically registering the field information of the service data table into a column information metadata table.
S12: and according to the service model definition content, a development interface designer in the metadata registration module automatically generates a mobile application user interface metadata model in a standard format.
In this embodiment, the development interface designer is an auxiliary tool in a development phase, and is configured to load table metadata information and field metadata information of a certain service type, drag and drop a field to a design window in a visual manner, adjust interface layout, set relevant attributes of interface control elements, and issue an interface layout as a standard user interface metadata model, where the model data is in a json format, the first layer is container component information, the second layer is below basic control information in a container component, and the information in the format is displayed on an interface through a rendering rule of the container component in a document interface during running.
After a certain defined service type is selected, entering a development interface designer, loading data sheet information and field information contained in the service type, performing interface layout in a mode of automatically laying out or visually dragging the field to an interface, releasing after the interface layout is completed, generating a mobile application user interface element data model in a standard format, and registering the information of the model in a user-defined interface element data information sheet.
S13: and the mobile application user-defined interface designer loads a mobile application user interface data model, adjusts the interface layout and then stores the interface layout to generate a user-defined interface.
And the custom field registration binds the custom field with the corresponding UI control. And the date type field can only bind the date control, so that the error report in operation caused by invalid binding is prevented.
And the mobile application custom interface designer loads a mobile application user interface data model and custom fields, drags the custom fields to corresponding container components in a visual mode, adjusts the interface layout position in the visual mode, modifies the attributes of the related UI controls, and obtains a new custom interface after storage.
In the embodiment, the container components are form container components and form components; the basic controls are form controls and comprise a text control, a digital control, a pull-down selection control, a date control and a basic data selection control. The UI control properties include properties of "read only", "fill necessary", "hidden", "label color", etc. of the basic control and properties of "label width", "border color", "height" of the container component. After the attributes of the basic control or the container component are modified, attribute value information is temporarily stored in the corresponding node of the control, when a user-defined interface is stored, each node of the component layout structure tree is recursively traversed, and new user-defined interface information is constructed according to the two-layer structure of the standard interface metadata model.
S14: and establishing a relationship between the information of the user-defined interface stored by the user-defined interface designer and a service unit, an organization or a role.
S2: and respectively corresponding the enterprise number to different application server URLs through service registration, service discovery and service routing, and routing the request of the mobile application to the corresponding application server URL to obtain data.
And acquiring the distributed custom interface through the login information of the user and displaying the custom interface in the business document interface.
S21: the service registration allocates an enterprise number to each private deployment enterprise client in a registration center database, and registers the URL address of an application server of the enterprise private deployment.
S22: when a terminal user logs in the mobile application, an enterprise number is input, and an application server URL address corresponding to the enterprise number is obtained from a registration center database through service discovery.
S23: all data requests of the mobile application, including obtaining the user-defined interface information, are sent to the URL address through the service route.
The service route is used for obtaining the address of the service end of the current enterprise number through the service discovery module before the mobile application sends a data request to the service end, and after the 'server placeholder' in the address is replaced, the request can be routed to the correct address of the application service end.
The method comprises the steps that employees of different enterprises download apps of the mobile applications from the same application store, enterprise numbers are input during login, URLs of service terminals corresponding to the enterprise numbers are obtained through service discovery according to the enterprise numbers after login is completed, and requests sent by subsequent apps are all routed to the URLs of the service terminals to obtain data.
Therefore, the method can meet the requirement that only one app is put on shelf and corresponds to a plurality of service terminals of a plurality of enterprise users; each enterprise realizes that different custom interfaces are stored on the server side of the enterprise, and the custom interfaces of the enterprise can be loaded by the staff of the enterprise when the staff are used; if the custom interfaces are distributed according to the organizations in each enterprise and different custom interfaces are distributed by different organizations, the custom interfaces seen by the employees in different organizations in the same enterprise are different.
S3: and the user individuates a user-defined interface, and self-defines and expands the service logic through self-defined script injection.
S31: and selecting the service type information registered in advance, and newly generating a user-defined interface scheme. The two attributes of the custom interface information and the script information of the newly generated custom interface scheme are null.
S32: the data model and the custom field information of the mobile application user interface are obtained and dragged to the custom interface in a dragging mode, so that the user customized interface is personalized.
The steps of the enterprise user personalized user-defined interface are as follows:
and opening the data of the custom interface scheme in the custom interface designer, and sending two requests to the server side by the custom interface designer:
and request 1, acquiring a mobile application user interface element data model in a standard format from a server according to the service type.
After a mobile application user interface element data model in a standard format is successfully obtained from a server side, the model is loaded and displayed in nodes through a user-defined interface designer, the model information is of a two-layer structure, the first layer is container component information, and the second layer is basic control information in a container component.
In this embodiment, the layout of the first container component node is rendered and presented by default; and simultaneously, displaying the related attribute information of the first container component in a list form.
And 2, according to the service type code, associating and searching the self-defined field information contained in the service type from a pre-registered service type containing table and a list information metadata table.
And after the custom field information is successfully acquired from the server, the custom interface designer interface loads and displays the custom field information to be a two-layer tree structure, the first layer of nodes are names of the data table, the second layer of nodes are names of the custom fields under the data table, and the fields contain the bound UI control type information.
And after all the loaded data are displayed, designing an interface, selecting a certain custom field, dragging the selected custom field to a custom interface in a dragging mode, checking whether the table name of the custom field is consistent with the data table name bound to the currently displayed container component or not after dragging is finished, and prompting that dragging is not allowed if the table name is inconsistent with the data table name bound to the currently displayed container component, so that data saved to the rear end are not valid when the randomly dragged field runs.
The position of the node can be changed by dragging, so that the layout of the control is changed; showing the attribute information of the selected control in the current component structure tree in a list form, wherein the attributes of the basic control such as 'read only', 'mandatory', 'hidden' and 'label color' can be modified; the "label width", "border color", "height" of the container assembly may be modified; after the attributes of the basic control or the container component are modified, attribute value information is temporarily stored in a corresponding node of the control in the component layout structure tree, when a user-defined interface is stored, each node of the component layout structure tree is recursively traversed, and new user-defined interface information is constructed according to the two-layer structure of the standard interface metadata model.
And the code-free development is completed through the user-defined interface designer, the adjustment of the user-defined interface layout is completed in a very safe mode, the resetting of the control attribute is completed, and the operation effect of the control is changed.
S33: by writing the processing function code of the corresponding event of the control, when the control clicks or data changes, the corresponding event is triggered, and the event processing function is called to complete script injection.
Through script injection, the steps of self-defining the extended service logic are as follows:
selecting a user-defined interface scheme, and compiling script codes in a user-defined script interface; in this embodiment, the script code is a lifecycle hook function and an event handling function.
The custom script code is stored in the "script information" field of the custom interface schema.
And simultaneously, generating a script file with a suffix name js under a certain folder under the individualinfo path of the server, wherein the specific path rule is as follows: individualinfo/service type code/custom interface scheme code js; for example, a path of a custom script of "user information interface scheme 1" encoded as 000001 is,/individualinfo/userinfo/000001. js, and this path information may be stored in the "custom script path" field of the custom interface scheme data.
When a service interface is opened, reading a path of a self-defined script file according to self-defined interface scheme distribution information, mounting the path of the self-defined script file on a script tag of a page, loading a Javascript engine of a browser to self-defined script content according to a Uniform Resource Locator (URL) defined by the script tag, and loading a life cycle hook function and an event processing function defined by the self-defined script into the context of the Javascript engine of the browser so as to finish injection.
When the control related to the 'lifecycle hook function' or the 'event processing function' has an event, the 'lifecycle hook function' or the 'event processing function' which is loaded into the javascript engine is called, and the service logic of the functions can be operated; these processing functions are run independently and do not affect other existing logic.
It should be understood that the examples are for illustrative purposes only and are not intended to limit the scope of the present invention. Further, it should be understood that various changes or modifications of the present invention may be made by those skilled in the art after reading the teaching of the present invention, and such equivalents may fall within the scope of the present invention as defined in the appended claims.
Claims (8)
1. A method for realizing a custom interface of a mobile application is characterized by comprising the following steps:
s1: adding pre-registered service information through a mobile application custom interface designer, adjusting interface layout and generating a custom interface;
s2: the enterprise number is respectively corresponding to different application server URLs through service registration, service discovery and service routing, and the request of the mobile application is routed to the corresponding application server URL to obtain data;
s3: and the user individuates a user-defined interface, and self-defines and expands the service logic through self-defined script injection.
2. The method for implementing the custom interface of the mobile application according to claim 1, wherein the step S1 comprises the following steps:
s11: the method comprises the following steps of defining a service model, and performing service type registration, data table information registration and field information registration in a metadata registration module;
s12: according to the service model definition content, a development interface designer in the metadata registration module automatically generates a mobile application user interface metadata model in a standard format;
s13: the mobile application user-defined interface designer loads a mobile application user interface element data model, adjusts the interface layout and then stores the interface layout to generate a user-defined interface;
s14: and establishing a relationship between the information of the user-defined interface stored by the mobile application user-defined interface designer and a service unit, an organization or a role.
3. The method of claim 2, wherein the service type registration comprises registering service code and service name information and storing them in a service type data table; registering data table information, including registering the name of the data table contained in the service type into a service type containing table; and field information registration, including registering the field information of the service data table into a column information metadata table.
4. The method for implementing the custom interface of the mobile application according to claim 2 or 3, wherein the field information registration further comprises custom field registration, and the custom field registration binds the custom field to the UI control of the corresponding property; the UI control comprises a container component and a basic control, wherein the container component comprises a form container component and a form component; the basic controls are form controls and comprise a text control, a digital control, a pull-down selection control, a date control and a basic data selection control.
5. The method for implementing the custom interface of the mobile application according to claim 1, wherein the step S2 comprises the following steps:
s21: the service registration distributes an enterprise number for each private deployment enterprise client in a registration center database, and registers the URL address of an application server end of the enterprise private deployment;
s22: inputting an enterprise number when a terminal user logs in a mobile application, and acquiring an application server URL address corresponding to the enterprise number from a registry database through service discovery;
s23: all data requests of the mobile application are sent to the URL address through a service route; the data request comprises the user-defined interface information.
6. The method for implementing the custom interface of the mobile application according to claim 1, wherein the step S3 comprises the following steps:
s31: selecting pre-registered service type information, and newly generating a user-defined interface scheme; the two attributes of the custom interface information and the script information of the newly generated custom interface scheme are null;
s32: the method comprises the steps that a mobile application user interface data model and custom field information are obtained and dragged to a custom interface in a dragging mode, so that a user personalized custom interface is realized;
s33: by writing the processing function codes of the corresponding events of the control, when the control clicks or data changes, the corresponding events are triggered, the processing function codes are called, and script injection is completed.
7. The method for implementing the custom interface of the mobile application as claimed in claim 6, wherein the step S32 comprises the following steps:
opening a custom interface scheme in a custom interface designer, and sending two requests to a server side by the custom interface designer:
the method comprises the steps that 1, a mobile application user interface element data model in a standard format is obtained from a server according to the service type;
request 2, according to the service type, the self-defined field information contained in the service type is searched out in a correlation manner from a pre-registered service type containing table and a list information metadata table;
after a mobile application user interface element data model in a standard format and a custom field are successfully obtained from a server, loading and displaying the data in nodes through a mobile application custom interface designer;
and designing an interface, selecting a certain custom field, dragging the selected field to a custom interface in a dragging mode, checking whether the table name of the custom field is consistent with the data table name bound with the currently displayed container component, and prompting that dragging is not allowed if the table name is inconsistent with the data table name bound with the currently displayed container component.
8. The method for implementing the custom interface of the mobile application as claimed in claim 6, wherein the step S33 comprises the following steps:
selecting a user-defined interface scheme, and compiling script codes in a user-defined script interface;
storing the custom script code into a script information field of the custom interface scheme;
and simultaneously, generating a script file with a suffix name js under a certain folder under the individualinfo path of the server, wherein the specific path rule is as follows: individualinfo/service type code/custom interface scheme code js;
when the service interface is opened, the path of the self-defined script file is mounted on the script tag of the page according to the read path of the self-defined script file, and a javascript engine of the browser loads the self-defined script content according to the URL defined by the script tag to complete injection.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110315222.2A CN113515281A (en) | 2021-03-24 | 2021-03-24 | Method for realizing user-defined interface of mobile application |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110315222.2A CN113515281A (en) | 2021-03-24 | 2021-03-24 | Method for realizing user-defined interface of mobile application |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113515281A true CN113515281A (en) | 2021-10-19 |
Family
ID=78061883
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110315222.2A Pending CN113515281A (en) | 2021-03-24 | 2021-03-24 | Method for realizing user-defined interface of mobile application |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113515281A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114090162A (en) * | 2021-11-24 | 2022-02-25 | 中国建设银行股份有限公司 | Front-end interface display method and related device of multi-tenant system |
| CN114860367A (en) * | 2022-05-07 | 2022-08-05 | 金蝶软件（中国）有限公司 | User interface event processing method, device and system |
| CN114995814A (en) * | 2022-06-07 | 2022-09-02 | 重庆大学 | Method and device for engineering intelligent view layout of application system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101706720A (en) * | 2009-11-23 | 2010-05-12 | 浪潮集团山东通用软件有限公司 | Method for showing interface according to customized information during operation |
| CN110673848A (en) * | 2019-09-30 | 2020-01-10 | 厦门荆艺软件有限公司 | Enterprise information management system configuration platform based on JavaWeb |
| CN110688117A (en) * | 2019-09-30 | 2020-01-14 | 厦门荆艺软件有限公司 | Interface designer and platform based on JavaWeb and page configuration method thereof |
| CN112463124A (en) * | 2020-12-03 | 2021-03-09 | 杭州新中大科技股份有限公司 | System for realizing one-time design thousand-face display based on metadata model |
-
2021
- 2021-03-24 CN CN202110315222.2A patent/CN113515281A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101706720A (en) * | 2009-11-23 | 2010-05-12 | 浪潮集团山东通用软件有限公司 | Method for showing interface according to customized information during operation |
| CN110673848A (en) * | 2019-09-30 | 2020-01-10 | 厦门荆艺软件有限公司 | Enterprise information management system configuration platform based on JavaWeb |
| CN110688117A (en) * | 2019-09-30 | 2020-01-14 | 厦门荆艺软件有限公司 | Interface designer and platform based on JavaWeb and page configuration method thereof |
| CN112463124A (en) * | 2020-12-03 | 2021-03-09 | 杭州新中大科技股份有限公司 | System for realizing one-time design thousand-face display based on metadata model |
Non-Patent Citations (1)
| Title |
|---|
| DOC1314521: "新中大i6p11.0用户登陆手册", Retrieved from the Internet <URL:https:doc88.com/p-9979019783529.html> * |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114090162A (en) * | 2021-11-24 | 2022-02-25 | 中国建设银行股份有限公司 | Front-end interface display method and related device of multi-tenant system |
| CN114860367A (en) * | 2022-05-07 | 2022-08-05 | 金蝶软件（中国）有限公司 | User interface event processing method, device and system |
| CN114860367B (en) * | 2022-05-07 | 2023-10-03 | 金蝶软件（中国）有限公司 | User interface event processing method, device and system |
| CN114995814A (en) * | 2022-06-07 | 2022-09-02 | 重庆大学 | Method and device for engineering intelligent view layout of application system |
| CN114995814B (en) * | 2022-06-07 | 2023-03-28 | 重庆大学 | Method and device for engineering intelligent view layout of application system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10929116B2 (en) | Generation of dynamic software models using input mapping with feature definitions | |
| Freeman | Pro Asp. net core MVC | |
| US9021419B2 (en) | System and method for supporting intelligent design pattern automation | |
| US9158534B2 (en) | Smart endpoint architecture | |
| CN113515281A (en) | Method for realizing user-defined interface of mobile application | |
| US8997038B2 (en) | Systems and methods for building and deploying mobile applications | |
| US11822870B2 (en) | Customizable user interface layouts | |
| US10095381B2 (en) | Task flow pin for a portal web site | |
| CN104111826A (en) | Software project development method and device | |
| CN112463124B (en) | System for realizing one-time design thousand-face display based on metadata model | |
| US20140280484A1 (en) | Dynamic Service Extension Infrastructure For Cloud Platforms | |
| CN105487864A (en) | Method and device for automatically generating code | |
| KR101275871B1 (en) | System and method for producing homepage in SaaS ENVIRONMENT, A computer-readable storage medium therefor | |
| CN115712413B (en) | Low code development method, device, equipment and storage medium | |
| CN104793961A (en) | Quick JavaWeb development method and system using native Web codes | |
| US20130117719A1 (en) | Context-Based Adaptation for Business Applications | |
| CN110020356A (en) | A kind of code generating method of page module, apparatus and system | |
| WO2012148867A1 (en) | Web-based app builder for mobile devices with automatic updates | |
| CN106257418A (en) | For by using assistance application to evaluate the technology of application | |
| US11782822B2 (en) | Templates for content spaces in a content management system | |
| JPWO2011118003A1 (en) | Web application construction system, web application construction method, web application construction program, and recording medium recording web application construction program | |
| CN112214202B (en) | Mobile phone program development system without writing codes | |
| CN113703743B (en) | Page configuration method and device, page rendering method, client and server | |
| US11783293B1 (en) | Templates for content spaces in a content management system | |
| US11783294B1 (en) | Templates for content spaces in a content management system |
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 |