Vehicle-mounted desktop card implementation method and device, computer equipment and storage medium

Abstract

The invention belongs to the vehicle-mounted field, and relates to a vehicle-mounted desktop card implementation method and device, computer equipment and a storage medium, and the method comprises the steps that desktop applications construct a card container, and the card container is used for bearing cards displayed by the applications; the method comprises the steps that a desktop application obtains cards needing to be displayed in a current system, the collected application cards are put into a set, and the application cards are sorted according to requirements; a card parent layout is realized by the desktop application, and cards of all applications in the set are added into a card container; performing event monitoring registration on the control of the card by the card application; and when the card application receives a broadcast sent according to the registered content after the user clicks the desktop card, the card application responds to the event. A desktop card is realized by using an Android native Widget scheme, the workload of a desktop can be reduced, and the display content and layout of the card are realized by a card application; the coupling degree between the application and the desktop can be reduced, and the development efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the field of vehicle-mounted technology, and in particular to a method, device, computer equipment and storage medium for realizing a vehicle-mounted desktop card. Background Art

[0002] As a vehicle-mounted accessory, the car desktop card is designed to improve the driver's driving experience and information acquisition efficiency. It usually refers to a small, exquisite and feature-rich vehicle display accessory that can fit the layout of the vehicle's center console and display various practical information or shortcut functions in the form of cards.

[0003] In the current in-vehicle system, it is a common practice to display application card information on the car desktop. Displaying cards on the car desktop allows users to view application information more intuitively and operate related applications more quickly. In the in-vehicle scenario, users do not need to open the applications one by one to operate, but can operate the functions directly on the desktop card. For example, for multimedia applications, the current multimedia playback information can be directly displayed on the car desktop and shortcut operation buttons can be provided for users to control multimedia playback.

[0004] In the prior art, desktop cards are usually implemented by defining protocols between desktop applications and card applications, which requires both parties to jointly define data protocols based on business scenarios. If there is too much card data, the required protocol interfaces will also increase, and both parties will also need to establish a connection through Binder. Furthermore, if the requirements on the application side are modified, the desktop application must also change accordingly, and the coupling between the two sides is obviously too much. Summary of the invention

[0005] In order to solve the above technical problems, the present invention provides a method for realizing a vehicle-mounted desktop card, which adopts the following technical solution, including:

[0006] A card container is constructed by a desktop application, and the card container is used to carry the cards displayed by each application;

[0007] The desktop application obtains the cards that need to be displayed in the current system, puts the collected application cards into a collection, and sorts the application cards according to the needs;

[0008] The desktop application implements the card parent layout, and adds the cards of all applications in the collection to the card container one by one;

[0009] The card application registers event monitoring for the card's controls;

[0010] When the card application receives a broadcast from the user because the user clicks on the desktop card, it responds to the event based on the registered content.

[0011] Preferably, the step of constructing a card container by a desktop application, wherein the card container is used to carry cards displayed by each application specifically includes:

[0012] Select the container type based on the system's memory, CPU resources, and whether the card needs to scroll horizontally or vertically;

[0013] Design the layout of the card container;

[0014] Initialize the card container.

[0015] Preferably, the step of obtaining the cards that need to be displayed in the current system by the desktop application, putting the collected application cards into a set, and sorting the application cards according to the needs specifically includes:

[0016] Traverse all installed applications in the system and obtain the card data they provide;

[0017] Store the collected card data in a data structure;

[0018] Sort the cards according to user needs or information display priority.

[0019] Preferably, the step of implementing the card parent layout by the desktop application and adding the cards of all applications in the collection to the card container one by one specifically includes:

[0020] Design the overall layout of the card, including the card size, margins, and background;

[0021] Fill the card data in the collection into the card layout to generate a specific card view;

[0022] Add the populated card view to the card container to display it on the page.

[0023] Preferably, the step of registering event monitoring for the card control by the card application specifically includes:

[0024] Identify the individual controls in the card layout;

[0025] Register event listeners for each control;

[0026] Implement event handling logic in event listeners and perform actions based on user operations.

[0027] Preferably, when the card application receives a broadcast from the user according to the registered content after clicking on the desktop card, the step of responding to the event specifically includes:

[0028] The card application receives user operation notifications from the desktop application through a broadcast receiver;

[0029] Extract user operation information from the received broadcast;

[0030] Execute response actions based on the parsed user operation information.

[0031] Preferably, after the card application receives a broadcast from the user according to the registered content after clicking the desktop card, the step of responding to the event also includes:

[0032] The card application updates the data and sends the updated data to the desktop application, and the desktop card refreshes the desktop layout.

[0033] In order to solve the above technical problems, the present invention also provides a vehicle-mounted desktop card implementation device, which adopts the following technical solution, including:

[0034] A construction module, used to construct a card container from a desktop application, wherein the card container is used to carry cards displayed by each application;

[0035] The acquisition module is used to obtain the cards that need to be displayed in the current system from the desktop application, put the collected application cards into a collection, and sort the application cards according to the needs;

[0036] An adding module is used to implement the card parent layout by the desktop application, and add the cards of all applications in the collection to the card container one by one;

[0037] The registration module is used for the card application to register event monitoring for the card controls;

[0038] The response module is used to respond to events when the card application receives a broadcast from the user based on the registered content after clicking on the desktop card.

[0039] In order to solve the above technical problems, the present invention also provides a computer device, which adopts the technical solution described below, including a memory and a processor, wherein the memory stores computer-readable instructions, and the processor implements the steps of the above-mentioned vehicle-mounted desktop card implementation method when executing the computer-readable instructions.

[0040] In order to solve the above technical problems, the present invention also provides a computer-readable storage medium, which adopts the technical solution described below. The computer-readable storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the steps of the above-mentioned vehicle-mounted desktop card implementation method are implemented.

[0041] Compared with the prior art, the present invention has the following beneficial effects: using the Android native Widget solution to implement desktop cards instead of the binder communication method can reduce the workload of the desktop, and the card display content and layout are implemented by the card application; it can reduce the coupling between the application and the desktop and improve development efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] In order to more clearly illustrate the scheme in the present invention, a brief introduction is given below to the drawings required for use in the description of the embodiments of the present invention. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0043] Figure 1 is a flow chart of an embodiment of a method for implementing a vehicle-mounted desktop card of the present invention;

[0044] Figure 2 It is a schematic diagram of the interaction between the desktop application and the card application in the vehicle-mounted desktop card implementation method of the present invention;

[0045] Figure 3 It is a structural schematic diagram of an embodiment of the vehicle-mounted desktop card implementation device of the present invention;

[0046] Figure 4 It is a schematic structural diagram of an embodiment of a computer device of the present invention. DETAILED DESCRIPTION

[0047] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by technicians in the technical field of the present invention; the terms used in the specification of the application herein are only for the purpose of describing specific embodiments and are not intended to limit the present invention; the terms "including" and "having" and any variations thereof in the specification and claims of the present invention and the above-mentioned drawings are intended to cover non-exclusive inclusions. The terms "first", "second", etc. in the specification and claims of the present invention or the above-mentioned drawings are used to distinguish different objects, not to describe a specific order.

[0048] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present invention. The appearance of the phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0049] In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings.

[0050] It should be noted that the vehicle-mounted desktop card implementation method provided in the embodiment of the present invention is generally executed by a server / terminal device, and accordingly, the vehicle-mounted desktop card implementation device is generally arranged in the server / terminal device.

[0051] It should be understood that the number of terminal devices, networks and servers is only illustrative. Depending on the implementation requirements, there can be any number of terminal devices, networks and servers.

[0052] The following embodiments are described by taking a vehicle desktop card implemented based on an Android native widget as an example.

[0053] Android native system-based widgets, also known as application widgets or small components, are miniature application views that can be embedded in other applications (such as the home screen). These widgets can receive regular updates and provide users with a convenient way to view part of the application without opening the application itself.

[0054] In the Android system, widgets have various functions. They can display information that users are interested in, such as weather, time, calendar events, etc. Users can view this information directly on the desktop, which improves the convenience of information acquisition. Secondly, widgets can also provide quick operation functions, such as music playback control, alarm setting, etc., so that users can perform related operations directly on the desktop, saving time and steps. In addition, some widgets also have reminder functions, which can be used to remind users of important matters, such as to-do items, reminder events, etc., further enhancing the efficiency of users' lives and work.

[0055] In addition to the above functions, Widgets also have the feature of personalized customization. Users can customize the style and functions of Widgets according to their needs and preferences, such as selecting different themes, adjusting the size and position, etc. This personalized customization feature makes Widgets more in line with users' personalized needs and improves user experience.

[0056] In addition, Widgets can update information in real time, allowing users to keep up to date with the latest developments. For example, news, stock quotes and other information can be displayed on the desktop in real time through Widgets, allowing users to obtain the latest information as soon as possible.

[0057] Embodiment 1

[0058] Please refer to Figure 1, shows a flow chart of an embodiment of a method for implementing a vehicle-mounted desktop card of the present invention. The method for implementing a vehicle-mounted desktop card comprises the following steps:

[0059] Step S1: A card container is constructed by a desktop application, and the card container is used to carry cards displayed by each application.

[0060] In this embodiment, the electronic device (e.g., server / terminal device) on which the vehicle desktop card implementation method runs can receive the vehicle desktop card implementation request through a wired connection or a wireless connection. It should be noted that the above wireless connection method may include but is not limited to 3G / 4G / 5G connection, WiFi connection, Bluetooth connection, WiMAXX connection, Zigbee connection, UWB (ultra wideband) connection, and other wireless connection methods currently known or to be developed in the future.

[0061] In this embodiment, step S1, a card container is constructed by a desktop application, and the card container is used to carry the cards displayed by each application, and specifically may include the following steps:

[0062] S11. Select a container type based on the system's memory, CPU resources, and whether the card needs to scroll horizontally or vertically.

[0063] For system memory and CPU resources, if resources are limited, choose a simpler CardLayout type to avoid overly complex layout management that consumes too many resources. For example, use the basic CardLayout class to manage the display of cards through the add and show methods to reduce unnecessary calculations and rendering.

[0064] If the card needs to achieve horizontal or vertical scrolling effects, you need to consider using a CardLayout variant that supports scrolling or combining it with other layout managers. In Java Swing, although CardLayout itself does not support scrolling, this function can be achieved by nesting scroll panels (such as JScrollPane). At the same time, you can also consider customizing CardLayout to meet specific scrolling requirements.

[0065] On the Android platform, if you need to achieve a horizontal card-style sliding effect, you can combine RecyclerView with CardView. RecyclerView provides flexible scrolling and layout management, while CardView can achieve a beautiful card effect. By properly setting the layout manager of RecyclerView (such as LinearLayoutManager) and the layout of the card items, you can easily achieve horizontal or vertical scrolling.

[0066] S12. Design the layout of the card container.

[0067] You can use XML or code to define container layout parameters, such as margins, alignment, etc. This ensures that the container can adapt to different screen sizes and resolutions.

[0068] S13. Initialize the card container.

[0069] Call the constructor of the container class to create a container instance. Set the initial properties of the container, such as background color, scroll speed, etc.

[0070] Step S2, the desktop application obtains the cards that need to be displayed in the current system, puts the collected application cards into a collection, and sorts the application cards according to the needs.

[0071] In this embodiment, step S2, the desktop application obtains the cards that need to be displayed in the current system, puts the collected application cards into a set, and sorts the application cards according to the needs, which may specifically include the following steps:

[0072] S21. Traverse all installed applications in the system and obtain the card data provided by them.

[0073] Call the system API to obtain the list of installed applications. Traverse the application list and call the interface provided by each application to obtain the card data. Store the obtained card data in a collection, such as List or Map.

[0074] S22. Store the collected card data in a data structure.

[0075] Data is stored in categories based on card type or source. This ensures that the data structure supports fast access and updates.

[0076] S23. Sort the cards according to user needs or information display priority.

[0077] Define sorting rules, such as by time, priority, user preference, etc. Use a sorting algorithm to sort the card collection. Verify the sorting results to ensure they meet expectations.

[0078] For example, after the desktop application is started, you can also use the getAllProviders method in AppWidgetManagerCompat to obtain the cards that need to be displayed for the applications in the current system, put the collected application cards into a collection, and sort the cards according to needs.

[0079] Step S3: The desktop application implements the card parent layout and adds the cards of all applications in the collection to the card container one by one.

[0080] In this embodiment, step S3, implementing the card parent layout by the desktop application, and adding the cards of all applications in the collection to the card container one by one, may specifically include the following steps:

[0081] S31. Design the overall layout of the card, including the card size, margins, and background.

[0082] Define the XML layout file of the card, including the layout and style of the card content. Adjust the layout parameters of the card as needed, such as width, height, padding, etc.

[0083] S32. Fill the card data in the collection into the card layout to generate a specific card view.

[0084] Traverse the card collection and get the data for each card. Use data binding or manual settings to populate the card data into the controls of the card view. This ensures that the card content is displayed correctly without missing or incorrect data.

[0085] S33. Add the filled card view to the card container to display it on the page.

[0086] Call the add method of the container class to add the card views to the container one by one. Update the container's view to ensure that the newly added cards can be displayed immediately. Verify the position and order of the cards in the container to ensure that they meet expectations.

[0087] Desktop applications can also implement their own card parent layout by inheriting the AppWidgetHostView class, and then add all the application cards in the collection to the card container one by one.

[0088] In specific implementation, since the card application is active, the desktop application needs to monitor whether the current card is uninstalled. If it is uninstalled, the card of the application needs to be removed from the card container.

[0089] Step S4: The card application registers event monitoring for the card's controls.

[0090] In this embodiment, step S4, the card application registers event monitoring for the card control, and specifically may include the following steps:

[0091] S41. Identify each control in the card layout.

[0092] Traverse all controls in the card layout and identify the control type, such as buttons, text boxes, etc. According to the control type, select the appropriate event listener type, such as OnClickListener, OnFocusChangeListener, etc.

[0093] S42. Register event listeners for each control.

[0094] Call the control's registration method and pass in the event listener instance. Make sure the event listener can correctly receive and process events.

[0095] In specific implementation, the card application can register event listeners for the card controls through the remoteView mechanism.

[0096] S43. Implement event processing logic in the event listener and perform actions based on user operations.

[0097] Write event handling code, such as opening the app after clicking a button, displaying detailed information, etc. Test event handling logic to ensure that it functions properly and provides a good user experience.

[0098] Step S5, when the card application receives a broadcast from the user according to the registered content after clicking the desktop card, it responds to the event.

[0099] In this embodiment, step S5, when the card application receives a broadcast from the user according to the registered content after clicking on the desktop card, responding to the event may further include the following steps:

[0100] S51. The card application receives a user operation notification from the desktop application through a broadcast receiver.

[0101] Define the broadcast receiver class and override the onReceive method. Register the broadcast receiver in AndroidManifest.xml and specify the broadcast Action to be received.

[0102] S52: Extract user operation information from the received broadcast.

[0103] Information about user operations, such as the card ID clicked, operation type, etc. Call the getExtras method of the broadcast to obtain additional data. Parse the data and extract the required information.

[0104] S53: Execute a response action according to the parsed user operation information.

[0105] Call the corresponding processing method according to the operation type, such as opening the application, displaying the details page, executing a specific function, etc. Verify whether the response action is executed successfully to ensure user experience.

[0106] In some optional implementations of this embodiment, in step S5, after the card application receives a broadcast from the user according to the registered content after clicking the desktop card, after responding to the event, the following steps may be further included:

[0107] S6. The card application updates data and sends the updated data to the desktop application. The desktop card refreshes the desktop layout.

[0108] The card application is responsible for acquiring and updating data, including pulling the latest information from the network or other data sources and processing the data for subsequent use. When the data is updated, the card application needs to notify the desktop application.

[0109] Using Android's App Widget framework, card apps can send updated data to desktop apps. This can be done through the RemoteViews object, which allows apps to update the widget's UI without launching a full Activity. The card app builds a RemoteViews containing the new data and pushes it to the system service.

[0110] After receiving RemoteViews, the system service will apply it to the corresponding desktop widget. At this time, the desktop application will capture this change and trigger a refresh of the desktop layout. The refresh process involves redrawing the widget to display the latest data.

[0111] It should be noted that the Android native Widget framework provides a rich set of APIs, which enables this process to be carried out efficiently and reliably. At the same time, in order to ensure the consistency and real-time nature of the data, a synchronization mechanism can be established between the card application and the desktop application, such as using BroadcastReceiver to listen to data update events.

[0112] Figure 2 Schematic diagram of the interaction between the desktop application and the card application in the vehicle-mounted desktop card implementation method of the present invention. Figure 2 As shown, in Figure 1 In the in-vehicle desktop card implementation method shown, the desktop application interacts with the card application. It can be seen that the desktop application and the card application are independent of each other, through process isolation, and the remoteViews method of the Android native Widget is used to transmit data.

[0113] In-vehicle desktop applications refer to the user-vehicle interaction interface used in the in-vehicle infotainment system (IVI) or intelligent connected car platform. Users can intuitively and conveniently access and manage various functions and information in the in-vehicle system.

[0114] Features of the in-vehicle desktop application include:

[0115] With high integration, in-vehicle desktop applications usually integrate multiple functions such as navigation, music, telephone, vehicle settings, etc. Users can access and operate them through a unified interface.

[0116] It can be customized. Users can personalize the desktop layout, themes, and shortcuts according to their preferences and car-using habits to improve the user experience.

[0117] It can perform multi-task management and support multi-task parallel processing. Users can switch freely between different applications to improve operational efficiency.

[0118] The usage scenarios of the in-vehicle desktop application are:

[0119] In daily driving, users can quickly start common functions such as navigation, playing music, answering calls, etc. through the in-vehicle desktop application to improve driving safety and convenience.

[0120] Vehicle management: users can view vehicle status and make vehicle settings through desktop applications, such as adjusting seats, air conditioning, lights, etc., to achieve comprehensive management of the vehicle.

[0121] Entertainment and leisure: During long-distance driving or parking for a rest, users can enjoy music, videos and other entertainment content through desktop applications to enrich their travel life.

[0122] The in-car card application is a more lightweight and modular application form. It presents various functions and information in the form of cards, and users can quickly access the required content through simple operations such as sliding and clicking. The design of the card application is to improve the efficiency of information acquisition and reduce the cognitive burden of users.

[0123] The features of the vehicle card application are:

[0124] Intuitive and concise, the card application uses a simple interface and intuitive display method, allowing users to quickly obtain the required information and reduce the difficulty of operation.

[0125] Modular design, each card is an independent functional module, users can add or delete cards as needed to achieve flexible configuration of functions.

[0126] Dynamic updates: The card application supports real-time updates and can dynamically display real-time data such as vehicle status, weather forecast, and road conditions.

[0127] The usage scenarios of vehicle card applications are:

[0128] Quick access: During driving, users can quickly view key information such as vehicle status, navigation information, weather forecast, etc. through the card application to improve driving safety.

[0129] Personalized recommendations: Based on the user's car-using habits and preferences, the in-vehicle system can intelligently recommend relevant card applications, such as recommending cards for turning on the air conditioner or windows based on weather conditions.

[0130] Service subscription: users can subscribe to various services through the card application, such as charging reminders, maintenance reminders, roadside assistance, etc., to achieve intelligent management of services.

[0131] The beneficial effects of implementing this embodiment are: using the Android native Widget solution to implement desktop cards instead of using the binder communication method can reduce the desktop workload, and the card display content and layout are all implemented by the card application; it can reduce the coupling between the application and the desktop and improve development efficiency.

[0132] The present invention can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronic devices, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc. The present invention can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present invention can also be practiced in distributed computing environments, in which tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.

[0133] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through computer-readable instructions, and the computer-readable instructions can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, the aforementioned storage medium can be a non-volatile storage medium such as a disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

[0134] It should be understood that, although the steps in the flowchart of the accompanying drawings are displayed in sequence as indicated by the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least a part of the steps in the flowchart of the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a part of the sub-steps or stages of other steps.

[0135] Embodiment 2

[0136] Further references Figure 3 , as a response to the above Figure 1 The present invention provides an embodiment of a vehicle-mounted desktop card implementation device, and the device embodiment is similar to Figure 1 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.

[0137] like Figure 3 As shown, the vehicle-mounted desktop card implementation device 70 of this embodiment includes: a construction module 71, an acquisition module 72, an addition module 73, a registration module 74 and a response module 75. Among them:

[0138] A construction module 71, configured to construct a card container from a desktop application, wherein the card container is configured to carry cards displayed by each application;

[0139] The acquisition module 72 is used to acquire the cards that need to be displayed in the current system from the desktop application, put the collected application cards into a collection, and sort the application cards according to the requirements;

[0140] An adding module 73, used to implement a card parent layout by a desktop application, and add the cards of all applications in the collection to the card container one by one;

[0141] A registration module 74, used for the card application to register event monitoring for the card's controls;

[0142] The response module 75 is used to respond to the event when the card application receives a broadcast from the user according to the registered content after clicking the desktop card.

[0143] The beneficial effects of implementing this embodiment are: using the Android native Widget solution to implement desktop cards instead of using the binder communication method can reduce the desktop workload, and the card display content and layout are all implemented by the card application; it can reduce the coupling between the application and the desktop and improve development efficiency.

[0144] Embodiment 3

[0145] To solve the above technical problems, the embodiment of the present invention also provides a computer device. Figure 4 , Figure 4 This is a basic structural block diagram of the computer device in this embodiment.

[0146] The above-mentioned computer device 8 includes a memory 81, a processor 82, and a network interface 83 that are interconnected and communicated through a system bus. It should be noted that the figure only shows a computer device 8 having components of a memory 81, a processor 82, and a network interface 83, but it should be understood that it is not required to implement all the components shown, and more or fewer components can be implemented instead. Among them, those skilled in the art can understand that the computer device here is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to a microprocessor, an application specific integrated circuit (ASIC), a programmable gate array (FPGA), a digital processor (DSP), an embedded device, etc.

[0147] The computer device may be a desktop computer, a notebook computer, a PDA, a cloud server, etc. The computer device may interact with the user through a keyboard, a mouse, a remote control, a touch pad, or a voice control device.

[0148] The memory 81 includes at least one type of readable storage medium, including flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, disk, optical disk, etc. In some embodiments, the memory 81 may be an internal storage unit of the computer device 8, such as a hard disk or memory of the computer device 8. In other embodiments, the memory 81 may also be an external storage device of the computer device 8, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (FlashCard), etc. equipped on the computer device 8. Of course, the memory 81 may also include both the internal storage unit of the computer device 8 and its external storage device. In this embodiment, the memory 81 is generally used to store the operating system and various application software installed on the computer device 8, such as computer-readable instructions of the vehicle-mounted desktop card implementation method, etc. In addition, the memory 81 can also be used to temporarily store various types of data that have been output or are to be output.

[0149] The processor 82 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chips in some embodiments. The processor 82 is generally used to control the overall operation of the computer device 8. In this embodiment, the processor 82 is used to run the computer-readable instructions stored in the memory 81 or process data, such as running the computer-readable instructions of the vehicle-mounted desktop card implementation method.

[0150] The network interface 83 may include a wireless network interface or a wired network interface. The network interface 83 is generally used to establish a communication connection between the computer device 8 and other electronic devices.

[0151] The beneficial effects of implementing this embodiment are: using the Android native Widget solution to implement desktop cards instead of using the binder communication method can reduce the desktop workload, and the card display content and layout are all implemented by the card application; it can reduce the coupling between the application and the desktop and improve development efficiency.

[0152] Embodiment 4

[0153] The present invention also provides another embodiment, namely, providing a computer-readable storage medium, which stores computer-readable instructions, and the computer-readable instructions can be executed by at least one processor to enable the at least one processor to perform the steps of the above-mentioned vehicle desktop card implementation method.

[0154] The beneficial effects of implementing this embodiment are: using the Android native Widget solution to implement desktop cards instead of using the binder communication method can reduce the desktop workload, and the card display content and layout are all implemented by the card application; it can reduce the coupling between the application and the desktop and improve development efficiency.

[0155] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the various embodiment methods of the present invention.

[0156] Obviously, the embodiments described above are only some embodiments of the present invention, rather than all embodiments. The preferred embodiments of the present invention are given in the accompanying drawings, but they do not limit the patent scope of the present invention. The present invention can be implemented in many different forms. On the contrary, the purpose of providing these embodiments is to make the understanding of the disclosure of the present invention more thorough and comprehensive. Although the present invention has been described in detail with reference to the aforementioned embodiments, for those skilled in the art, it is still possible to modify the technical solutions recorded in the aforementioned specific embodiments, or to perform equivalent replacements for some of the technical features therein. Any equivalent structure made using the contents of the specification and drawings of the present invention, directly or indirectly used in other related technical fields, is also within the scope of patent protection of the present invention.

Claims

1. A method for implementing a vehicle-mounted desktop card, characterized in that: The steps include: A card container is constructed by a desktop application, and the card container is used to carry the cards displayed by each application; The desktop application obtains the cards that need to be displayed in the current system, puts the collected application cards into a collection, and sorts the application cards according to the needs; The desktop application implements the card parent layout, and adds the cards of all applications in the collection to the card container one by one; The card application registers event monitoring for the card's controls; When the card application receives a broadcast from the user because the user clicks on the desktop card, it responds to the event based on the registered content.

2. The method for implementing the vehicle-mounted desktop card according to claim 1, characterized in that: The step of constructing a card container by a desktop application, wherein the card container is used to carry the cards displayed by each application specifically includes: Select the container type based on the system's memory, CPU resources, and whether the card needs to scroll horizontally or vertically; Design the layout of the card container; Initialize the card container.

3. The method for implementing the vehicle-mounted desktop card according to claim 1, characterized in that: The step of obtaining the cards that need to be displayed in the current system by the desktop application, putting the collected application cards into a set, and sorting the application cards according to the needs specifically includes: Traverse all installed applications in the system and obtain the card data they provide; Store the collected card data in a data structure; Sort the cards according to user needs or information display priority.

4. The method for implementing the vehicle-mounted desktop card according to claim 1, characterized in that: The step of implementing the card parent layout by the desktop application and adding the cards of all applications in the collection to the card container one by one specifically includes: Design the overall layout of the card, including the card size, margins, and background; Fill the card data in the collection into the card layout to generate a specific card view; Add the populated card view to the card container to display it on the page.

5. The method for implementing the vehicle-mounted desktop card according to claim 1, characterized in that: The step of registering event monitoring for the card control by the card application specifically includes: Identify the individual controls in the card layout; Register event listeners for each control; Implement event handling logic in event listeners and perform actions based on user operations.

6. The method for implementing the vehicle-mounted desktop card according to claim 1, characterized in that: When the card application receives a broadcast from the user according to the registered content after clicking on the desktop card, the steps of responding to the event specifically include: The card application receives user operation notifications from the desktop application through a broadcast receiver; Extract user operation information from the received broadcast; Execute response actions based on the parsed user operation information.

7. The method for implementing the vehicle-mounted desktop card according to any one of claims 1 to 6, characterized in that: After the card application receives a broadcast from the user according to the registered content after clicking the desktop card, the step of responding to the event also includes: The card application updates the data and sends the updated data to the desktop application, and the desktop card refreshes the desktop layout.

8. A vehicle-mounted desktop card implementation device, characterized in that: include: A construction module, used to construct a card container from a desktop application, wherein the card container is used to carry cards displayed by each application; The acquisition module is used to obtain the cards that need to be displayed in the current system from the desktop application, put the collected application cards into a collection, and sort the application cards according to the needs; An adding module is used to implement the card parent layout by the desktop application, and add the cards of all applications in the collection to the card container one by one; The registration module is used for the card application to register event monitoring for the card controls; The response module is used to respond to events when the card application receives a broadcast from the user based on the registered content after clicking on the desktop card.

9. A computer device, comprising a memory and a processor, wherein the memory stores computer-readable instructions, and the processor implements the steps of the vehicle-mounted desktop card implementation method as described in any one of claims 1 to 7 when executing the computer-readable instructions.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the steps of the vehicle-mounted desktop card implementation method according to any one of claims 1 to 7 are implemented.

Images