CN117492731A - Component management method, device, equipment and storage medium - Google Patents
Component management method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN117492731A CN117492731A CN202311696011.3A CN202311696011A CN117492731A CN 117492731 A CN117492731 A CN 117492731A CN 202311696011 A CN202311696011 A CN 202311696011A CN 117492731 A CN117492731 A CN 117492731A
- Authority
- CN
- China
- Prior art keywords
- component
- editing
- target
- request
- area
- 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
- 238000007726 management method Methods 0.000 title claims abstract description 158
- 238000012986 modification Methods 0.000 claims abstract description 49
- 230000004048 modification Effects 0.000 claims abstract description 49
- 230000004044 response Effects 0.000 claims abstract description 40
- 238000000034 method Methods 0.000 claims abstract description 14
- 230000001960 triggered effect Effects 0.000 claims description 25
- 230000003993 interaction Effects 0.000 claims description 24
- 230000006870 function Effects 0.000 claims description 19
- 238000011161 development Methods 0.000 claims description 15
- 238000013461 design Methods 0.000 claims description 14
- 238000004321 preservation Methods 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 15
- 238000004891 communication Methods 0.000 description 8
- 238000004590 computer program Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 6
- 230000000694 effects Effects 0.000 description 5
- 238000012217 deletion Methods 0.000 description 4
- 230000037430 deletion Effects 0.000 description 4
- 230000002452 interceptive effect Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000002457 bidirectional effect Effects 0.000 description 2
- 238000013479 data entry Methods 0.000 description 2
- VOZKAJLKRJDJLL-UHFFFAOYSA-N 2,4-diaminotoluene Chemical compound CC1=CC=C(N)C=C1N VOZKAJLKRJDJLL-UHFFFAOYSA-N 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
- 238000011022 operating instruction Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
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/33—Intelligent editors
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
-
- 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/34—Graphical or visual programming
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Computational Linguistics (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The application provides a component management method, device, equipment and storage medium, and relates to the field of big data, wherein the method comprises the following steps: displaying, on a component library management page, a functional description of a target component in a component description area, an implementation code and an implementation style of the target component in a component code demonstration area, interface information of the target component in a component interface demonstration area, and a modification record of the target component in the past time and/or a modification suggestion input for the target component in a component editing record area in response to a component viewing request for the target component in a component list; in response to a component editing request for a target component, an editing notification message for the target component is generated and sent to a participant object associated with the target component. Therefore, the components are displayed on the component library management page, and related personnel are timely notified after the components are edited, so that the components are convenient to manage by the multiparty personnel, and the component management efficiency is improved.
Description
Technical Field
The present disclosure relates to the field of big data, and in particular, to a method, an apparatus, a device, and a storage medium for managing components.
Background
In the component development process, a designer provides the style and the function requirements of the component, and the developer writes software codes to realize the component meeting the style and the function requirements. Because the same component can be applied to one or more pages and one or more projects, a component library is established to manage a plurality of components, repeated development of the components can be avoided, and the utilization rate of the components is improved.
Most of component libraries are unilaterally managed and maintained by developers, the developers develop components on a certain component library page, and the developers need to communicate with the designers on line and/or off line for many times before and after development, so that a large amount of manpower and material resources are consumed.
As can be seen, component management is inefficient.
Disclosure of Invention
The application provides a component management method, device, equipment and storage medium, which are used for solving the problem of low component management efficiency.
In a first aspect, the present application provides a component management method, where a component library management page of a component library management platform includes a component list, a component display area, and a component editing record area, where the component display area includes a component description area, a component code presentation area, and a component interface display area, and the component management method includes:
Receiving a component view request for a target component in the component list;
in response to the component viewing request, displaying the function description of the target component in the component description area, displaying the implementation code of the target component and the implementation style of the target component in the component code demonstration area, and displaying the interface information of the target component in the component interface display area;
in response to the component view request, displaying, within the component edit record area, a record of modifications of the target component over time and/or a suggestion of modifications entered for the target component;
receiving a component editing request for the target component on the component library management page;
responding to the component editing request, and generating an editing notification message of the target component;
and sending the editing notification message to the participation object related to the target component.
In a second aspect, the present application provides a component management apparatus, where a component library management page of a component library management platform includes a component list, a component display area, and a component editing record area, where the component display area includes a component description area, a component code presentation area, and a component interface display area, and the component management apparatus includes:
A view request receiving module, configured to receive a component view request for a target component in the component list;
the component description display module is used for responding to the component viewing request, displaying the function description of the target component in the component description area, displaying the realization code of the target component and the realization style of the target component in the component code demonstration area, and displaying the interface information of the target component in the component interface display area;
a modification display module, configured to display, in response to the component view request, a modification record of the target component in the past time and/or a modification suggestion input for the target component in the component edit record area;
the editing request receiving module is used for receiving a component editing request aiming at the target component on the component library management page;
and the editing notification module is used for responding to the component editing request, generating an editing notification message of the target component and sending the editing notification message to the participation object related to the target component.
In a third aspect, the present application provides an electronic device, comprising: a processor, and a memory communicatively coupled to the processor; the memory stores computer-executable instructions; the processor executes computer-executable instructions stored in the memory to implement the component management method as described in the first aspect.
In a fourth aspect, the present application provides a computer-readable storage medium having stored therein computer-executable instructions, which when executed by a processor, are configured to implement the component management method according to the first aspect.
In a fifth aspect, the present application provides a computer program product comprising a computer program which, when executed by a processor, implements the component management method as provided in the first aspect.
According to the component management method, device, equipment and storage medium, each component in the component list can be checked on the component library management page: upon viewing one of the components, a functional description of the component is presented in a component description area, an implementation code and an implementation style of the component are presented in a component code presentation area, interface information of the component is presented in a component interface presentation area, and a record of modifications of the component over time and/or a suggestion of modifications entered for the component is displayed in a component edit record area. Therefore, detailed design development content of the component can be seen on the component library management page, and modification records and modification suggestions of related participation objects (such as developers and designers) of the component can be seen, so that the participation objects can communicate with each other conveniently and quickly. When the component is edited, editing notification information of the component can be generated and sent to the participating object, so that the participating object can know the editing condition of the component in time. Therefore, the management and communication of the components by multiparty personnel can be realized on the component library management page, and the component management efficiency is improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.
Fig. 1 is an exemplary diagram of an application scenario applicable to an embodiment of the present application;
FIG. 2 is a flow chart of a component management method according to an embodiment of the present disclosure;
FIG. 3 is a diagram of an example of a page provided in an embodiment of the present application;
FIG. 4 is a diagram of a page example provided in an embodiment of the present application;
FIG. 5 is a third example diagram of a page provided in an embodiment of the present application;
FIG. 6 is a diagram of an example of a page provided in an embodiment of the present application;
fig. 7 is a schematic structural diagram of a component management device according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Specific embodiments thereof have been shown by way of example in the drawings and will herein be described in more detail. These drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.
It should be noted that the component management method, device, apparatus and storage medium provided in the present application may be used in the big data field, and may also be used in any field other than the big data field, and the application fields of the component management method, device, apparatus and storage medium provided in the present application are not limited.
Most of component libraries are unilaterally managed and maintained by developers, and a way for bidirectional feedback of the developers and the designers is lacking to update and maintain the component libraries, so that the component management efficiency is low.
In order to solve the above problems, the present application provides a component management method, apparatus, device, and storage medium. In the application, in response to the component viewing request, the functional description, the implementation code, the implementation style and the interface information of the component can be displayed on the component library management page, and the information is related to the design of the component and the development of the component, so that the multiparty participation objects of the component can master the specific situation of the component in an omnibearing manner; the modification record of the component in the past time and/or the modification suggestion input for the component can be displayed on the component library management page, so that multiparty participation objects of the component can know the modification condition of the component, and communication of the modification suggestion can be performed on the component library management page. And responding to the component editing request, generating an editing notification message of the component and sending the editing notification message to the participation object of the component to realize timely message feedback. Therefore, the component participators can know the specific conditions of the components through the component library management page, smooth and timely message feedback can be realized, and the management efficiency of the components is effectively improved.
Fig. 1 is an exemplary diagram of an application scenario applicable to an embodiment of the present application. As shown in fig. 1, an application scenario may involve a terminal 101 and a database 102. The terminal 101 may be a plurality of terminals, for example, a terminal where a developer is located, a terminal where a designer is located, and a terminal where a tester is located; the database 102 has a library of components stored therein. In the component management process, the terminal 101 may access a component library management page of the component library management platform, during which interaction with the database 102 is required to obtain component information in the component library and display the component information on the component library management page.
The terminal may be a personal digital assistant (personal digital assistant, PDA for short), a handheld device with a wireless communication function (e.g., a smart phone, a tablet computer), a computing device (e.g., a personal computer (personal computer, PC for short)), a wearable device (e.g., a smart watch, a smart bracelet), a smart home device (e.g., a smart speaker, a smart display device), etc.
The following describes the technical solution of the present application and how the technical solution of the present application solves the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
Fig. 2 is a flowchart of a component management method according to an embodiment of the present application. As shown in fig. 2, the component management method includes the steps of:
s201, receiving a component view request for a target component in a component list.
It should be noted that, the present embodiment is implemented based on the component library management platform, and the steps of the present embodiment may be implemented based on the displayed component library management page after the component library management page is displayed.
The component library management page of the component library management platform comprises a component list, a component display area and a component editing and recording area, wherein the component display area comprises a component description area, a component code display area and a component interface display area. The component list may include component names of a plurality of components, so the component list may also be referred to as a component name list, and existing components in the component library are shown by a series of component names. The component display area is used for displaying detailed information of the component, and the component editing recording area is used for displaying information related to editing and modifying of the component.
In this embodiment, on the component library management page, the user may select one of the components in the component list, for example, select the component by clicking, and select the component, for example, by inputting the component name of the component in the component selection box, to request to view the component information of the component. A component view request triggered by a selection operation for a target component in the component list, wherein the target component is a component selected by a user in the component list, can be received.
S202, in response to the component viewing request, displaying the function description of the target component in the component description area, displaying the implementation code of the target component and the implementation style of the target component in the component code demonstration area, and displaying the interface information of the target component in the component interface display area.
The function description of the target component describes an application scene of the target component, realizes functions (such as specifically performed data processing operation) in a text mode, and can describe component advantages and/or component disadvantages; the implementation code of the target component is program code written by a developer for implementing the component; the implementation style of the target component may include a design style of the target component, which may be provided by a designer, and a development style of the target component, which is a final style implemented based on implementation code of the target component, which may provide one or more design styles; the interface information of the target component may include interface information of an application programming interface (application program interface, API) provided by the target component.
In this embodiment, in response to a component view request for a target component, a function description, an implementation code, an implementation style, and component information of the target component may be acquired from a database, then the function description of the target component is displayed in a component description area, the implementation code of the target component and the implementation style of the target component are displayed in a component code presentation area, and interface information of the target component is displayed in a component interface display area. Thus, component information of the target component is revealed both from the design and development aspects. When a developer accesses the component library management page to request to view the component information of the target component, the function, the style and the code development condition of the target component can be seen, when a designer accesses the component library management page to request to view the component information of the target component, the function, the style and the code development condition of the target component can be seen, convenience is brought to two parties to communicate conveniently under the condition of grasping the accurate information of the target component, and the component management efficiency and the effect are improved.
S203, in response to the component viewing request, in the component editing record area, a modification record of the target component in the past time and/or a modification suggestion input for the target component are displayed.
The steps S202 and S203 may be performed simultaneously or sequentially. The content in the component presentation area may not be displayed at the same time as the content in the component edit recording area because the loading speeds may be different.
The modification suggestion input for the target component is a modification suggestion input for the target component by a participant (e.g., developer, designer) related to the target component in the component editing and recording area, for example, the designer suggests to modify the color of the prompt text of the target component to gray.
In this embodiment, in response to a component view request for a target component, a record of modifications of the target component over time and/or a suggestion of modifications entered for the target component may be obtained from a database. If a modification record of the target component in the past time is acquired, the modification record of the target component in the past time is displayed in the component editing record area. If the modification suggestion for the target component input is obtained, the modification suggestion for the target component input is displayed in the component edit recording area.
S204, receiving a component editing request for the target component on the component library management page.
In this embodiment, the user may request to edit the target component on the component library management page, and trigger a component editing request for the target component.
S205, in response to the component editing request, an editing notification message of the target component is generated.
The editing notification message of the target component can include user information (such as employee numbers) of the participation object editing the target component and editing operations of the participation object on the target component, so that other participation objects related to the target component can know which participation object performs which editing operations on the target component, timely information feedback of the participation objects is achieved, and component management efficiency is improved.
In this embodiment, in response to a component editing request, user information of a participant object editing a target component and an editing operation of the participant object on the target component may be obtained, and an editing notification message of the target component may be generated according to the user information of the participant object and the editing operation of the participant object on the target component.
S206, sending an editing notification message to the participation object related to the target component.
In this embodiment, an edit notification message is sent to a participant object associated with the target component. In one manner, an edit notification message may be sent to a communication address (e.g., mailbox address, instant chat address) of a participant associated with a target component; in another approach, the edit notification message may be displayed on the component library management page such that the edit notification message is visible to all participating objects entering the component library management page.
In the embodiment of the application, in response to a view request of a component, functional description, implementation codes, implementation patterns, interface information and modification information of the component are displayed on a component library management page in a region-by-region manner, and the modification information comprises modification records and/or modification suggestions, so that a participating object of the component can accurately grasp the component information through full access, and communication related to the component can be performed through the modification records and/or the modification suggestions. And in response to the editing request of the component, editing notification information is sent to the participating object, so that the participating object can know the editing condition of the component in time. Therefore, mutual bidirectional feedback and timely communication of the participating objects related to the components are realized, the components are managed by multiple parties, and the component management efficiency is improved.
In some embodiments, a plurality of component types and components under each component type are included in a component list. In the component list, the classified display of the components can be performed, the order of the component display is improved, and the user experience is improved.
Optionally, the plurality of component types may include a generic type, a layout type, a navigation type, a data entry type. The system comprises components such as buttons, icons, typesetting and the like under a general type, components such as dividing lines, grids, layouts, intervals and the like under a layout type, components such as anchor points, drop-down menus, navigation menus, paging, step bars and the like under a navigation type, and components such as cascade selection, multiple selection boxes, date selection boxes, forms and the like under a data input type. Therefore, the components in the component library are rich, and the ordered management of the components in the component library is realized by classifying the components.
In some embodiments, the implementation code of the target component may include a programming language type of the target component and programming code of the target component under the programming language type. Therefore, the integrity and accuracy of code display are improved by displaying the programming language types and the programming codes under the condition that the diversity of the programming language types is considered.
In some embodiments, the interface information of the target component may include an interface parameter of the target component, a text description corresponding to the interface parameter, a type of the interface parameter, a default value of the interface parameter, and a version number corresponding to the interface parameter, so that the interface information of the target component is provided in detail from multiple aspects, and the interface inspection is facilitated for the participants.
In the following, embodiments relating to editing of a target component are provided.
In some embodiments, generating the edit notification message for the target component in response to the component edit request for the target component may include: responding to a component editing request aiming at a target component, and switching a component library management page into an editing-allowed state; storing the target components subjected to editing operation on the component library management page, wherein the editing operation comprises deleting the target components, modifying the target components and/or adding modification suggestions for the target components; and generating an editing notification message according to the editing operation. Therefore, the participating object can directly edit the component on the component library management page by switching the component library management page into the editing permission state, so that the component editing efficiency is improved.
In this embodiment, in response to a component editing request for a target component, the component library management page is switched to an editing-permitted state. In the editing-permitted state, the form on the component library management page is in an activated state, and editing is permitted in the content in the form, wherein the interface information of the target component on the component library management page is presented in the form of the form; in the editing-allowed state, the vocabulary entries on the component library management page are released, and each field content in the vocabulary entries allows editing, wherein the function description, the realization code, the realization style and the modification suggestion of the target component on the component library management page are presented in the form of the vocabulary entries, and the component list can also be presented in the form of the vocabulary entries. Therefore, in the component library management page, the participating object may edit the component information of the target component, may delete the target component, modify the target component, and/or add modification suggestions to the target component. After the target component subjected to the editing operation on the component library management page is saved, an editing notification message may be generated according to the editing operation, and the editing notification message may refer to the foregoing embodiment and will not be described in detail.
In one possible implementation, the component editing record area includes an editing control, and the method includes receiving a component editing request for a target component on a component library management page, including: and receiving a component editing request triggered by the interaction operation of the editing-oriented control. Therefore, by setting the editing control in the component editing area, the user can conveniently trigger the component editing request. Wherein the interactive operation facing the editing control is, for example, a single click operation, a double click operation, etc.
It should be noted that, the user in this embodiment may understand the participation object currently performing the page operation.
In one possible implementation manner, the storing the target component subjected to the editing operation on the component library management page includes: displaying a first save control and a first notification control in the component editing and recording area; receiving a component saving request triggered by interaction operation facing a first saving control; and responding to the component-oriented preservation request, and preserving the target component subjected to the editing operation. Generating an editing notification message according to an editing operation, including: receiving a component editing notification request triggered by interaction operation facing a first notification control; in response to the component editing notification request, an editing notification message is generated according to the editing operation. Therefore, through the first storage control and the first notification control, convenience of information storage and information notification of a user in the editing process is improved, and interaction experience of the user in the assembly editing process is improved.
Wherein the first save control and the first notification control may be virtual buttons.
In this implementation, the first save control and the first notify control may be displayed within the component edit record area in response to a component edit request for the target component on the component library management page. In particular, before receiving the component editing request, an editing control is displayed in the component editing recording area, after the user interacts with the editing control, the component editing request is triggered, the editing control in the component editing recording area is hidden in response to the component editing request, and a first storage control and a first notification control are displayed in the component editing recording area. The user interacts with the first storage control, a triggered component storage request is responded to the component-oriented storage request, and the target component subjected to editing operation is stored; the user interacts with the first notification control, and triggers the component to edit the notification request; in response to the component editing notification request, an editing notification message is generated according to the editing operation, and the editing notification message may refer to the foregoing embodiment and will not be described in detail.
In one possible implementation manner, a deletion control can be displayed in the component editing recording area, and a component deletion request triggered by interaction operation facing the deletion control is received; in response to the component deletion request, the target component is deleted. Therefore, the convenience of deleting the components by the user is improved by improving the mode of deleting the controls.
In this implementation, the first save control, the first notify control, and the delete control may be displayed within the component edit record area in response to a component edit request for the target component on the component library management page. And under the condition that the component display area displays the target component, a component deleting request triggered by interaction with a deleting control in the component editing and recording area is used for requesting to delete the target component, and the target component can be deleted in response to the component deleting request.
Optionally, after the editing operation is performed on the target component, an updated flag may be added to the target component in the component list, and the updated flag prompts that the target component has been edited recently.
In some embodiments, the area where the component list is located includes a component new control, based on which the component management method further includes: receiving a component newly-added request triggered by interaction operation of a component-oriented newly-added control; responding to the component newly-added request, and displaying a component newly-added page; acquiring and storing the component information of the newly added component from the component newly added page; and sending the new message of the new component to the participation object related to the new component. Therefore, by interacting with the component newly-added control and the component newly-added page, a new component is added, the component newly-added function of the component library management platform is realized, the function of the component library management platform is enriched, and the efficiency of component management is further improved.
In this embodiment, the components included in the component list are existing components in the component library, and the component new control is used to add new components, and the component new control is displayed in the area where the component list is located, so that the page layout logic is more satisfied. Under the condition that a new component needs to be added, a user can perform interactive operation with a component new control, such as clicking operation, long-press operation and the like, so as to trigger a component new request; and under the condition that the component newly-added request is received, the component newly-added page is displayed in response to the component newly-added request, and the component newly-added page can be displayed in a popup window mode, namely, is displayed above the component library management page in the popup window mode. On the newly added page of the component, the user can input the component information of the newly added component; component information of the newly-added component is obtained from the component newly-added page, the component information of the newly-added component is stored in the component library, and then a newly-added message of the newly-added component can be sent to a participation object related to the newly-added component, so that the participation object related to the newly-added component can know that the newly-added component is added in the component library in time.
Optionally, after the component information of the newly added component is saved in the component library, the component name of the newly added component may be displayed in the component list, so as to implement timely update of the component list.
Optionally, the new message of the new component may be sent to a communication address (such as a mailbox address and an instant chat address) of the participant object.
Alternatively, the sending of the new message of the new component to the participating object related to the new component may be displaying the new message on the component library management page, so that the participating object entering the component library management page may all see the new message.
In one possible implementation manner, the newly added page of the component contains a second save control, the first save control and the second save control are both save controls, and the first and second only play a role in distinguishing. The obtaining and storing the component information of the newly added component from the component newly added page may include: receiving a new component adding and saving request triggered by the interaction operation facing the second saving control; and responding to the component newly-added storage request, acquiring and storing the component information of the newly-added component from the component newly-added page. Therefore, the second storage control is provided on the newly added page of the component, and the operation convenience for storing the newly added component is improved.
In one possible implementation manner, the newly added page of the component contains a second notification control, the first notification control and the second notification control are interaction controls for triggering message notification, and the first and second controls only play a role in distinguishing. Before sending the new message of the new component to the participation object related to the new component, the method further comprises: receiving a component newly-added notification request triggered by interaction operation facing to a second notification control; responding to a new notification request of the component, and displaying a message editing page of the newly added component, wherein the message editing page comprises a message input control; and acquiring the newly added message from the message input control. Therefore, the input of the newly added message of the newly added component is realized by interacting with the second notification control, the message editing page and the message input control, so that the user can conveniently input the newly added message according to the actual situation, the newly added message is clearer and more clear, and the actual scene is met.
The message input control can be an input box on the message editing page, and is used for inputting a new message of a text version; the message input control may also be a drop down selection box, and the user may select one or more of the selectable content as a new message by clicking on the drop down selection box.
In one possible implementation manner, the component type list and the component information input area are included on a component newly-added page, the component information of the newly-added component includes the component type, design style and interface information of the newly-added component, and the obtaining the component information of the newly-added component from the component newly-added page may include: responding to a selection operation of a target type in a component type-oriented list, and determining the component type of the newly added component as the target type; displaying a component effect input box, a component code input box and a component interface information input box in a component information input area; the design style of the newly added component is obtained from the component effect input box, the realization code of the newly added component is obtained from the component code input box, and the interface information of the newly added component is obtained from the component interface information input box. Therefore, the editing input of the detailed information of the newly added component can be realized through the newly added page of the component.
As an example, fig. 3 is a schematic diagram of a page example provided in an embodiment of the present application, and as shown in fig. 3, on a component library management page, a component list is on the left side, a component display area is in the middle, a component edit recording area is on the right side, and the component display area includes a component description area, a component code demonstration area, and a component interface display area. First, a plurality of components are displayed separately in a component list according to types, such as "general" type "," layout "," data entry ", component names of the plurality of components are displayed under each type, such as" button "," icon "," typesetting "," layout "type, etc., a" dividing line "," grid "etc., a" cascade selection "," multi-box "etc., are displayed under" general "type.
As shown in fig. 3, in the case where "cascade selection" is selected, detailed information of "cascade selection" will be displayed in the middle component presentation area: displaying the functional description of the component, such as application scenes, roles and advantages, in a component description area; displaying the realization code and the realization style of the component in a component code demonstration area; and displaying interface information of the component in a component interface display area. The component edit recording area on the right side may display the modification opinion of the component (i.e., the modification suggestion entered for the component in the foregoing embodiment), the modification history (i.e., the modification record of the component in the foregoing embodiment over the past time).
As shown in fig. 3, a "+component requirement" button, that is, the component new control in the foregoing embodiment, may also be displayed in the region where the component list is located; the component edit recording area on the right side may also display an "edit" button, i.e., the edit control in the foregoing embodiment. After clicking the "edit" button, as shown in fig. 3, the "edit" button is hidden, and the "save" button (i.e., the first save control in the foregoing embodiment), the "notify item group" button (i.e., the first notify control in the foregoing embodiment), and the "delete" button (i.e., the delete control in the foregoing embodiment) are displayed in the component edit recording area on the right side.
By way of example, fig. 4 is a diagram of an example of a page provided in an embodiment of the present application.
As shown in fig. 4, after clicking "+ component requirements", a component add request is triggered, and a component add page is popped up. In the component newly added page, a component type list is displayed, such as type one, type two and the like in fig. 4; in the component newly added page, an input box of a component effect (i.e., a component effect input box in the foregoing embodiment), an input box of a component code (i.e., a component code input box in the foregoing embodiment), and an input box of a component interface (i.e., a component interface information input box in the foregoing embodiment) are also displayed. In the process of adding the components, a user can select the types of the components in the component type list, and detailed information of the added components is input in an input box on the right side.
As shown in fig. 4, the component newly added page also displays a "save" button (i.e., the second save control in the foregoing embodiment) and a "notify item group" button (i.e., the second notify control in the foregoing embodiment). The user clicks a save button to save the component information of the newly added component; the user clicks the "notify item group" button, which can trigger the display of the message editing page of the newly added component, and display a message input box on the message editing page, in which the user can input a corresponding notification message, such as "please add 3 styles for the component" in fig. 4, click "send" and then send to the item group members, and click "cancel" and then cancel the message sending.
As an example, fig. 5 is a third exemplary diagram of a page provided in an embodiment of the present application. As shown in fig. 5, the instant notification may be displayed on the component library management page in a popup window manner, where the instant notification may include a new message of a component, and may further include an edit notification message of a component, for example, a message in fig. 5 that "developer a newly adds … … component design requirements 1 month 1 day 1 year, and" developer B newly adds/deletes/modifies … … components 2 days 1 year, 1 month 1 day ".
In some embodiments, call volume management controls are also included on the component library management page. Based on this, the component management method further includes: receiving a call volume statistics request triggered by interaction operation facing to a call volume management control; responding to the call volume statistics request, displaying a component call volume management page, and displaying a component list and a component call volume statistics area on the component call volume management page; and displaying the call volume of each component in the component list in the component call volume statistics area, wherein the call volume comprises a development call volume and/or a design call volume. Therefore, automatic statistics of the component call quantity is realized, the component library management platform has a component call quantity statistics function, manual statistics of the component call quantity is not needed, and component management efficiency is improved.
In this embodiment, the user may trigger the call volume statistics request by performing an interactive operation, such as a click operation, with the call volume management control. Under the condition that a call volume statistics request is received, the call volume of each component can be obtained from a database, wherein the call volume comprises the development call volume of each component and/or the design call volume of each component; and then, displaying a component call quantity management page, displaying a component list and a component call quantity statistical area on the component call quantity management page, and displaying the call quantity of each component in the component list in the component call quantity statistical area.
Alternatively, the component call management page may be presented as a popup page, displayed above the component library management page.
Alternatively, the call quantity of each component in the component list can be displayed in the component call quantity statistics area in the form of a statistical chart (such as a bar chart), so that the call quantity of the component can be intuitively and visually displayed to the user.
In one possible implementation, after displaying the component call volume management page in response to the call volume statistics request, the call volume of the target component in the component list may be displayed in the component call volume statistics area in response to a selected operation on the component call volume management page on the target component. Thus, the call volume of a component can be viewed on the component call volume management page by individually selecting the component.
The target component is a component selected by a user in a component list on a component call management page.
Alternatively, the call volume of the target component may be displayed in the component call volume statistics area in the form of a statistics graph (such as a ring statistics graph) to intuitively and intuitively display the call volume of the single component to the user.
Optionally, in response to the selection operation of the target component in the component list on the component call volume management page, the historical version of the target component and the update time corresponding to the historical version may be displayed in the component call volume statistics area, so that the user may perform component analysis by combining the update condition of the target component and the call volume statistics condition of the target component.
As an example, fig. 6 is a diagram illustrating a page example provided in an embodiment of the present application, and as shown in fig. 6, clicking a "call volume management" button on a component library management page may trigger display of a component call volume management page, and on the component call volume management page, a component list is displayed, and component call volume statistics including development call volumes and design call volumes of respective components are vividly shown through a histogram.
As shown in fig. 6, when the component "button" is selected from the component list on the component call amount management page, the historical version and the historical update time of the component "button" are displayed in the component call amount statistics area on the right side, and the development call amount and the design call amount of the component are also displayed in a ring statistics diagram manner.
Fig. 7 is a schematic structural diagram of a component management device according to an embodiment of the present application. The component library management page based on the component library management platform includes a component list, a component display area and a component editing recording area, where the component display area includes a component description area, a component code display area and a component interface display area, as shown in fig. 7, the component management device 700 provided in this embodiment includes:
A view request receiving module 701, configured to receive a component view request for a target component in the component list;
the component description display module 702 is configured to display, in response to a component viewing request, a function description of a target component in a component description area, display, in a component code presentation area, an implementation code of the target component and an implementation style of the target component, and display, in a component interface display area, interface information of the target component;
a modification display module 703 for displaying, in response to the component view request, a modification record of the target component in the past time and/or a modification suggestion input for the target component in the component edit record area;
an edit request receiving module 704, configured to receive a component edit request for a target component on a component library management page;
the editing notification module 705 generates an editing notification message of the target component in response to the component editing request, and transmits the editing notification message to the participation object related to the target component.
In some embodiments, the edit notification module 705 is specifically configured to: responding to the component editing request, and switching the component library management page into an editing-allowed state; storing the target components subjected to editing operation on the component library management page, wherein the editing operation comprises deleting the target components, modifying the target components and/or adding modification suggestions for the target components; and generating an editing notification message according to the editing operation.
In some embodiments, the component edit recording area contains an edit control, and the edit request receiving module 704 is specifically configured to: and receiving a component editing request triggered by the interaction operation of the editing-oriented control. The editing notification module is specifically configured to: displaying a first save control and a first notification control in the component editing and recording area; receiving a component saving request triggered by interaction operation facing a first saving control; responding to a component-oriented storage request, and storing the target component subjected to editing operation; receiving a component editing notification request triggered by interaction operation facing a first notification control; in response to the component editing notification request, an editing notification message is generated according to the editing operation.
In some embodiments, the area where the component list is located includes a component adding control, and the component management device further includes: a new request receiving module (not shown in the figure) for receiving a new component request triggered by the interaction operation of the new component-oriented control; a newly added page display module (not shown in the figure) for displaying a newly added page of the component in response to the component newly added request; the new component saving module (not shown in the figure) is used for acquiring and saving the component information of the new component from the component new page; an add notification module (not shown in the figure) is configured to send an add message of the add component to the participant object related to the add component.
In some embodiments, the component newly added page includes a second notification control, and the newly added notification module is further configured to: receiving a component newly-added notification request triggered by interaction operation facing to a second notification control; responding to a new notification request of the component, and displaying a message editing page of the newly added component, wherein the message editing page comprises a message input control; and acquiring the newly added message from the message input control.
In some embodiments, the component library management page further includes a call volume management control, and the component management device further includes: a call volume statistics request module (not shown in the figure) for receiving a call volume statistics request triggered by the interaction operation facing the call volume management control; a call volume page display module (not shown in the figure) for displaying a component call volume management page in response to a call volume statistics request, wherein a component list and a component call volume statistics area are displayed on the component call volume management page; and the first call volume display module (not shown in the figure) is used for displaying call volumes of all components in the component list in the component call volume statistics area, wherein the call volumes comprise development call volumes and/or design call volumes.
In some embodiments, the component management apparatus further comprises: and a second call amount display module (not shown in the figure) for displaying the call amount of the target component in the component call amount statistics area in response to a selected operation on the component call amount management page on the target component in the component list.
Fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present application. As shown in fig. 8, the electronic device 800 may include: at least one processor 801 and a memory 802. Fig. 8 shows an electronic device using one processor as an example.
A memory 802 for storing programs of the processor 801. In particular, the program may include program code including computer-operating instructions.
Memory 802 may comprise high-speed RAM memory or may also include non-volatile memory (non-volatile memory), such as at least one disk memory.
The processor 801 is configured to execute a computer program stored in the memory 802 to realize the steps in the component management method in the above method embodiments.
The processor 801 may be a central processing unit (central processing unit, abbreviated as CPU), or an application specific integrated circuit (application specific integrated circuit, abbreviated as ASIC), or one or more integrated circuits configured to implement embodiments of the present application.
Alternatively, the memory 802 may be separate or integrated with the processor 801. When the memory 802 is a device separate from the processor 801, the electronic device 800 may further include: bus 803 for connecting processor 801 and memory 802. The bus may be an industry standard architecture (industry standard architecture, abbreviated ISA) bus, an external device interconnect (peripheral component, PCI) bus, or an extended industry standard architecture (extended industry standard architecture, EISA) bus, among others. Buses may be divided into address buses, data buses, control buses, etc., but do not represent only one bus or one type of bus.
Alternatively, in a specific implementation, if the memory 802 and the processor 801 are integrated on a chip, the memory 802 and the processor 801 may complete communication through an internal interface.
The present application also provides a computer-readable storage medium, which may include: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, etc., and may store program codes, and in particular, the computer-readable storage medium stores computer-executable instructions, which, when executed by at least one processor of an electronic device, perform the steps of the component management methods provided in the above-described various embodiments.
Embodiments of the present application also provide a computer program product comprising a computer program stored in a readable storage medium. The computer program may be read from a readable storage medium by at least one processor of an electronic device, and executed by the at least one processor, causes the electronic device to implement the steps of the component management method provided by the various embodiments described above.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It is to be understood that the present application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.
Claims (10)
1. The component management method is characterized in that a component library management page of a component library management platform comprises a component list, a component display area and a component editing record area, wherein the component display area comprises a component description area, a component code demonstration area and a component interface display area, and the component management method comprises the following steps:
receiving a component view request for a target component in the component list;
In response to the component viewing request, displaying the function description of the target component in the component description area, displaying the implementation code of the target component and the implementation style of the target component in the component code demonstration area, and displaying the interface information of the target component in the component interface display area;
in response to the component view request, displaying, within the component edit record area, a record of modifications of the target component over time and/or a suggestion of modifications entered for the target component;
receiving a component editing request for the target component on the component library management page;
responding to the component editing request, and generating an editing notification message of the target component;
and sending the editing notification message to the participation object related to the target component.
2. The component management method according to claim 1, wherein the generating an edit notification message of the target component in response to the component edit request includes:
responding to the component editing request, and switching the component library management page into an editing-allowed state;
storing the target component subjected to editing operation on the component library management page, wherein the editing operation comprises deleting the target component, modifying the target component and/or adding modification suggestions for the target component;
And generating the editing notification message according to the editing operation.
3. The component management method according to claim 2, wherein the component editing record area contains an editing control, and the receiving a component editing request for the target component on the component library management page includes:
receiving a component editing request triggered by the interaction operation facing the editing control;
the storing the target component subjected to the editing operation on the component library management page comprises the following steps:
displaying a first save control and a first notification control in the component editing and recording area;
receiving a component saving request triggered by interaction operation facing the first saving control;
responding to the component preservation request, and preserving the target component subjected to editing operation;
the generating the editing notification message according to the editing operation includes:
receiving a component editing notification request triggered by interaction operation facing the first notification control;
and responding to the component editing notification request, and generating the editing notification message according to the editing operation.
4. A component management method according to any one of claims 1 to 3, wherein the region in which the component list is located contains a component new control, and the component management method further comprises:
Receiving a component newly-added request triggered by interaction operation for the component newly-added control;
responding to the component newly-added request, and displaying a component newly-added page;
acquiring and storing the component information of the newly added component from the newly added page of the component;
and sending the newly added information of the newly added component to the participation object related to the newly added component.
5. The method for managing components according to claim 4, wherein the newly added page of the component includes a second notification control, and before sending the newly added message of the newly added component to the participating object related to the newly added component, the method further comprises:
receiving a component newly-added notification request triggered by the interaction operation facing the second notification control;
responding to the new notification request of the component, and displaying a message editing page of the new component, wherein the message editing page comprises a message input control;
and acquiring the newly added message from the message input control.
6. A component management method according to any one of claims 1 to 3, wherein the component library management page further comprises a call amount management control thereon, and the component management method further comprises:
receiving a call volume statistics request triggered by the interaction operation facing the call volume management control;
Responding to the call volume statistics request, displaying a component call volume management page, and displaying the component list and a component call volume statistics area on the component call volume management page;
and displaying the call quantity of each component in the component list in the component call quantity statistics area, wherein the call quantity comprises a development call quantity and/or a design call quantity.
7. The component management method according to claim 6, wherein after displaying the component call volume management page in response to the call volume statistics request, further comprising:
in response to a selected operation on the component call volume management page on the target component, displaying the call volume of the target component in the component call volume statistics area.
8. A component management apparatus, wherein a component library management page of a component library management platform includes a component list, a component presentation area, and a component edit record area, the component presentation area including a component description area, a component code presentation area, and a component interface presentation area, the component management apparatus comprising:
a view request receiving module, configured to receive a component view request for a target component in the component list;
The component description display module is used for responding to the component viewing request, displaying the function description of the target component in the component description area, displaying the realization code of the target component and the realization style of the target component in the component code demonstration area, and displaying the interface information of the target component in the component interface display area;
a modification display module, configured to display, in response to the component view request, a modification record of the target component in the past time and/or a modification suggestion input for the target component in the component edit record area;
the editing request receiving module is used for receiving a component editing request aiming at the target component on the component library management page;
and the editing notification module is used for responding to the component editing request, generating an editing notification message of the target component and sending the editing notification message to the participation object related to the target component.
9. An electronic device, comprising:
a processor, and a memory communicatively coupled to the processor;
the memory stores computer-executable instructions;
the processor executes the computer-executable instructions stored in the memory to implement the component management method as claimed in any one of claims 1 to 7.
10. A computer-readable storage medium, wherein computer-executable instructions are stored in the computer-readable storage medium, which when executed by a processor, are configured to implement the component management method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311696011.3A CN117492731A (en) | 2023-12-11 | 2023-12-11 | Component management method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311696011.3A CN117492731A (en) | 2023-12-11 | 2023-12-11 | Component management method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117492731A true CN117492731A (en) | 2024-02-02 |
Family
ID=89674788
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311696011.3A Pending CN117492731A (en) | 2023-12-11 | 2023-12-11 | Component management method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117492731A (en) |
-
2023
- 2023-12-11 CN CN202311696011.3A patent/CN117492731A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109614424B (en) | Page layout generation method, device, computing equipment and medium | |
| CN107391134B (en) | Method and device for automatically generating and dynamically transforming universal mobile application interactive interface | |
| CN111309213A (en) | Comment display method and device, electronic equipment and storage medium | |
| CN109408764B (en) | Page area dividing method, device, computing equipment and medium | |
| US20180321830A1 (en) | Screen-based workflow configuration and execution platform | |
| CN113268226A (en) | Page data generation method and device, storage medium and equipment | |
| CN114564252A (en) | Event configuration method, system, equipment and medium for low-code platform | |
| CN108958731B (en) | Application program interface generation method, device, equipment and storage medium | |
| CN111586464A (en) | Content display method, device and equipment based on media information stream and storage medium | |
| CN112558967A (en) | Page automatic generation method and device, electronic equipment and storage medium | |
| CN111857718A (en) | List editing method, device, equipment and storage medium | |
| CN114239524A (en) | Questionnaire generation method, questionnaire generation device, computer equipment and storage medium | |
| US10289388B2 (en) | Process visualization toolkit | |
| CN113641719A (en) | Data processing method, data processing device, computer and storage medium | |
| CN117492731A (en) | Component management method, device, equipment and storage medium | |
| CN115617441A (en) | Method and device for binding model and primitive, storage medium and computer equipment | |
| CN104808896A (en) | Data processing method and system | |
| CN114995931A (en) | Display method and device of project bulletin board, storage medium and computer equipment | |
| CN115130442A (en) | Report generation method and device, storage medium and computer equipment | |
| CN114841604A (en) | Cooperative task processing method, device and equipment and computer readable storage medium | |
| US20030204567A1 (en) | System and method for creating e-mail object attributes | |
| CN108984176B (en) | High-definition desktop development system | |
| CN114967992A (en) | Information interaction method, label viewing method and device | |
| CN116204267B (en) | Method and device for generating intellectual property flow form | |
| CN115293121B (en) | Element-UI-based form linkage method and terminal |
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 |