Plug-in display method and device and computing equipment

Abstract

The embodiment of the invention provides a plug-in display method and device and computing equipment, and the method comprises the steps that a card type plug-in manager recognizes at least one target plug-in from a plurality of plug-ins, and the at least one target plug-in is registered to the card type plug-in manager, the configuration file of each target plug-in comprises UI (User Interface) layout information of the target plug-in, and the UI layout information of the target plug-in indicates that the target plug-in is displayed on the UI in a card manner; the card type plug-in manager displays at least one target plug-in on a target page of the UI in a card mode according to the UI layout information of each target plug-in, the target page comprises at least one card type display unit, and each card type display unit is used for displaying one target plug-in. According to the card type plug-in display form provided by the invention, the plug-in development efficiency of a user can be improved, and the plug-in use experience of the user can be improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of software development, and more specifically, to a method, apparatus, and computing device for displaying a plug-in. Background Art

[0002] A plug-in is a program or component that extends or enhances the functionality of software. It can be installed in the software or interact with the software as an external module. Plug-ins are usually provided by third-party developers to meet the needs or preferences of different users.

[0003] However, the operation methods of various plug-ins are complicated, there is no unified entrance, and different plug-ins are used in different ways. This makes it extremely inconvenient for users to operate plug-ins. Users need to find different plug-ins in different places. The display and interactive use of plug-ins are not flexible enough, which increases the user's usage cost and learning difficulty, and reduces the user's efficiency and experience in using plug-ins.

[0004] Therefore, how to improve the efficiency and experience of users in using plug-ins has become a technical problem that needs to be solved urgently. Summary of the invention

[0005] The embodiments of the present application provide a method, apparatus, and computing device for displaying a plug-in. The card-type plug-in display format can not only improve the user's plug-in development efficiency, but also improve the user's experience in using the plug-in.

[0006] In a first aspect, a method for plug-in display is provided, the method comprising: a card-type plug-in manager identifies at least one target plug-in from multiple plug-ins, the at least one target plug-in is registered with the card-type plug-in manager, each configuration file of the target plug-in includes user interface UI layout information of the target plug-in, the UI layout information of the target plug-in indicates that the target plug-in is to be displayed in a card manner on the UI; the card-type plug-in manager displays the at least one target plug-in in a card manner on a target page of the UI according to the UI layout information of each target plug-in, the target page includes at least one card-type display unit, and each card-type display unit is used to display a target plug-in.

[0007] In the above technical solution, plug-ins are quickly configured and accessed through cards. Users can quickly find the plug-ins they need to use through a unified entrance, browse and use different plug-ins, and can efficiently get started with the functions of the plug-ins. The quick interaction brought by the card method helps to improve the efficiency of users' use of plug-ins, increase users' stickiness to plug-ins, and then improve the reputation of plug-ins, thereby further increasing user usage and enhancing the value of plug-ins.

[0008] In combination with the first aspect, in certain implementations of the first aspect, each of the card-type display units displays function and business content information of the target plug-in.

[0009] In combination with the first aspect, in certain implementations of the first aspect, the configuration file of the target plug-in also includes the function and business content information of the target plug-in, and the method also includes: the card-type plug-in manager obtains the function and main content information of the target plug-in from the configuration file of the target plug-in through the registration interface of the target plug-in; the card-type plug-in manager fills the function and main content information of the target plug-in into the card-type display unit corresponding to the target plug-in.

[0010] In combination with the first aspect, in some implementations of the first aspect, the card-type display unit supports a user to use a target plug-in displayed in the card-type display unit.

[0011] In the above technical solution, the main capabilities of the plug-in are presented on the card-type display unit. By displaying the main capabilities of the plug-in on the card-type display unit, the plug-in capabilities can be used without entering the plug-in details page, saving the user's time in searching for the plug-in entrance, and by presenting the main capabilities of the plug-in extracted in the card-type display unit, the user can focus more on the operation of key capabilities, thereby improving the user's efficiency in using the plug-in capabilities.

[0012] In combination with the first aspect, in certain implementations of the first aspect, the method also includes: the card-type plug-in manager receives first instruction information from the user, and the first instruction information is used to instruct an operation to be performed on a first target plug-in displayed in a first card-type display unit; the card-type plug-in manager completes the interaction between the user and the first target plug-in according to the first instruction information.

[0013] In combination with the first aspect, in certain implementations of the first aspect, the configuration file of the target plug-in also includes interaction logic information between the target plug-in and the UI, and the card-type plug-in manager completes the interaction between the user and the first target plug-in based on the first indication information and the interaction logic information between the target plug-in and the UI.

[0014] In combination with the first aspect, in certain implementations of the first aspect, the method also includes: the card-type plug-in manager receives second instruction information from the user, and the second instruction information is used to indicate access to detailed content information of the first target plug-in displayed in the first card-type display unit; the card-type plug-in manager jumps to the details page of the first target plug-in according to the second instruction information, and the details page is used to display the detailed content information of the first target plug-in.

[0015] In the above technical solution, in addition to supporting quick interaction with card-type plug-ins, it also supports quick navigation to the plug-in details module to perform more other capabilities or detailed operations.

[0016] In combination with the first aspect, in certain implementations of the first aspect, the target page supports the user to personalize the page, and the personalization includes modifying the style of the target page and modifying the style of the at least one card-type display unit.

[0017] In the above technical solution, the card-type plug-in manager can jump to the personalized setting interface according to the user's instructions to realize the personalized layout configuration of the target interface and / or the card-type plug-in. In this way, the user can create a card-type display interface that suits his own habits and tastes.

[0018] In combination with the first aspect, in certain implementations of the first aspect, the method also includes: the card-type plug-in manager receives third indication information from the user, and the third indication information is used to indicate that the style of the target page is modified; the card-type plug-in manager jumps to the interface of personalized settings of the target page according to the third indication information, and personalizes the target page.

[0019] In combination with the first aspect, in certain implementations of the first aspect, the personalized configuration of the target page includes configuring a theme, a font, and a color of the target page.

[0020] In combination with the first aspect, in certain implementations of the first aspect, the method also includes: the card-type plug-in manager receives fourth indication information from the user, and the fourth indication information is used to indicate that the style of the first target plug-in displayed in the first card-type display unit is modified; the card-type plug-in manager jumps to the plug-in personalization setting interface according to the fourth indication information, and personalizes the size, layout, and display order of the first target plug-in.

[0021] In combination with the first aspect, in certain implementations of the first aspect, the at least one card-type display unit is laid out in the target page in a waterfall flow manner, or in a horizontal scrolling manner.

[0022] In a second aspect, a device for displaying plug-ins is provided, which is applied to a card-type plug-in manager, and includes: an identification module and a display module. The identification module is used to identify at least one target plug-in from multiple plug-ins, and the at least one target plug-in is registered with the card-type plug-in manager. The configuration file of each target plug-in includes the user interface UI layout information of the target plug-in, and the UI layout information of the target plug-in indicates that the target plug-in is displayed in the form of a card on the UI; the display module is used to display the at least one target plug-in in the form of a card on the target page of the UI according to the UI layout information of each target plug-in, and the target page includes at least one card-type display unit, and each card-type display unit is used to display a target plug-in.

[0023] In combination with the second aspect, in certain implementations of the second aspect, each of the card-type display units displays function and business content information of the target plug-in.

[0024] In combination with the second aspect, in certain implementations of the second aspect, the configuration file of the target plug-in also includes the function and business content information of the target plug-in, and the device also includes: an acquisition module, used to obtain the function and main content information of the target plug-in from the configuration file of the target plug-in through the registration interface of the target plug-in; the processing module is used to fill the function and main content information of the target plug-in into the card-type display unit corresponding to the target plug-in.

[0025] In combination with the second aspect, in some implementations of the second aspect, the card-type display unit supports the user to use the target plug-in displayed in the card-type display unit.

[0026] In combination with the second aspect, in certain implementations of the second aspect, the device also includes: a receiving module for receiving a user's first instruction information, the first instruction information being used to instruct an operation to be performed on a first target plug-in displayed in a first card-type display unit; and a processing module for completing the interaction between the user and the first target plug-in according to the first instruction information.

[0027] In combination with the second aspect, in certain implementations of the second aspect, the configuration file of the target plug-in also includes interaction logic information between the target plug-in and the UI, and the processing module is specifically used to complete the interaction between the user and the first target plug-in based on the first indication information and the interaction logic information between the target plug-in and the UI.

[0028] In combination with the second aspect, in certain implementations of the second aspect, the receiving module is used to receive second instruction information from the user, and the second instruction information is used to indicate access to detailed content information of the first target plug-in displayed in the first card-type display unit; the processing module is used to jump to the details page of the first target plug-in according to the second indication information, and the details page is used to display the detailed content information of the first target plug-in.

[0029] In combination with the second aspect, in certain implementations of the second aspect, the target page supports the user to personalize the page, and the personalization includes modifying the style of the target page and modifying the style of the at least one card-type display unit.

[0030] In combination with the second aspect, in certain implementations of the second aspect, the receiving module is used to receive a third indication information from the user, and the third indication information is used to indicate modification of the style of the target page; the processing module is used to jump to the interface of personalized settings of the target page according to the third indication information, and personalize the target page.

[0031] In combination with the second aspect, in some implementations of the second aspect, the personalized configuration of the target page includes configuring the theme, font, and color of the target page.

[0032] In combination with the second aspect, in certain implementations of the second aspect, the receiving module is used to receive a fourth indication information from the user, and the fourth indication information is used to indicate that the style of the first target plug-in displayed in the first card-type display unit is modified; the processing module is used to jump to the plug-in personalization interface according to the fourth indication information, and personalize the size, layout, and display order of the first target plug-in.

[0033] In combination with the second aspect, in certain implementations of the second aspect, the at least one card-type display unit is laid out in the target page in a waterfall flow manner, or in a horizontal scrolling manner.

[0034] In a third aspect, a computing device is provided, comprising: a memory for storing programs; a processor for executing the programs stored in the memory, and when the program stored in the memory is executed, the processor is used to execute the method in the first aspect and any one of the implementations of the first aspect.

[0035] The processor in the third aspect above may be a general-purpose processor, which may be implemented by hardware or software. When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor may be a general-purpose processor, which is implemented by reading software code stored in a memory, and the memory may be integrated in the processor or located outside the processor and exist independently.

[0036] According to a fourth aspect, a computer-readable medium is provided, wherein the computer-readable medium stores a program code for execution by a computing device, wherein the program code includes a method for executing the first aspect and any one of the implementations of the first aspect.

[0037] By way of example, these computer-readable storages include, but are not limited to, one or more of the following: read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), Flash memory, electrically EPROM (EEPROM), and hard drive.

[0038] Optionally, as an implementation manner, the above-mentioned storage medium may specifically be a non-volatile storage medium.

[0039] According to a fifth aspect, a computer program product comprising instructions is provided. When the computer program product is run on a computing device, the computing device executes the method in the first aspect and any one of the implementations of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0041] Figure 1 It is a schematic flow chart of a method for displaying a plug-in provided in an embodiment of the present application.

[0042] Figure 2 It is a schematic diagram of a UI design effect of displaying a card-type plug-in in a waterfall flow manner provided in an embodiment of the present application.

[0043] Figure 3 This is an example diagram of quick interaction with a theme plug-in.

[0044] Figure 4 This is an example diagram of quick interaction with a project management plug-in.

[0045] Figure 5 This is an example diagram of a recommended plug-in for quick interaction.

[0046] Figure 6 This is an example diagram of quick interaction with an input plug-in.

[0047] Figure 7 This is an example of a quick jump using a theme plugin.

[0048] Figure 8 This is an example diagram of a quick jump for a project management plug-in.

[0049] Fig. 9 This is an example diagram of a recommended plug-in for quick redirection.

[0050] Fig.10 This is an example of a quick jump using a search plugin.

[0051] Fig.11 It is a schematic block diagram of a plug-in display device 1100 according to an embodiment of the present application.

[0052] Fig.12 It is a schematic diagram of the hardware structure of the computing device 1200 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0053] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0054] The present application will present various aspects, embodiments or features around a system including multiple devices, components, modules, etc. It should be understood and appreciated that each system may include additional devices, components, modules, etc., and / or may not include all devices, components, modules, etc. discussed in conjunction with the figures. In addition, combinations of these schemes may also be used.

[0055] In addition, in the embodiments of the present application, words such as "exemplary" and "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" in the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of the word "exemplary" is intended to present concepts in a concrete way.

[0056] In the embodiments of the present application, "corresponding (corresponding, relevant)" and "corresponding (corresponding)" can sometimes be used interchangeably. It should be pointed out that when the distinction between them is not emphasized, the meanings they intend to express are consistent.

[0057] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. A person of ordinary skill in the art can appreciate that with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.

[0058] References to "one embodiment" or "some embodiments" etc. described in this specification mean that a particular feature, structure or characteristic described in conjunction with the embodiment is included in one or more embodiments of the present application. Thus, the phrases "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear at different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0059] In the present application, "at least one" means one or more, and "plurality" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: including the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.

[0060] For the convenience of description, the basic concepts involved in the embodiments of the present application are first described in detail below.

[0061] 1. Integrated development environment (IDE)

[0062] IDE is an application that supports software development. It integrates functions such as editing, compiling, debugging, and running programming languages ​​so that developers can complete various stages of software development in one interface.

[0063] 2. Plugins

[0064] A plug-in is a program or component that extends or enhances the functionality of software. It can be installed in the software or interact with the software as an external module. Plug-ins are usually provided by third-party developers to meet the needs or preferences of different users.

[0065] Taking IDE as an example, the types of IDE plug-ins may include but are not limited to: functional plug-ins, configuration operation plug-ins, editing area operation plug-ins, etc.

[0066] Functional plug-ins are divided into two categories. The first category is the function of accessing third-party system platforms. This type of plug-in allows users to directly access and operate data and services of other systems or platforms in the IDE, such as DTS order management, Issue management, AR management, search function, multi-language translation, and recommendations for current users. The second category is the middleware embedding function. This type of functional plug-in allows users to directly use and manage some commonly used middleware tools in the IDE, such as database query, HDFS big data storage, SFTP file management operations, Kafka message analysis and monitoring, etc.

[0067] Configuration operation plug-ins are mainly used to modify or adjust some settings or parameters of IDE or other plug-ins. This type of plug-in is divided into two categories. The first category is IDE global configuration, which allows users to customize some global properties or options in the IDE, such as theme style configuration, font size configuration, shortcut key configuration, etc. The second category is the plug-in's own function option configuration, which allows users to modify or adjust some functions or behaviors of the plug-in itself in the IDE, such as data collection settings, plug-in content display settings, etc.

[0068] Editing area operation plug-ins are mainly used to enhance or improve the code editing function in the IDE. There are many types of such plug-ins, such as code completion / generation plug-ins, which can automatically prompt or generate some appropriate code snippets based on user input or context, such as variable names, function names, keywords, etc.; syntax highlighting plug-ins can add different colors or styles to different elements in the code according to different programming languages ​​or file types, such as comments, strings, operators, etc.; there are also language LSP service-related plug-ins, which can provide some advanced editing functions for some specific programming languages, such as syntax checking, error prompts, refactoring, jump definitions, etc.

[0069] 3. Card-style interaction

[0070] Card-based interaction is a design pattern that supports flexible user interfaces. It divides information or functions into small pieces so that users can quickly browse and select. Each card is an independent entry point and can contain content such as text, images, videos, links, and some action buttons or menus. Card-based interaction can adapt to the window size for dynamic layout, improving user experience and information communication efficiency.

[0071] 4. Waterfall display

[0072] Waterfall display is a page layout method that arranges multiple cards in multiple columns at different heights, creating an uneven effect similar to a waterfall. Waterfall display can make full use of space and display more content, while also having good visual effects and user experience.

[0073] 5. Personalized layout

[0074] Personalized layout dynamically adjusts the content and order of cards based on user preferences and behaviors to provide information or functions that better meet user needs and interests. Personalized card layout can increase user engagement and satisfaction, while also improving the efficiency and value of information dissemination.

[0075] The relevant technologies and solutions of the embodiments of the present application are described in detail below.

[0076] Since the 1990s, with the demand for software development and the advancement of technology, many excellent lightweight text editors and code development IDEs have emerged. They provide developers with powerful functions, efficient interfaces, rich plug-ins and flexible customization. Among them, Sublime, Notepad++ and others are some lightweight and fast text editors that support lightweight and fast code editing or text processing. Subsequently, some popular IDE products including Visual Studio, Eclipse, VSCode, Intellij family series (such as Idea, Pycharm) appeared, which support multiple programming languages ​​and platforms and can help developers write, build, debug and run various software projects.

[0077] According to Github's 2022 annual report, by the end of 2022, there were 94 million developers around the world hosting and collaborating on Github for code. These developers will choose one or more code editors or IDEs that suit their needs and preferences to complete their work.

[0078] In addition to providing basic editing and development functions, all of these text and code editors support the extension of existing functions in the form of plug-ins to enhance their performance and applicability. Developers can install different plug-ins to implement different functions according to their needs and preferences, such as code completion, syntax highlighting, formatting, debugging, version control, etc. Some popular editors and IDEs also have a large plug-in community where developers can find or share various useful plug-ins. An extensible plug-in ecosystem has been formed based on basic editors and IDEs, providing developers with more choices and convenience.

[0079] The number and download volume of plugins reflect the popularity and feature richness of editors and IDEs. Taking the current mainstream IDEs Intellij and VSCode as examples, the number of plugins in the current plugin market is in the tens of thousands, covering various programming languages ​​and development tools. For some popular plugins, the download volume has reached tens of millions, indicating that they have high practical value. These plugins not only improve the work efficiency of developers, but also enrich the developer experience of using IDE by extending more functions.

[0080] However, the operation methods of various plug-ins are complicated, there is no unified entrance, and different plug-ins are used in different ways. This makes it extremely inconvenient for users to operate plug-ins. Users need to find different plug-ins in different places. The display and interactive use of plug-ins are not flexible enough, which increases the user's usage cost and learning difficulty, and reduces the user's efficiency and experience in using plug-ins.

[0081] Since the card-style display mechanism is a design display mode that presents information to users in a concise, clear, and interactive manner, it can help users quickly browse the main content of the card display module and achieve quick interaction. In view of this, the embodiment of the present application provides a method for displaying and managing plug-ins through a card-style display mechanism, providing users with the ability to quickly interact with plug-ins, thereby reducing the user's usage cost and learning difficulty, and improving the user's efficiency and experience in using plug-ins.

[0082] It should be noted that the method of displaying plug-ins through the card display mechanism can be applied to any scenario that includes the plug-in mechanism, such as: Office software such as Word, Excel, PowerPoint, lightweight editors such as Notepad++, SublimeText, and web browsers such as Chrome, Firefox, and Edge. These products can use the card form to manage and display plug-ins, thereby enhancing the expressiveness and efficiency of plug-ins.

[0083] Figure 1is a schematic flow chart of a method for displaying a plug-in provided in an embodiment of the present application. Figure 1 As shown, the method may include steps 110-120, and steps 110-120 are described in detail below.

[0084] Step 110: The card-type plug-in manager identifies at least one target plug-in from a plurality of plug-ins.

[0085] As an example, in an embodiment of the present application, a card-style plug-in manager can be loaded into a target page (also referred to as a card display page), and the card-style plug-in manager is responsible for identifying and managing all plug-ins that can be displayed in the form of cards on the target page.

[0086] It should be understood that the above-mentioned plug-in that can be displayed in the form of a card on the target page can also be called a target plug-in.

[0087] For example, taking IDE as an example, after the plug-in developer puts the plug-in online on the plug-in market, the user downloads the plug-in to the IDE. The card-style plug-in manager will scan the newly installed plug-in through the plug-in discovery mechanism to determine whether the plug-in meets the specification requirements for being displayed in the form of a card. If the plug-in meets the specification requirements for display, the plug-in can be determined as a target plug-in.

[0088] In the embodiment of the present application, the target plug-in needs to be registered with the card-type plug-in manager, and the user interface (UI) included in the configuration file of the target plug-in indicates that the target plug-in is displayed in the UI in the form of a card.

[0089] The following is a solution for plug-in developers to develop plug-ins that can be displayed in the form of cards on the target page.

[0090] As an example, the above scheme relies on the IDE environment, and the IDE base contains many core services, such as language services, debugging services, tuning services, perception services, etc. Based on the capabilities provided by these services, support for the necessary capabilities of upper-level modules, applications, and plug-ins can be provided. For the development and integration of plug-ins, there will be a plug-in development support module to support. In order to expand the effects and capabilities of the card-style display of plug-ins, it is necessary to embed the card-style plug-in management and display capabilities in the plug-in development support module. At the same time, during the plug-in development process, the plug-in developer performs relevant configurations on the plug-in that needs to be displayed in the form of a card in accordance with the access mechanism specification of the card plug-in. For example, the plug-in is registered with the above-mentioned card-style plug-in manager. For another example, by specifying the layout and design of the UI in the plug-in configuration file (for example, the Service plugin.xml configuration file), the layout and design of the UI is to display the plug-in in the form of a card on the UI, so that the plug-in can be displayed and run in the form of a card in the card display page. For another example, the interaction logic between the plug-in and the card display page can be specified in the plug-in configuration file (eg, Service plugin.xml configuration file) so that the main content information of the plug-in's functions and business content information can be displayed in the plug-in card in the card display page.

[0091] Step 120: The card-type plug-in manager displays the target plug-in on the target page in the form of a card.

[0092] In the embodiment of the present application, the card-type plug-in manager can display the target plug-in in the target page in the form of a card. That is, the target page includes at least one card-type display unit, and each card-type display unit is used to display a target plug-in. The user can directly operate the main functions of the target plug-in displayed in the card-type display unit, and the user can also directly view the main business content information of the target plug-in displayed in the card-type display unit.

[0093] It should be understood that the target plug-in displayed in the above-mentioned card-type display unit can also be called a card-type plug-in.

[0094] In the embodiment of the present application, the card-type plug-in manager can support real-time projection between the main functions and main business content information of the target plug-in and the card-type display unit. In a possible implementation, the card-type plug-in manager can obtain the functions and main content information of the target plug-in from the configuration file of the target plug-in through the registration interface of the target plug-in, and fill the functions and main content information of the target plug-in into the card-type display unit corresponding to the target plug-in. The user can perform simple and quick operations such as clicking or inputting on the plug-in (card-type plug-in) displayed in the card-type display unit, thereby realizing rapid interaction with the plug-in function.

[0095] In the above technical solution, plug-ins are quickly configured and accessed through cards. Users can quickly find the plug-ins they need to use through a unified entrance, browse and use different plug-ins, and can efficiently get started with the functions of the plug-ins. The card-style plug-in display and interaction form is a novel plug-in management method. It presents the main functions and information of the plug-in in the form of cards, allowing users to quickly browse, select and use the plug-in. The quick interaction brought by the card method helps to improve the user's efficiency in using the plug-in, increase the user's stickiness to the plug-in, and then improve the reputation of the plug-in, thereby further increasing user usage and enhancing the value of the plug-in.

[0096] The embodiment of the present application does not specifically limit the layout of multiple card-type plug-ins on the target page, and the layout may include but is not limited to: layout in a waterfall flow manner, layout in a horizontal scrolling manner.

[0097] As an example, Figure 2 In order to display the UI design effect of card-type plug-ins in a waterfall flow manner, a waterfall-like visual effect is formed. Each plug-in is presented in the form of a card, which can display the main functions and main business content information of the plug-in. It allows users to browse, manage and use multiple plug-ins on one interface. This UI design effect is not only beautiful, but also convenient for users to quickly find and use the required plug-ins.

[0098] Optional, such as Figure 2 As shown, this UI interface also provides the functions of user personalization and plug-in custom configuration. One example allows users to modify the theme, font, color and other styles of the target interface according to their needs and preferences. Another example allows users to drag and drop layout card-style plug-ins according to their needs and scenarios, adjust or customize the size, layout, order, etc. of card-style plug-ins, so that the arrangement order and layout of card-style plug-ins are more in line with their own habits. Different users can have different layout display effects, and personalized layout configuration is supported. In this way, users can create a card-style plug-in waterfall display interface that suits their own habits and tastes.

[0099] For example, in a specific implementation process, the card-type plug-in manager can jump to the personalized setting interface according to the user's instruction to implement personalized layout configuration of the target interface and / or the card-type plug-in.

[0100] Optionally, in some embodiments, in terms of the column dimension, it is also possible to support nesting of column layout scaffolds, that is, nesting sub-columns in columns, thereby providing flexible and diverse layout display effects according to different plug-in content display requirements.

[0101] In the embodiment of the present application, users can quickly interact with the plug-in functions by clicking on the card-type plug-in. The card presents the main capabilities of the plug-in. By displaying the main capabilities of the plug-in on the card, the plug-in capabilities can be used without entering the plug-in details page, saving the user time to find the plug-in entrance, and by presenting the main capabilities of the plug-in extracted in the card, the user can focus more on the operation of key capabilities, improving the efficiency of the user in using the plug-in capabilities.

[0102] Combine the following Figures 3 to 6 A specific implementation method for fast interaction between a user and a card-type plug-in is described in detail. It should be understood that Figures 3 to 6 The examples are only intended to help those skilled in the art understand the embodiments of the present application, and are not intended to limit the embodiments of the present application to the specific numerical values ​​or specific scenarios illustrated. Figures 3 to 6 It is obvious that various equivalent modifications or changes can be made, and such modifications and changes also fall within the scope of the embodiments of the present application.

[0103] For example, Figure 3 This is an example of quick interaction with theme plug-ins. Users only need to click on the corresponding theme style on the card to complete the one-click switch, and the configuration will take effect in real time. Figure 4 This is an example of quick interaction of project management plug-ins. Users can understand the status of each project issue in real time through the content displayed in the card, including some metadata information such as the severity level of the issue and the repair status. As the issue status changes, the card list can also be dynamically updated. Figure 5 This is an example of a quick interaction with a recommendation plug-in. It can use rich media such as pictures to focus on the content that the current user is interested in. A good display method can also attract more user clicks. Figure 6 This is an example of quick interaction with input plug-ins. For example, when using the currently popular Copilot code assistance plug-in, the prerequisite is to log in to the Github account. Through the card-style method, users can explicitly perceive this operation, and the card-style entrance can guide users to log in quickly, thereby improving the interactive experience between users and plug-ins.

[0104] Optionally, in some embodiments, in addition to quick interaction with the card-type plug-in, quick navigation to the plug-in details module is also supported to perform more other capabilities or detailed operations.

[0105] Combine the following Figures 7 to 10 A specific implementation method for users to quickly navigate to the plug-in details module through a card-type plug-in is described in detail. It should be understood that Figures 7 to 10The examples are only intended to help those skilled in the art understand the embodiments of the present application, and are not intended to limit the embodiments of the present application to the specific numerical values ​​or specific scenarios illustrated. Figures 7 to 10 It is obvious that various equivalent modifications or changes can be made, and such modifications and changes also fall within the scope of the embodiments of the present application.

[0106] For example, Figure 7 This is an example of a quick jump to a theme plug-in. For theme configuration, in addition to quick template-based interactions, users can also make more advanced and fine-grained configurations as needed. For example, you can quickly navigate to the plug-in details module by clicking Customization. Figure 8 This is an example of a quick jump to a project management plug-in. For issue management, users can also find an unfinished issue and click on it to enter the details for further viewing and modification of the issue details as needed. Fig. 9 This is an example of a quick jump to a recommendation plug-in. For personalized recommendations, users can scroll through the card-style display to select the content they are interested in, and click to enter the details to view the specific recommended content. Fig.10 This is an example of a quick jump for search plug-ins. It can also be presented in a good interactive form in the form of a card, providing a simple and generous search box. Users can search on demand and click the search button to navigate to the search results list.

[0107] It can be seen from the above embodiments that the card-style display method greatly provides the flexibility of plug-in use and improves the efficiency of users using plug-ins. At the same time, the good display and interaction form also greatly enhances the user's plug-in use experience.

[0108] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0109] Combination of the above Figures 1 to 10 , describes in detail the method provided by the embodiment of the present application, and will be combined with Figure 11-Figure 12 , describes in detail the embodiment of the device of the present application. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, so the parts not described in detail can refer to the previous method embodiment.

[0110] Fig.11It is a schematic block diagram of a device 1100 for displaying plug-ins in an embodiment of the present application. The device 1100 is applied to a card-type plug-in manager, and the device 1100 includes: an identification module 1110 and a display module 1120. Among them, the identification module 1110 is used to identify at least one target plug-in from multiple plug-ins, and the at least one target plug-in is registered with the card-type plug-in manager. The configuration file of each of the target plug-ins includes the user interface UI layout information of the target plug-in, and the UI layout information of the target plug-in indicates that the target plug-in is displayed in the form of a card on the UI; the display module 1120 is used to display the at least one target plug-in in the form of a card on the target page of the UI according to the UI layout information of each target plug-in, and the target page includes at least one card-type display unit, and each card-type display unit is used to display a target plug-in.

[0111] Optionally, each of the card-type display units displays the function and business content information of the target plug-in.

[0112] Optionally, the configuration file of the target plug-in also includes the function and business content information of the target plug-in, and the device 1100 also includes: an acquisition module, used to obtain the function and main content information of the target plug-in from the configuration file of the target plug-in through the registration interface of the target plug-in; a processing module is used to fill the function and main content information of the target plug-in into a card-type display unit corresponding to the target plug-in.

[0113] Optionally, the card-type display unit supports a user to use a target plug-in displayed in the card-type display unit.

[0114] Optionally, the device 1100 also includes: a receiving module for receiving a user's first instruction information, wherein the first instruction information is used to instruct an operation on a first target plug-in displayed in a first card-type display unit; and a processing module for completing the interaction between the user and the first target plug-in according to the first instruction information.

[0115] Optionally, the receiving module is used to receive second instruction information from the user, wherein the second instruction information is used to indicate access to detailed content information of the first target plug-in displayed in the first card-type display unit; the processing module is used to jump to the details page of the first target plug-in according to the second instruction information, and the details page is used to display the detailed content information of the first target plug-in.

[0116] Optionally, the target page supports a user to personalize the page, and the personalization includes modifying the style of the target page and modifying the style of the at least one card-type display unit.

[0117] Optionally, the receiving module is used to receive a third indication information from the user, and the third indication information is used to indicate modification of the style of the target page; the processing module is used to jump to the interface of personalized settings of the target page according to the third indication information, and personalize the target page.

[0118] Optionally, the personalized configuration of the target page includes configuring the theme, font, and color of the target page.

[0119] Optionally, the receiving module is used to receive a fourth indication information from the user, and the fourth indication information is used to indicate that the style of the first target plug-in displayed in the first card-type display unit should be modified; the processing module is used to jump to the plug-in personalization setting interface according to the fourth indication information, and personalize the size, layout, and display order of the first target plug-in.

[0120] Optionally, the at least one card-type display unit is arranged in a waterfall flow manner or in a horizontal scrolling manner in the target page.

[0121] It should be noted that the device 1100 shown in the data processing plug-in is embodied in the form of a functional module. As an example, the "module" can be a software program that implements the above functions.

[0122] Fig.12 It is a schematic diagram of the hardware structure of the computing device 1200 provided in an embodiment of the present application. Fig.12 The computing device 1200 shown includes a memory 1201, a processor 1202, a communication interface 1203, and a bus 1204. The memory 1201, the processor 1202, and the communication interface 1203 are connected to each other through the bus 1204.

[0123] The memory 1201 may be a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1201 may store a program. When the program stored in the memory 1201 is executed by the processor 1202, the processor 1202 is used to execute each step of the method of the embodiment of the present application. For example, the processor 1202 may execute the above Figure 1 The method shown.

[0124] The communication interface 1203 uses a transceiver device such as but not limited to a transceiver to implement communication between the computing device 1200 and other devices or a communication network.

[0125] The bus 1204 may include a path for transmitting information between various components of the computing device 1200 (eg, the memory 1201 , the processor 1202 , and the communication interface 1203 ).

[0126] Processor 1202 can adopt a general central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), a graphics processing unit (GPU) or one or more integrated circuits to execute relevant programs to implement the method of the method embodiment of the present application.

[0127] The processor 1202 may also be an integrated circuit chip with signal processing capability. In the implementation process, each step of the method of the present application may be completed by an integrated logic circuit of hardware in the processor 1202 or by instructions in the form of software.

[0128] The processor 1202 may also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, or discrete hardware components. The methods, steps, and logic block diagrams disclosed in the embodiments of the present application may be implemented or executed. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc. The steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed by a hardware decoding processor, or may be executed by a combination of hardware and software modules in the decoding processor. The software module may be located in a mature storage medium in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, or the like. The storage medium is located in the memory 1201, and the processor 1202 reads the information in the memory 1201 and completes the processing in combination with its hardware. Fig.11 The functions required to be performed by the modules included in the device 1100 shown, or the functions required to perform the method embodiments of the present application Figure 1 The method shown.

[0129] The embodiment of the present application also provides a computer-readable medium, which stores a program code for execution by a device, and the program code includes a program for executing the method in the embodiment of the present application.

[0130] As an example, the computer-readable storage medium may be any available medium that can be stored by a computing device or a data storage device such as a data center that includes one or more available media. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk).

[0131] The embodiment of the present application also provides a computer program product including instructions, which may include instructions. When the instructions in the computer program product are executed on a computer, the computer executes the method in the embodiment of the present application.

[0132] The above embodiments can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented by software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that contains one or more available media sets. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium. The semiconductor medium can be a solid-state hard disk.

[0133] It should be understood that the term "and / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. A and B can be singular or plural. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship, but it may also indicate an "and / or" relationship. Please refer to the context for specific understanding.

[0134] In this application, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can be represented by: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.

[0135] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0136] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0137] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0138] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0139] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0140] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories (ROM), random access memories (RAM), magnetic disks or optical disks.

[0141] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for displaying a plug-in, characterized in that: include: The card-type plug-in manager identifies at least one target plug-in from multiple plug-ins, and the at least one target plug-in is registered with the card-type plug-in manager. The configuration file of each target plug-in includes user interface UI layout information of the target plug-in, and the UI layout information of the target plug-in indicates that the target plug-in is displayed in a card manner on the UI. The card-type plug-in manager displays the at least one target plug-in in a card-like manner on a target page of the UI according to the UI layout information of each target plug-in. The target page includes at least one card-type display unit, and each card-type display unit is used to display a target plug-in.

2. The method according to claim 1, characterized in that Each of the card-type display units displays the function and business content information of the target plug-in.

3. The method according to claim 2, characterized in that The target plug-in configuration file also includes the function and business content information of the target plug-in. The method further comprises: The card-type plug-in manager obtains the function and main content information of the target plug-in from the configuration file of the target plug-in through the registration interface of the target plug-in; The card-type plug-in manager fills the function and main content information of the target plug-in into the card-type display unit corresponding to the target plug-in.

4. The method according to any one of claims 1 to 3, characterized in that The card-type display unit supports a user to use a target plug-in displayed in the card-type display unit.

5. The method according to claim 4, characterized in that The method further comprises: The card-type plug-in manager receives first instruction information from a user, where the first instruction information is used to instruct to operate a first target plug-in displayed in a first card-type display unit; The card-type plug-in manager completes the interaction between the user and the first target plug-in according to the first indication information.

6. The method according to claim 4 or 5, characterized in that: The method further comprises: The card-type plug-in manager receives second instruction information from a user, where the second instruction information is used to instruct access to detailed content information of a first target plug-in displayed in a first card-type display unit; The card-type plug-in manager jumps to the detail page of the first target plug-in according to the second indication information, and the detail page is used to display detailed content information of the first target plug-in.

7. The method according to any one of claims 1 to 6, characterized in that The target page supports the user to personalize the page, and the personalization includes modifying the style of the target page and modifying the style of the at least one card-type display unit.

8. The method according to claim 7, characterized in that The method further comprises: The card-type plug-in manager receives third instruction information from a user, where the third instruction information is used to instruct to modify the style of the target page; The card-type plug-in manager jumps to the interface for personalized settings of the target page according to the third indication information, and performs personalized configuration on the target page.

9. The method according to claim 8, characterized in that The personalized configuration of the target page includes configuring the theme, font, and color of the target page.

10. The method according to any one of claims 7 to 9, characterized in that The method further comprises: The card-type plug-in manager receives fourth instruction information from a user, where the fourth instruction information is used to instruct to modify the style of the first target plug-in displayed in the first card-type display unit; The card-type plug-in manager jumps to the plug-in personalization setting interface according to the fourth indication information, and performs personalization configuration on the size, layout, and display order of the first target plug-in.

11. The method according to any one of claims 1 to 10, characterized in that The at least one card-type display unit is arranged in the target page in a waterfall flow manner or in a horizontal scrolling manner.

12. A device for displaying a plug-in, characterized in that: The device is applied to a card-type plug-in manager, and the device includes: an identification module, configured to identify at least one target plug-in from a plurality of plug-ins, wherein the at least one target plug-in is registered with the card-type plug-in manager, wherein the configuration file of each target plug-in includes user interface (UI) layout information of the target plug-in, and the UI layout information of the target plug-in indicates that the target plug-in is displayed in a card-like manner on the UI; A display module is used to display the at least one target plug-in in a card-like manner on a target page of the UI according to the UI layout information of each target plug-in, wherein the target page includes at least one card-like display unit, and each card-like display unit is used to display a target plug-in.

13. The device according to claim 12, characterized in that Each of the card-type display units displays the function and business content information of the target plug-in.

14. The device according to claim 13, characterized in that The target plug-in configuration file also includes the function and business content information of the target plug-in. The device also includes: An acquisition module, used to acquire the function and main content information of the target plug-in from the configuration file of the target plug-in through the registration interface of the target plug-in; The processing module is used to fill the function and main content information of the target plug-in into the card-type display unit corresponding to the target plug-in.

15. The device according to any one of claims 12 to 14, characterized in that The card-type display unit supports a user to use a target plug-in displayed in the card-type display unit.

16. The device according to claim 15, characterized in that The device also includes: A receiving module, used for receiving first instruction information from a user, where the first instruction information is used for instructing to operate a first target plug-in displayed in a first card-type display unit; A processing module is used to complete the interaction between the user and the first target plug-in according to the first indication information.

17. The device according to claim 15 or 16, characterized in that A receiving module, used for receiving second instruction information from a user, where the second instruction information is used for instructing to access detailed content information of a first target plug-in displayed in a first card-type display unit; A processing module is used to jump to a detail page of the first target plug-in according to the second indication information, wherein the detail page is used to display detailed content information of the first target plug-in.

18. The device according to any one of claims 12 to 17, characterized in that The target page supports the user to personalize the page, and the personalization includes modifying the style of the target page and modifying the style of the at least one card-type display unit.

19. The device according to claim 18, characterized in that A receiving module, used for receiving third instruction information from a user, wherein the third instruction information is used for instructing to modify the style of the target page; The processing module is used to jump to the interface of personalized settings of the target page according to the third indication information, and perform personalized configuration on the target page.

20. The device according to claim 19, characterized in that The personalized configuration of the target page includes configuring the theme, font, and color of the target page.

21. The device according to any one of claims 18 to 20, characterized in that A receiving module, used for receiving fourth instruction information from a user, where the fourth instruction information is used for instructing to modify the style of the first target plug-in displayed in the first card-type display unit; The processing module is used to jump to the plug-in personalized setting interface according to the fourth indication information, and perform personalized configuration on the size, layout and display order of the first target plug-in.

22. The device according to any one of claims 12 to 21, characterized in that The at least one card-type display unit is arranged in the target page in a waterfall flow manner or in a horizontal scrolling manner.

23. A computing device, characterized in that include: A processor and a memory, wherein the memory is used to store program instructions, and the processor is used to call the program instructions to execute the method according to any one of claims 1 to 11.

24. A computer-readable storage medium, characterized in that: The computer-readable medium stores a program code for execution by a computing device, the program code including instructions for executing the method according to any one of claims 1 to 11.

25. A computer program product comprising instructions, characterized in that When the computer program product is executed on a computing device, the computing device is caused to execute the method according to any one of claims 1 to 11.

Images