CN112099897A

CN112099897A - Method for displaying logo, computing device and computer-readable storage medium

Info

Publication number: CN112099897A
Application number: CN202011219706.9A
Authority: CN
Inventors: 常建龙; 陈延平; 毛宇; 张辛宇
Original assignee: Shanghai Cash Bar Internet Technology Co ltd; Nanjing Yanli Technology Co ltd
Current assignee: Shanghai shouqianba Internet Technology Co.,Ltd.
Priority date: 2020-11-05
Filing date: 2020-11-05
Publication date: 2020-12-18
Anticipated expiration: 2040-11-05
Also published as: CN112099897B

Abstract

The present disclosure provides a method of displaying a logo, a computing device, and a computer-readable storage medium. The method comprises the following steps: obtaining a logo tree configured for at least one view object in an application, the logo tree indicating a logo attribute and a logo configuration for each view object, the logo attribute being declared by a developer of the application; determining a logo attribute and a logo configuration of a target view object based on the logo tree when a target view object of the at least one view object is about to enter the user field of view; generating a logo for the target view object based on the logo configuration of the target view object; superimposing the logo of the target view object on the target view object based on the logo attribute of the target view object to produce a display view of the target view object; and displaying a display view of the target view object as the target view object enters the user field of view. Therefore, the logo is displayed without depending on the view object and the development platform, and the design burden of a developer is reduced.

Description

Method for displaying logo, computing device and computer-readable storage medium

Technical Field

The present disclosure relates generally to the field of application programming, and more particularly, to a method, computing device, and computer-readable storage medium for displaying a logo.

Background

Currently, a logo (badge) control is widely used in many applications, which is attached to a view object to indicate information about the view object. For example, the logo may be in the form of a red dot, a number, or text to tell the user that there is content or amount to be prompted about the view object. For example, on a view object (as indicated by reference numeral 301 of fig. 3A-3D) representing a message, various forms of logos may be displayed to indicate a new message or the number of new messages to be read. Since logo controls appear most of the time as red dots, the word "red dots" is also often used in practice to represent a logo.

In order to display the logo on the view object, in the application program design process, a developer needs to modify the code of the view object or the view objects respectively according to the product needs in advance to implement the logo interaction logic. This approach makes the implementation of the function more complex, the lead time longer, the invasiveness to the old code very high, the coupling is also very severe, and the iteration cost of the code is very high.

Disclosure of Invention

In view of the above problems, the present disclosure provides a solution for displaying a logo, which enables the display of the logo to be independent of a view object and a used development platform by uniformly managing the display of the logo in an application program, thereby reducing the design burden of a developer and providing higher platform applicability.

According to one aspect of the present disclosure, a method of displaying a logo is provided. The method comprises the following steps: obtaining a logo tree configured for at least one view object in an application, wherein the logo tree indicates a logo attribute and a logo configuration for each view object, the logo attribute being declared by a developer of the application; determining a logo attribute and a logo configuration of a target view object of the at least one view object based on the logo tree when the target view object is about to enter the user field of view; generating a logo for the target view object based on the logo configuration of the target view object; superimposing the logo of the target view object on the target view object based on the logo attribute of the target view object to generate a display view of the target view object; and displaying a display view of the target view object when the target view object enters the user field of view.

According to another aspect of the present disclosure, a computing device is provided. The computing device includes: at least one processing unit; and at least one storage unit coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions, when executed by the at least one processing unit, causing the computing device to perform steps according to the above-described method.

According to yet another aspect of the present disclosure, a computer-readable storage medium is provided, having stored thereon computer program code, which, when executed, performs the method as described above.

Drawings

The present disclosure will be better understood and other objects, details, features and advantages thereof will become more apparent from the following description of specific embodiments of the disclosure given with reference to the accompanying drawings.

Fig. 1 shows a schematic diagram of a system for displaying a logo according to an embodiment of the present disclosure.

Fig. 2 illustrates a flow diagram of a method for displaying a logo, according to some embodiments of the present disclosure.

Fig. 3A shows a schematic diagram of a display view containing a view object and a basic type logo, fig. 3B shows a schematic diagram of a display view containing a view object and an english type logo, fig. 3C shows a schematic diagram of a display view containing a view object and a digital type logo, and fig. 3D shows a schematic diagram of a display view containing a view object and another digital type logo.

FIG. 4 illustrates a flowchart of steps for generating a logo for a target view object, according to some embodiments of the invention.

FIG. 5 shows a flowchart of the steps of generating a display view according to an embodiment of the invention.

FIG. 6 shows a flowchart of the steps of updating a display view and a logo tree, according to an embodiment of the present invention.

FIG. 7 shows a schematic diagram of an updated display view according to an embodiment of the invention.

FIG. 8 illustrates a block diagram of a computing device suitable for implementing embodiments of the present disclosure.

Detailed Description

Preferred embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While the preferred embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

In the following description, for the purposes of illustrating various inventive embodiments, certain specific details are set forth in order to provide a thorough understanding of the various inventive embodiments. One skilled in the relevant art will recognize, however, that the embodiments may be practiced without one or more of the specific details. In other instances, well-known devices, structures and techniques associated with this application may not be shown or described in detail to avoid unnecessarily obscuring the description of the embodiments.

Throughout the specification and claims, the word "comprise" and variations thereof, such as "comprises" and "comprising," are to be understood as an open, inclusive meaning, i.e., as being interpreted to mean "including, but not limited to," unless the context requires otherwise.

Reference throughout this specification to "one embodiment" or "some embodiments" means that a particular feature, structure, or characteristic described in connection with the embodiments is included in at least one embodiment. Thus, the appearances of the phrases "in one embodiment" or "in some embodiments" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

Furthermore, the terms first, second and the like used in the description and the claims are used for distinguishing objects for clarity, and do not limit the size, other order and the like of the described objects.

Fig. 1 shows a schematic view of a system 1 for displaying a logo according to an embodiment of the present disclosure. As shown in fig. 1, the system 1 may include a developer terminal 10 of an application, a user terminal 20 on which the application runs, and a background server 30. Here, the developer terminal 10 is generally a mobile or fixed terminal, such as a desktop computer, a notebook computer, etc., used by a developer to develop the application, and the user terminal 20 is generally a mobile or fixed terminal, such as a mobile phone, a tablet computer, a notebook computer, etc., which can be used to run the application. In the application development phase, the developer declares a logo attribute for each view object requiring an additional logo through the developer terminal 10, the background server 30 manages the logo attributes of all the view objects declared by the developer, and establishes a logo tree to indicate the logo attributes of the view objects.

The user terminal 20 and the server 30 may communicate with each other through a wired or wireless network. The user terminal 20 may include at least one processing unit and at least one memory unit coupled to the at least one processing unit and having instructions stored therein that are executable by the at least one processing unit. The instructions may include operating system code for the user terminal 20, various application program code running on the user terminal 20, code that causes a graphical user interface to be displayed on a display screen of the user terminal 20 (such as the output unit 870 shown in fig. 8), and so forth. Further, in the present invention, the instructions in the memory unit further comprise code such that, when executed by the at least one processing unit, at least a part of the method 100 as described below is performed. The specific structure of the user terminal 20 may be described below with reference to fig. 7, for example.

Fig. 2 illustrates a flow diagram of a method 100 for displaying a logo, according to some embodiments of the present disclosure. The method 100 may be performed, for example, at the user terminal 20 in the system 1 shown in fig. 1. The method 100 is described below in conjunction with fig. 2-7.

As shown in fig. 2, at step 110, a logo tree configured for at least one view object in an application is obtained. As previously described, during the application development phase, a developer may declare logo attributes for view objects in the application that the developer is developing, backend server 30 manages the logo attributes for all view objects declared by the developer, and builds a logo tree to indicate the logo attributes for those view objects. In addition, background server 30 also sets a logo configuration for each view object and stores the logo configuration in the logo tree in association with the logo attributes of the view object. Furthermore, backend server 30 may establish the logo trees as described above for different applications or view objects of different interfaces of the same application, respectively, i.e. backend server 30 may store multiple logo trees.

In one embodiment, the acquisition of the logo tree may be based on a request-response pattern. Specifically, upon startup of the application, user terminal 20 may send a logo tree request to backend server 30. In response to the request, backend server 30 may determine a logo tree of the view object associated with the application currently running on user terminal 20 or the interface on which the application is located and send the logo tree to user terminal 20. That is, the user terminal 20 receives a pre-configured logo tree for at least one view object in the application from the backend server 30 after issuing the logo tree request.

In another embodiment, the acquisition of the logo tree may be in push mode. Specifically, user terminal 20 receives the pushed logo tree for at least one view object in the application from backend server 30. The logo tree may be initially set by the backend server 30 for the at least one view object or subsequently updated. For example, the backend server 30 may actively push the logo tree to the user terminal 20 upon detecting the application startup, or may push the logo tree to the user terminal 20 upon an update of the logo tree (e.g., a change in the number or transactions to be processed as indicated by the logo, or the backend server 30 updating the logo configuration of the view object) or at a push opportunity configured by the backend server 30.

Furthermore, the acquisition of the logo tree may also be a hybrid of the above. For example, during execution of an application, when a logo tree for the application changes at backend server 30, backend server 30 may push a logo update event to the application in user terminal 20, and user terminal 20 requests and receives an updated logo tree from backend server 30 in response to the logo update event.

In an embodiment according to the invention, the logo attributes of the view object comprise at least a logo identification of the view object. The logo identifier is used to uniquely identify the logo of the view object, which may be any non-empty string that the developer has previously declared for the logo of the view object. The developer may declare different logo identifiers for at least one view object in the application during the development phase of the application, and based on the relationships between the view objects (parent view object and child view object), backend server 30 constructs the logo identifiers as a tree structure, i.e., a logo tree.

In addition, in some embodiments, the developer declared logo attributes may also include the logo location of the view object. The logo position is used to indicate the display position of the logo on the view object. For example, the logo position may be any one of eight positions, upper, lower, left, right, upper left, lower left, upper right, and lower right.

Further, in some embodiments, the logo attributes declared by the developer may include a logo offset for the view object in addition to the logo identification and logo location. The logo offset is used to indicate an offset of the logo relative to the logo position. For example, the logo offset may indicate a distance (e.g., a pixel distance) by which the logo is offset in the abscissa and ordinate directions relative to the display position indicated by "logo position".

As described above, backend server 30 also sets a logo configuration for each view object in the logo tree. The logo configuration may include at least a logo style and logo interaction logic of the view object.

The logo pattern may include any one of a basic logo, a literary logo, a digital logo, a picture-type logo, and an motion picture-type logo. Fig. 3A shows a schematic view of a display view 300a comprising a view object 301 and a basic type logo 302a, fig. 3B shows a schematic view of a display view 300B comprising a view object 301 and an english type logo 302B, fig. 3C shows a schematic view of a display view 300C comprising a view object 301 and a digital type logo 302C, and fig. 3D shows a schematic view of a display view 300D comprising a view object 301 and another digital type logo 302D. As shown in fig. 3A through 3D, the base type logo 301a and the english type logo 301b may indicate that the corresponding view object 301 has a transaction to be processed, and the digital type logos 301c and 301D may indicate the relative number (e.g., the number of unread messages) of the corresponding view object 301. Wherein the digital type logo 301d is a variation of the digital type logo 301c in the form when the number indicated by the digital type logo 301c exceeds a predetermined threshold (e.g., 99). Furthermore, the logo pattern may further include a logo color, i.e., a background color of the logos 302a to 302D as shown in fig. 3A to 3D. Hereinafter, the logos 302a to 302d may be collectively referred to as the logos 302, and the display views 300a to 300d may be collectively referred to as the display views 300.

The picture-type logo means that a picture is displayed at the position of the logo, and the moving-picture-type logo means that a moving picture (such as a progress chart) is displayed at the position of the logo. In both cases, pictures or motion pictures (collectively referred to as assets) may be pre-stored in the user device 20 or the backend server 30, and when the logo needs to be displayed, the corresponding asset is invoked to generate a view of the logo.

Further, logo interaction logic refers to the elimination of a logo from a target view object when what user interaction occurs. The logo interaction logic may include any one of click cancellation, browse cancellation, and non-interactivity. Click dismissal refers to dismissing the logo from the target view object when the user terminal 20 detects a user click on the target view object, browse dismissal refers to dismissing the logo from the target view object when the user terminal 20 detects user browsing of the target view object (e.g., the target view object is in the user's field of view for a predetermined length of time (e.g., 3-5 seconds)), and non-interactivity refers to dismissal of the logo with no action by the user (e.g., the content indicated by the logo is forcibly displayed by the backend server 30, and only the backend server 30 can dismissal the logo).

In some embodiments, the logo configuration of the view object may also include a logo variable value, where the logo variable value determines the display content of the logo 302. For example, for a basic logo or a typeface logo, when the background server 30 determines that the view object 301 corresponding to the logo 302 has new content to be prompted, the value of the logo variable of the view object may be set to a predetermined value (e.g., 1), so that the user terminal 20 may combine the value of the logo variable with the logo style to generate the logo 302a or 302B as shown in fig. 3A or 3B. For a digital type logo, the background server 30 may determine the number of contents to be prompted of the view object 301 corresponding to the logo 302, and may set the logo variable value of the view object to the number, so that the user terminal 20 may combine the logo variable value with the logo style to generate the logo 302C or 302D as shown in fig. 3C or 3D. Alternatively, in another embodiment, for a digital logo, the backend server 30 may determine how many sub-view objects in the sub-view objects of the view object 301 corresponding to the logo 302 have content to be prompted (i.e., the value of the logo variable of the sub-view object is a predetermined value (e.g., 1)), so that the user terminal 20 may generate the logo 302C or 302D shown in fig. 3C or 3D according to the number of sub-view objects of the view object 301 having content to be prompted and the logo style of the view object 301.

In addition, in some embodiments, the logo configuration of a view object may also include the placement policy of the logo tree in which the view object is located. For example, the background server 30 may set a push object (i.e. to which user terminals 20 to push), a push order (e.g. to push all user terminals 20 in batch), a push timing (e.g. to set a push time or to push when the user terminals 20 are in an active state or an inactive state, etc.) for the logo tree.

In the present invention, the logo configuration of a view object is variable so that a logo tree with respect to the view object is updatable. In particular, background server 30 may make changes to at least one of the logo style, logo interaction logic, and logo variable values of one or more view objects in the logo tree, and update the logo tree accordingly. For example, the backend server 30 may change the logo style of a certain view object from a basic type to a digital type or a picture type, or the backend server 30 may change the logo interaction logic of a certain view object from click dismissal to browse dismissal, or the like. The value of the logo variable may vary over time.

Next, at step 120, when a view object (hereinafter referred to as target view object 301) is about to enter the user's field of view, the logo attributes and logo configuration of the target view object 301 may be determined based on the logo tree acquired at step 110.

Specifically, the user terminal 20 may display various graphical user interfaces on its display screen, and may monitor the content displayed on the graphical user interfaces on the display screen. For example, as the user interacts with the user terminal 20, different graphical user interfaces may be displayed on the display screen, which may have different various view objects therein. The range currently displayed on the display screen is the user's viewable range, referred to herein as the user field of view. The user terminal 20 may determine which view objects are currently within the user's field of view and which view objects are about to enter the user's field of view (e.g., about to enter the user's field of view the next time the user performs a scrolling operation or within a predetermined distance from the current user's field of view) based on the positional relationships between the view objects in the various pages.

For a target view object 301 that is about to enter the user's field of view, the logo attributes and logo configuration of the target view object 301 are determined based on the logo tree of step 110, step 120.

Unlike conventional view display, here, the logo view display function described in the present invention can be implemented by using a hook function in an application program, where a hook point is set to monitor the life cycle of the target view object 301. Furthermore, although the operation is described herein with respect to one target view object 301, the method of the present invention may in fact operate in sequence or in parallel with respect to multiple target view objects.

Next, in step 130, in the user terminal 20, a logo 302 for the target view object 301 may be generated based on the logo configuration of the target view object 301.

FIG. 4 shows a flowchart of step 130 for generating a logo 302 of a target view object 301, according to some embodiments of the invention.

As shown in fig. 4, step 130 may include sub-step 132, wherein a logo view 302 is generated based on the logo style of the target view object 301 determined in step 120. As described above, the logo pattern may include any one of a basic logo, a literary logo, a digital logo, a pictorial logo, and an motion picture logo. As shown in fig. 3A to 3D, when it is determined that the logo style of the target view object 301 is a basic type logo (the style or background color thereof may be preset in the user terminal 20), the user terminal 20 generates a logo view 302a as shown in fig. 3A; when it is determined that the logo style of the target view object 301 is an english-type logo (text content, font, size, background color, etc. may be preset in the user terminal 20), the user terminal 20 generates a logo view 302B as shown in fig. 3B; when it is determined that the logo style of the target view object 301 is a digital type logo (text content, font, size, background color, etc. may be preset in the user terminal 20), the user terminal 20 may generate a logo view 302C or 302D as shown in fig. 3C or 3D in combination with information (such as the number of new messages) of the background server 30. Note that the logo view referred to herein merely refers to a static display form of the logo, and does not contain the interaction logic behind the logo.

Next, in sub-step 134, the logo interaction logic of the target view object 301 may be set for the logo view to generate the logo. That is, the logos 302a to 302D that really need to be superimposed on the target view object 301 are generated by attaching the corresponding logo interaction logic to the logo views 302a to 302D shown in fig. 3A to 3D. Here, for convenience of explanation, the same reference numerals 302a to 302D in fig. 3A to 3D are used to denote both the logo view and the logo, however, it is understood by those skilled in the art that the meanings of these two terms are not completely the same herein.

Continuing with FIG. 2, next, at step 140, a logo 302 of the target view object 301 is superimposed on the target view object 301 based on the logo attributes of the target view object 301 to produce a display view 300 of the target view object 301.

Specifically, when the logo attribute of the target view object 301 contains only the logo identifier, the user terminal 20 may superimpose the logo on the target view object 301 by a default value set in advance. For example, in the default value set in advance, the logo position is the upper right position, and thus the logos 302a to 302d generated in step 130 may be superimposed on the target view object 301 to generate the corresponding display views 300a to 300 d. When the logo attribute of the target view object further includes a logo position (any one of eight positions, i.e., up, down, left, right, up-left, down-left, up-right, and down-right), the user terminal 20 may superimpose the logo generated in step 130 on the target view object according to the logo position. Further, when the logo attribute of the target view object further includes both the logo position and the logo offset, the user terminal 20 may determine the actual position of the logo display according to the logo position and the logo offset, and superimpose the logo generated in step 130 on the target view object according to the actual position.

In some cases, the generation of the final display view 300 may also require consideration of the interaction logic associated with the target view object 301 itself. This is because the interaction logic of the logo 302 is only directed to the logo itself, whereas in actual use, the user's normal interaction habit is to operate (click or browse) on the target view object 301 (or the display view 300), rather than directly on the logo 302 (especially for click operations, the logo 302 is small relative to the display view 300 and not easily hit exactly).

Thus, in order to adapt to user operating habits to provide a better user experience, the generation of the final display view 300 in step 140 may further comprise adapting the view interaction logic for that display view 300. Fig. 5 shows a flowchart of the step 140 of generating the display view 300 (more specifically, the adapted view interaction logic) according to an embodiment of the present invention. As shown in fig. 5, step 140 may further include a substep 141, in which the interaction logic of the target view object 301 may be determined.

In sub-step 142, it is determined whether the interaction logic of target view object 301 is non-interactable. The interaction logic of the target view object 301 may be divided into interactable (or more specifically including supported interactive forms) and non-interactable. Wherein, the interaction logic of each view object in the application program can be stored in the user terminal 20 in advance. For non-interactable target view objects 301, the logo 302 on the display view 300 cannot be eliminated by the interaction between the user and it, and thus the interaction logic thereof needs to be modified.

If the interaction logic of the target view object 301 is determined to be non-interactable ("yes" determination of substep 142), the interaction logic of the target view object 301 is modified to be interactable in substep 143.

In some cases, when target view object 301 has a parent view object, its interchangeability is also subject to the interaction logic of its parent view object. To this end, in sub-step 144, the interaction logic may continue to determine the parent view object of the target view object 301. Here, a view tree may be maintained in the user terminal 20 in advance to indicate the relationship between the respective view objects. In sub-step 144, the parent view object of target view object 301 may be determined from the view tree, thereby determining the interaction logic of the parent view object.

Next at substep 145, similar to substep 142, a determination is made as to whether the interaction logic of the parent view object is non-interactable. If it is determined that the interaction logic of the parent view object is not interactable ("yes" determination of substep 145), the interaction logic of the parent view object is modified to interactable in substep 146.

In the above manner, the interaction logic of the target view object 301 of the display view 300 is adapted, resulting in the final display view 300 (substep 147). The display view 300 generated here is a display view that contains the complete interaction logic.

Continuing with FIG. 2, at step 150, a display view 300 of the target view object 301 is displayed when the target view object 301 enters the user's field of view. As previously described, the user terminal 20 may monitor the content displayed on the graphical user interface on its display screen to determine which content (e.g., view objects) have entered the user's field of view. When the user terminal 20 detects that the target view object 301 enters the user's field of view, the display view 300 with the logo 302 generated in step 140 is displayed on the display screen. The hook point set at step 120 may be released at this point to release the display process back to the conventional view display function.

In some cases, the logo style of the target view object 301 may be a picture-type logo or an animation-type logo, in which case, in the above sub-step 132, a link of the resource (picture or animation) indicated by the logo style needs to be associated with the generated logo view 302, and in step 150, when the target view object 301 enters the user field of view, the corresponding resource is loaded according to the link, and the display view 300 loaded with the resource is displayed. For example, if the logo style set by the background server 30 is a picture-type logo or an motion picture-type logo, the corresponding resource may be stored in the user terminal 20 or the background server 30 in advance. While displaying the display view 300, the user terminal 20 may determine whether to retrieve the resource locally or request the resource from the backend server 30 based on the link to the resource.

As described above, the logo configuration of the view object set by the background server 30 may change, so that the logo tree of the view object changes accordingly. In some embodiments, the background server 30 will push the updated logo tree to the user terminal 20 in time after the logo configuration of the view object is changed. In this case, even when the display view 300 is in the user view in step 150, the user terminal 20 may determine whether the logo configuration of the target view object 301 has changed based on the updated logo tree. When user terminal 20 determines that the logo configuration of target view object 301 corresponding to display object 300 being displayed has changed, it may re-render logo 302 of target view object 301 based on the new logo configuration of target view object 301 in the updated logo tree (as described in step 130 above), generate new display view 300 (as described in step 140 above), and display new display view 300. For example, if the logo style of the target view object 301 corresponding to the display view 300 is changed from a basic type to a moving pattern when the display view 300 appears in the user field, the user terminal 20 may generate a new logo 302 based on the new logo style and replace the logo 302 on the current display view 300 with it.

Further, after step 150, method 100 may further include step 160 (not shown in FIG. 2), wherein display view 300 and the logo tree are updated based on user interaction with display view 300. Fig. 6 shows a flow chart of the step 160 of updating the display view and logo tree according to an embodiment of the invention.

As depicted in fig. 6, step 160 may include sub-step 162, wherein user terminal 160 detects a user interaction with display view 300 and determines whether the interaction conforms to the logo interaction logic of the logo configuration of display view 300 at sub-step 164. As previously described, the logo configuration set by backend server 30 for view object 301 includes logo interaction logic, which may be click to cancel, browse to cancel, or not to interact, etc. When user terminal 20 detects a user interaction with display view 300, it determines whether the interaction is logically consistent with the logo interaction set by backend server 30. For example, if the logo interaction logic set by the background server 30 for the view object 301 is click elimination, the interaction of the user is determined to be consistent with the logo interaction logic only when the click operation of the user on the display view 300 is detected. For another example, if the logo interaction logic set by the backend server 30 for the view object 301 is browse elimination, when it is detected that the display view 300 stays in the user's field of view for a predetermined time (e.g., 3-5 seconds), it is determined that the user's interaction is consistent with the logo interaction logic.

If it is determined that the user's interaction corresponds to the logo interaction logic ("yes" determination of sub-step 164), then in sub-step 166, logo 302 is removed from display view 300 to update the display view 300. FIG. 7 shows a schematic diagram of an updated display view 400 according to an embodiment of the invention. The display view 400 may be, for example, the display view 300a or 300B shown in fig. 3A or 3B updated after interaction with the user, i.e., the logo 302 is removed from the display view 300 and only the target view object 301 remains. In this way, user device 20 may locally update its graphical user interface immediately after a user interaction with display view 300 without having to wait for backend server 30 to respond to the interaction, thereby enhancing the user experience.

Next, in sub-step 168, user terminal 20 reports to backend server 30 of the application the fact that logo 302 of target view object 301 was removed to cause backend server 30 to update the logo tree. The user's interaction with the display view 300 indicates that the user has learned what the backend server 30 is to prompt the user, so the backend server 30 can update the logo configuration for that display view 300 in the logo tree accordingly. For example, the value of the logo variable of the target view object 301 may be set to another predetermined value (e.g., 0).

FIG. 8 illustrates a block diagram of a computing device 800 suitable for implementing embodiments of the present disclosure. The computing device 800 may be, for example, the user terminal 20 described above.

As shown in fig. 8, computing device 800 may include one or more Central Processing Units (CPUs) 810 (only one of which is schematically shown) that may perform various suitable actions and processes in accordance with computer program instructions stored in a Read Only Memory (ROM) 820 or loaded from a storage unit 880 into a Random Access Memory (RAM) 830. In the RAM 830, various programs and data required for the operation of the computing device 800 may also be stored. The CPU 810, ROM 820, and RAM 830 are connected to each other by a bus 840. An input/output (I/O) interface 850 is also connected to bus 840.

A number of components in computing device 800 are connected to I/O interface 850, including: an input unit 860 such as a keyboard, a mouse, and the like; an output unit 870 such as various types of displays, speakers, and the like; a storage unit 880 such as a magnetic disk, optical disk, or the like; and a communication unit 890 such as a network card, modem, wireless communication transceiver, or the like. The communication unit 890 allows the computing device 800 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunications networks.

The method 100 described above may be performed, for example, by the CPU 810 of the computing device 800 (e.g., user terminal 20). For example, in some embodiments, method 100 may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 880. In some embodiments, some or all of the computer program can be loaded onto and/or installed onto computing device 800 via ROM 820 and/or communications unit 890. When loaded into RAM 830 and executed by CPU 810, the computer program may perform one or more of the operations of method 100 described above. Further, the communication unit 890 may support wired or wireless communication functions.

Those skilled in the art will appreciate that the computing device 800 illustrated in FIG. 8 is merely illustrative. In some embodiments, user terminal 20 may contain more or fewer components than computing device 800. For example, where user terminal 20 is a portable mobile terminal, it may contain fewer components than shown for computing device 800.

By utilizing the scheme of the invention, the display of the logo is uniformly managed in the application program, so that the display of the logo can be independent of the view object and the used development platform, thereby reducing the design burden of a developer and simultaneously providing higher platform applicability. In addition, since a developer can arbitrarily declare the logo of a view object, the logo can be displayed at any location of the graphical user interface (e.g., by adding an empty view object at that location).

The method 100 for displaying a logo and the computing device 800 usable as the user terminal 20 according to the present invention are described above with reference to the accompanying drawings. However, it will be appreciated by those skilled in the art that the performance of the steps of the method 100 is not limited to the order shown in the figures and described above, but may be performed in any other reasonable order. Further, the computing device 800 also need not include all of the components shown in FIG. 8, it may include only some of the components necessary to perform the functions described in the present disclosure, and the manner in which these components are connected is not limited to the form shown in the figures.

The present disclosure may be methods, apparatus, systems, and/or computer program products. The computer program product may include a computer-readable storage medium having computer-readable program instructions embodied thereon for carrying out various aspects of the present disclosure.

In one or more exemplary designs, the functions described in this disclosure may be implemented in hardware, software, firmware, or any combination thereof. For example, if implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.

The units of the apparatus disclosed herein may be implemented using discrete hardware components, or may be integrally implemented on a single hardware component, such as a processor. For example, the various illustrative logical blocks, modules, and circuits described in connection with the disclosure may be implemented or performed with a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein.

Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both.

The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method of displaying a logo, comprising:

obtaining a logo tree configured for at least one view object in an application, wherein the logo tree indicates a logo attribute and a logo configuration for each view object, the logo attribute being declared by a developer of the application;

determining a logo attribute and a logo configuration of a target view object of the at least one view object based on the logo tree when the target view object is about to enter a user field of view;

generating a logo for the target view object based on the logo configuration of the target view object;

superimposing a logo of the target view object on the target view object based on the logo attribute of the target view object to produce a display view of the target view object; and

displaying a display view of the target view object when the target view object enters the user field of view.

2. The method of claim 1, wherein obtaining a logo tree configured for at least one view object in an application comprises:

when the application program is started, a logo tree request is sent to a background server of the application program; and

receiving the logo tree preconfigured for at least one view object in the application from the backend server, wherein the logo configuration for each view object is set by the backend server for the view object.

3. The method of claim 1, wherein obtaining a logo tree configured for at least one view object in an application comprises:

receiving the logo tree pushed by the backend server for at least one view object in the application, wherein the logo configuration of each view object is set or updated for the view object by the backend server.

4. The method of claim 1, wherein the logo attributes comprise a logo identification of the view object.

5. The method of claim 4, wherein the logo attributes further comprise a logo location of the view object; or

The logo attributes also include a logo position and a logo offset for the view object.

6. The method of claim 1, wherein the logo configuration comprises a logo style and logo interaction logic for the view object,

wherein the logo pattern includes any one of a basic logo, a literary logo, a digital logo, a pictorial logo, and an motion picture logo; and

the logo interaction logic includes any one of click elimination, browse elimination, and non-interactivity.

7. The method of claim 6, wherein generating the logo for the target view object based on the logo configuration of the target view object comprises:

generating a logo view based on a logo style of the target view object; and

setting logo interaction logic of the target view object for the logo view to generate the logo.

8. The method of claim 7, wherein generating a logo view based on the logo style of the target view object further comprises:

if the logo style of the target view object is a pictorial or an animated logo, associating a link to the resource indicated by the logo style for the logo view, and generating the display view of the target view object further comprises:

loading the resource according to the link when the target view object enters the user view; and

displaying the display view with the resource loaded.

9. The method of claim 7, wherein generating the display view of the target view object further comprises:

determining interaction logic of the target view object;

if the interaction logic of the target view object is not interactive, the interaction logic of the target view object is modified into interactive;

determining interaction logic for a parent view object of the target view object; and

and if the interaction logic of the parent view object is not interactive, modifying the interaction logic of the parent view object to be interactive.

10. The method of claim 1, further comprising:

detecting user interaction with the display view;

logo interaction logic that determines whether the interaction conforms to a logo configuration of the display view;

updating the display view to remove the logo if the interaction is determined to conform to the logo interaction logic;

reporting the fact that the logo of the target view object is eliminated to a backend server of the application program so that the backend server updates the logo tree.

11. A computing device, comprising:

at least one processing unit; and

at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions when executed by the at least one processing unit causing the computing device to perform the steps of the method of any of claims 1-10.

12. A computer readable storage medium having stored thereon computer program code which, when executed, performs the method of any of claims 1 to 10.