CN110858139B

CN110858139B - Information display, reminding event creation and event type creation methods and equipment

Info

Publication number: CN110858139B
Application number: CN201810961146.0A
Authority: CN
Inventors: 李谦
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2018-08-22
Filing date: 2018-08-22
Publication date: 2023-05-26
Anticipated expiration: 2038-08-22
Also published as: CN110858139A

Abstract

The embodiment of the application provides a method and equipment for information display, reminding event creation and event type creation. The information display method comprises the following steps: displaying a label control corresponding to at least one event type on a calendar interface; responding to the association operation of a label control corresponding to a first event type and a first date displayed on the calendar interface, and creating a reminding event which is associated with the first date and belongs to the first event type; and displaying the page element corresponding to the first event type in an associated mode with the first date. In the technical scheme provided by the embodiment of the application, the user can realize the creation of the reminding event by only carrying out the association operation on the label control corresponding to the reminding event and the corresponding date on the calendar interface, and the user operation cost is low and the creation efficiency is high.

Description

Information display, reminding event creation and event type creation methods and equipment

Technical Field

The present disclosure relates to the field of electronic technologies, and in particular, to a method and an apparatus for displaying information, creating a reminder event, and creating an event type.

Background

In the existing terminals, especially in mobile phones, event reminding functions are provided. The user can set the task to be processed in the calendar of the system or the calendar of the third party application, and when the reminding time of the set task is reached, the user can be reminded in a default or self-defined reminding mode such as alarm clock, vibration and the like.

In the prior art, the form filling is performed after the page is jumped in a mode of adding the reminding event to the calendar of the terminal as a main program, and the flow of adding the reminding event is complicated, so that the operation cost of a user is high, and the creation efficiency of the reminding event is low.

Disclosure of Invention

In view of the foregoing, the present application has been developed to provide a method and apparatus for information display, alert event creation, event type creation that solve, or at least partially solve, the foregoing problems.

Thus, in one embodiment of the present application, an information display method is provided. The method comprises the following steps:

displaying a label control corresponding to at least one event type on a calendar interface;

responding to the association operation of a label control corresponding to a first event type and a first date displayed on the calendar interface, and creating a reminding event which is associated with the first date and belongs to the first event type;

and displaying the page element corresponding to the first event type in an associated mode with the first date.

In another embodiment of the present application, a reminder event creation method is provided. The method comprises the following steps:

acquiring a first event type and a first date selected by a user;

Creating a reminding event according to the first event type;

and associating the first date and the reminding event.

In yet another embodiment of the present application, a method of event type creation is provided. The method comprises the following steps:

displaying an add control of the add event type on the calendar interface;

responding to the touch operation of a user on the adding control, and displaying label creation guide information;

creating a second event type according to the creation content input by the user according to the label creation guide information;

and displaying the label control corresponding to the second event type on the calendar interface.

In yet another embodiment of the present application, an electronic device is provided. The electronic device includes: a first memory, a first processor, and a first display; wherein,,

the first memory is used for storing programs;

the first display is coupled with the first processor and is used for displaying a label control corresponding to at least one event type on a calendar interface;

the first processor is coupled to the first memory for executing the program stored in the first memory for:

And controlling the first display to display the page element corresponding to the first event type and the first date in an associated mode.

In yet another embodiment of the present application, an electronic device is provided. The electronic device includes: a second memory and a second processor; wherein,,

the second memory is used for storing programs;

the second processor is coupled with the second memory, and is configured to execute the program stored in the second memory, for:

acquiring a first event type and a first date selected by a user;

creating a reminding event according to the first event type;

and associating the first date and the reminding event.

In yet another embodiment of the present application, an electronic device is provided. The electronic device includes: a third memory, a third processor, and a third display, wherein,

the third memory is used for storing programs;

the third display is coupled with the third processor and is used for displaying an adding control of the adding event type on a calendar interface;

the third processor is coupled with the third memory, and is configured to execute the program stored in the third memory, for:

Controlling the third display to display label creation guide information in response to touch operation of a user on the adding control;

and controlling the third display to display a label control corresponding to the second event type on the calendar interface.

In the technical scheme provided by the embodiment of the application, different event types are created in advance for users to select, and the follow-up users can realize the creation of the reminding event by selecting the corresponding event type and the corresponding date when the reminding event is created. Compared with the prior art, the technical scheme provided by the embodiment of the application is low in user operation cost and high in creation efficiency.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, a brief description will be given below of the drawings that are needed in the embodiments or the prior art descriptions, and it is obvious that the drawings in the following description are some embodiments of the present application, and that other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a flow chart of an information display method according to an embodiment of the present application;

FIG. 2 is a first display state diagram of a calendar interface provided by an embodiment of the present application;

FIG. 3 is a second display state diagram of a calendar interface provided by an embodiment of the present application;

FIG. 4 is a third display state diagram of a calendar interface provided by an embodiment of the present application;

FIG. 5 is a fourth display state diagram of a calendar interface provided by an embodiment of the present application;

FIG. 6 is a fifth display state diagram of a calendar interface provided by an embodiment of the present application;

FIG. 7 is a sixth display state diagram of a calendar interface provided by an embodiment of the present application;

FIG. 8 is a flowchart illustrating a method for creating a reminder event according to another embodiment of the present disclosure;

FIG. 9 is a flowchart of an event type creation method according to another embodiment of the present application;

fig. 10 is a block diagram of an information display device according to an embodiment of the present application;

FIG. 11 is a block diagram illustrating a reminder creation device according to one embodiment of the present disclosure;

FIG. 12 is a block diagram of an event type creation device according to an embodiment of the present application;

FIG. 13 is a block diagram of an electronic device according to an embodiment of the present disclosure;

fig. 14 is a block diagram of an electronic device according to another embodiment of the present application;

Fig. 15 is a block diagram of an electronic device according to another embodiment of the present application.

Detailed Description

In order to enable those skilled in the art to better understand the present application, the following description will make clear and complete descriptions of the technical solutions in the embodiments of the present application with reference to the accompanying drawings in the embodiments of the present application.

In some of the flows described in the specification, claims, and drawings described above, a plurality of operations occurring in a particular order are included, and the operations may be performed out of order or concurrently with respect to the order in which they occur. The sequence numbers of operations such as 101, 102, etc. are merely used to distinguish between the various operations, and the sequence numbers themselves do not represent any order of execution. In addition, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first" and "second" herein are used to distinguish different messages, devices, modules, etc., and do not represent a sequence, and are not limited to the "first" and the "second" being different types.

The existing process of adding the reminding event into the calendar is as follows: after entering the calendar interface, the user clicks the add reminding event button and jumps to a form page (a plurality of items to be input such as title, position, invitees, calendar sharing and the like are provided in the form page), and after entering the detailed content in the form page, the user clicks a completion button on the form page and returns (i.e. jumps to) the corresponding calendar interface. Therefore, the existing reminding event has complicated creation process and low creation efficiency; in addition, when the user creates the reminding event aiming at the same type of task, the user needs to walk through the process each time to input information such as a title, and the operation cost of the user is high. In order to reduce the operation cost of a user and improve the creation efficiency, the application provides a scheme capable of effectively simplifying the user process.

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. It will be apparent that the described embodiments are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.

Fig. 1 is a schematic flow chart of an information display method according to an embodiment of the present application. As shown in fig. 1, includes:

101. and displaying a label control corresponding to at least one event type on the calendar interface.

102. And responding to the association operation of the label control corresponding to the first event type and the first date displayed on the calendar interface, and creating a reminding event which is associated with the first date and belongs to the first event type.

103. And displaying the page element corresponding to the first event type in an associated mode with the first date.

In 101 above, the user may enter a calendar interface provided by the terminal system calendar application or a third party calendar application by voice or clicking an application icon operation. The event types described above include, but are not limited to: meeting, birthday, airplane, holiday, etc. The user can create various event types according to actual needs. The display position of the label control corresponding to the event type on the calendar interface can be configured according to actual needs. For example: in order not to affect the user's view of the calendar on the calendar interface, a tab control may be displayed at the bottom of the calendar interface. In addition, the display style (e.g., shape, color, transparency) of the label control may be configured by default or by user-defined configuration. To facilitate user recognition of different label controls, the display styles of the different label controls may be different, for example: different shapes and/or different colors. As shown in fig. 2, the conference label control is red in color; the birthday label control is blue in color. Wherein the shape may include, but is not limited to: oval, rectangular, circular, pentagonal.

In addition, due to the size of the terminal display screen, pagination or waterfall pages are commonly used in the prior art to present calendars. In order to ensure that the date to be selected by the user and the label control are displayed in the same interface, when the paging display method is adopted, the label control needs to be added in each page; when the waterfall flow page display method is adopted, label controls are required to be added at a plurality of positions of the waterfall flow page. Such repeated addition of tab controls may make the page design less compact. Thus, in one implementation, the tab control may be presented through a floating layer, i.e., the calendar interface may include a stacked calendar base layer and tab floating layer, with the calendar base layer being used to present the calendar. The user can perform any operation on the calendar bottom layer alone, for example: in the process of turning pages or scrolling pages by sliding down and up, the label floating layer is always positioned in the calendar interface. In this way, only one label floating layer is needed to ensure that the date to be selected by the user and the label control are displayed in the same interface, so that the associated operation of the user in the follow-up 102 is facilitated.

The display position of the label floating layer in the calendar interface can be configured according to actual needs, for example, the label floating layer can be displayed at the bottom of the calendar interface, as shown in fig. 2. The tag float may support hiding and unfolding functions such as: the floating layer hiding control and the floating layer unfolding control can be displayed on the calendar interface, the user can hide the tag floating layer by clicking the floating layer hiding control, and the tag floating layer can be unfolded by clicking the floating layer unfolding control.

In the above 102, the associating operation may include at least one of:

a first drag operation from a first position to a second position for a label control corresponding to the first event type; the first position is a display position of a label control corresponding to the first event type, and the second position is a display position of the first date.

As shown in fig. 3 and 4, the first event type is a meeting, and the first date is 2017, 11, 24. The user drags the conference tab control from its display position to the display position of 2017, 11 and 24, thereby associating the conference with 2017, 11 and 24.

And second, aiming at the continuous clicking operation of the label control corresponding to the first event type and the first date.

The click sequence may be configured in advance, for example: the tab control is clicked first, and then the date is clicked.

As shown in fig. 3 and 4, the first event type is a meeting, and the first date is 2017, 11, 24. The user can respectively click the conference label control and the No. 24 of the 11 th month of 2017 within a preset time period (for example, 1 s), so that the association of the conference and the No. 24 of the 11 th month of 2017 is realized.

Thirdly, selecting the label control corresponding to the first event type, dragging the label control corresponding to the first event type from the first position to the second position, and long-pressing the label control detained at the second position.

Wherein the selecting operation may include a clicking operation or a long press operation. The long-on-demand duration of the long-press operation that remains in the second position is required to be greater than or equal to a preset duration, for example: 1s. The long press operation may give the user a confirmation time of the selected label and date to avoid a selection error.

After the dragged label control is placed on the first date and stagnates for a preset time period, visual feedback is generated after interaction between the first date and the label control, so that a user is informed of successful association, and the user can release the label control.

In addition, the reminder event mentioned in 102 above may be created from the first event type. The created reminder event is associated with a first date such that a later period triggers a reminder when the first date arrives. The event content corresponding to the first event type may be a template content configured for the first event type in advance, or may be a content in which a user re-edits the template content, etc., which is not specifically limited in the embodiment of the present application.

From 102, it can be seen that the user can implement the creation of the reminder event only by executing the association operation once for the tab control corresponding to the first event type and the first date on the calendar interface. The creation process does not involve any page jump, and the interaction is simple and lightweight; and the label is set only once aiming at the same event type, so that the label can be reused later, and repeated input operation of a user aiming at the task of the same event type is avoided.

In 103, the association display may be understood as displaying the page element corresponding to the first event type in the display area associated with the first date. The display area associated with the first date may be a display area of the first date and/or a display area surrounding the display area of the first date (e.g., a page element corresponding to the first event type is displayed below the display area of the first date, as shown in fig. 6).

In order to facilitate the user to identify the event type corresponding to the page element later, the display style of the page element may be set in combination with the display style of the tab control corresponding to the first event type, for example: if the colors of the different label controls are different, setting the color in the display style of the page element corresponding to the first event type to the color of the label control corresponding to the first event type; alternatively, if the shapes of the different label controls are different, the shape in the display style of the page element corresponding to the first event type may be set to the shape of the label control corresponding to the first event type.

According to the technical scheme provided by the embodiment of the application, corresponding label controls are set for different event types in advance, and a follow-up user can establish a reminding event only by carrying out association operation on the label controls corresponding to the event to be reminded and corresponding dates on a calendar interface. Compared with the prior art, the technical scheme provided by the embodiment of the application is low in user operation cost and high in creation efficiency.

Further, in the foregoing embodiment 102, "creating a reminder event associated with the first date and belonging to the first event type" may be implemented by:

1021. and creating a reminding event according to the first event type.

1022. And associating the first date and the reminding event.

In 1021, the reminder event may not include content information such as event time and event place. For example, the "birthday" tab control in FIG. 4 refers to the birthday event type; the user creates a reminder event using the birthday event type, only the day that wants to remind himself of the marked birthday is his own birthday, without any birthday activity being scheduled. At this time, the reminder event belonging to the first event type can be directly created without acquiring any content information.

The reminding event needs to include content information such as event time (e.g. airplane take-off time, meeting start time, etc.), event place (e.g. airport terminal building, meeting place, etc.) and the like, corresponding to the travel event type indicated by the airplane label control, the meeting event type indicated by the meeting label control, etc. Thus, the above step 1021 may be implemented as follows:

S1, acquiring corresponding template content according to the first event type.

S2, creating the reminding event according to the template content.

In the above S1, the template content may be configured by the system for the first event type or may be saved by user-defined in advance, which is not specifically limited in the embodiment of the present application. The template content may contain information such as a title, start time information, end time information, and the like. The cost of manual input by the user can be reduced to some extent by pre-configuring the template content.

In order to ensure that the template content meets the real requirements of users, in the implementation, the template content preconfigured for the first event type can be acquired and displayed in a floating layer popped up on a calendar interface to remind the users of confirmation in response to the association operation of a label control corresponding to the first event type and a first date displayed on the calendar interface; and monitoring a confirmation event of the user on the template content, and taking the template content as the event content.

In addition, the user may be supported to modify the template content. Namely, the technical scheme provided by the embodiment of the application can further comprise the steps of: the template content is modified in response to a user modification event for the template content.

In a specific embodiment, the modification event may be triggered when the user edits the template content as shown in fig. 5, or triggered after the user touches the photographing control on the current interface, or triggered after the user touches the scanning control on the current interface, or the like, which is not limited in this embodiment. For ease of understanding, the above trigger conditions will be exemplified below, respectively. For example, a modification event is triggered after a user modifies the start time and/or end time of a meeting in the template content as shown in fig. 5, the system modifies the template content according to the user modified content and uses the modified template content as a basis for creating a reminder event. For another example, the user may find that the content item in the template content shown in FIG. 5 needs to be modified, at which point the user may click on a "take a picture" control on the current interface. Identifying an image (such as an image of a train ticket) acquired by a camera on the terminal, and extracting information such as driving time, starting station, terminal station and the like from the identified information; and modifying the corresponding content item in the template content window based on the content extracted from the identified information. For another example, the user may find that the content item in the template content shown in FIG. 5 needs to be modified, at which point the user may click on the "scan" control on the current interface. Extracting active content in two-dimensional code information, such as information of an active name, an active time, an active ending time, an active place and the like, through a two-dimensional code image acquired by a camera on the terminal; and modifying the corresponding content item in the template content based on the identified two-dimensional code information.

What is needed here is that: the "shoot" control and the "scan" control may be disposed within the template content window, may be disposed in the calendar interface (e.g., the user may pull down the "+" control on the calendar interface to find the "shoot" control and/or the "scan" control), and the like, which is not particularly limited in this embodiment of the present application.

In addition to modifying the template content by taking a photograph or scanning a code, the template content may also be modified by importing a photograph. Suppose that Zhang San purchased an airplane flying from Beijing to Shanghai on the network for 7 months 30 days 8:00 using a cell phone. And thirdly, the detail page of the currently purchased air ticket can be subjected to screen capturing by using the mobile phone. Extracting the contents such as departure date, time, terminal building and the like from the identified information by identifying the information in the screen capture; based on the extracted content, the corresponding content item in the template content is modified.

The shooting, scanning or importing modes are suitable for scenes in which a user needs to modify more contents, such as modifying addresses, so that the user can modify corresponding content items of the template contents only by performing simple operations, the user does not need to modify the template verbatim, and modification time is saved.

It should be noted that, in all the above mentioned floating layers, a cancel and confirm button (as shown in fig. 5) may be displayed, the user clicks the confirm button to complete the creation of the reminder event, and the user clicks the cancel button to discard the creation.

The event content is displayed to the user through the floating layer, so that the number of times of jumping among pages can be reduced, and the problems that the jumping of the pages damages the continuity of the user operation, the repeated operation of the user is caused by the jumping of the pages and the like are avoided. The applicant analyses and discovers that many times, users are very concise when adding tasks, complex functions such as invitees, addresses, calendar sharing and the like are not needed, only tasks corresponding to corresponding dates are marked and reminded are received, and subsequent users can recall detailed contents by virtue of memories after receiving the corresponding reminded. Therefore, the event content can be condensed, and only the title, the start time point information, and the end time point information are retained. Thus, the simplified event content can be displayed through the floating layer. The floating layer is used for displaying information or obtaining user input, so that the function of a plurality of pages can be realized by only one page, and a plurality of pages are not needed to be written or jumped. And, from the user perception, the use of the floating layer makes them feel faster and simpler than the adjusted secondary page.

In the foregoing 1022, associating the first date and the reminder event may be simply understood as: and storing the first date and the reminding event in an associated mode. Specifically, the reminder operation may be performed on the day of the first date and prior to the beginning of the reminder event, such as: 5 minutes or half an hour before start; or reminding operation corresponding to the reminding event on the day before the first date arrives.

In a practical application scenario, the user sometimes only views the calendar, not creates reminder events. In order to avoid that the display of the label control in the calendar interface affects the calendar viewing function of the user, the label control corresponding to the at least one event type can support hiding and unfolding functions. That is, the above method may further include:

106. and responding to an event triggered by a user and displaying the label control, and displaying the label control corresponding to at least one event type on the calendar interface.

107. And hiding the label control corresponding to at least one event type on the calendar interface in response to the event triggered by the user and hiding the label control.

For convenience of use, the user may also be provided with an add control of the user add event type on the calendar interface, in particular, the add control may be displayed on the tab float mentioned in the above embodiment. Specifically, the method may further include:

108. an add control for adding event types is displayed on the calendar interface.

109. And responding to the touch operation of the user on the adding control, and displaying the label creation guide information.

110. And creating a second event type according to the creation content input by the user according to the label creation guide information.

111. And displaying the label control corresponding to the second event type on the calendar interface.

In 108, the adding control may be displayed side by side with a label control corresponding to the at least one event type, as shown in fig. 2. A "+" may be displayed on the add control to alert the user that the control is used to add a new event type.

In 109, the tag creation guide information may be displayed in the newly skipped page (i.e., the created tag page) or may be displayed on the created tag floating layer popped up on the calendar interface. The label creation guide information may include: a tag name input box, alternatives to the display style of the tag control (for user selection), a template content input box, and a confirmation control. The pattern shown in fig. 7 includes color, shape.

In the above 110, the creating content includes at least one of: label name, label control color, label control shape, template content.

In 111 above, in order to coordinate and display the label control corresponding to the added second event type with the label control corresponding to the previous at least one event type, the label control corresponding to the second event type may be added at the end of the label control corresponding to the at least one event type, and before the adding of the label control.

It is to be added that when a plurality of label controls corresponding to the event types exist, the label controls corresponding to the event types can be set to be displayed in a plurality of rows; alternatively, a label control corresponding to the event type may be displayed on the above-mentioned label floating layer; the label float may be arranged in a multi-line display or support sliding viewing of more label controls (e.g., label bubbles). For example: for the label floating layer, the screen is slid left and right to view more label controls.

Further, the method may further include:

113. when a reminding event which is associated with the first date and belongs to a third event type exists, displaying a page element corresponding to the first event type and a page element corresponding to the third event type in an area associated with the first date.

In practical application, a user may create a reminder event of multiple event types for the same date, so that page elements corresponding to the created multiple event types can be displayed in an area associated with the first date.

In summary, the technical scheme provided by the embodiment of the application is simple and lightweight in interaction, and can reduce the number of hops between pages and reduce the operation cost.

Fig. 8 is a flowchart illustrating a method for creating a reminder event according to another embodiment of the present application. As shown in fig. 8, the method includes:

201. a first event type and a first date selected by a user are obtained.

202. And creating a reminding event according to the first event type.

203. And associating the first date and the reminding event.

The foregoing 202 and 203 may be referred to the corresponding content in the foregoing embodiments, and will not be described herein.

In 201 above, at least one event type may be displayed on a calendar interface for selection by a user, for example: a tab control corresponding to the at least one event type may be displayed on the calendar interface. And responding to triggering operation of the user on the label control corresponding to the first event type and the first date on the calendar interface, and acquiring the first event type and the first date selected by the user.

It is considered that the user's operation on the calendar interface may be more arbitrary to avoid creating false reminder events due to the user's erroneous operation. The above 201 may specifically include: and responding to the association operation of the label control corresponding to the first event type and the first date displayed on the calendar interface, and acquiring the first event type and the first date selected by the user. The specific implementation of the association operation may refer to the corresponding content in each embodiment, which is not described herein.

In 202, according to the first event type, the alert event is created by the following steps: acquiring corresponding template content according to the first event type; and creating the reminding event according to the template content.

Further, the method provided by the embodiment of the application may further include: the template content is modified in response to a user modification event for the template content.

What needs to be explained here is: the specific implementation of each step in this embodiment, and the parts not described in detail in this embodiment may refer to the relevant content in each embodiment, which is not described herein. In addition, the method provided in the embodiment of the present application may further include steps mentioned in the foregoing embodiment but not mentioned in the present embodiment, and the steps not mentioned in the embodiment of the present application may refer to corresponding contents in the foregoing embodiment, which are not repeated herein.

Fig. 9 is a flow chart illustrating an event type creation method according to an embodiment of the present application. As shown in fig. 9, the method includes:

301. an add control for adding event types is displayed on the calendar interface.

302. And responding to the touch operation of the user on the adding control, and displaying the label creation guide information.

303. And creating a second event type according to the creation content input by the user according to the label creation guide information.

304. And displaying the label control corresponding to the second event type on the calendar interface.

For the details of the foregoing embodiments 301 to 304, reference may be made to the corresponding details in the foregoing embodiments, and details are not repeated here.

The creation may include at least one of: label name, label control color, label control shape, template content.

Further, the method provided by the embodiment of the application may further include the following steps:

and responding to the association operation of the label control corresponding to the second event type and the first date displayed on the calendar interface, and creating a reminding event associated with the first date and belonging to the second event type.

The following describes the solution provided in the embodiment of the present application with reference to specific application examples shown in fig. 2 to 7.

A calendar interface as shown in fig. 2 displays a tab control corresponding to a month, a date, and an event type. The calendar interface shown in fig. 2 shows: a label control 1 corresponding to the conference event type, a label control 2 corresponding to the birthday event type, a label control 3 corresponding to the airplane event type, a label control 4 corresponding to the vacation event type and an adding control 5. In particular implementations, the tags may be displayed in a floating layer in the calendar interface. The tag float may support both the hiding and unfolding functions. For example: the floating layer hiding control and the floating layer unfolding control can be displayed on the calendar interface, the user can hide the tag floating layer by clicking the floating layer hiding control, and the tag floating layer can be unfolded by clicking the floating layer unfolding control.

As shown in fig. 3, the user presses the tab control 1 for a long time, drags and moves the tab control 1 to the position of 24 days in the calendar interface after selecting, and as shown in fig. 4, the tab control 1 is displayed above 24 days in a semitransparent manner. The dragged tab-control 1 is placed on the 24-day position for n seconds (e.g., 1 second, 2 seconds, etc.), and the pop-up window as shown in fig. 5 is released, i.e., popped up. Template content pre-configured for the label control 1 is currently in the popup, and the content in the popup supports manual modification by a user. The user clicks a 'determination' control in the popup window to finish the creation of the reminding event; clicking the "cancel" control in the popup window gives up the creation of the reminder event. After the reminder event is successfully created, as shown in fig. 6, the page element 10 corresponding to the tab control 1 appears at the bottom of 24 days. The page element may be preset, for example, the page element is a pattern with the same color and shape as the label control 1.

The scheme also supports tag custom augmentation. As shown in fig. 4, after the user clicks the add control (i.e., the "+" control in the figure), the create tab window as shown in fig. 7 pops up. The create tab window may be displayed in a floating layer on the calendar interface. The created tag window displays tag creation guide information. Label name, label color for user selection as shown in fig. 7. And the user inputs the label name according to the label creation guide information, and after selecting the label color, the user clicks the 'confirm' control to complete the deletion of the label.

The scheme also supports the deletion of tags. For example, after clicking the label control 1, the user may delete the label control 1 by sliding down or up; or, the user presses the label control 1 for a long time for more than a set time period (for example, 3 seconds), the deleting control is displayed at the upper right corner of the label control 1, and the deleting action of the label control 1 is completed after the user clicks the deleting control; and the like, the application can also comprise other modes of label deletion schemes, and the comparison is not particularly limited.

Fig. 10 shows a schematic structural diagram of an information display device according to an embodiment of the present application. As shown in fig. 10, the apparatus includes: a first display module 401, a first creation module 402, wherein,

a first display module 401, configured to display a label control corresponding to at least one event type on a calendar interface;

a first creating module 402, configured to create a reminder event associated with a first date and belonging to a first event type, in response to an association operation of a label control corresponding to the first event type and the first date displayed on the calendar interface;

the first display module 401 is further configured to display a page element corresponding to the first event type in association with the first date.

Further, the first creating module 402 is further configured to: creating a reminding event according to the first event type; and associating the first date and the reminding event.

Further, the first creating module 402 is further configured to obtain corresponding template content according to the first event type; and creating the reminding event according to the template content.

Further, the device also comprises a modification module. The modification module is used for responding to a modification event of the event content by a user, and modifying the event content.

Further, the associating operation includes: drag operation from a first position to a second position for the label control corresponding to the first event type; the first position is a display position of a label control corresponding to the first event type, and the second position is a display position of the first date; or the associating operation includes: continuous clicking operation of the label control corresponding to the first event type and the first date; or the associating operation includes: and aiming at the selection operation of the label control corresponding to the first event type, the dragging operation from the first position to the second position of the label control corresponding to the first event type, and the long-press operation remained at the second position.

Further, the first display module 301 is further configured to: and responding to an event triggered by a user and displaying the label control, and displaying the label control corresponding to at least one event type on the calendar interface.

Further, the first display module 401 is further configured to: displaying an add control of the add event type on the calendar interface; and responding to the touch operation of the user on the adding control, and displaying the label creation guide information. Correspondingly, the first creating module is further used for creating a second event type according to the creation content input by the user on the creation tag interface. The first display module 301 is further configured to: and displaying the label control corresponding to the second event type on the calendar interface.

Further, the label control corresponding to the at least one event type is displayed side by side with the adding control; and the first display module 401 is specifically configured to: and adding the label control corresponding to the second event type at the tail end of the label control corresponding to the at least one event type, and before adding the control.

Further, the creation content includes at least one of: label name, label control color, label control shape, template content.

Further, the first display module 401 is further configured to: when a reminding event which is associated with the first date and belongs to a third event type exists, displaying a page element corresponding to the first event type and a page element corresponding to the third event type in an area associated with the first date.

What needs to be explained here is: the information display device provided in the foregoing embodiments may implement the technical solutions described in the foregoing method embodiments, and the specific implementation principles of the foregoing modules or units may refer to corresponding contents in the foregoing method embodiments, which are not repeated herein.

Fig. 11 is a schematic structural diagram of a reminder creating apparatus according to an embodiment of the present application. As shown in fig. 11, the apparatus includes: an acquisition module 501, a second creation module 502 and an association module 503. Wherein,,

An obtaining module 501, configured to obtain a first event type and a first date selected by a user;

a second creating module 502, configured to create a reminder event according to the first event type;

and an association module 503, configured to associate the first date with the reminder event.

Further, the second creating module 502 is further configured to: acquiring corresponding template content according to the first event type; and creating the reminding event according to the template content.

Further, the apparatus also includes a modification module for modifying the template content in response to a modification event by a user for the template content.

What needs to be explained here is: the reminder event creating device provided in the foregoing embodiments may implement the technical solutions described in the foregoing method embodiments, and the specific implementation principles of the foregoing modules or units may refer to the corresponding content in the foregoing method embodiments, which is not described herein again.

Fig. 12 is a schematic diagram showing the structure of an event type creation apparatus according to an embodiment of the present application. As shown, the event type creation means includes: the second display module 601 and the third creation module 602. The second display module 601 is configured to display an add control of an add event type on a calendar interface; and responding to the touch operation of the user on the adding control, and displaying the label creation guide information. The third creating module 602 is configured to create a second event type according to the created content input by the user according to the tag creation guide information. The second display module 601 is further configured to display a label control corresponding to the second event type on the calendar interface.

Further, the third creating module 602 is further configured to create a reminder event associated with the first date and belonging to the second event type in response to an association operation of the tab control corresponding to the second event type and the first date displayed on the calendar interface.

What needs to be explained here is: the event type creating device provided in the foregoing embodiments may implement the technical solutions described in the foregoing method embodiments, and the specific implementation principles of the foregoing modules or units may refer to the corresponding content in the foregoing event type creating method embodiments, which is not described herein again.

Fig. 13 is a schematic structural diagram of an electronic device according to an embodiment of the present application. The electronic device includes: a first memory 1301, a first display 1304, and a first processor 1302. The first memory 1301 may be configured to store various other data to support operations on the electronic device. Examples of such data include instructions for any application or method operating on an electronic device. The first memory 1301 may be implemented by any type of volatile or non-volatile memory device or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, or optical disk.

The first display 1304, coupled to the first processor 1301, is configured to display a tab control corresponding to at least one event type on a calendar interface;

the first processor 1302 is coupled to the first memory 1301 for executing the program stored in the first memory 1201 for:

and controlling the first display 1304 to display the page element corresponding to the first event type and the first date in an associated manner.

In addition, the first processor 1302 may implement other functions in addition to the above functions when executing the program in the first memory 1301, and the above description of the embodiments may be referred to specifically.

Further, as shown in fig. 13, the electronic device further includes: a first communication component 1303, a first power component 1305, a first audio component 1306, and other components. Only some of the components are schematically shown in fig. 13, which does not mean that the electronic device only comprises the components shown in fig. 13.

Accordingly, the present embodiments also provide a computer-readable storage medium storing a computer program capable of implementing the steps or functions of the information display method provided in the above embodiments when the computer program is executed by a computer.

Fig. 14 shows a schematic structural diagram of an electronic device according to another embodiment of the present application. As shown in fig. 14, the electronic device includes a second memory 1401 and a second processor 1402. The second memory 1401 may be configured to store other various data to support operations on the electronic device. Examples of such data include instructions for any application or method operating on an electronic device. The second memory 1401 may be implemented by any type of volatile or non-volatile memory device or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.

The second processor 1402, coupled to the second memory 1401, is configured to execute the program stored in the second memory 1401, for:

Acquiring a first event type and a first date selected by a user;

creating a reminding event according to the first event type;

and associating the first date and the reminding event.

In addition, the second processor 1402 may realize other functions in addition to the above functions when executing the program in the second memory 1401, and the description of the foregoing embodiments may be referred to specifically.

Further, as shown in fig. 14, the electronic device further includes: a second communication component 1403, a second display 1404, a second power component 1405, a second audio component 1406, and other components. Only some of the components are schematically shown in fig. 14, which does not mean that the electronic device only comprises the components shown in fig. 14.

Accordingly, the embodiments of the present application further provide a computer readable storage medium storing a computer program, where the computer program when executed by a computer can implement the steps or functions of the alert event creating method provided in the foregoing embodiments.

Fig. 15 is a schematic structural diagram of an electronic device according to another embodiment of the present application. The electronic device includes: a third memory 1501, a third processor 1502 and a third display 1504. The third memory 1501 may be configured to store other various data to support operations on the electronic device. Examples of such data include instructions for any application or method operating on an electronic device. The first memory 1501 may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

The third display 1504 is coupled to the third processor 1502 for displaying an add control of an add event type on a calendar interface;

the third processor 1502 is coupled to the third memory 1501 for executing the program stored in the third memory 1501 for:

controlling the third display 1504 to display label creation guide information in response to touch operation of a user on the adding control;

and controlling the third display 1504 to display a label control corresponding to the second event type on the calendar interface.

In addition, the third processor 1502 may realize other functions in addition to the above functions when executing the program in the third memory 1501, and the above description of the embodiments may be referred to specifically.

Further, as shown in fig. 15, the electronic device further includes: a third communication component 1503, a third power component 1505, a third audio component 1506, and other components. Only some of the components are schematically shown in fig. 15, which does not mean that the electronic device only comprises the components shown in fig. 15.

Accordingly, the present embodiments also provide a computer-readable storage medium storing a computer program capable of implementing the steps or functions of the event type creation method provided in the above embodiments when the computer program is executed by a computer.

The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.

From the above description of the embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by means of software plus necessary general hardware platforms, or of course may be implemented by means of hardware. Based on this understanding, the foregoing technical solution may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a computer readable storage medium, such as ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in the respective embodiments or some parts of the embodiments.

Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and are not limiting thereof; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the corresponding technical solutions.

Claims

1. An information display method, comprising:

displaying page elements corresponding to the first event type in an associated mode with the first date;

displaying an adding control of an adding event type on the calendar interface;

Creating a second event type according to the creation content input by the user according to the label creation guide information; the creation content includes at least one of: tag name, tag control color, tag control shape, template content;

2. The method of claim 1, wherein creating a reminder event associated with the first date that belongs to the first event type comprises:

creating a reminding event according to the first event type;

and associating the first date and the reminding event.

3. The method of claim 2, wherein creating a reminder event based on the first event type comprises:

acquiring corresponding template content according to the first event type;

and creating the reminding event according to the template content.

4. A method according to claim 3, further comprising:

the template content is modified in response to a user modification event for the template content.

5. The method according to any one of claim 1 to 4, wherein,

The associating operation includes: drag operation from a first position to a second position for the label control corresponding to the first event type; the first position is a display position of a label control corresponding to the first event type, and the second position is a display position of the first date; or alternatively

The associating operation includes: continuous clicking operation of the label control corresponding to the first event type and the first date; or alternatively

The associating operation includes: and aiming at the selection operation of the label control corresponding to the first event type, the dragging operation from the first position to the second position of the label control corresponding to the first event type, and the long-press operation remained at the second position.

6. The method according to any one of claims 1 to 4, further comprising:

and responding to an event triggered by a user and displaying the label control, and displaying the label control corresponding to at least one event type on the calendar interface.

7. The method of claim 1, wherein a label control corresponding to the at least one event type is displayed side-by-side with the add control; and

Displaying a label control corresponding to the second event type on the calendar interface, including:

and adding the label control corresponding to the second event type at the tail end of the label control corresponding to the at least one event type, and before adding the control.

8. The method according to any one of claims 1 to 4, further comprising:

when a reminding event which is associated with the first date and belongs to a third event type exists, displaying a page element corresponding to the first event type and a page element corresponding to the third event type in an area associated with the first date.

9. A method for creating a reminder event, comprising:

responding to triggering operation of a user on a label control corresponding to a first event type and a first date on the calendar interface, and acquiring the first event type and the first date selected by the user;

creating a reminding event according to the first event type;

associating the first date with the reminder event;

displaying an adding control of an adding event type on the calendar interface;

Responding to the touch operation of the user on the adding control, and displaying label creation guide information;

10. The method of claim 9, wherein creating a reminder event based on the first event type comprises:

acquiring corresponding template content according to the first event type;

and creating the reminding event according to the template content.

11. The method as recited in claim 10, further comprising:

12. A method of event type creation, comprising:

displaying an add control of the add event type on the calendar interface;

13. The method as recited in claim 12, further comprising:

14. An electronic device, comprising: a first memory, a first processor, and a first display; wherein,,

the first memory is used for storing programs;

controlling the first display to display the page element corresponding to the first event type and the first date in an associated mode;

Displaying an adding control of an adding event type on the calendar interface;

15. An electronic device, comprising: a second memory and a second processor; wherein,,

the second memory is used for storing programs;

creating a reminding event according to the first event type;

Associating the first date with the reminder event;

displaying an adding control of an adding event type on the calendar interface;

16. An electronic device, comprising: a third memory, a third processor, and a third display, wherein,

the third memory is used for storing programs;

controlling the third display to display a label control corresponding to the second event type on the calendar interface;

controlling the third display to display an adding control of an adding event type on the calendar interface;

controlling the third display to display label creation guide information in response to the touch operation of the user on the adding control;