CN111078220A - Method and system for implementing front-end state change management - Google Patents
Method and system for implementing front-end state change management Download PDFInfo
- Publication number
- CN111078220A CN111078220A CN201911314516.2A CN201911314516A CN111078220A CN 111078220 A CN111078220 A CN 111078220A CN 201911314516 A CN201911314516 A CN 201911314516A CN 111078220 A CN111078220 A CN 111078220A
- Authority
- CN
- China
- Prior art keywords
- service
- interface
- parent
- component
- module
- 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.)
- Granted
Links
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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Human Computer Interaction (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The invention discloses a method and a system for realizing front-end state change management, belonging to a front-end Angular technical framework, aiming at solving the technical problem of how to realize logic for refreshing element states when interface elements change and reduce the number of times of repeatedly requesting a rear end, and adopting the technical scheme that: the method is characterized in that when data or button of a front-end interface has state change, a service is shared in parent and child assemblies through an angular dependency injection mechanism, monitoring of state change events in families of the parent and child assemblies is achieved through the service, the parent and child assemblies react, and unified management of state change of the front-end interface is achieved. The system comprises a service creation module, a Subject object subscription module, a service instance introduction module, an interface element state updating module and a Subject interception cancellation module.
Description
Technical Field
The invention belongs to a front-end Angular technical framework, mainly relates to Angular component interaction and event monitoring, and particularly relates to a method and a system for realizing front-end state change management.
Background
Angular is an excellent front end frame and is now widely used. Its goal is to enhance browser-based applications through MVC Mode (MVC) functionality, making development and testing easier, the framework employs and extends traditional HTML, adapts to dynamic content through bi-directional data binding, which allows automatic synchronization between models and views.
It is a mainstream trend for the front end to add state management to some elements of the interface. The user can more clearly sense own operation through the interface style and the interactive effect. After the user operates, the change of the page element can clearly show the current state. However, if a user writes a piece of code to refresh all relevant elements after the user operation, all refresh logic is independent and part of the code is duplicated. Code readability is poor, backend data is repeatedly requested, and unified logic is lacking. Therefore, how to implement logic for refreshing element states when interface elements change and reduce the number of times of repeatedly requesting back ends is a technical problem which needs to be solved urgently in the prior art at present.
Disclosure of Invention
The technical task of the invention is to provide a method and a system for realizing front-end state change management, which are used for solving the problems of how to realize logic for refreshing element states when interface elements change and reducing the number of times of repeatedly requesting a back end.
The technical task of the invention is realized in the following way, the method is that when the state of the data or button of the front-end interface changes, a service is shared in the parent-child assembly through an angular dependence injection mechanism, the monitoring of the home state change event of the parent-child assembly is realized through the service, and the parent-child assembly makes a response to realize the uniform management of the state change of the front-end interface.
Wherein, the method has the precondition that: monitoring the change of the state of the interface element among the parent and child components of Angular, if only monitoring the brother components, packaging a parent component for the brother components.
Preferably, the method is as follows:
s1, declaring a service, wherein the service is injected into a module where the parent-child component is located or into the parent component;
s2, subscribing the Subject object in the service when initializing in the component;
s3, introducing the sub-component into the service instance through a constructor;
s4, when a back-end interface is requested, setting loading prompt information or updating a medium intermediate state, after the return is successful, canceling the loading prompt or the intermediate state, and updating the interface element state according to the return result;
and S5, when the parent interface is closed, canceling the monitoring to the Subject in the service.
Preferably, in step S1, a service is declared, and the module in which the service is injected into the parent component or the module in which the service is injected into the parent component is specifically as follows:
s101, the service instance can be shared in the parent-child component by means of an injector inheritance mechanism of Angular DI;
s102, declaring the corresponding number of Subject objects according to the number of the front-end interface element states related to the rear-end interfaces.
Preferably, the details of the Subject object in the subscription service at the time of intra-component initialization in step S2 are as follows:
s201, when the subscription monitors any object pushing event, acquiring an interface of a related rear end, and providing the acquired data to a sub-component through @ Input attribute;
s202, the interface elements in the parent component and the interface elements in the child components can update the element states according to the latest data information.
Preferably, in step S202, the interface element in the parent component and the interface element in the child component can update the element state according to the latest data information as follows:
s20201, acquiring quota information, and executing the step S20202;
s20202, the creation button judges whether a residual space quota exists according to the matching change information returned by the back end:
①, if there is a remaining quota, executing step S20203;
②, if there is no remaining quota, go to step S20204;
s20203, displaying the creating button to be in a normal state, and executing the step S20205;
s20204, displaying that the creating button is in a grey setting state which cannot be clicked, and executing the step S20205 next;
s20205, judging whether the interface is closed:
①, if yes, go to step S20206;
②, if not, go to step S20201;
and S20206, ending.
Preferably, in the step S3, the sub-component is introduced into the service instance through the constructor as follows:
after the user operates, when the interface element update state is needed to give visual feedback to the user, the parent component can acquire the push event by triggering the push event of the relevant Subject in the service instance, so that the back-end interface is called, the latest information is acquired, and the interface element state of the parent component and the child component is refreshed.
A system for implementing front-end state change management comprises,
the service creation module is used for declaring a service, and the service is injected into a module where a parent-child component is located or a parent component;
the Subject object subscription module is used for subscribing the Subject object in the service during the initialization in the component;
the service instance introducing module is used for introducing the service instances by the sub-components through the constructors;
the interface element state updating module is used for setting loading prompt information or updating a medium intermediate state when a back-end interface is requested, canceling the loading prompt or the intermediate state after the back is successfully returned, and updating the interface element state according to a returned result;
and the monitoring canceling module of the Subject is used for canceling the monitoring of the Subject in the service when the parent interface is closed.
Preferably, the service creation module works as follows:
(1) the service instance can be shared among parent and child components via the injector inheritance mechanism of Angular DI;
(2) and declaring the corresponding number of Subject objects according to the number of the front-end interface element states related to the back-end interface.
Preferably, the object subscribing module works as follows:
when the subscription monitors any object pushing event, acquiring an interface of a related back end, and providing the acquired data to a subcomponent through an @ Input attribute;
and secondly, the interface elements in the parent component and the interface elements in the child components can update the element states according to the latest data information, such as: and the creation button displays whether the creation button is in a normal state or in a grey setting state which cannot be clicked according to the residual space size information returned by the back end.
Preferably, the service instance importing module works as follows:
after the user operates, when the interface element update state is needed to give visual feedback to the user, the parent component can acquire the push event by triggering the push event of the relevant Subject in the service instance, so that the back-end interface is called, the latest information is acquired, and the interface element state of the parent component and the child component is refreshed.
The method and the system for realizing the front-end state change management have the following advantages that:
the invention provides a realization method of unified management of the state of a front-end interface element, when the interface element changes, the logic of refreshing the state of the element is realized by fewer codes, and the frequency of a back end of a surface request is reduced;
the invention reduces redundant codes and improves the code quality;
interface interaction is optimized, and the response styles of interface elements are consistent;
the invention reduces the number of back-end requests and optimizes the interface response speed;
the method can replace the function of pushing and updating the interface element state of the websocket message, and reduces the use of project plug-ins;
and sixthly, uniformly managing the state change of the interface elements by utilizing the principle that the parent-child components of Angular share the service instance, thereby realizing the uniform management of the state of the front-end interface elements.
Drawings
The invention is further described below with reference to the accompanying drawings.
FIG. 1 is a block diagram illustrating a process by which interface elements in parent components and interface elements in child components can update the state of the elements based on the latest data information.
Detailed Description
The method and system for implementing front-end state change management according to the present invention will be described in detail with reference to the drawings and specific embodiments.
Example 1:
the method is characterized in that when data or buttons of a front-end interface have state changes, a service is shared in parent-child assemblies through an angular dependency injection mechanism, monitoring of state change events inside families of the parent-child assemblies is achieved through the service, the parent-child assemblies react, and unified management of state change of the front-end interface is achieved. The method comprises the following specific steps:
s1, declaring a service, wherein the service is injected into a module where the parent-child component is located or into the parent component; the method comprises the following specific steps:
s101, the service instance can be shared in the parent-child component by means of an injector inheritance mechanism of Angular DI;
s102, declaring the corresponding number of Subject objects according to the number of the front-end interface element states related to the rear-end interfaces.
S2, subscribing the Subject object in the service when initializing in the component; the method comprises the following specific steps:
s201, when the subscription monitors any object pushing event, acquiring an interface of a related rear end, and providing the acquired data to a sub-component through @ Input attribute;
s202, updating element states according to the latest data information by the interface elements in the parent component and the interface elements of the child components; as shown in fig. 1, the following are specific:
s20201, acquiring quota information, and executing the step S20202;
s20202, the creation button judges whether a residual space quota exists according to the matching change information returned by the back end:
①, if there is a remaining quota, executing step S20203;
②, if there is no remaining quota, go to step S20204;
s20203, displaying the creating button to be in a normal state, and executing the step S20205;
s20204, displaying that the creating button is in a grey setting state which cannot be clicked, and executing the step S20205 next;
s20205, judging whether the interface is closed:
①, if yes, go to step S20206;
②, if not, go to step S20201;
and S20206, ending.
S3, introducing the sub-component into the service instance through a constructor; the method comprises the following specific steps:
after the user operates, when the interface element update state is needed to give visual feedback to the user, the parent component can acquire the push event by triggering the push event of the relevant Subject in the service instance, so that the back-end interface is called, the latest information is acquired, and the interface element state of the parent component and the child component is refreshed.
S4, when a back-end interface is requested, setting loading prompt information or updating a medium intermediate state, after the return is successful, canceling the loading prompt or the intermediate state, and updating the interface element state according to the return result;
and S5, when the parent interface is closed, canceling the monitoring to the Subject in the service.
Example 2:
the invention relates to a front-end state change management implementation system, which comprises,
the service creation module is used for declaring a service, and the service is injected into a module where a parent-child component is located or a parent component;
the Subject object subscription module is used for subscribing the Subject object in the service during the initialization in the component;
the service instance introducing module is used for introducing the service instances by the sub-components through the constructors;
the interface element state updating module is used for setting loading prompt information or updating a medium intermediate state when a back-end interface is requested, canceling the loading prompt or the intermediate state after the back is successfully returned, and updating the interface element state according to a returned result;
and the monitoring canceling module of the Subject is used for canceling the monitoring of the Subject in the service when the parent interface is closed.
The working process of the service creation module is as follows:
(1) the service instance can be shared among parent and child components via the injector inheritance mechanism of Angular DI;
(2) and declaring the corresponding number of Subject objects according to the number of the front-end interface element states related to the back-end interface.
The object subscription module works as follows:
when the subscription monitors any object pushing event, acquiring an interface of a related back end, and providing the acquired data to a subcomponent through an @ Input attribute;
and secondly, the interface elements in the parent component and the interface elements in the child components can update the element states according to the latest data information, such as: and the creation button displays whether the creation button is in a normal state or in a grey setting state which cannot be clicked according to the residual space size information returned by the back end.
The working process of the service instance introduction module is as follows:
after the user operates, when the interface element update state is needed to give visual feedback to the user, the parent component can acquire the push event by triggering the push event of the relevant Subject in the service instance, so that the back-end interface is called, the latest information is acquired, and the interface element state of the parent component and the child component is refreshed.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (10)
1. A method for realizing front-end state change management is characterized in that when data or button of a front-end interface has state change, a service is shared in parent-child components through an angular dependency injection mechanism, monitoring of state change events in families of the parent-child components is achieved through the service, the parent-child components react, and unified management of state change of the front-end interface is achieved.
2. The method for implementing front-end state change management according to claim 1, wherein the method is as follows:
s1, declaring a service, wherein the service is injected into a module where the parent-child component is located or into the parent component;
s2, subscribing the Subject object in the service when initializing in the component;
s3, introducing the sub-component into the service instance through a constructor;
s4, when a back-end interface is requested, setting loading prompt information or updating a medium intermediate state, after the return is successful, canceling the loading prompt or the intermediate state, and updating the interface element state according to the return result;
and S5, when the parent interface is closed, canceling the monitoring to the Subject in the service.
3. The method for implementing front-end state change management according to claim 2, wherein a service is declared in step S1, and the module in which the service is injected into the parent component or the module in which the service is injected into the parent component specifically includes:
s101, the service instance can be shared in the parent-child component by means of an injector inheritance mechanism of Angular DI;
s102, declaring the corresponding number of Subject objects according to the number of the front-end interface element states related to the rear-end interfaces.
4. The method for implementing front-end state change management according to claim 2, wherein in step S2, the details of the Subject object in the subscription service at the time of intra-component initialization are as follows:
s201, when the subscription monitors any object pushing event, acquiring an interface of a related rear end, and providing the acquired data to a sub-component through @ Input attribute;
s202, the interface elements in the parent component and the interface elements in the child components can update the element states according to the latest data information.
5. The method for implementing front-end state change management according to claim 4, wherein in step S202, the interface elements in the parent component and the interface elements in the child components can update the states of the elements according to the latest data information as follows:
s20201, acquiring quota information, and executing the step S20202;
s20202, the creation button judges whether a residual space quota exists according to the matching change information returned by the back end:
①, if there is a remaining quota, executing step S20203;
②, if there is no remaining quota, go to step S20204;
s20203, displaying the creating button to be in a normal state, and executing the step S20205;
s20204, displaying that the creating button is in a grey setting state which cannot be clicked, and executing the step S20205 next;
s20205, judging whether the interface is closed:
①, if yes, go to step S20206;
②, if not, go to step S20201;
and S20206, ending.
6. The method for implementing front-end state change management according to claim 2, wherein the sub-component in the step S3 introduces the service instance through a constructor as follows:
after the user operates, when the interface element update state is needed to give visual feedback to the user, the parent component can acquire the push event by triggering the push event of the relevant Subject in the service instance, so that the back-end interface is called, the latest information is acquired, and the interface element state of the parent component and the child component is refreshed.
7. A system for implementing front-end state change management is characterized in that the system comprises,
the service creation module is used for declaring a service, and the service is injected into a module where a parent-child component is located or a parent component;
the Subject object subscription module is used for subscribing the Subject object in the service during the initialization in the component;
the service instance introducing module is used for introducing the service instances by the sub-components through the constructors;
the interface element state updating module is used for setting loading prompt information or updating a medium intermediate state when a back-end interface is requested, canceling the loading prompt or the intermediate state after the back is successfully returned, and updating the interface element state according to a returned result;
and the monitoring canceling module of the Subject is used for canceling the monitoring of the Subject in the service when the parent interface is closed.
8. The system for implementing front-end state change management according to claim 7, wherein the service creation module operates as follows:
(1) the service instance can be shared among parent and child components via the injector inheritance mechanism of Angular DI;
(2) and declaring the corresponding number of Subject objects according to the number of the front-end interface element states related to the back-end interface.
9. The system for implementing front-end state change management according to claim 7, wherein the object subscription module works as follows:
when the subscription monitors any object pushing event, acquiring an interface of a related back end, and providing the acquired data to a subcomponent through an @ Input attribute;
and secondly, the interface elements in the parent component and the interface elements in the child components can update the element states according to the latest data information.
10. The system for implementing front-end state change management according to claim 7, wherein the service instance importing module works as follows:
after the user operates, when the interface element update state is needed to give visual feedback to the user, the parent component can acquire the push event by triggering the push event of the relevant Subject in the service instance, so that the back-end interface is called, the latest information is acquired, and the interface element state of the parent component and the child component is refreshed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911314516.2A CN111078220B (en) | 2019-12-19 | 2019-12-19 | Method and system for realizing front-end state change management |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911314516.2A CN111078220B (en) | 2019-12-19 | 2019-12-19 | Method and system for realizing front-end state change management |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111078220A true CN111078220A (en) | 2020-04-28 |
| CN111078220B CN111078220B (en) | 2023-04-21 |
Family
ID=70315788
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911314516.2A Active CN111078220B (en) | 2019-12-19 | 2019-12-19 | Method and system for realizing front-end state change management |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111078220B (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111611314A (en) * | 2020-05-21 | 2020-09-01 | 山东汇贸电子口岸有限公司 | Angular-based synchronous refreshing method for different components on same page |
| CN111638932A (en) * | 2020-06-01 | 2020-09-08 | 山东汇贸电子口岸有限公司 | Angle-based public cloud private cloud height multiplexing front-end sharing method and system |
| CN112241282A (en) * | 2020-10-27 | 2021-01-19 | 上海万向区块链股份公司 | Method and system for managing global state data based on act project |
| CN112507356A (en) * | 2020-12-04 | 2021-03-16 | 上海易校信息科技有限公司 | Centralized front-end ACL (access control list) authority control method based on Angular |
| CN113687872A (en) * | 2021-07-19 | 2021-11-23 | 北京鸿腾智能科技有限公司 | Selection component control method, device, storage medium and apparatus |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB201621255D0 (en) * | 2016-03-25 | 2017-01-25 | Google Inc | Navigation application programming interface to accommodate multiple waypoint routing |
| US20180285328A1 (en) * | 2017-03-30 | 2018-10-04 | Ice Tea Group Llc | Pixel perfect real-time web application framework |
| CN108881213A (en) * | 2018-06-13 | 2018-11-23 | 山东浪潮商用系统有限公司 | JMS instant message service system based on intranet and extranet secure interactive |
| CN109117222A (en) * | 2018-07-24 | 2019-01-01 | 北京酷我科技有限公司 | A kind of implementation method for the interactive button prompting network load progress |
| CN110442816A (en) * | 2019-07-12 | 2019-11-12 | 平安科技（深圳）有限公司 | Web form configuration method, device and computer readable storage medium |
| US20200133982A1 (en) * | 2017-06-26 | 2020-04-30 | Nasdaq, Inc. | Systems and methods for enterprise web application dashboard management |
-
2019
- 2019-12-19 CN CN201911314516.2A patent/CN111078220B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB201621255D0 (en) * | 2016-03-25 | 2017-01-25 | Google Inc | Navigation application programming interface to accommodate multiple waypoint routing |
| US20180285328A1 (en) * | 2017-03-30 | 2018-10-04 | Ice Tea Group Llc | Pixel perfect real-time web application framework |
| US20200133982A1 (en) * | 2017-06-26 | 2020-04-30 | Nasdaq, Inc. | Systems and methods for enterprise web application dashboard management |
| CN108881213A (en) * | 2018-06-13 | 2018-11-23 | 山东浪潮商用系统有限公司 | JMS instant message service system based on intranet and extranet secure interactive |
| CN109117222A (en) * | 2018-07-24 | 2019-01-01 | 北京酷我科技有限公司 | A kind of implementation method for the interactive button prompting network load progress |
| CN110442816A (en) * | 2019-07-12 | 2019-11-12 | 平安科技（深圳）有限公司 | Web form configuration method, device and computer readable storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 刘一田;刘士进;: "一种柔性Web展现框架模型" * |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111611314A (en) * | 2020-05-21 | 2020-09-01 | 山东汇贸电子口岸有限公司 | Angular-based synchronous refreshing method for different components on same page |
| CN111638932A (en) * | 2020-06-01 | 2020-09-08 | 山东汇贸电子口岸有限公司 | Angle-based public cloud private cloud height multiplexing front-end sharing method and system |
| CN112241282A (en) * | 2020-10-27 | 2021-01-19 | 上海万向区块链股份公司 | Method and system for managing global state data based on act project |
| CN112241282B (en) * | 2020-10-27 | 2024-02-23 | 上海万向区块链股份公司 | Global state data management method and system based on reaction project |
| CN112507356A (en) * | 2020-12-04 | 2021-03-16 | 上海易校信息科技有限公司 | Centralized front-end ACL (access control list) authority control method based on Angular |
| CN113687872A (en) * | 2021-07-19 | 2021-11-23 | 北京鸿腾智能科技有限公司 | Selection component control method, device, storage medium and apparatus |
| CN113687872B (en) * | 2021-07-19 | 2024-03-29 | 三六零数字安全科技集团有限公司 | Selection component control method, device, storage medium and apparatus |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111078220B (en) | 2023-04-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111078220A (en) | Method and system for implementing front-end state change management | |
| US9146832B2 (en) | Debugging functionality embedded in an application | |
| US20060184569A1 (en) | Data processing systems and methods | |
| US20130097485A1 (en) | Template-based content creation | |
| US20140053063A1 (en) | User interface control framework for stamping out controls using a declarative template | |
| US20110090236A1 (en) | Graphic Object Data Binding | |
| US9092572B2 (en) | Development life cycle management tool for set-top box widgets | |
| CN103518377A (en) | Method and apparatus for updating a database in a receiving device | |
| US20130151571A1 (en) | Interface defined virtual data fields | |
| CN103440285A (en) | Large-scale mobile phone game system and database updating method of large-scale mobile phone game system | |
| US20130152054A1 (en) | Setting breakpoints in optimized instructions | |
| US9779176B2 (en) | Accessing external functionality within a component-based web application | |
| CN107220275B (en) | Database handles processing method, device and computer equipment | |
| CN111061522B (en) | Method, device, equipment and storage medium for generating front-end card assembly based on back end | |
| CN111339187B (en) | Data processing method, device, equipment and storage medium based on intelligent contract | |
| US10216493B2 (en) | Distributed UI development harmonized as one application during build time | |
| CN106970872B (en) | Information point burying method and device | |
| CN111078693B (en) | Method and device for generating database record primary key | |
| CN108804178A (en) | Information-pushing method, device, system and equipment | |
| CN112738550A (en) | Content data processing method and device, electronic equipment and medium | |
| CN107589962A (en) | A kind of method for displaying user interface and device | |
| CN109725818A (en) | A kind of information displaying method, equipment and computer-readable medium | |
| CN107492031B (en) | Quasi-real-time financial system account checking method based on function contract bypass analysis | |
| CN112037016A (en) | Service processing method, device and equipment | |
| US20140257806A1 (en) | Flexible animation framework for contextual animation display |
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 |
Address after: 250100 No. 1036 Tidal Road, Jinan High-tech Zone, Shandong Province, S01 Building, Tidal Science Park Applicant after: Inspur cloud Information Technology Co.,Ltd. Address before: 250100 No. 1036 Tidal Road, Jinan High-tech Zone, Shandong Province, S01 Building, Tidal Science Park Applicant before: Tidal Cloud Information Technology Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |