CN110750248B - Method and device for transmitting extension information of existing component - Google Patents
Method and device for transmitting extension information of existing component Download PDFInfo
- Publication number
- CN110750248B CN110750248B CN201810813608.4A CN201810813608A CN110750248B CN 110750248 B CN110750248 B CN 110750248B CN 201810813608 A CN201810813608 A CN 201810813608A CN 110750248 B CN110750248 B CN 110750248B
- Authority
- CN
- China
- Prior art keywords
- component
- instance
- existing
- container
- extension information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
Abstract
The invention discloses a method and a device for transmitting extension information of an existing component. The disclosed method comprises the following steps: defining a container label for housing an instance of an existing component; defining a container component instance for accommodating an instance of an existing component using a container label, the instance of the existing component being defined in the container component instance; extension information for an instance of an existing component is conveyed using an extension field for the instance of the container component. The disclosed technical scheme can add states to a single field structure without affecting the display structure of the controlled component.
Description
Technical Field
The invention relates to the technical field of Internet front-end development, in particular to a method and a device for transmitting extension information of an existing component.
Background
Conventional Web page components, such as standard text entry boxes, password entry boxes, check boxes, radio buttons, etc., and user-defined form components (which may include standard components or other user-defined components described above), are essentially front-end components for displaying and collecting data, and data corresponding to instances of these components ultimately need to be passed to the back-end for database-related add, delete, check, and change operations.
For example, taking a form component as an example, the controlled form component can be bound with a back-end form, which is convenient for the form to be more flexible and convenient when handling errors and submitting information. While the controlled form component brings some convenience, there are bottlenecks, such as label of fields in the control and inconvenient customization of the control, the control is data in a single dimension, and no additional information can be added on the control without adding additional presentation controls or components.
Taking the example of the user-defined front-end form component with input text boxes employed by the prior art shown in FIG. 1 (FIG. 2 illustratively shows the instance definition code of the user-defined front-end form component shown in FIG. 1, which contains two instances of different levels of containers, the first level container FormContainer and the second level container FormItemContainer, however, those skilled in the art will also envision the use of only one level container or no container) through which the user enters a name, which is saved in the 'name' field. When a user enters a name in a text box, there are at least two different situations: 1) Newly creating a user name; 2) The existing user name is changed. However, the form component of FIG. 1 cannot display these 2 different states to the user at the front end.
In addition, an input text box corresponding to label 'name' and field 'name' can only submit { name: the field structure of 'Litsea-Sichuan' is such that additional status information (i.e., description information of which specific operation of creating and modifying a user name the user performs) cannot be transferred to the back-end without adding additional presentation controls or components.
The prior art, when solving the above-mentioned problem of adding additional state information to the same field, is generally implemented by adding new presentation control or component instance. However, because of the need to add new fields corresponding to new presentation controls or component instances, the ability to expand the original controlled component (instance) is required. For example, a new Input component (for passing status state values) needs to be added.
The above manner of expanding the display components can solve the above problems, but the cost is high, and each component needs to be expanded in a customized manner, for example, for Radio, checkbox, and needs to be expanded again. Meanwhile, due to the limitation of controlled components, label is necessary on the display: the mode of wrapper. Are not flexible in display and easily understand the deviations.
In order to solve the above-mentioned problem, a new solution needs to be proposed to add a state to a single field structure without affecting the controlled component display structure (i.e. without adding additional display controls or components), so as to implement the following operations in { name: 'Liuanfeng', status: 'rename' (i.e., case 2 above) } to interact with the backend, informing the backend that the corresponding backend form of the control component needs not to be a new name but to rewrite the original name (e.g., to inform the backend to directly perform the corresponding database operation). Or, the method is used for displaying the specific state corresponding to the current user operation to the user at the front end, and different forms of front end display are performed according to different states corresponding to the current user operation.
Disclosure of Invention
The method for transferring extension information of the existing component according to the present invention comprises:
defining a container label for housing an instance of an existing component;
defining a container component instance for accommodating an instance of an existing component using a container label, the instance of the existing component being defined in the container component instance;
extension information for an instance of an existing component is conveyed using an extension field for the instance of the container component.
The method for transferring extension information of an instance of an existing component according to the present invention further comprises:
the extension information is rendered on the label of the instance of the existing component.
The method for transferring extension information of the existing component according to the present invention further comprises:
according to the difference of the expansion information, the instance of the existing component is rendered in different structures,
the existing components have various component structures corresponding to different rendering modes one by one.
The method for transferring extension information of the existing component according to the present invention further comprises:
the current field value of the instance of the existing component and the current extension field value of the instance of the container component are submitted to the backend for the backend to perform a logical operation in accordance with the current field value and the current extension field value.
According to the method for transferring the extension information of the existing component, the existing component comprises at least one of an existing standard component and a user-defined component, the existing standard component comprises a text input box, a password input box, a check box, a radio button and a hidden text input box, and the extension information is used for describing specific operations currently corresponding to fields of an instance of the existing component, wherein the specific operations comprise new creation, modification and addition.
An apparatus for transferring extension information of an existing component according to the present invention includes:
a container tag definition module for defining a container tag for housing an instance of an existing component;
an instance definition module for defining a container component instance for housing an instance of an existing component using a container label, the instance of the existing component being defined in the container component instance;
and the information transfer module is used for transferring the extension information of the instance of the existing component by using the extension field of the instance of the container component.
The device for transferring extension information of an instance of an existing component according to the present invention further comprises:
and the first rendering module is used for rendering the extension information on the label of the instance of the existing component.
The apparatus for transferring extension information of an existing component according to the present invention further comprises:
a second rendering module for rendering the instance of the existing component in a different structure according to the difference of the extension information,
the existing components have various component structures corresponding to different rendering modes one by one.
The apparatus for transferring extension information of an existing component according to the present invention further comprises:
and the information submitting module is used for submitting the current field value of the instance of the existing component and the current extension field value of the instance of the container component to the back end and executing logic operation by the back end according to the current field value and the current extension field value.
The device for transferring the extension information of the existing component comprises at least one of the existing standard component and the user-defined component, wherein the existing standard component comprises a text input box, a password input box, a check box, a radio button and a hidden text input box, and the extension information is used for describing specific operations currently corresponding to fields of the instance of the existing component, and the specific operations comprise new creation, modification and addition.
According to the technical scheme, the state can be added to the single field structure on the premise of not affecting the display structure of the controlled component.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention. In the drawings, like reference numerals are used to identify like elements. The drawings, which are included in the description, illustrate some, but not all embodiments of the invention. Other figures can be derived from these figures by one of ordinary skill in the art without undue effort.
FIG. 1 illustrates exemplary prior art user-defined front-end form components with input text boxes.
FIG. 2 illustrates example definition code for the custom front-end form component shown in FIG. 1.
Fig. 3 schematically shows a flow diagram of a method for delivering extension information of an existing component according to the invention.
Fig. 4 schematically shows a block schematic of an apparatus for delivering extension information of an existing component according to the present invention.
FIG. 5 illustrates exemplary user-defined front-end form components with input text boxes that can be implemented in accordance with the teachings of the present invention.
FIG. 6 illustrates example definition code for the custom front-end form component illustrated in FIG. 5.
Fig. 7 schematically illustrates a specific embodiment of a method for delivering extension information of an existing component according to the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention. It should be noted that, in the case of no conflict, the embodiments and features in the embodiments may be arbitrarily combined with each other.
Fig. 3 schematically shows a flow diagram of a method for delivering extension information of an existing component according to the invention.
As shown in the solid line box of fig. 3, the method for transferring extension information of an existing component according to the present invention includes:
step S302: defining a container label for housing an instance of an existing component;
step S304: defining a container component instance for accommodating an instance of an existing component using a container label, the instance of the existing component being defined in the container component instance;
step S306: extension information for an instance of an existing component is conveyed using an extension field for the instance of the container component.
Optionally, as shown in a dashed box in fig. 3, the method for transferring extension information of an instance of an existing component according to the present invention further includes:
step S308: the extension information is rendered on the label of the instance of the existing component.
Optionally, as shown in a dashed box in fig. 3, the method for transferring extension information of an existing component according to the present invention further includes:
step S310: according to the difference of the expansion information, the instance of the existing component is rendered in different structures,
the existing components have various component structures corresponding to different rendering modes one by one.
Optionally, as shown in a dashed box in fig. 3, the method for transferring extension information of an existing component according to the present invention further includes:
step S312: the current field value of the instance of the existing component and the current extension field value of the instance of the container component are submitted to the backend for the backend to perform a logical operation in accordance with the current field value and the current extension field value.
Optionally, the existing component includes at least one of an existing standard component and a user-defined component, the existing standard component includes a text input box, a password input box, a check box, a radio button, and a hidden text input box, and the specific operation of the extension information is used for describing a specific operation currently corresponding to a field of an instance of the existing component, and the specific operation includes new creation, modification and addition.
Fig. 4 schematically shows a block schematic of an apparatus 400 for communicating extension information of an existing component according to the invention.
As shown in the solid line box of fig. 4, the apparatus 400 for transferring extension information of an existing component includes:
a container tag definition module 401 for defining container tags for housing instances of existing components;
an instance definition module 403 for defining a container component instance for housing an instance of an existing component using a container label, the instance of the existing component being defined in the container component instance;
an information delivery module 405 for delivering extension information for an instance of an existing component using an extension field of an instance of a container component.
Optionally, as shown in the dashed box of fig. 4, the apparatus 400 for transferring extension information of an instance of an existing component further includes:
a first rendering module 407, configured to render the extension information on a label of an instance of the existing component.
Optionally, as shown in the dashed box of fig. 4, the apparatus 400 for transferring extension information of an existing component further includes:
a second rendering module 409 for rendering the instance of the existing component in a different structure according to the difference of the extension information,
the existing components have various component structures corresponding to different rendering modes one by one.
Optionally, as shown in the dashed box of fig. 4, the apparatus 400 for transferring extension information of an existing component further includes:
the information submitting module 411 is configured to submit the current field value of the instance of the existing component and the current extension field value of the instance of the container component to the backend, and the backend is configured to perform a logic operation according to the current field value and the current extension field value.
Optionally, the existing component includes at least one of an existing standard component and a user-defined component, the existing standard component includes a text input box, a password input box, a check box, a radio button, and a hidden text input box, and the specific operation of the extension information is used for describing a specific operation currently corresponding to a field of an instance of the existing component, and the specific operation includes new creation, modification and addition.
In order to make the above-described technical solutions according to the present invention more clearly understood by those skilled in the art, the following description will be made with reference to specific embodiments.
FIG. 5 illustrates exemplary user-defined front-end form components with input text boxes that can be implemented in accordance with the teachings of the present invention.
The new user-defined form component at the top left of FIG. 5 adds a presentation of additional status information as compared to the user-defined form component employed in the prior art of FIG. 1, see "name" displayed therein: the "overlay" displayed above corresponds to the "extension information" rendered in the above step S308, and more specifically, corresponds to the "modification" in the above "specific operation including new, modification, and addition", and is used to indicate that the current front-end operation state of the user is "modifying" the original user name. It is contemplated that, for example, when a user creates a personal account, the "name" it displays may be: "New" is shown above. This process of making different presentations (i.e., renderings) on the label for different operations corresponds to step S308 described above.
Alternatively, one input text box may be displayed when "new" (i.e., the display of the new user-defined form component at the top left of fig. 5 corresponds to the first component structure associated with step S310), and two input text boxes may be displayed when "overlay" or "modify" (corresponding to the second component structure associated with step S310), the first text box displaying the original name and the second text box displaying the modified name. This process of differently exhibiting (i.e., rendering) in different structures for different operations corresponds to the above-described step S310.
The new user-defined form component on the upper right of fig. 5 also adds the presentation of additional status information, see "replacement" presented above "default source (standby)" displayed by it, corresponding to the "extended information" rendered in step S308 described above, more specifically, "modification" in "specific operations including new, modification, and addition" described above, to indicate that the current front-end operation status of the user is "modifying" the original default source (standby) device. It is contemplated that, for example, when a user establishes a master/slave rule between a first default source (slave) device, a "new" may be presented above the "default source (slave)" that it displays. This process of making different presentations (i.e., renderings) on the label for different operations corresponds to step S308 described above.
The new user-defined form component below fig. 5 also adds the presentation of additional status information, see "append" presented above "telecommunications source" shown on the left side below fig. 5, corresponding to "extension information" rendered in step S308 above, and more specifically, "append" in "concrete operations including new, modified, append" above to indicate that the user' S current front-end operational state is "append" the master/slave rules between the new telecommunications source (slave) devices. It is envisaged that, for example, when a user establishes a master-slave rule between a first telecommunication source (slave) device, a "new" may be presented above the "telecommunication source" it displays. This process of making different presentations (i.e., renderings) on the label for different operations corresponds to step S308 described above.
FIG. 6 illustrates example definition code for the custom front-end form component illustrated in FIG. 5.
The same as the instance definition code shown in fig. 2 is that the instance definition code shown in fig. 6 also contains instances of two containers of different levels, the first-level container FormContainer and the second-level container formitem container, however, those skilled in the art can also envisage using only one-level containers (corresponding to the "container tag" in step S302 described above) (i.e., using only FormContainer or using only formitem container), in which one instance of an input text box (input) is defined (corresponding to the "instance of an existing component" in step S304 described above).
The difference from the instance definition code shown in fig. 2 is that the instance definition code shown in fig. 5 adds a mode field, configured as "status", on the first level FormContainer instance, where the input box is not changed, but only the name is extended, where the state is open, and clicking on the name switches the modification state (corresponding to the "extension information of the instance of the existing component" in step S306) to the overlay (i.e., modification). The field output at this time is { name: 'xxx', status: 'cover (i.e., overlay)' } (mode: 'cover' corresponds to "extension field pass … using container component instance" in step S306 described above).
Fig. 7 schematically illustrates a specific embodiment of a method for delivering extension information of an existing component according to the present invention.
As shown in fig. 7, this embodiment includes the steps of:
1. when entering a form, the form mode (mode) is determined first, and if the mode is in the band state (i.e., mode= 'status'), rendering is entered.
2. When mode= 'status', two operations are performed, one is to rewrite the FormItem of the external container (or its internal container) of the original controlled component (e.g., corresponding to the modification operation), and one is to keep the original behavior rendering the controlled component (e.g., corresponding to the new operation, i.e., the new operation keeps the existing display mode).
3. The essence of overwriting FormItem is to rewrite label, which only reveals text, where hidden state needs to be rendered, and if necessary, some additional value needs to be output, such as in the case of replacement (i.e. modification), and to rewrite label into two input boxes (see, for example, the new user-defined form component at the upper right of FIG. 5).
4. After the state is customized, the controlled component is affected, and an additional state value is added on the original unique Key according to the unique Key of the controlled form item.
5. When the form is submitted, the state values (i.e., the current extension field values of the container component instance) are submitted to the server (corresponding to step S312), and the server performs a logical operation according to the state values.
According to the technical scheme provided by the invention, the state can be added to the single field structure on the premise of not influencing the display structure of the controlled component (namely, not adding additional display controls or components). For example, one can use { name: 'Liuanfeng', status: the 'rename' approach interacts with the backend informing the backend that the corresponding backend form of the control component needs not to be a new name but to overwrite the original name (e.g., to inform the backend to directly perform the corresponding database operation).
According to the technical scheme, the specific state corresponding to the current user operation can be displayed to the user at the front end, and different forms of front end display can be performed according to different states corresponding to the current user operation.
According to the technical scheme of the invention, the capability of expanding the label can be realized on the basis of maintaining the writing method of the original controlled component, so that the label can not only carry out the original input operation, but also bring the state of the current input operation (whether the current input value is a new value or a replacement value), and meanwhile, the logic interaction with the back end is realized.
According to the technical scheme of the invention, the method has the following advantages:
1. compared with the prior art, the writing method of the original controlled component is unchanged, for example, the mode of the controlled component can be switched into a form of a band state only by setting a mode= 'status'.
2. There is no need to extend the presentation components (i.e., no need to add additional presentation components), interactively without disruption to the original approach, e.g., by adding new placeholders on the interface.
3. For example, the state information can be displayed on the label to expand the capability of the existing label of the component, expand the meaning of the existing label of the component and reduce the occupation space on the page.
4. The fields are not required to be customized, and the fields only need to be expanded and customized on the same component and are decoupled from the controlled component, so that the method is more flexible.
The above description may be implemented alone or in various combinations and these modifications are within the scope of the present invention.
Those of ordinary skill in the art will appreciate that all or some of the steps, systems, functional modules/units in the apparatus, and methods disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between the functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed cooperatively by several physical components. Some or all of the components may be implemented as software executed by a processor, such as a digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as known to those skilled in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer. Furthermore, as is well known to those of ordinary skill in the art, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present invention, and are not limiting. Although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims (10)
1. A method for communicating extension information of an existing component, comprising:
defining a container label for housing an instance of the existing component;
defining a container component instance for housing an instance of the existing component using the container label, the instance of the existing component being defined in the container component instance;
using the extension field of the container component instance to transfer extension information of the existing component instance, specifically including: when the container component instance enters the container component instance mode, when the container component instance mode is the ribbon mode, the container label of the container component instance is rewritten, additional value is output, the additional state value is added in an extension field of the container component instance, and when the container component instance is submitted, the extension information corresponding to the extension field is submitted to a server together.
2. The method for communicating extension information of an existing component of claim 1, further comprising:
rendering the extension information on a label of the instance of the existing component.
3. The method for delivering extension information for an existing component according to claim 1 or 2, further comprising:
rendering instances of the existing component in different structures based on the extension information,
the existing components are provided with various component structures corresponding to different rendering modes one by one.
4. The method for delivering extension information for an existing component according to claim 1 or 2, further comprising:
and submitting the current field value of the instance of the existing component and the current extension field value of the instance of the container component to a back end for the back end to execute logic operation according to the current field value and the current extension field value.
5. The method for delivering extension information of an existing component according to claim 1 or 2, wherein the existing component includes at least one of an existing standard component and a user-defined component, the existing standard component includes a text input box, a password input box, a check box, a radio button, a hidden text input box, and the extension information is used to describe a specific operation currently corresponding to a field of an instance of the existing component, and the specific operation includes new creation, modification, and addition.
6. An apparatus for communicating extension information of an existing component, comprising:
a container tag definition module for defining a container tag for housing an instance of the existing component;
an instance definition module for defining a container component instance for housing an instance of the existing component using the container label, the instance of the existing component being defined in the container component instance;
the information transfer module is used for transferring the extension information of the instance of the existing component by using the extension field of the instance of the container component, and specifically comprises the following steps: when the container component instance enters the container component instance mode, when the container component instance mode is the ribbon mode, the container label of the container component instance is rewritten, additional value is output, the additional state value is added in an extension field of the container component instance, and when the container component instance is submitted, the extension information corresponding to the extension field is submitted to a server together.
7. The apparatus for communicating extension information of an existing component according to claim 6, further comprising:
and the first rendering module is used for rendering the extension information on the label of the instance of the existing component.
8. The apparatus for communicating extension information of an existing component according to claim 6 or 7, further comprising:
a second rendering module for rendering the instance of the existing component in a different structure according to the difference of the extension information,
the existing components are provided with various component structures corresponding to different rendering modes one by one.
9. The apparatus for communicating extension information of an existing component according to claim 6 or 7, further comprising:
and the information submitting module is used for submitting the current field value of the instance of the existing component and the current extension field value of the instance of the container component to the back end and executing logic operation by the back end according to the current field value and the current extension field value.
10. The apparatus for delivering extension information of an existing component according to claim 6 or 7, wherein the existing component includes at least one of an existing standard component and a user-defined component, the existing standard component includes a text input box, a password input box, a check box, a radio button, a hidden text input box, and the extension information is used to describe a specific operation currently corresponding to a field of an instance of the existing component, and the specific operation includes new creation, modification, and addition.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810813608.4A CN110750248B (en) | 2018-07-23 | 2018-07-23 | Method and device for transmitting extension information of existing component |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810813608.4A CN110750248B (en) | 2018-07-23 | 2018-07-23 | Method and device for transmitting extension information of existing component |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110750248A CN110750248A (en) | 2020-02-04 |
| CN110750248B true CN110750248B (en) | 2023-06-02 |
Family
ID=69275149
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810813608.4A Active CN110750248B (en) | 2018-07-23 | 2018-07-23 | Method and device for transmitting extension information of existing component |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110750248B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106055342A (en) * | 2016-06-13 | 2016-10-26 | 数普金通数据技术有限公司 | Method for using third-party Form extension component under dojango |
| CN106371844A (en) * | 2016-08-31 | 2017-02-01 | 北京奇艺世纪科技有限公司 | Method and system for presenting webpage by native user interface assembly |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7480867B1 (en) * | 2003-03-31 | 2009-01-20 | Unisys Corporation | Logistic management system having user interface with customizable data fields |
| CN103902634B (en) * | 2012-12-30 | 2017-09-29 | 航天信息股份有限公司 | The method that View components are bound automatically with Database field is realized using Adapter |
| CN105022615B (en) * | 2014-04-21 | 2018-09-11 | 大唐软件技术股份有限公司 | A kind of generation method and system at interface |
| CN105095348B (en) * | 2015-06-09 | 2019-03-26 | 北京织星科技有限公司 | A method of passing through XML dynamic configuration website |
| CN106846163A (en) * | 2016-07-05 | 2017-06-13 | 国网内蒙古东部电力有限公司 | A kind of electric power payment channel overall analysis system |
| CN106354513A (en) * | 2016-09-13 | 2017-01-25 | 济南浪潮高新科技投资发展有限公司 | Layered development method for form |
| CN106469223B (en) * | 2016-09-23 | 2018-07-03 | 交通运输部规划研究院 | The space of compatible ArcGIS a kind of and the unified control method and system of attribute data |
-
2018
- 2018-07-23 CN CN201810813608.4A patent/CN110750248B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106055342A (en) * | 2016-06-13 | 2016-10-26 | 数普金通数据技术有限公司 | Method for using third-party Form extension component under dojango |
| CN106371844A (en) * | 2016-08-31 | 2017-02-01 | 北京奇艺世纪科技有限公司 | Method and system for presenting webpage by native user interface assembly |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110750248A (en) | 2020-02-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109614545A (en) | Page loading method, device and equipment | |
| CN109725901A (en) | Development approach, device, equipment and the computer storage medium of front-end code | |
| CN104391725A (en) | Page display method and page display device | |
| CN102096694A (en) | Display rendering system with supporting components | |
| US8001180B2 (en) | Web page data providing system, web page data providing method, and computer-readable medium | |
| CN110119386A (en) | Data processing method, data processing equipment, medium and calculating equipment | |
| US10963635B2 (en) | Extensibility of compound data objects | |
| CN110750248B (en) | Method and device for transmitting extension information of existing component | |
| CN108196921B (en) | Document development method and device, computer equipment and storage medium | |
| CN117130697A (en) | Method and device for fixing application on taskbar | |
| CN115409002A (en) | Method and device for obtaining report, electronic equipment and computer storage medium | |
| US9342530B2 (en) | Method for skipping empty folders when navigating a file system | |
| US9936015B2 (en) | Method for building up a content management system | |
| CN114995699A (en) | Interface interaction method and device | |
| JP2002108677A (en) | Device for managing document and method for the same and storage medium | |
| CN114095511B (en) | Method and equipment for data synchronization of mobile distributed system | |
| CN115017110A (en) | Information processing method, device, terminal and storage medium | |
| CN113110829A (en) | Multi-UI component library data processing method and device | |
| CN112241267A (en) | Configuration tool and method for realizing form page development by using same | |
| CN115756443B (en) | Script generation method and device, electronic equipment and readable storage medium | |
| CN111192096B (en) | Multi-connection electronic invoice management method and device, readable medium and electronic equipment | |
| CN114553954B (en) | Information pushing method, nonvolatile storage medium and electronic equipment | |
| US9141377B2 (en) | Visualization of code units across disparate systems | |
| CN114036171B (en) | Application data management method, device, computer equipment and storage medium | |
| CN112800370B (en) | Processing method and device of business document, 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |