HK1240354A1

HK1240354A1 - Method and apparatus for issuance and update of desktop application component

Info

Publication number: HK1240354A1
Application number: HK17113617.7A
Authority: HK
Inventors: 袁志俊
Original assignee: 斑马智行网络(香港)有限公司
Filing date: 2017-12-21
Publication date: 2018-05-18

Description

Desktop application component publishing and updating method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for publishing and updating a desktop application component.

Background

Widget mainly refers to an application extension. The Widget can be applied to many kinds of platforms or operating systems, and is mainly used for making some desktop Widget extension programs, for example, a Widget which has a toolbar on the left or right side on a mobile phone desktop and can be dragged out is provided, and widgets are provided on the toolbar on the right side on the desktop of a Windows Vista or Windows7 operating system. Widgets may facilitate a user opening or using a particular application in a shortcut, and are therefore also referred to as desktop application components.

The Widget technology is an application description technology for displaying a UI (user interface developed based on js) as a script by using XML (Extensible Markup Language), HTML (Hyper Text-up Language), CSS (cascading style sheet), and the like. The parsing tool may be a browser or other application.

Currently, the mainstream mobile operating systems in the industry provide the ability for developers to add desktop application components to the desktop, such as the desktop Widget of the Android system and the today of the IOS system. The Android system provides the App (application program) with the capability of creating a Widget to a desktop, and a user selects to place the Widget provided by the App on the desktop; the IOS system provides a today module in the notification center, provides the App with the capability of creating the Widget, and the user selects to place the Widget provided by the App in the notification center. Each App can utilize the characteristic to externalize information and operation on a desktop of the terminal, so that the user can use the App more quickly, and the content of the App can be promoted to have more and quicker entries.

In the using process of the desktop application component, an App installation package needs to be issued, and the user can only apply and update the App installation package after installing the App installation package. Fast updating of desktop application components is not facilitated.

Content of application

The embodiment of the application provides a method and a device for releasing and updating a desktop application component.

The method for releasing the desktop application component provided by the embodiment of the application comprises the following steps:

the server acquires desktop application component updating information according to the desktop application component issuing instruction;

and the server pushes the desktop application component updating information to the terminal, and the desktop application component updating information is used by the terminal to update the desktop application component used by the terminal.

Preferably, the desktop application component is obtained by editing according to a preset template, the preset template of the desktop application component is configured in the terminal, and the desktop application component update information includes setting parameters of the preset template corresponding to the desktop application component.

The desktop application component updating information comprises a style parameter of a preset template corresponding to the desktop application component, and the style parameter corresponds to a group of different types of setting parameters of the preset template.

The preset template setting parameters comprise: and one or more of layout parameters and display effect parameters of the desktop application component interface.

Preferably, the desktop application component update information comprises one or more of the following combinations:

a file describing a desktop application component interface layout;

code for executing desktop application component functions;

interface element resources used by the desktop application component.

Preferably, the server pushes the desktop application component update information to the terminal, including:

the server acquires a terminal using the desktop application component;

and the server pushes the update information of the desktop application component to a terminal using the desktop application component.

The desktop application component updating method provided by the embodiment of the application comprises the following steps:

the terminal receives desktop application component updating information pushed by the server;

and the terminal updates the desktop application component used by the terminal according to the desktop application component updating information.

Preferably, the desktop application component is obtained by editing according to a preset template, the preset template of the desktop application component is configured in the terminal, and the desktop application component update information includes setting parameters of the preset template corresponding to the desktop application component;

the terminal updates the desktop application component used by the terminal according to the desktop application component updating information, and the method comprises the following steps:

and the terminal updates the setting parameters of the preset template in the terminal according to the setting parameters of the preset template corresponding to the desktop application component.

a file for describing a desktop application component interface layout;

program code for implementing desktop application component functionality;

interface element resources used by the desktop application component.

The terminal updates the desktop application component used by the terminal according to the desktop application component updating information, wherein the desktop application component updating information comprises one or more of the following combinations:

updating the interface layout of the desktop application component used by the terminal according to the file for describing the interface layout of the desktop application component;

updating the function codes of the desktop application components used by the terminal according to the program codes for realizing the functions of the desktop application components;

and updating the interface element resource of the desktop application component used by the terminal according to the interface element resource.

Preferably, the updating, by the terminal, the desktop application component used by the terminal according to the desktop application component update information includes:

the terminal loads a program code for realizing the functions of the desktop application component in the desktop application component updating information;

the terminal loads interface element resources used by the desktop application component in the desktop application component updating information;

and the terminal executes the program code for updating the desktop application component in the desktop application component updating information so as to update the desktop application component used by the terminal.

The server provided by the embodiment of the application comprises:

the acquisition module is used for acquiring the update information of the desktop application component according to the desktop application component issuing instruction;

and the sending module is used for pushing the desktop application component updating information to the terminal, and the desktop application component updating information is used by the terminal for updating the desktop application component used by the terminal.

a file describing a desktop application component interface layout;

code for executing desktop application component functions;

interface element resources used by the desktop application component.

Preferably, the sending module is specifically configured to:

acquiring a terminal using the desktop application component;

and pushing the update information of the desktop application component to a terminal using the desktop application component.

The terminal provided by the embodiment of the application comprises:

the receiving module is used for receiving the update information of the desktop application component pushed by the server;

and the updating module is used for updating the desktop application component used by the terminal according to the desktop application component updating information.

the update module is specifically configured to: and updating the setting parameters of the preset template in the terminal according to the setting parameters of the preset template corresponding to the desktop application component.

a file for describing a desktop application component interface layout;

program code for implementing desktop application component functionality;

interface element resources used by the desktop application component.

Wherein the update module is specifically configured to perform one or more of the following:

Preferably, the update module is specifically configured to:

loading a program code for realizing the functions of the desktop application component in the desktop application component updating information;

loading the interface element resource used by the desktop application component in the desktop application component updating information;

and executing the program code for updating the desktop application component in the desktop application component updating information so as to update the desktop application component used by the terminal.

Another embodiment of the present application provides a terminal, including:

a display;

a memory for storing computer program instructions;

a processor, coupled to the memory, for reading computer program instructions stored by the memory and, in response, performing the following:

receiving desktop application component updating information pushed by a server;

and updating the desktop application component used by the terminal according to the desktop application component updating information.

the processor is specifically configured to: and updating the setting parameters of the preset template in the terminal according to the setting parameters of the preset template corresponding to the desktop application component.

a file for describing a desktop application component interface layout;

program code for implementing desktop application component functionality;

interface element resources used by the desktop application component.

Wherein the processor is specifically configured to perform one or more combinations of the following steps:

Preferably, the processor is specifically configured to:

In the above embodiment of the application, the server pushes the update information of the desktop application component to the terminal according to the instruction issued by the desktop application component, so that the terminal updates the desktop application component used by the terminal according to the update information of the desktop application component.

Drawings

FIG. 1 is a schematic diagram of a network architecture suitable for use in embodiments of the present application;

FIG. 2 is a diagram illustrating template layout styles of an editing mode in an embodiment of the present application;

fig. 3 is a schematic view illustrating a desktop application component publishing flow provided in an embodiment of the present application;

FIG. 4 is a schematic diagram illustrating a desktop application component update flow according to an embodiment of the present application;

FIG. 5 is a diagram of one implementation of step 402 of FIG. 4;

fig. 6 and fig. 7 are schematic diagrams of a Widget in an embodiment of the present application, respectively;

fig. 8 is a schematic structural diagram of a server according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a terminal according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a terminal according to another embodiment of the present application.

Detailed Description

The embodiment of the application provides a release and update scheme of a desktop application component, on one hand, after a developer creates or updates the desktop application component, the desktop application component can be pushed to a terminal in time, the desktop application component on the terminal side is guaranteed to be updated in time, and user interaction experience is guaranteed; on the other hand, the terminal does not need user participation when updating the desktop application component, so that the user experience is improved, and the user operation complexity is reduced.

Fig. 1 schematically illustrates a network architecture to which the embodiments of the present application are applicable. As shown in fig. 1, the network architecture may include a terminal and a server on the network side, and the terminal and the server communicate with each other through a network.

The server in the above architecture can receive and publish the desktop application component submitted by the developer user of the desktop application component through the terminal where the developer user is located. For a newly created desktop application component, the server may publish the newly created desktop application component to an application publishing directory such as an "application store", and a general user (different from the "developer user", where the general user refers to a user using the desktop application component or a potential user of the desktop application component) may know the available desktop application component through the application publishing directory, and then select to use the desktop application component required by the user. For a desktop application component that has been created but later updated, the server can push update information for the desktop application component to a terminal that has used the desktop application component to enable updating of the desktop application component at the terminal side without user involvement.

The terminal in the above architecture can receive the desktop application component update information pushed by the server from the server, and update the local desktop application component. The terminal may be a mobile terminal or a PC (Personal computer), and the mobile terminal may be a mobile phone, a PDA (Personal Digital Assistant), an intelligent wearable device, or the like.

In the network architecture, the terminal and the server may perform information interaction through a network, where the network may be a wide area network, a local area network, or the internet using a mobile communication technology. The terminal can access the internet in a wireless mode, and the server is usually connected with the internet in a wired mode.

Preferably, the server may employ a cloud computing technology to implement information processing based on powerful functions of the cloud computing technology. The server and the terminal can adopt an operating system based on cloud computing technology, such as YunOS, so that resources and services of the cloud and the terminal can be integrated.

In order to facilitate development of a desktop application component by a developer user, the embodiment of the application provides a simple and convenient desktop application component development method: an edit mode and a develop mode. Accordingly, the publishing method and the updating method of the desktop application component are different in implementation according to different development methods of the desktop application component.

First, the encoding mode and the development mode will be described in detail.

(1) Editing mode

The editing mode is mainly realized based on a preset template. A developer user can select a preset template on line and can further set parameters of the template, so that a needed desktop application component is designed and submitted to a server for publishing.

These templates may be pre-configured on the server and the terminal. When a new template is created, the newly created template may be sent to the terminal, for example, the new template may be included in an os update package and sent to the terminal, so that the terminal stores the new template during the os update process.

A template for a desktop application component may define the appearance of the desktop application component as well as the logical processing functions. The appearance of the desktop application component may include, among other things, the layout of the components of the component, the pictures displayed in the interface (or other media-type objects such as video, audio, animation, etc.), the background color of the interface, and the display effects of the text in the interface (such as font size, font color, font type, etc.).

The layout and/or display effect defined by the template of a desktop application component can be set through corresponding parameters, for example, the setting parameters of a template can include one or more of layout parameters and display effect parameters of an interface. A template for a desktop application component can be preconfigured with default parameters and can provide selectable parameters for selection by a developer user to create the desktop application component desired by the developer user. A template for a component on a desktop may also allow a developer user to customize the values of parameters such as the layout and/or display effect of the interface.

Taking a Widget template for browsing portal news as an example, the template may provide a portal for browsing portal news 1, and the default layout may be as shown in fig. 2. The Widget interface includes 3 vertically arranged regions: area 201 is used for displaying the headline and picture of the temporal headline news of portal 1, area 202 is used for displaying the headline and picture of the economic headline news of portal 1, and area 203 is used for displaying the headline and picture of the entertainment headline news of portal 1. The area 201, the area 202, and the area 203 contain a picture display area and a title display area, respectively. In the default layout case, the area 201, the area 202, and the area 203 and the picture display area are on the left side, and the title display area is on the right side.

Other alternative layouts provided by the template are as follows:

alternative layout 1: the area 201, the area 202 and the area 203 are vertically arranged, the picture display area is on the right side, and the title display area is on the left side;

alternative layout 2: the area 201, the area 202, and the area 203 are vertically arranged, and the title display area is below the picture display area.

The optional layout manner and the default layout manner may be distinguished by layout identification numbers, for example, layout identification numbers 0 indicate a default layout, layout identification numbers 1 indicate an optional layout 1, and layout identification numbers 2 indicate an optional layout 2, that is, layout identification numbers are used as layout parameters to define the layout of the Widget.

The default font provided by the template is Song style, the size of the font is 5, the color is black, and the values of the corresponding default parameters can be expressed as: font _ type is 0, font _ size is 0, and font _ color is 0.

Other optional font setting parameters provided by the template may include:

the font is one of a regular font (font _ type ═ 1) and a bold font (font _ type ═ 2);

the font size is one of size 6 (font _ size ═ 1) and size 7 (font _ size ═ 2);

the font color is one of blue (font _ color ═ 1) and red (font _ color ═ 2).

The various layout parameters (including default parameters and optional parameters) and various display effect parameters (including default parameters and optional parameters) of the template are configured in advance on the server side and the terminal side.

Thus, if the developer user selects the following layout and display effects: the area 201, the area 202 and the area 203 are vertically arranged, the picture display area is on the right side, and the title display area is on the left side; the font is regular font, font size is 7, font color is blue, and then corresponding parameter and value include: layout 1, font _ type 1, font _ size 2, and font _ color 1. When the developer issues the Widget, the developer only needs to submit the parameters and the values of the template to the server (certainly, other necessary information, such as template identification and the like, is not excluded), when the server issues the Widget to the terminal, the server only needs to send the parameters and the values of the template to the terminal, and when the terminal updates the local Widget, the terminal only needs to update the values of the corresponding parameters of the current Widget template according to the received parameters of the Widget template.

In the parameters of the Widget template, different values of a group of different types of parameters may also be set as corresponding patterns, that is, one pattern corresponds to a group of parameters and values thereof. For example, also taking the above Widget template as an example, the default layout (layout ═ 0) + font is a combination of song body (font _ type ═ 0) + font size 5 ═ font _ size 0) + color black (font _ color ═ 0), and may be set as the default style 0(sample ═ 0); layout 1(layout 1) + font is a combination of regular font (font _ type 1) + font size 6 (font _ size 1) + color blue (font _ color 1), which can be set as style 1(sample 1); layout 2(layout ═ 2) + font is a combination of bold (font _ type ═ 2) + font size No. 7 (font _ size ═ 2) + color red (font _ color ═ 2), and may be set as style 2(sample ═ 2).

Thus, if the developer user selects the following layout and display effects: the area 201, the area 202 and the area 203 are vertically arranged, the picture display area is on the right side, and the title display area is on the left side; the font is regular font, font size is 6, font color is blue, and then corresponding parameter and value include: sample 1. When the developer issues the Widget, the developer only needs to submit the parameters and the values of the template to the server, when the server issues the Widget to the terminal, the server only needs to send the parameters and the values of the template to the terminal, and when the terminal updates the local Widget, the terminal only needs to update the values of the corresponding parameters of the current Widget template according to the received parameters of the Widget template. Therefore, the creating process and the updating process of the Widget can be further simplified, and the network resource overhead for transmitting the template parameters can be reduced.

The above example only shows one option and optional parameters of a Widget template for browsing portal news, and various templates can be provided according to different functions implemented by the Widget, which are not listed one by one here.

(2) Development model

The development mode allows a developer user to design a Widget based on a system component provided by an operating system, for example, allows the developer user to customize the Widget based on a view component of an Android system, and the developer user packs elements constituting the Widget into an Android Package (APK) Package of the Android system standard and distributes the APK Package to a server (such as a Widget cloud platform).

The APK package can comprise one or more of the following contents:

-a file describing the interface layout of the desktop application component, which file may describe the interface layout of the desktop application component. The file can use an XML format file and can be named as layout.xml;

code for executing the functions of the desktop application, by means of which the logical processing functions of the desktop application can be implemented, such as, for example, the aforementioned news browsing Widget, when clicking on area 201, the temporal headline news content of web portal 1 will be exposed. The code can be realized based on java technology and can be named as card.

Interface element resources used by the desktop application component, including but not limited to the resources of icons, pictures, animations, video, audio used by the interface. The resource can be packaged into a png file, which can be named icon.

When a new Widget is developed, the contents can be packaged into an APK package, the APK package constitutes the Widget, and the APK package can be distributed through a server. When the original Widget is updated, one or more files can be selected and packaged into an APK program package according to the updated content, and the APK program package is issued through a server.

For example, if only the layout of the Widget is updated, only the layout of layout.xml needs to be packaged into an APK package for publishing; and if the function and interface element resources of the Widget are updated, packaging the layout.xml and the icon.png into an APK (android package) for publishing.

Referring to fig. 3, a schematic diagram of a desktop application component publishing flow provided in the embodiment of the present application is shown. The process may be implemented by a server. As shown, the process may include the following steps:

step 301: and the server acquires the update information of the desktop application component according to the instruction issued by the desktop application component.

Taking the desktop application component as the Widget as an example, as described above, the developer user may publish the Widget through the server after creating the new Widget. The specific publishing process may include: a developer user sends a Widget release instruction to a server through a terminal where the developer user is located, where the instruction includes identification information (such as a Widget ID, a Widget name, and the like) of a Widget requested to be released, and content of the Widget, and further may include other information, such as operating environment information of the Widget (such as an applicable operating system type); after receiving the Widget publishing instruction, the server registers the Widget (for example, stores the Widget and the related information thereof) and publishes the Widget to the publishing directory. The publishing process described above may be implemented based on web technology.

In the above process, the content of the Widget carried in the release instruction differs according to the different development methods adopted by the developer users. If the developer user adopts the editing mode to create the Widget, the content of the Widget carried in the release instruction may include related information of the template used by the Widget, such as a template ID, a template name, and the like, and a setting parameter of the template; and if the developer user adopts a development mode to create the Widget, packaging the content of the Widget carried in the issuing instruction into an APK (application program), wherein the APK comprises files such as layout.

If the Widget is created but needs to be updated, the developer user can update the Widget and send the update information of the Widget through the server. Specifically, the publishing process of the updated Widget is similar to the publishing process of the newly created Widget, and is not repeated here. It should be noted that the content of the Widget carried in the release instruction is Widget update information. The Widget update information differs according to the development method adopted by the developer user. If the developer user adopts the editing mode to update the Widget, the Widget updating information comprises a template ID, a template name and the like and setting parameters of the template, wherein the setting parameters of the template only comprise parameters needing to be updated; if the developer user adopts a development mode to update the Widget, the Widget update information comprises one or more combinations of the files of the layout.xml, the card.java, the icon.png and the like, and specifically, one or more combinations of the files of the layout.xml, the card.java, the icon.png and the like can be packaged into the APK program package according to the updated content.

Generally, if a developer user creates a Widget in an editing mode, the Widget is updated in the same way; and if the developer user adopts the development mode to create the Widget, updating the Widget in the same way.

Step 302: the server pushes desktop application component updating information to the terminal, and the desktop application component updating information is used by the terminal to update the desktop application component used by the terminal.

In the step, for the newly created Widget, after the server issues the Widget to a Widget issuing directory, after receiving a request of a terminal requesting to use the Widget, the server sends the Widget to the terminal; for the updated Widget, the server can directly send the updated Widget to the terminal.

When the method is implemented specifically, the server side can store or access a user database, wherein information of the widgets used by the terminal is recorded, and after the server receives a release instruction sent by a developer user for updating a certain Widget, the server can obtain the information of the user using the Widget by inquiring the user database, and then send the update information of the Widget to the corresponding terminal.

It can be seen from the above description that, since the server pushes the desktop application component update information to the terminal according to the desktop application component issue instruction, so that the terminal updates the desktop application component used by the terminal according to the desktop application component update information, on one hand, when the updated desktop application component is issued, the server can actively push the updated desktop application component to the terminal, and on the other hand, the server can push only the update information of the desktop application component to the terminal to update the desktop application component, and the terminal updates the desktop application component without user participation, and does not need to push the installation package of the desktop application component to the terminal and need to be installed by the user as in the prior art, so that the terminal can update the desktop application component in time and simplify the update operation process of the desktop application component.

Referring to fig. 4, the process for updating the desktop application component provided in the embodiment of the present application may be implemented on the terminal side. As shown in fig. 4, the process may include the following steps:

step 401: and the terminal receives the desktop application component updating information pushed by the server.

For the desktop application component update information pushed by the server and the pushing manner, refer to the foregoing embodiments, and are not repeated again.

Step 402: and the terminal updates the desktop application component used by the terminal according to the received desktop application component updating information.

In this step, taking a desktop application component as a Widget as an example, when the terminal detects that there is a Widget update (for example, when receiving Widget update information pushed by the server), the Widget may be seamlessly updated to the desktop of the terminal without installing an update package. According to the difference of the development method of the Widget, the updating process is also different.

If the Widget is developed by using the editing mode, since the Widget is generated by the preset template, and the Widget update information mainly includes the relevant setting parameters of the template, the corresponding Widget template parameter on the terminal can be updated only according to the received Widget update information when the Widget is updated, that is, the updated template parameter received from the server in step 401 is applied to the local preset template of the terminal.

And if the Widget is developed by adopting a development mode, the Widget is an APK generated based on the standard development mode of the Android system. Under the standard package management system of the Android system, if a new APK needs to be applied to a terminal, a process of installing and updating a program package needs to be triggered by a user, which is also a way adopted by Widget updating on all other platforms. In the embodiment of the present application, in order to provide a user with an imperceptible update experience, a process as shown in fig. 5 may be adopted to implement a Widget update.

As shown in fig. 5, the process may include:

step 501: and the terminal loads a program file.

Specifically, the updated program code in the APK may be loaded into the running environment of the terminal through the Android program class loader Classloader.

Step 502: and the terminal loads the resource file.

Specifically, the APK may include resource files such as various pictures for view generation of the Widget, and this step requires loading all resource files in the APK into a Context (Context) of the terminal by a method of adding resources additionally by the Android resource manager. After loading is finished, the updated resource file in the APK can be found through the updated context environment.

Step 503: the terminal executes the APK code.

Through the loading process of the program file and the resource file in the two steps, the terminal has the condition of executing the code in the APK under the condition that the APK is not installed, in step 503, the code for generating and/or updating the Widget in the APK is executed in the desktop application of the terminal, and finally the Widget on the desktop is updated.

In order to more clearly understand the desktop application component update process, a specific application scenario is taken as an example.

In this scenario, a developer user first adopts a development mode to develop a Widget for implementing a news browsing function, and an interface layout of the Widget is as shown in fig. 6, where:

the area 601 displays the function description information of the Widget as ' science and technology news today ' headline ' for briefly explaining the function of the Widget;

area 602 displays news headlines;

area 603 displays news related pictures;

an area 604 for displaying news content, which when clicked can trigger the browser to be opened to display the details of the news item;

area 605 displays the headlines of other news, and when a headline is clicked, the browser is triggered to be opened to display the detailed content of the news; further, the number of comments of the news can be displayed behind the news title, and when the number of comments is clicked, the browser can be triggered to be opened to display the content of the comments of the news;

area 606 is a function button for triggering browsing of another set of scientific and technical news;

area 607 is a function button for triggering browsing of other categories of news (non-technical news).

As shown in fig. 6, the files contained in the APK package stored on the terminal side may include:

-layout. xml: for describing the interface layout shown in FIG. 6;

java: for defining the functions in the Widget shown in fig. 6, for example, for the area 602, the title of the headline news can be obtained from the scientific news of the web portal 1 through code definition, and the headline is displayed in the area 602; for another example, for the region 607, after the region is defined by the code to be clicked, the titles and pictures of the top news and the titles of a plurality of non-top news are obtained from other news of the portal site 1, and are displayed in the corresponding region according to the layout of fig. 6;

png, icon: including the resources such as pictures, icons, etc. used in the interface shown in fig. 6. For example, a resource file may include an icon for representing comment information.

Thereafter, the developer user finds that the user prefers to obtain the peripheral food information rather than the news in the communication field, and therefore can update the Widget, and the updated Widget is shown in fig. 7, in which:

the area 701 displays that the function description information of the Widget is 'peripheral food' for briefly explaining the function of the Widget;

the area 702, the area 703 and the area 704 respectively display information of a piece of peripheral food, wherein the area 702, the area 703 and the area 704 respectively comprise 3 areas: the system comprises a picture display area, a text brief introduction display area of the food information and a display area of distance information between the picture display area and the current position of the terminal;

area 705 is a function button for triggering display of other bars of peripheral food information after being clicked.

As shown in fig. 7, the files contained in the APK package of the Widget may include:

-layout. xml: for describing the interface layout shown in FIG. 7;

java: for example, regarding the region 701, food information (such as information about a restaurant name, a food picture, average person consumption, a geographic location, and the like) around the current location of the terminal may be obtained through code definition, and a distance from the restaurant to the current location of the terminal is obtained, and an obtained piece of food related information is displayed in the region 701; for another example, for the region 705, after the region is clicked, 3 other pieces of food related information are acquired by defining the region through a code, and are displayed in the corresponding region according to the layout of fig. 7;

png, icon: including the resources such as pictures, icons, etc. used in the interface shown in fig. 7. For example,

an icon file that may include background icons for the function buttons in area 705.

The developer user publishes the updated Widget through the server, and the server sends the APK program package of the updated Widget to the terminal using the Widget; after receiving the APK package sent by the server, the terminal loads the card.java and icon.png in the APK, executes the APK code to generate a new Widget as shown in fig. 7, thereby completing the update of the Widget without the perception of the user.

Based on the same technical concept, the embodiment of the application further provides a server, and the server can realize the desktop application component publishing process.

Referring to fig. 8, a schematic structural diagram of a server provided in the embodiment of the present application is shown, where the server may include: an obtaining module 801 and a sending module 802, wherein:

an obtaining module 801, configured to obtain desktop application component update information according to a desktop application component issue instruction;

a sending module 802, configured to push the desktop application component update information to a terminal, where the desktop application component update information is used by the terminal to update a desktop application component used by the terminal.

a file describing a desktop application component interface layout;

code for executing desktop application component functions;

interface element resources used by the desktop application component.

Preferably, the sending module 802 is specifically configured to: and acquiring a terminal using the desktop application component, and pushing the update information of the desktop application component to the terminal using the desktop application component.

Based on the same technical concept, the embodiment of the application further provides a terminal, and the terminal can achieve the desktop application component updating process.

Referring to fig. 9, a schematic structural diagram of a terminal provided in the embodiment of the present application is shown, where the terminal may include: a receiving module 901 and an updating module 902, wherein:

a receiving module 901, configured to receive desktop application component update information pushed by a server;

and an updating module 902, configured to update the desktop application component used by the terminal according to the desktop application component update information.

Preferably, the desktop application component is obtained by editing according to a preset template, the preset template of the desktop application component is configured in the terminal, and the desktop application component update information includes setting parameters of the preset template corresponding to the desktop application component. Accordingly, the update module 902 may be specifically configured to: and updating the setting parameters of the preset template in the terminal according to the setting parameters of the preset template corresponding to the desktop application component.

a file for describing a desktop application component interface layout;

program code for implementing desktop application component functionality;

interface element resources used by the desktop application component.

The update module 902 may be specifically configured to perform one or more of the following operations:

Preferably, the updating module 902 is specifically configured to: loading a program code for realizing the functions of the desktop application component in the desktop application component updating information; loading the interface element resource used by the desktop application component in the desktop application component updating information; and executing the program code for updating the desktop application component in the desktop application component updating information so as to update the desktop application component used by the terminal.

Referring to fig. 10, a schematic structural diagram of a terminal provided in the embodiment of the present application is shown. As shown, the apparatus may generally include: a processor 1001, a memory 1002, and a display 1003.

The processor 1001 may be, among other things, a general-purpose processor (such as a microprocessor or any conventional processor, etc.), a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components. The memory 1002 may specifically include an internal memory and/or an external memory, such as a random access memory, a flash memory, a read only memory, a programmable read only memory or an electrically erasable programmable memory, a register, and other storage media that are well known in the art. The display 1003 may include touch screen control circuitry.

Data communication connections exist between the processor 1001 and other modules, and data communication can be performed based on a bus architecture, for example. The bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by the processor 1001, and various circuits, represented by the memory 1002, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The processor 1001 is responsible for managing the bus architecture and general processing, and the memory 1002 may store data used by the processor 1001 in performing operations.

The electronic map display process disclosed in the embodiment of the present application may be applied to the processor 1001, or implemented by the processor 1001. In implementation, the steps of the notification message processing flow may be implemented by integrated logic circuits of hardware or instructions in the form of software in the processor 1001. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art.

In particular, the processor 1001, coupled to the memory 1002, is configured to read the computer program instructions stored by the memory 1002 and, in response, perform the following:

Preferably, the desktop application component is obtained by editing according to a preset template, the preset template of the desktop application component is configured in the terminal, and the desktop application component update information includes setting parameters of the preset template corresponding to the desktop application component. Accordingly, the processor 1001 is specifically configured to: and updating the setting parameters of the preset template in the terminal according to the setting parameters of the preset template corresponding to the desktop application component.

a file for describing a desktop application component interface layout;

program code for implementing desktop application component functionality;

interface element resources used by the desktop application component.

Preferably, the processor 1001 is specifically configured to perform one or more combinations of the following steps:

Preferably, the processor 1001 may be specifically configured to:

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of 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.

While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.

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

1. A desktop application component publishing method is characterized by comprising the following steps:

2. The method of claim 1, wherein the desktop application component is edited according to a preset template, the preset template of the desktop application component is configured in the terminal, and the desktop application component update information includes setting parameters of the preset template corresponding to the desktop application component.

3. The method of claim 2, wherein the desktop application component update information comprises a style parameter of the preset template corresponding to the desktop application component, and the style parameter corresponds to a set of different types of setting parameters of the preset template.

4. The method of claim 2 or 3, wherein the presetting of the setting parameters of the template comprises: and one or more of layout parameters and display effect parameters of the desktop application component interface.

5. The method of claim 1, wherein the desktop application component update information comprises one or more combinations of:

a file describing a desktop application component interface layout;

code for executing desktop application component functions;

interface element resources used by the desktop application component.

6. The method of claim 1, wherein the server pushes the desktop application component update information to a terminal, comprising:

the server acquires a terminal using the desktop application component;

7. A desktop application component update method, comprising:

8. The method of claim 7, wherein the desktop application component is edited according to a preset template, the preset template of the desktop application component is configured in the terminal, and the desktop application component update information includes setting parameters of the preset template corresponding to the desktop application component;

9. The method of claim 8, wherein the desktop application component update information comprises a style parameter of the preset template corresponding to the desktop application component, and the style parameter corresponds to a set of different types of setting parameters of the preset template.

10. The method of claim 8 or 9, wherein the presetting of the setting parameters of the template comprises: and one or more of layout parameters and display effect parameters of the desktop application component interface.

11. The method of claim 7, wherein the desktop application component update information comprises one or more combinations of:

a file for describing a desktop application component interface layout;

program code for implementing desktop application component functionality;

interface element resources used by the desktop application component.

12. The method of claim 11, wherein the terminal updates the desktop application component used by the terminal according to the desktop application component update information, and the method comprises one or more of the following steps:

13. The method of claim 11, wherein the terminal updating the desktop application component used by the terminal according to the desktop application component update information comprises:

14. A server, comprising:

15. The server according to claim 14, wherein the desktop application component is edited according to a preset template, the preset template of the desktop application component is configured in the terminal, and the desktop application component update information includes setting parameters of the preset template corresponding to the desktop application component.

16. The server according to claim 15, wherein the desktop application component update information includes a style parameter of a preset template corresponding to the desktop application component, and the style parameter corresponds to a set of different types of setting parameters of the preset template.

17. The server according to claim 15 or 16, wherein the preset template setting parameters comprise: and one or more of layout parameters and display effect parameters of the desktop application component interface.

18. The server of claim 14, wherein the desktop application component update information comprises one or more combinations of:

a file describing a desktop application component interface layout;

code for executing desktop application component functions;

interface element resources used by the desktop application component.

19. The server according to claim 14, wherein the sending module is specifically configured to:

acquiring a terminal using the desktop application component;

20. A terminal, comprising:

21. The terminal of claim 20, wherein the desktop application component is edited according to a preset template, the preset template of the desktop application component is configured in the terminal, and the desktop application component update information includes setting parameters of the preset template corresponding to the desktop application component;

22. The terminal of claim 21, wherein the desktop application component update information comprises a style parameter of a preset template corresponding to the desktop application component, and the style parameter corresponds to a set of different types of setting parameters of the preset template.

23. The terminal according to claim 21 or 22, wherein the preset template setting parameters comprise: and one or more of layout parameters and display effect parameters of the desktop application component interface.

24. The terminal of claim 20, wherein the desktop application component update information comprises one or more of the following in combination:

a file for describing a desktop application component interface layout;

program code for implementing desktop application component functionality;

interface element resources used by the desktop application component.

25. The terminal of claim 24, wherein the update module is operative to perform one or more combinations of the following:

26. The terminal of claim 24, wherein the update module is specifically configured to:

27. A terminal, comprising:

a display;

a memory for storing computer program instructions;