CN113900740A - Method and device for loading multiple list data - Google Patents
Method and device for loading multiple list data Download PDFInfo
- Publication number
- CN113900740A CN113900740A CN202111282613.5A CN202111282613A CN113900740A CN 113900740 A CN113900740 A CN 113900740A CN 202111282613 A CN202111282613 A CN 202111282613A CN 113900740 A CN113900740 A CN 113900740A
- Authority
- CN
- China
- Prior art keywords
- plug
- data
- launcher
- list data
- view
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 70
- 230000006378 damage Effects 0.000 claims description 8
- 238000011161 development Methods 0.000 abstract description 7
- 230000003993 interaction Effects 0.000 abstract description 6
- 239000007858 starting material Substances 0.000 abstract description 4
- 238000010586 diagram Methods 0.000 description 21
- 239000010410 layer Substances 0.000 description 19
- 238000012545 processing Methods 0.000 description 18
- 230000006870 function Effects 0.000 description 15
- 238000004590 computer program Methods 0.000 description 9
- 230000008569 process Effects 0.000 description 9
- 238000007726 management method Methods 0.000 description 7
- 238000003860 storage Methods 0.000 description 7
- 230000008859 change Effects 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 5
- 230000007246 mechanism Effects 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 238000012544 monitoring process Methods 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000005236 sound signal Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 230000003247 decreasing effect Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000015572 biosynthetic process Effects 0.000 description 1
- 230000036772 blood pressure Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 230000000295 complement effect Effects 0.000 description 1
- 239000012792 core layer Substances 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 230000004927 fusion Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000003786 synthesis reaction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/60—Information retrieval; Database structures therefor; File system structures therefor of audio data
- G06F16/63—Querying
- G06F16/638—Presentation of query results
- G06F16/639—Presentation of query results using playlists
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/60—Information retrieval; Database structures therefor; File system structures therefor of audio data
- G06F16/64—Browsing; Visualisation therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
Abstract
The application relates to the technical field of terminals, and discloses a method and a device for loading multinomial list data, which are used for solving the problem that the display mode of multinomial lists is single due to an integrated development mode. The method comprises the following steps: acquiring the resources of the plug-in by adopting an android system desktop starter (launcher); instantiating the plug-in by adopting the launcher based on the plug-in resource to obtain a first view and displaying the first view; and loading a plurality of items of list data into the first view for display in the form of tab pages by adopting the plug-in. The method realizes the interaction between the plug-in and the launcher, loads the complex android system desktop with the plurality of list data, and can conveniently and quickly perform various application operations on the desktop without entering the application.
Description
Technical Field
The present application relates to the field of terminal technologies, and in particular, to a method and an apparatus for loading multiple list data.
Background
Nowadays, electronic data is more and more, and some data can be shown in the form of a multi-item list. Taking a music application as an example, a user may view different categories of data provided in a network, such as two categories of radio music and internet music, each category may include multiple pieces of music, and each category may correspond to a list.
However, the development mode of showing multiple lists based on applications in an integrated manner makes the showing mode of the multiple lists single, so how to show the multiple lists more flexibly is still a concern in the industry.
Disclosure of Invention
The application aims to provide a method for loading multi-item list data, which is used for solving the problem that the display mode of a multi-item list is single due to an integrated development mode.
In a first aspect, the present application provides a method for loading multiple list data, the method comprising:
acquiring the resources of the plug-in by adopting a launcher (android system desktop starter);
instantiating the plug-in by adopting the launcher based on the plug-in resource to obtain a first view and displaying the first view;
and loading a plurality of items of list data into the first view for display in the form of tab pages by adopting the plug-in.
In one possible embodiment, the method further comprises:
detecting a declaration statement associated with the plug-in by using the launcher;
and if the launcher detects the statement associated with the plug-in and the plug-in meets the preset requirement, executing the step of acquiring the resources of the plug-in.
In a possible embodiment, the preset requirements comprise:
the prefix of the plug-in is consistent with the appointed prefix;
the information such as the identification icon, the preview icon, the name of the plug-in, the type of the plug-in, the horizontal and vertical occupation lattice number of the plug-in and the like conforms to the convention of the plug-in and is completely defined.
In a possible implementation, the instantiating the plug-in based on the resource of the plug-in specifically includes:
acquiring context information of the plug-in by using the launcher;
and initializing the layout file of the plug-in by using the launcher and utilizing the context information of the plug-in to obtain the first view.
In one possible embodiment, the method further comprises:
transmitting the state of the launcher to the plug-in based on a state acquisition interface so as to enable the plug-in to execute the operation corresponding to the state;
wherein the plug-in performing the operation corresponding to the state comprises at least one of:
updating the operation corresponding to the state into an update plug-in;
the operation corresponding to the running state is to run the plug-in;
the operation corresponding to the destruction state is a destruction plug-in.
In a possible implementation manner, before the plug-in is adopted to load a plurality of items of list data into the first view for display in the form of tab pages, the method further includes:
and acquiring the plurality of items of list data based on the context of the plug-in.
In one possible embodiment, the method further comprises:
creating a dialog box or a prompt box based on the launcher context.
In one possible embodiment, the method further comprises:
reading the multiple list data from a local database by adopting the plug-in and storing the multiple list data into a specified array; after the multiple list data in the local database are completely read to the designated array, caching the data in the designated array into a cache queue;
the first view includes a plurality of tab pages, and the loading, by using the plug-in, of the plurality of items of list data in the form of tab pages into the first view for display specifically includes:
acquiring a current label page identifier;
inquiring whether the buffer queue is empty;
if the cache queue is not empty, acquiring the data to be displayed corresponding to the current label page identifier from the cache queue;
if the cache queue is empty, acquiring the data to be displayed from the designated array;
and loading the data to be shown into the current tab page of the first view for display.
In one possible embodiment, the method further comprises:
and if the specified data in the local database is updated, the specified data is synchronously updated to the cache queue.
In one possible embodiment, the method further comprises:
transferring the sliding event of the current tab page to an onInterceptTouchent () method;
calling a switch interface by adopting the onInterceptTouchent () method to obtain an indicated value; the switch interface is used for returning the indicated value to be a first value when the sliding event is left-right sliding, and returning the indicated value to be a second value when the sliding event is up-down sliding; the first value is used for indicating that the sliding event is continuously transmitted downwards, and the second value is used for indicating that the sliding event is blocked from being continuously transmitted downwards;
and executing corresponding operation based on the indication value.
In one possible embodiment, the method further comprises:
monitoring a sliding event of the label page, and determining the up-down sliding distance and the left-right sliding distance of the sliding event;
when the left-right sliding distance is larger than the up-down sliding distance, determining that a left-right sliding event is detected; if the left-right sliding distance is greater than a preset threshold value, determining that left sliding is detected, and if the left-right sliding distance is less than the preset threshold value, determining that right sliding is detected;
when the left-right sliding distance is smaller than the up-down sliding distance, determining that an up-down sliding event is detected, if the up-down sliding distance is larger than the preset threshold value, determining that an upward sliding event is detected, and if the up-down sliding distance is smaller than the preset threshold value, determining that a downward sliding event is detected;
and if the sliding event is a left-right sliding event, transmitting the first value by the switch interface, and if the sliding event is an up-down sliding event, transmitting the second value by the interface.
In a second aspect, the present application provides a terminal device, comprising:
a display, a processor, and a memory;
the display is used for displaying data;
the memory to store the processor-executable instructions;
the processor is configured to execute the instructions to implement a method of loading a plurality of items of list data as described in any one of the above first aspects.
In a third aspect, the present application provides a computer-readable storage medium comprising:
the instructions in the computer readable storage medium, when executed by the terminal device, enable the terminal device to perform a method of loading a plurality of items of list data as described in any one of the above first aspects.
In a fourth aspect, the present application provides a computer program product comprising a computer program which, when executed by a processor, implements a method of loading a plurality of items of list data as described in any one of the first aspects above.
The technical scheme provided by the embodiment of the application at least has the following beneficial effects:
in the embodiment of the application, resources of a plug-in are obtained by adopting an android system desktop starter (launcher), and the plug-in is instantiated based on the resources of the plug-in to obtain a first view and is displayed; and then, the plug-in is adopted to load the plurality of items of list data into the first view in a tab page mode for display, so that the interaction between the plug-in and the launcher is realized, the complex desktop of the android system with the plurality of items of list data is loaded, and a user can conveniently and quickly perform various application operations on the desktop without entering the application.
Additional features and advantages of the application will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by the practice of the application. The objectives and other advantages of the application may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the embodiments of the present application will be briefly described below, and it is obvious that the drawings described below are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic structural diagram of a terminal device according to an embodiment of the present application;
fig. 2 is a block diagram of a software structure of a terminal device according to an embodiment of the present disclosure;
fig. 3 is a schematic view of an application scenario provided in an embodiment of the present application;
fig. 4 is a schematic flowchart of a method for loading multiple items of list data according to an embodiment of the present application;
FIG. 5 is a schematic diagram illustrating a user creating a first view according to an embodiment of the present application;
FIG. 6 is a schematic diagram illustrating a first view provided by an embodiment of the present application;
FIG. 7 is a block diagram of a plug-in status provided by an embodiment of the present application;
fig. 8 is a schematic flowchart of loading multiple items of list data into a first view for display according to an embodiment of the present application;
FIG. 9 is a schematic diagram of the effect of the music plug-in finally shown in the launcher provided by the embodiment of the present application;
FIG. 10 is a schematic flow chart illustrating batch loading of data according to an embodiment of the present application;
fig. 11 is a schematic flowchart of determining a return indication value according to a sliding distance according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. The embodiments described are some, but not all embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Also, in the description of the embodiments of the present application, "/" indicates or means, for example, a/B may indicate a or B; "and/or" in the text is only an association relationship describing an associated object, and means that three relationships may exist, for example, a and/or B may mean: three cases of a alone, a and B both, and B alone exist, and in addition, "a plurality" means two or more than two in the description of the embodiments of the present application.
The terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as implying or implying relative importance or otherwise implying any number of technical features indicated. Thus, a feature defined as "first," "second," or "second" may explicitly or implicitly include one or more of that feature, and in the description of embodiments of the application, "a plurality" means two or more unless stated otherwise.
With the advent of the big data age, electronic data is increasing, and some data can be shown in the form of a multi-item list. Taking a music application as an example, a user may view different categories of data provided in a network, such as two categories of radio music and internet music, each category may include multiple pieces of music, and each category may correspond to a list. However, based on the integrated development mode of displaying multiple lists by an application, complex multiple list data cannot be loaded on the desktop of the android system, so that a user can perform various application operations only by entering the application, and therefore, the integrated development mode for displaying multiple categories is single in display mode, which is not enough to meet the requirements of the user, and a new mode is still needed for displaying multiple lists. How to more flexibly display multiple lists is still a concern in the industry.
In view of this, the present application provides a method and an apparatus for loading multiple list data, so as to solve the problem that the display mode of displaying multiple lists in an integrated development mode is single and is not enough to meet the requirements of users.
The inventive concept of the present application can be summarized as follows: the method comprises the steps that resources of a plug-in are obtained through an android system desktop starter (launcher), the plug-in is instantiated based on the resources of the plug-in, and a first view is obtained and displayed; and then, the plug-in is adopted to load the plurality of items of list data into the first view in a tab page mode for display, so that the complicated desktop loading of the android system of the plurality of items of list data is realized, and a user can conveniently and quickly perform various application operations on the desktop without entering the application.
After the inventive concept of the present application is introduced, the terminal device provided in the present application will be described below. Fig. 1 shows a schematic structural diagram of a terminal device 100. It should be understood that the terminal device 100 shown in fig. 1 is only an example, and the terminal device 100 may have more or less components than those shown in fig. 1, may combine two or more components, or may have a different configuration of components. The various components shown in fig. 1 may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.
A block diagram of a hardware configuration of a terminal device 100 according to an exemplary embodiment is exemplarily shown in fig. 1. As shown in fig. 1, the terminal device 100 includes: a Radio Frequency (RF) circuit 110, a memory 120, a display unit 130, a camera 140, a sensor 150, an audio circuit 160, a Wireless Fidelity (Wi-Fi) module 170, a processor 180, a bluetooth module 181, and a power supply 190.
The RF circuit 110 may be used for receiving and transmitting signals during information transmission and reception or during a call, and may receive downlink data of a base station and then send the downlink data to the processor 180 for processing; the uplink data may be transmitted to the base station. Typically, the RF circuitry includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
The memory 120 may be used to store software programs and data. The processor 180 performs various functions of the terminal device 100 and data processing by executing software programs or data stored in the memory 120. The memory 120 may include high speed random access memory and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. The memory 120 stores an operating system that enables the terminal device 100 to operate. The memory 120 may store an operating system and various application programs, and may also store program codes for performing the methods described in the embodiments of the present application.
The display unit 130 may be used to receive input numeric or character information and generate signal input related to user settings and function control of the terminal device 100, and particularly, the display unit 130 may include a touch screen 131 disposed on the front surface of the terminal device 100 and may collect touch operations of a user thereon or nearby, such as clicking a button, dragging a scroll box, and the like.
The display unit 130 may also be used to display a Graphical User Interface (GUI) of information input by or provided to the user and various menus of the terminal apparatus 100. Specifically, the display unit 130 may include a display screen 132 disposed on the front surface of the terminal device 100. The display screen 132 may be configured in the form of a liquid crystal display, a light emitting diode, or the like.
The touch screen 131 may cover the display screen 132, or the touch screen 131 and the display screen 132 may be integrated to implement the input and output functions of the terminal device 100, and after the integration, the touch screen may be referred to as a touch display screen for short. In this application, the display unit 130 may display the first view and the corresponding operation steps.
The camera 140 may be used to capture still images or video. The object generates an optical image through the lens and projects the optical image to the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The light sensing elements convert the light signals into electrical signals which are then passed to the processor 180 for conversion into digital image signals.
The terminal device 100 may further comprise at least one sensor 150, such as an acceleration sensor 151, a distance sensor 152, a fingerprint sensor 153, a temperature sensor 154. The terminal device 100 may also be configured with other sensors such as a gyroscope, barometer, hygrometer, thermometer, infrared sensor, light sensor, motion sensor, and the like.
The audio circuitry 160, speaker 161, microphone 162 may provide an audio interface between the user and the terminal device 100. The audio circuit 160 may transmit the electrical signal converted from the received audio data to the speaker 161, and convert the electrical signal into a sound signal for output by the speaker 161. The terminal device 100 may also be provided with a volume button for adjusting the volume of the sound signal. On the other hand, the microphone 162 converts the collected sound signal into an electrical signal, converts the electrical signal into audio data after being received by the audio circuit 160, and outputs the audio data to the RF circuit 110 to be transmitted to, for example, another terminal device, or outputs the audio data to the memory 120 for further processing.
Wi-Fi belongs to a short-distance wireless transmission technology, and the terminal device 100 can help a user to send and receive e-mails, browse webpages, access streaming media and the like through the Wi-Fi module 170, and provides wireless broadband internet access for the user.
The processor 180 is a control center of the terminal device 100, connects various parts of the entire terminal device using various interfaces and lines, and performs various functions of the terminal device 100 and processes data by running or executing software programs stored in the memory 120 and calling data stored in the memory 120. In some embodiments, processor 180 may include one or more processing units; the processor 180 may also integrate an application processor, which mainly handles operating systems, user interfaces, applications, etc., and a baseband processor, which mainly handles wireless communications. It will be appreciated that the baseband processor described above may not be integrated into the processor 180. The processor 180 may run an operating system, an application program, a user interface display, a touch response, and the method for loading multiple items of list data described in the embodiments of the present application. Further, the processor 180 is coupled with the display unit 130.
And the bluetooth module 181 is configured to perform information interaction with other bluetooth devices having a bluetooth module through a bluetooth protocol. For example, the terminal device 100 may establish a bluetooth connection with a wearable electronic device (e.g., a smart watch) having a bluetooth module via the bluetooth module 181, so as to perform data interaction.
The terminal device 100 also includes a power supply 190 (such as a battery) for powering the various components. The power supply may be logically connected to the processor 180 through a power management system to manage charging, discharging, power consumption, etc. through the power management system. The terminal device 100 may further be configured with a power button for powering on and off the terminal device, and locking the screen.
Fig. 2 is a block diagram of a software configuration of the terminal device 100 according to the embodiment of the present application.
The layered architecture divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android system may be divided into four layers, an application layer, an application framework layer, an Android runtime (Android runtime) and system library, and a kernel layer, from top to bottom, respectively.
The application layer may include a series of application packages.
As shown in fig. 2, the application package may include applications such as camera, gallery, calendar, phone call, map, navigation, WLAN, bluetooth, music, video, short message, etc.
The application framework layer provides an Application Programming Interface (API) and a programming framework for the application program of the application layer. The application framework layer includes a number of predefined functions.
As shown in FIG. 2, the application framework layers may include a window manager, content provider, view system, phone manager, resource manager, notification manager, and the like.
The window manager is used for managing window programs. The window manager can obtain the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.
The content provider is used to store and retrieve data and make it accessible to applications. The data may include video, images, audio, dialed and answered calls, browsing history and bookmarks, phone books, short messages, etc.
The view system includes visual controls such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, the display interface including the short message notification icon may include a view for displaying text and a view for displaying a picture.
The phone manager is used to provide the communication function of the terminal device 100. Such as management of call status (including on, off, etc.).
The resource manager provides various resources, such as localized strings, icons, pictures, layout files, video files, etc., to the application.
The notification manager allows the application to display notification information (e.g., message digest of short message, message content) in the status bar, can be used to convey notification-type messages, and can automatically disappear after a short dwell without user interaction. Such as a notification manager used to inform download completion, message alerts, etc. The notification manager may also be a notification that appears in the form of a chart or scroll bar text at the top status bar of the system, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, text information is prompted in the status bar, a prompt tone is given, the terminal device vibrates, an indicator light flickers, and the like.
The Android Runtime comprises a core library and a virtual machine. The Android runtime is responsible for scheduling and managing an Android system.
The core library comprises two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.
The application layer and the application framework layer run in a virtual machine. And executing java files of the application program layer and the application program framework layer into a binary file by the virtual machine. The virtual machine is used for performing the functions of object life cycle management, stack management, thread management, safety and exception management, garbage collection and the like.
The system library may include a plurality of functional modules. For example: surface managers (surface managers), Media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), and the like.
The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.
The media library supports a variety of commonly used audio, video format playback and recording, and still image files, among others. The media library may support a variety of audio-video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.
The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.
A 2D (an animation mode) graphics engine is a drawing engine for 2D drawing.
The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.
The terminal device 100 in the embodiment of the present application may be an electronic device that employs an android system, including but not limited to a mobile phone, a mobile terminal, a desktop computer, a mobile computer, a tablet computer, a household sign data acquisition device (such as a blood pressure monitor), a television, and the like.
Some brief descriptions are given below to application scenarios to which the technical solution of the embodiment of the present application can be applied, and it should be noted that the application scenarios described below are only used for describing the embodiment of the present application and are not limited. In specific implementation, the technical scheme provided by the embodiment of the application can be flexibly applied according to actual needs.
Fig. 3 is a schematic diagram illustrating an application scenario provided by an embodiment of the present application. The application scene graph comprises the following steps: a developer 301 and a terminal device 302, wherein:
the developer 301 creates a plug-in on a launcher of an android system suitable for the terminal device 302, the terminal device 302 can obtain data from a local database based on the plug-in, and update the data to the newly created plug-in a tab page form for displaying, and a user of the terminal device 302 can touch the terminal device 302, so as to touch the tab page in the newly created plug-in, and perform operations such as sharing, deleting, modifying and the like on the data in the plug-in.
The plug-in the embodiment of the application is suitable for scenes of playing music, reading novels, viewing pictures, searching files, viewing historical communication data of an instant messaging tool and other scenes, and the application is not limited to the above. In implementation, the music data can correspond to one plug-in, and the electronic book can correspond to the other plug-in. Or a plug-in can be used for showing the local data such as music data and electronic books in a multi-item list mode.
The method for loading multiple list data provided by the embodiment of the application can be mainly applied to ink-water screens, but is also applicable to other color screens, and the application is not limited to this.
Of course, the method provided in the embodiment of the present application is not limited to the application scenario shown in fig. 3, and may also be used in other possible application scenarios, and the embodiment of the present application is not limited. The functions that can be implemented by each device in the application scenario shown in fig. 3 will be described in the following method embodiments, and will not be described in detail herein.
To further illustrate the technical solutions provided by the embodiments of the present application, the following detailed description is made with reference to the accompanying drawings and the detailed description.
Referring to fig. 4, a schematic flowchart of a method for loading multiple list data according to an embodiment of the present application is shown in fig. 4, where the method includes the following steps:
in step 401, a launcher (android system desktop launcher) is used to obtain the resources of the plug-in.
In a possible implementation manner, in order to ensure that the source of the plug-in is legal and the information security of the terminal device, the launcher may be used to detect the declaration statement associated with the plug-in before the plug-in resource is acquired; and if the launcher detects the statement associated with the plug-in and the plug-in meets the preset requirement, executing the step of acquiring the resources of the plug-in. Therefore, the source of the plug-in can be ensured to be legal, and the information safety problem caused by using illegal plug-ins can be avoided.
In some possible embodiments, the android system may provide one or more plug-ins for the user of the terminal device to select for use. As shown in fig. 5, for creating a schematic diagram of a first view for a user provided in the embodiment of the present application, in order to obtain a plug-in resource when the user creates the first view, a launcher is first required to detect a declaration statement associated with a plug-in a plug-in package android manifest (xml) file of an android system, that is, whether the following statement is declared:
″com.android.launcher.plugin.InitAction″
if the declaration statement "com.android.launcher.plugin.initaction" associated with the plugin is detected, determining that the plugin package of the android system contains the credible plugin, and then detecting the plugin to determine whether the plugin meets the preset requirement.
In a possible embodiment, the preset requirement may comprise at least one of the following: the prefix of the plug-in is consistent with the appointed prefix; and the information such as the identification icon, the preview icon, the name of the plug-in, the type of the plug-in, the horizontal and vertical occupation lattice number of the plug-in and the like conforms to the convention of the plug-in and is completely defined. Of course, when implemented, the requirements can be increased or decreased according to actual requirements, and the method and the device are applicable to the embodiment of the application.
Whether the plug-in meets the preset requirement or not can be implemented by determining the conformity and the integrity of the plug-in the plug-in package of the android system according to a statement, namely detecting whether the prefix of the plug-in is consistent with the specified prefix or not according to the preset requirement, detecting whether the information such as the identification icon, the preview icon, the name of the plug-in, the type of the plug-in and the horizontal and vertical occupation lattice number of the plug-in is consistent with the convention of the plug-in or not and detecting whether the information such as the identification icon, the preview icon, the name of the plug-in, the type of the plug-in and the horizontal and vertical occupation lattice number of the plug-in is completely defined or not, if the prefix of the plug-in is consistent with the specified prefix and the information such as the identification icon, the preview icon, the name of the plug-in, the type of the plug-in and the horizontal and vertical occupation lattice number of the plug-in are consistent with the convention of the plug-in and are completely defined, and determining that the plug-in meets the preset requirement, then acquiring the resource of the plug-in, and storing the resource in the launcher.
In step 402, the launcher instantiates the plug-in based on the plug-in's resources to obtain a first view and displays the first view.
Due to the requirement of android on the processing mode of information, different information needs corresponding contexts to be processed. In the embodiment of the application, in order to instantiate a plug-in, the launcher may be used to obtain context information of the plug-in; and initializing the layout file of the plug-in by using the context information of the plug-in by the launcher to obtain the first view.
In implementation, the resource of the plug-in package can be obtained through step 401 based on the code of the plug-in package running in the background of the android system, then the resource of the plug-in package is loaded to a JVM (Java virtual machine) of the launcher, the launcher obtains the context information of the plug-in package through a system interface, initializes the layout file of the plug-in package by using the context information of the plug-in package, that is, obtains the ID of the main layout resource of the plug-in package through the context information of the plug-in package, obtains the standard layout file interface of the system service according to the context information of the plug-in package, obtains the ID of the main layout resource according to the standard layout file interface, and adds the first view to the launcher for display, as shown in fig. 6, the first view obtained after the plug-in package is instantiated in the embodiment of the present application is schematically illustrated.
The context information of the plug-in is an interface of global information during program operation, and is a bridge between each component. The context information based on the plug-in can be well suitable for the android system to acquire and process information.
In a possible implementation manner, the generated plug-in does not have states such as updating, running, destroying and the like, in order to enable the plug-in to simulate some states to meet the running requirement of the page in the embodiment of the application, each state change of the plug-in can be simulated by using the state change of the android system window and the state change of the android desktop function. When the method is implemented, the state of the launcher can be transferred to the plug-in based on a state acquisition interface so that the plug-in can execute the operation corresponding to the state. Wherein the plug-in performing the operation corresponding to the state comprises at least one of:
updating the operation corresponding to the state into an update plug-in;
the operation corresponding to the running state is to run the plug-in;
the operation corresponding to the destruction state is a destruction plug-in.
As shown in fig. 7, for a framework schematic diagram of a plug-in state provided in the embodiment of the present application, state events such as onUpdate, onEnter, onLeave, onPause, onResume, onCover, onunover, and endstroy are designed in fig. 7, where:
onUpdate denotes: informing the plug-in to initialize and update the view layout, carrying out update operation by the plug-in, initializing a plug-in layout file, and acquiring a new view layout;
oneenter denotes: informing the plug-in state to be switched into a focus display state, wherein the focus displays the current label page in the plug-in when the plug-in is in the running state;
onLeave denotes: informing the plug-in state to be shifted to a focus losing state, and enabling the plug-in to leave the current label page and enter the process of the next label page by responding to a user operation event in the running state;
onPause denotes: informing the plug-in state to enter a pause state, and enabling the plug-in to enter the pause state;
onResume denotes: informing the plug-in state to enter the state of operation again after entering the pause state, and enabling the plug-in to enter the state of operation from the pause state;
onCover denotes: after the plug-in is informed to have obvious change, the user can see the plug-in;
onUnceover indicates: after the plug-in is informed to have obvious change, the user can not see the plug-in;
onDestroy denotes: notifying the plug-in to destroy the current plug-in instance.
The states provided by the embodiment of the present application include, but are not limited to, states of updating, running, destroying, and the like, and the states may be increased or decreased according to actual situations, which is not limited by the embodiment of the present application.
Therefore, the state of the launcher is transmitted to the plugin through the state acquisition interface, so that the plugin executes the operation corresponding to the state of the launcher, the plugin can be guaranteed to execute correct operation in the state changes, normal operation, updating and destruction of the plugin are achieved, meanwhile, the plugin in each state is not required to be stored in a memory, the normal operation, updating and destruction of the plugin are achieved through the state changes, excessive occupation of a system CPU (central processing unit) memory is avoided, power consumption is reduced, and a stable and reliable plugin framework is formed.
In step 403, the plug-in is adopted to load a plurality of items of list data into the first view for display in the form of tab pages.
In a possible implementation manner, because the plug-in runs in the launcher, the context of the launcher and the context of the plug-in need to be simultaneously obtained when the plug-in is used, before the plug-in is adopted to load the multiple items of list data into the first view in the form of tab pages for display, the multiple items of list data are obtained based on the context of the plug-in, a dialog box or a prompt box is created based on the context of the plug-in, and then the data of the multiple items of list and the information of the dialog box or the prompt box are loaded by calling a tabhost.
The application resources comprise resource information such as a prompt word, a descriptive text, a font color and the like in each application, the dialog box and the prompt box are created according to project requirements, if the user needs to be prompted and selects the next operation, the dialog box is used, and only the prompt box is used when the user does not need to be prompted.
In one possible implementation, in order to speed up the loading speed of the multiple list data, the multiple list data is displayed more quickly for the user to use. In the embodiment of the application, the plug-in is adopted to read the multiple items of list data from a local database and store the list data in a specified array; after the multiple list data in the local database are completely read to the designated array, caching the data in the designated array into a cache queue; and then, the data to be displayed can be preferentially read from the cache queue for displaying to accelerate the speed of displaying. As shown in fig. 8, it can be implemented as:
in step 801, a current tab page identification is obtained.
In a possible implementation manner, data is loaded in each tab page in a multi-item list manner, but each tab page shares one multi-item list, so that in order to avoid a situation that the loaded data is disordered, an identifier of a current tab page needs to be acquired, a currently displayed tab page is determined, and thus data of a corresponding tab page is loaded.
In step 802, query whether the buffer queue is empty; if the cache queue is not empty, in step 803, acquiring the data to be displayed corresponding to the current tab page identifier from the cache queue; if the cache queue is empty, in step 804, the data to be displayed is obtained from the designated array.
If the cache queue is empty, the data to be displayed are obtained from the local database, stored in the designated array, and then obtained from the designated array.
In step 805, the data to be shown is loaded into the current tab page of the first view for display.
Fig. 9 is a schematic diagram of the effect of the music plug-in finally shown in launcher provided in the embodiment of the present application. The functions of all music label pages in the music plug-in are basically consistent with those in the local music application, so that a user can quickly perform basic operations such as sharing, deleting and playing of data in the label pages of a single song and the like in the music plug-in; each music label page in the music plug-in and the local music application share one set of audio data, and the synchronism of the data of the music plug-in and the local music application is ensured by the modes of cross-process data reading and storing and the like.
When a large amount of list data needs to be loaded, a large amount of time is consumed for reading the data from the database, problems of slow data loading, unsmooth sliding and the like are caused, and bad experience is brought to a user. As shown in fig. 10, a schematic flow chart of batch loading data provided in the embodiment of the present application specifically includes the following steps:
in step 1001, the number m of items displayed on each screen is determined according to the height of the screen occupied by the multiple item lists and the height of the screen occupied by each item, wherein m is a positive integer greater than or equal to 1.
Wherein the height of the screen occupied by each item is the same and determined, and the number of items displayed on each screen is determined by dividing the height of the screen occupied by the list of items by the height of the screen occupied by each item.
In step 1002, when data is obtained from the local database, information of the first m items is saved in the array, and an Adapter (Adapter) is notified to update the data of each item in the current screen by using the data in the array, and meanwhile, the data is continuously saved in the array. Wherein the adapter acts as a bridge between the data and the first view, thereby exposing various data in the first view.
In step 1003, a sliding change of the multi-item list is monitored, and when the last item of the current screen is slid, the Adapter is informed to update the data of the current interface by using the data in the array.
In step 1004, after all data are stored in the array, all data in the array are buffered in the buffer queue.
Meanwhile, in order to ensure that data can still be correctly acquired after data modification, in the embodiment of the application, synchronization between data in a cache queue and data in a local database is required. That is, data in the cache queue needs to be modified synchronously when operations such as deleting and changing data are performed, for example, all data in the local database may be put into the cache queue, or the cache queue may be compared with data in the local database in the process, and if there is a difference, the data in the cache queue is updated according to the data in the local database.
Therefore, by the method, a large amount of data can be loaded into the multiple lists in a tag page mode, the identification of the tag page can be monitored, the situation that the data are loaded in a messy mode is avoided, and the list data can be loaded quickly in a mode that the data are cached in the cache queue.
In one possible implementation, when a plug-in is displayed on the launcher, the layout of the event delivery is from the launcher to the Viewgroup (layout manager) to the plug-in, the plug-in is at the top of the overall layout, and the event delivery is received by the final plug-in by default. The transfer process is from the launcher to the plug-in itself, and the onInterceptTouchervent () method of the launcher is used for processing the event and changing the transfer direction of the event, namely determining whether to allow the user operation event to continue to be transferred downwards, if the onInterceptTouchent () method returns True, the user operation event is processed in the component of the launcher on behalf, and the user operation event is blocked from continuing to be transferred downwards, so that the plug-in does not have the opportunity to participate in the processing of the user operation event; if the onInterceptTouchEvent () method returns false, the user action event is handed to the plug-in for processing.
In order to solve the conflict between the sliding event of the launcher itself and the sliding event of the tab page in the plug-in, in the embodiment of the present application, a switch interface is defined inside the tab page of the plug-in, so that the onInterceptTouchEvent () method can call the switch interface, thereby processing the sliding conflict events of multiple lists in the launcher. The method therefore further comprises: transferring the sliding event of the current tab page to an onInterceptTouchent () method; calling a switch interface by adopting the onInterceptTouchent () method to obtain an indicated value; the switch interface is used for returning the indicated value to be a first value when the sliding event is left-right sliding, and returning the indicated value to be a second value when the sliding event is up-down sliding; the first value is used for indicating that the sliding event is continuously transmitted downwards, and the second value is used for indicating that the sliding event is blocked from being continuously transmitted downwards; and performs a corresponding operation based on the indication value.
It may be implemented that, when the sliding event is a left-right sliding, the onInterceptTouchEvent () method calls a switch interface to return True using a reflection mechanism so that the plug-in receives and processes the sliding event; when the sliding event is up and down sliding, the onInterceptTouchEvent () method calls a switch interface to return false by using a reflection mechanism, so that the launcher intercepts and processes the sliding event.
In one possible implementation, the sliding event of the tab page needs to judge whether the tab page slides to the left or the right by monitoring the clicking and lifting events of the screen by the user and setting a threshold value according to the sliding distance. The specific process is shown in fig. 11:
in step 1101, a sliding event of the tab page is monitored, and an up-down sliding distance and a left-right sliding distance of the sliding event are determined.
And monitoring the sliding event of the label page, namely monitoring the click and lifting event of the user on the screen, and determining the distance of the sliding event according to the position of the user on the screen and the position away from the screen. Wherein, the click event and the lift event of the sliding event can be processed by setting the flag bit.
In step 1102, determining whether the left-right sliding distance is greater than the up-down sliding distance; when the left-right sliding distance is greater than the up-down sliding distance, in step 1103, it is determined that a left-right sliding event is detected; in step 1105, it is determined whether the sliding distance is greater than a preset threshold, if the sliding distance is greater than the preset threshold, then in step 1106, it is determined that the leftward sliding is detected, and if the sliding distance is less than the preset threshold, then in step 1107, it is determined that the rightward sliding is detected.
When the left-right sliding distance is smaller than the up-down sliding distance, in step 1104, it is determined that an up-down sliding event is detected, in step 1108, it is determined whether the up-down sliding distance is larger than a preset threshold, in step 1109, it is determined that an up-down sliding is detected, and in step 1110, it is determined that a down-down sliding is detected, if the up-down sliding distance is smaller than the preset threshold;
wherein if the sliding event is a side-to-side sliding event, the first value is passed by the switch interface in step 1111, and if the sliding event is a side-to-side sliding event, the second value is passed by the interface in step 1112.
Therefore, after the plug-in is generated, the conflict problem of the sliding event of the tab page in the multinomial list and the sliding event of the launcher can be solved by defining the switch interface in the tab page and calling the switch interface by using the reflection mechanism.
Based on the foregoing description, in the embodiment of the application, a launcher is used to obtain resources of a plug-in, and the plug-in is instantiated based on the resources of the plug-in to obtain a first view and is displayed; and then, the plug-in is adopted to load a plurality of items of list data into the first view in a label page mode for display, a plug-in development technology, a data loading optimization technology and a data paging loading and updating technology of the android desktop are used, interaction between the plug-in and the launcher is realized by using a reflection mechanism, the complicated desktop of the android system of the plurality of items of list data is loaded, a user does not need to enter the application, various application operations can be conveniently and rapidly carried out on the desktop, and the user can have more flexible, convenient and personalized use experience.
The embodiments provided in the present application are only a few examples of the general concept of the present application, and do not limit the scope of the present application. Any other embodiments extended according to the scheme of the present application without inventive efforts will be within the scope of protection of the present application for a person skilled in the art.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.
Claims (10)
1. A method of loading a plurality of items of list data, the method comprising:
adopting a launcher of an android system desktop to acquire the resources of the plug-in;
instantiating the plug-in by adopting the launcher based on the plug-in resource to obtain a first view and displaying the first view;
and loading a plurality of items of list data into the first view for display in the form of tab pages by adopting the plug-in.
2. The method of claim 1, further comprising:
detecting a declaration statement associated with the plug-in by using the launcher;
and if the launcher detects the statement associated with the plug-in and the plug-in meets the preset requirement, executing the step of acquiring the resources of the plug-in.
3. The method of claim 2, wherein the preset requirements comprise:
the prefix of the plug-in is consistent with the appointed prefix;
the information such as the identification icon, the preview icon, the name of the plug-in, the type of the plug-in, the horizontal and vertical occupation lattice number of the plug-in and the like conforms to the convention of the plug-in and is completely defined.
4. The method of claim 1, wherein instantiating the plug-in based on the plug-in's resources comprises:
acquiring context information of the plug-in by using the launcher;
and initializing the layout file of the plug-in by using the launcher and utilizing the context information of the plug-in to obtain the first view.
5. The method of claim 1, further comprising:
transmitting the state of the launcher to the plug-in based on a state acquisition interface so as to enable the plug-in to execute the operation corresponding to the state;
wherein the plug-in performing the operation corresponding to the state comprises at least one of:
updating the operation corresponding to the state into an update plug-in;
the operation corresponding to the running state is to run the plug-in;
the operation corresponding to the destruction state is a destruction plug-in.
6. The method according to claim 1, wherein before said employing said plug-in to load a plurality of items of list data in the form of tab pages into said first view for display, said method further comprises:
and acquiring the plurality of items of list data based on the context of the plug-in.
7. The method according to any one of claims 1-6, further comprising:
creating a dialog box or a prompt box based on the launcher context.
8. The method of claim 1, further comprising:
reading the multiple list data from a local database by adopting the plug-in and storing the multiple list data into a specified array; after the multiple list data in the local database are completely read to the designated array, caching the data in the designated array into a cache queue;
the first view includes a plurality of tab pages, and the loading, by using the plug-in, of the plurality of items of list data in the form of tab pages into the first view for display specifically includes:
acquiring a current label page identifier;
inquiring whether the buffer queue is empty;
if the cache queue is not empty, acquiring the data to be displayed corresponding to the current label page identifier from the cache queue;
if the cache queue is empty, acquiring the data to be displayed from the designated array;
and loading the data to be shown into the current tab page of the first view for display.
9. The method of claim 1, further comprising:
transmitting the sliding event of the current tab page to an interception event onInterceptTouchent () method;
calling a switch interface by adopting the onInterceptTouchent () method to obtain an indicated value; the switch interface is used for returning the indicated value to be a first value when the sliding event is left-right sliding, and returning the indicated value to be a second value when the sliding event is up-down sliding; the first value is used for indicating that the sliding event is continuously transmitted downwards, and the second value is used for indicating that the sliding event is blocked from being continuously transmitted downwards;
and executing corresponding operation based on the indication value.
10. A terminal device, comprising:
a display, a processor, and a memory;
the display is used for displaying the first view and a plurality of items of list data;
the memory to store the processor-executable instructions;
the processor is configured to execute the instructions to implement a method of loading a plurality of items of list data as claimed in any one of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111282613.5A CN113900740A (en) | 2021-11-01 | 2021-11-01 | Method and device for loading multiple list data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111282613.5A CN113900740A (en) | 2021-11-01 | 2021-11-01 | Method and device for loading multiple list data |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113900740A true CN113900740A (en) | 2022-01-07 |
Family
ID=79027226
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111282613.5A Pending CN113900740A (en) | 2021-11-01 | 2021-11-01 | Method and device for loading multiple list data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113900740A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115576952A (en) * | 2022-11-14 | 2023-01-06 | 润芯微科技(江苏)有限公司 | Method for realizing vehicle-mounted android platform communication structure based on Unreal |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102156750A (en) * | 2011-04-22 | 2011-08-17 | 宇龙计算机通信科技(深圳)有限公司 | Desktop component classification displaying method and mobile terminal |
| CN102841726A (en) * | 2011-06-21 | 2012-12-26 | 腾讯科技（深圳）有限公司 | System, device and method for achieving a plurality of Tab pages under Android system |
| CN103139349A (en) * | 2013-03-06 | 2013-06-05 | 广东欧珀移动通信有限公司 | Message informing method and message informing device of mobile terminal and mobile terminal |
| CN104239062A (en) * | 2014-09-23 | 2014-12-24 | 深圳市富途网络科技有限公司 | Various-type label page displaying method and system based on client side |
| CN106055337A (en) * | 2016-06-07 | 2016-10-26 | Tcl集团股份有限公司 | Interface generation method and device |
| CN108628651A (en) * | 2013-01-31 | 2018-10-09 | 华为终端（东莞）有限公司 | Desktop component creation method, device and terminal device |
| CN109643207A (en) * | 2017-04-05 | 2019-04-16 | 微软技术许可有限责任公司 | Desktop starter |
| CN110297644A (en) * | 2019-06-24 | 2019-10-01 | 深圳市酷开网络科技有限公司 | A kind of homepage, which suspends, applies setting method, intelligent terminal and storage medium |
| CN110780871A (en) * | 2018-07-31 | 2020-02-11 | 中兴通讯股份有限公司 | Negative one-screen loading method and device, terminal and computer readable storage medium |
| CN110889691A (en) * | 2019-11-11 | 2020-03-17 | 支付宝(杭州)信息技术有限公司 | Information display method, device and equipment |
| CN111813476A (en) * | 2020-06-30 | 2020-10-23 | 中天掌金(北京)科技有限公司 | Mobile banking application method based on android minus one screen |
| CN112148166A (en) * | 2020-09-28 | 2020-12-29 | 维沃移动通信有限公司 | Desktop component management method and device |
| CN112394952A (en) * | 2020-11-17 | 2021-02-23 | 珠海迈科智能科技股份有限公司 | Method and system for dynamically generating Launcher based on Hybrid App, and storage medium |
-
2021
- 2021-11-01 CN CN202111282613.5A patent/CN113900740A/en active Pending
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102156750A (en) * | 2011-04-22 | 2011-08-17 | 宇龙计算机通信科技(深圳)有限公司 | Desktop component classification displaying method and mobile terminal |
| CN102841726A (en) * | 2011-06-21 | 2012-12-26 | 腾讯科技（深圳）有限公司 | System, device and method for achieving a plurality of Tab pages under Android system |
| CN108628651A (en) * | 2013-01-31 | 2018-10-09 | 华为终端（东莞）有限公司 | Desktop component creation method, device and terminal device |
| CN103139349A (en) * | 2013-03-06 | 2013-06-05 | 广东欧珀移动通信有限公司 | Message informing method and message informing device of mobile terminal and mobile terminal |
| CN104239062A (en) * | 2014-09-23 | 2014-12-24 | 深圳市富途网络科技有限公司 | Various-type label page displaying method and system based on client side |
| CN106055337A (en) * | 2016-06-07 | 2016-10-26 | Tcl集团股份有限公司 | Interface generation method and device |
| CN109643207A (en) * | 2017-04-05 | 2019-04-16 | 微软技术许可有限责任公司 | Desktop starter |
| CN110780871A (en) * | 2018-07-31 | 2020-02-11 | 中兴通讯股份有限公司 | Negative one-screen loading method and device, terminal and computer readable storage medium |
| CN110297644A (en) * | 2019-06-24 | 2019-10-01 | 深圳市酷开网络科技有限公司 | A kind of homepage, which suspends, applies setting method, intelligent terminal and storage medium |
| CN110889691A (en) * | 2019-11-11 | 2020-03-17 | 支付宝(杭州)信息技术有限公司 | Information display method, device and equipment |
| CN111813476A (en) * | 2020-06-30 | 2020-10-23 | 中天掌金(北京)科技有限公司 | Mobile banking application method based on android minus one screen |
| CN112148166A (en) * | 2020-09-28 | 2020-12-29 | 维沃移动通信有限公司 | Desktop component management method and device |
| CN112394952A (en) * | 2020-11-17 | 2021-02-23 | 珠海迈科智能科技股份有限公司 | Method and system for dynamically generating Launcher based on Hybrid App, and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 李维勇主编: "《Android任务驱动式教程》", vol. 1, 北京航空航天大学出版社, pages: 111 - 11 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115576952A (en) * | 2022-11-14 | 2023-01-06 | 润芯微科技(江苏)有限公司 | Method for realizing vehicle-mounted android platform communication structure based on Unreal |
| CN115576952B (en) * | 2022-11-14 | 2023-05-26 | 润芯微科技(江苏)有限公司 | Method for realizing vehicle-mounted android platform communication structure based on Unreal |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111225108A (en) | Communication terminal and card display method of negative screen interface | |
| CN112612386B (en) | Mobile terminal and display method of application card thereof | |
| CN111124219A (en) | Communication terminal and card display method of negative screen interface | |
| CN113835571A (en) | Terminal device, information display method and storage medium | |
| CN111857531A (en) | Mobile terminal and file display method thereof | |
| CN113709026B (en) | Method, device, storage medium and program product for processing instant communication message | |
| CN113835569A (en) | Terminal device, quick start method for internal function of application and storage medium | |
| CN111935353B (en) | Mobile terminal and short message display method thereof | |
| CN113836540A (en) | Method, apparatus, storage medium, and program product for managing application rights | |
| CN113900740A (en) | Method and device for loading multiple list data | |
| CN114594894A (en) | Interface element marking method, terminal device and storage medium | |
| CN111399955B (en) | Mobile terminal and interface display method of application program thereof | |
| CN114546219A (en) | Picture list processing method and related device | |
| CN113641431A (en) | Method and terminal equipment for enhancing display of two-dimensional code | |
| CN114035870A (en) | Terminal device, application resource control method and storage medium | |
| CN113642010A (en) | Method for acquiring data of extended storage device and mobile terminal | |
| CN113760164A (en) | Display device and response method of control operation thereof | |
| CN111159734A (en) | Communication terminal and multi-application data inter-access processing method | |
| CN113253905B (en) | Touch method based on multi-finger operation and intelligent terminal | |
| CN113254132B (en) | Application display method and related device | |
| CN111913772A (en) | Terminal and desktop display method | |
| CN113691568A (en) | Terminal and method for acquiring file information | |
| CN113703655A (en) | Mobile terminal and fixed screen detection method thereof | |
| CN113901255A (en) | Image processing terminal and method | |
| CN115167796A (en) | Display content acquisition method, device, terminal equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |