CN110858139A

CN110858139A - Information display method, reminding event creation method, event type creation method and equipment

Info

Publication number: CN110858139A
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: 2020-03-03
Anticipated expiration: 2038-08-22
Also published as: CN110858139B

Abstract

The embodiment of the application provides a method and equipment for displaying information, 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; in response to the association operation of a label control corresponding to a first event type and a first date displayed on the calendar interface, creating a reminding event which is associated with the first date and belongs to the first event type; and displaying a page element corresponding to the first event type in association with the first date. According to the technical scheme provided by the embodiment of the application, the user only needs to perform association operation on the label control corresponding to the event to be reminded and the corresponding date on the calendar interface, so that the reminding event can be created, and the user operation cost is low and the creation efficiency is high.

Description

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

Technical Field

The present application 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

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

In the prior art, the method for adding the reminding event to the calendar of the terminal mostly uses form filling after page skipping as a main program, and the process of adding the reminding event is complicated, so that the operation cost of a user is high, and the creating efficiency of the reminding event is low.

Disclosure of Invention

In view of the above, the present application is proposed to provide an information display, reminder event creation, event type creation method and apparatus that solve the above problems or at least partially solve the above 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;

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

and displaying a page element corresponding to the first event type in association 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 with the reminding event.

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

displaying an adding control for adding an event type on a calendar interface;

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

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

and displaying a 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: the first processor is connected with the first memory; wherein the content of the first and second substances,

the first memory is used for storing programs;

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

the first processor, coupled with the first memory, to execute the program stored in the first memory to:

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

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 content of the first and second substances,

the second memory is used for storing programs;

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

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 with 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, coupled with the third processor, is configured to display an add control for adding an event type on a calendar interface;

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

responding to touch operation of a user for the adding control, and controlling the third display to display label creation guide information;

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

According to the technical scheme provided by the embodiment of the application, different event types are created in advance for a user to select, and the subsequent user can create the reminding event by selecting the corresponding event type and the corresponding date when creating the reminding event. Compared with the prior art, the technical scheme provided by the embodiment of the application has the advantages of low user operation cost and high creation efficiency.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.

Fig. 1 is a schematic flowchart 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 in accordance with an embodiment of the present application;

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

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

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

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

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

fig. 8 is a schematic flowchart of a method for creating a reminder event according to another embodiment of the present application;

fig. 9 is a flowchart illustrating an event type creating 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 configuration of a reminder event creating apparatus according to an embodiment of the present application;

fig. 12 is a block diagram illustrating an event type creating apparatus 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 application;

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 make the technical solutions better understood by those skilled in the art, 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.

In some of the flows described in the specification, claims, and above-described figures of the present application, a number of operations are included that occur in a particular order, which operations may be performed out of order or in parallel as they occur herein. The sequence numbers of the operations, e.g., 101, 102, etc., are used merely to distinguish between the various operations, and do not represent any order of execution per se. Additionally, 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", "second", etc. in this document are used for distinguishing different messages, devices, modules, etc., and do not represent a sequential order, nor limit the types of "first" and "second" to be different.

The existing process of adding a reminding event in a calendar comprises the following steps: after entering the calendar interface, a user clicks an add reminding event button, jumps to a form page (a plurality of items to be input such as titles, positions, invitees, calendar sharing and the like are provided in the form page), and after entering detailed contents in the form page, the user clicks a finish button on the form page to return to (i.e. jump to) the corresponding calendar interface. Therefore, the existing reminding event is complicated in creating process and low in creating efficiency; moreover, when the user creates the reminding event for the same type of task, the user needs to go through the above flow 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 method and the device for creating the file are 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 is to be understood that the embodiments described are only a few embodiments of the present application and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

Fig. 1 shows 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 in response to the association operation of the label control corresponding to the first event type and the first date displayed on the calendar interface, creating a reminding event which is associated with the first date and belongs to the first event type.

103. And displaying a page element corresponding to the first event type in association with the first date.

In the foregoing 101, the user may enter a calendar interface provided by the terminal system calendar application or the third-party calendar application through voice or by clicking an application icon. The above event types include, but are not limited to: meetings, birthdays, airplanes, vacations, 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 customization. To facilitate the user to identify different label controls, the display styles of different label controls may be different, for example: different shapes and/or different colors. As shown in fig. 2, the color of the conference tab control is red; the birthday label control is blue in color. Among others, shapes may include, but are not limited to: oval, rectangular, circular, pentagonal.

In addition, limited by the size of the terminal display screen, pagination or waterfall pages are commonly used in the prior art to present the calendar. In order to ensure that the date and the label control which are selected by the user are displayed in the same interface, when a 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 need to be added at multiple positions of the waterfall flow page. Such repeated addition of label controls may make the page design less concise. Thus, in one implementation, the label control can be exposed through the floating layer, i.e., the calendar interface can include a bottom calendar layer and a floating label layer which are stacked, and the bottom calendar layer is used for displaying the calendar. The user can independently perform any operation on the calendar bottom layer, such as: and in the process of turning pages or sliding the upper sliding screen and the lower sliding screen to roll pages, the tag floating layer is always positioned in the calendar interface. In this way, only one label floating layer is needed, the date and the label control which the user needs to select can be ensured to be displayed in the same interface, and the subsequent user correlation operation in 102 is facilitated.

The display position of the tag floating layer in the calendar interface can be configured according to actual needs, for example, the tag floating layer can be displayed at the bottom of the calendar interface, as shown in fig. 2. The label float may support hiding and unfolding functions, such as: the control can be hidden to the display flotation layer at calendar interface and the control is expanded to the flotation layer, and the user hides the label flotation layer through clicking the control is hidden to the flotation layer, expands the control through clicking the flotation layer and expands the label flotation layer.

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

a first dragging operation from a first position to a second position aiming at the label control corresponding to the first event type; and the first position is a display position of the 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 11/24 of 2017. The user drags the conference tab control from the display position of the conference tab control to the display position of No. 11/24 in 2017, so that the association of the conference and No. 11/24 in 2017 is realized.

And secondly, continuously clicking the label control corresponding to the first event type and the first date.

The click sequence may be configured in advance, for example: clicking the label control first and then clicking the date.

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

And thirdly, selecting operation of the label control corresponding to the first event type, dragging operation of the label control corresponding to the first event type from the first position to the second position, and long-press operation staying at the second position.

The selection operation can comprise a click operation or a long-time press operation. The long-press time period of the long-press operation staying at the second position needs to be greater than or equal to a preset time period, for example: 1 s. The long press operation may reserve the user a confirmation time for the selected label and date to avoid selection errors.

After the dragged label control is placed on the first date and stagnates for a preset time, visual feedback is generated after the first date and the label control interact with each other, so that a user is informed that the association is successful, and the user can release the label control.

Additionally, the reminder event mentioned above in 102 may be created based on the first event type. The created reminder event is associated with a first date such that a later date triggers a reminder upon arrival of the first date. The event content corresponding to the first event type may be a template content configured for the first event type in advance, or may also be a content re-edited by a user, and the like, which is not specifically limited in this embodiment of the present application.

From 102, it can be seen that the user only needs to perform one association operation on the tag control corresponding to the first event type and the first date on the calendar interface, so as to create the reminder event. No page jump is involved in the establishing process, and the interaction is simple and light; and the label is set only once for the same event type, and the label can be reused subsequently, so that repeated entry operation of the user for the task of the same event type is avoided.

In the above 103, the associated display may be understood as displaying a 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 the display area of the first date and/or a region 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 subsequently recognize the event type corresponding to the page element, the display style of the page element may be set in combination with the display style of the tag control corresponding to the first event type, for example: if the colors of different label controls are different, the color in the display style of the page element corresponding to the first event type can be set to be the color of the label control corresponding to the first event type; or, if the shapes of 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, the corresponding label controls are set for different event types in advance, and the subsequent user only needs to perform association operation on the label control corresponding to the event to be reminded and the corresponding date on the calendar interface to realize the creation of the reminding event. Compared with the prior art, the technical scheme provided by the embodiment of the application has the advantages of low user operation cost and high creation efficiency.

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

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

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

At 1021, the reminder event may not include content information such as the event time and the event occurrence location. For example, the birthday event type referred to by the "birthday" tab control in FIG. 4; the user creates a reminder event using the birthday event type, only the day that the user wants to remind him that he is marked is his birthday, and no birthday activity is 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 (such as departure time of the airplane, starting time of the meeting and the like), event occurrence place (such as airport terminal, meeting place and the like) and the like corresponding to the travel event type indicated by the label control of the airplane and the meeting event type indicated by the label control of the meeting. Therefore, the step 1021 can be implemented as follows:

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

And 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 stored by the user in a customized manner in advance, which is not specifically limited in this embodiment of the application. The template content may contain information such as a title, start time point information, end time point information, and the like. The cost of manual input by the user can be reduced to a certain extent by the pre-configured template content.

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

In addition, the modification of the template content by the user can be supported. Namely, the technical scheme provided by the embodiment of the application can further comprise the following steps: and modifying the template content in response to a modification event of the template content by the user.

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, and the like, which is not specifically limited in this embodiment of the present application. For ease of understanding, the above triggering cases will be illustrated separately below. For example, a modification event is triggered after the user modifies the meeting start time and/or end time in the template content as shown in fig. 5, that is, the system modifies the template content according to the content modified by the user and uses the modified template content as the basis for creating the reminder event. As another example, the user may click on the "take picture" control on the current interface when the user finds that a content item in the template content shown in FIG. 5 needs to be modified. Identifying an image (such as an image of a train ticket) acquired by a camera on a terminal, and extracting information such as driving time, a starting station, a 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. As another example, the user may find that the content items in the template content shown in FIG. 5 need to be modified, at which point the user may click on the "scan" control on the current interface. Extracting activity contents in the two-dimensional code information, such as information of activity names, activity time, activity ending time, activity places 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 needs to be added here is: the "taking" control and the "scanning" control may be disposed in the template content window, or may be disposed in the calendar interface (for example, the user may pull down the "+" control on the calendar interface to find the "taking" control and/or the "scanning" control), and so on, which is not particularly limited in this embodiment of the application.

Besides modifying the template content by taking a picture or scanning a code, the template content can be modified by importing a picture. Suppose that Zhang three purchased an airplane flying from Beijing to Shanghai at 7 months, 30 days, 8:00 on the network using a cell phone. Zhang III can use the cell phone to capture a detailed page of the currently purchased ticket. Extracting the contents such as departure date, time, terminal building and the like from the identified information by identifying the information in the screen shot; based on the extracted content, a corresponding content item in the template content is modified.

The mode of taking pictures, scanning or importing is suitable for scenes which need a user to modify more contents, such as modifying addresses, so that the user only needs to carry out simple operation to modify the corresponding content items of the template contents, the user does not need to modify the template contents word by word, and the modification time is saved.

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

The event content is displayed to the user through the floating layer, so that the jumping times among the pages can be reduced, and the problems of damage to the continuity of user operation caused by the jumping of the pages, repeated user operation caused by the jumping of the pages and the like are avoided. The applicant analyzes and finds that many times, a user is 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 need to be marked and reminders are received, and subsequent users can recall detailed contents by means of memory after receiving corresponding reminders. Accordingly, the event content can be condensed, and only the title, the start time point information, and the end time point information are retained. Therefore, the simplified event content can be displayed through the floating layer. The floating layer is used for displaying information or obtaining user input, and the advantage is that the function of multiple pages can be realized by only one page without writing or jumping several pages. And, from the user perception, compared with the adjusted secondary page, the floating layer is used to make the user feel faster and simpler.

In 1022, the association between the first date and the reminder event may be simply understood as: storing the first date in association with the reminder event. Specifically, the reminder operation may be performed on the first calendar day and prior to the start of the reminder event, such as: 5 minutes or half an hour before starting; or the reminding operation corresponding to the reminding event is carried out on the day before the first date.

In a real application scenario, users sometimes only view a calendar, and not create a reminder event. 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 may support the hiding and unfolding functions. That is, the above method may further include:

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

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

For the convenience of the user, an adding control for adding an event type to the user can be further provided for the user on the calendar interface, and particularly, the adding control can be displayed on the label floating layer mentioned in the above embodiment. Specifically, the method may further include:

108. an add control to add an event type is displayed on the calendar interface.

109. And responding to the touch operation of the user for the adding control, and displaying 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 a label control corresponding to the second event type on the calendar interface.

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

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

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

In 111, in order to make the added label control corresponding to the second event type and the previous label control corresponding to at least one event type displayed in a coordinated manner, 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, where the control is previous to the addition.

It is necessary to supplement that, when there are a large number of label controls corresponding to event types, the label controls corresponding to the event types may be set to be displayed in multiple rows; or, 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 to support a sliding view of more label controls (e.g., label bubbles). For example: for the label float, slide the screen left or right to see more label controls.

Further, the method may further include:

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

In practical application, a user may create a plurality of event types of reminder events for the same date, and therefore, page elements corresponding to the created plurality of event types may be displayed in an area associated with the first date.

In summary, the technical scheme provided by the embodiment of the application is simple in interaction and light in weight, and can reduce the inter-page jump times and reduce the operation cost.

Fig. 8 is a flowchart illustrating a method for creating a reminder event according to yet 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 with the reminding event.

The above 202 and 203 can refer to the corresponding contents in the above embodiments, and are not described herein again.

In 201, at least one event type may be displayed on the calendar interface for selection by the user, for example: a label control corresponding to at least one event type can be displayed on the calendar interface. And responding to the 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.

The calendar event generation method and the calendar event generation device have the advantages that the operation of a user on the calendar interface can be more random, so that the situation that the wrong operation of the user causes the wrong reminding event to be created is avoided. The foregoing 201 may specifically include: and responding to the label control corresponding to the first event type and the associated operation of the first date displayed on the calendar interface, and acquiring the first event type and the first date selected by the user. For specific implementation of the association operation, reference may be made to corresponding contents in the foregoing embodiments, and details are not described herein.

In 202, creating a reminding event according to the first event type may be implemented by the following steps: acquiring corresponding template contents 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 present application may further include: and modifying the template content in response to a modification event of the template content by the user.

Here, it should be noted that: for specific implementation of each step in this embodiment, reference may be made to relevant contents in each embodiment for parts not described in detail in this embodiment, and details are not described here again. In addition, the method provided in the embodiment of the present application may further include steps mentioned in the above embodiments but not mentioned in the embodiment, and the steps not mentioned in the embodiment of the present application may refer to corresponding contents in the above embodiments, and are not described herein again.

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

301. an add control to add an event type is displayed on the calendar interface.

302. And responding to the touch operation of the user for the adding control, and displaying 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 a label control corresponding to the second event type on the calendar interface.

For the above 301 to 304, reference may be made to the corresponding contents in the above embodiments, which are not described herein again.

The creating content 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 present application may further include the following steps:

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

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

The calendar interface shown in fig. 2 displays label controls corresponding to months, dates and event types. Among them, the calendar interface shown in fig. 2 displays: the system comprises a label control 1 corresponding to a conference event type, a label control 2 corresponding to a birthday event type, a label control 3 corresponding to an airplane event type, a label control 4 corresponding to a vacation event type and an adding control 5. In particular implementations, the tags may be displayed in a floating layer manner in the calendar interface. The label float may support both the hiding and unfolding functions. For example: the control can be hidden to the display flotation layer at calendar interface and the control is expanded to the flotation layer, and the user hides the label flotation layer through clicking the control is hidden to the flotation layer, expands the control through clicking the flotation layer and expands the label flotation layer.

As shown in fig. 3, the user long presses the selected tab control 1, and drags and moves the tab control 1 to the position of 24 days in the calendar interface after selecting, as shown in fig. 4, the tab control 1 is displayed above 24 days in a semi-transparent manner. And (3) placing the dragged label control 1 at the position of the 24 days for stagnation for n seconds (such as 1 second, 2 seconds and the like), and releasing, namely popping up the pop-up window shown in the figure 5. Template content pre-configured for the label control 1 exists in the popup window, and the content in the popup window supports manual modification of a user. The user clicks a 'determination' control in the popup window to complete the creation of the reminding event; clicking the "cancel" control in the pop-up window abandons the creation of the reminder event. After the reminder event is created successfully, 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 the custom addition of tags. As shown in FIG. 4, after the user clicks on the add control (i.e., the "+" control in the figure), the create tab window pops up as shown in FIG. 7. The create tab window may be displayed in a floating layer on the calendar interface. The create tab window displays tab creation guidance information. Such as the 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 the label color is selected, the user clicks the 'determination' control to finish the deletion of the label.

The scheme also supports the deletion of the label. For example, after clicking the label control 1, the user can slide downwards or upwards to delete the label control 1; or, if the user presses the label control 1 for a long time longer than a set time (for example, 3 seconds), the deletion control is displayed at the upper right corner of the label control 1, and the user clicks the deletion control to complete the deletion action of the label control 1; and the like, the present application may also include other tag deletion schemes, and the comparison is not particularly limited.

Fig. 10 is a schematic structural diagram illustrating 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,

the first display module 401 is 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, in response to an association operation on a tag control corresponding to a first event type and a first date displayed on the calendar interface, a reminder event associated with the first date and belonging to the first event type;

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 with 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 user aiming at the event content and modifying the event content.

Further, the associating operation includes: dragging operation from a first position to a second position aiming at 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 comprises: continuous clicking operation aiming at the label control corresponding to the first event type and the first date; or the associating operation comprises: the method comprises the steps of selecting operation of a label control corresponding to the first event type, dragging operation of the label control corresponding to the first event type from the first position to the second position, and long-press operation staying at the second position.

Further, the first display module 301 is further configured to: and responding to an event for displaying the label control triggered by the user, 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 adding control for adding an event type on a calendar interface; and responding to the touch operation of the user for the adding control, and displaying label creation guide information. Correspondingly, the first creating module is further configured to create a second event type according to the creation content input by the user on the creation label interface. The first display module 301 is further configured to: and displaying a label control corresponding to the second event type on the calendar interface.

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

Further, the creating 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: and when a reminding event which is related to the first date and belongs to a third event type exists, displaying the page element corresponding to the first event type and the page element corresponding to the third event type in an area related to the first date.

Here, it should be noted that: the information display device provided in the above embodiments may implement the technical solutions described in the above method embodiments, and the specific implementation principle of each module or unit may refer to the corresponding content in the above method embodiments, and is not described herein again.

Fig. 11 shows a schematic structural diagram of a reminder event creating device 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 the content of the first and second substances,

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 reminding event according to the first event type;

an associating module 503, configured to associate the first date with the reminding event.

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

Further, the apparatus further comprises a modification module configured to modify the template content in response to a modification event of the template content by a user.

Here, it should be noted that: the reminding event creating device provided in the above embodiments may implement the technical solutions described in the above method embodiments, and the specific implementation principle of each module or unit may refer to the corresponding content in the above method embodiments, and is not described herein again.

Fig. 12 is a schematic structural diagram illustrating an event type creating apparatus according to an embodiment of the present application. As shown in the figure, the event type creating device includes: a second display module 601 and a third creation module 602. The second display module 601 is configured to display an add control for adding an event type on a calendar interface; and responding to the touch operation of the user for the adding control, and displaying label creation guide information. The third creating module 602 is configured to create a second event type according to the creation content input by the user according to the tag creation guidance 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, in response to an association operation on the tag control corresponding to the second event type and the first date displayed on the calendar interface, a reminder event associated with the first date and belonging to the second event type.

Here, it should be noted that: 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 principle of each module or unit may refer to the corresponding content in the foregoing event type creating method embodiments, and 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 other various data to support operations on the electronic device. Examples of such data include instructions for any application or method operating on the 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 or optical disk.

The first display 1304, coupled to the first processor 1301, is used for displaying a label control corresponding to at least one event type on a calendar interface;

the first processor 1302, coupled to the first memory 1301, is configured to execute the program stored in the first memory 1201, so as to:

and controlling the first display 1304 to display the page element corresponding to the first event type in association with the first date.

When executing the program in the first memory 1301, the first processor 1302 may also implement other functions in addition to the above functions, which may be specifically referred to in the description of the foregoing embodiments.

Further, as shown in fig. 13, the electronic apparatus 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, and the electronic device is not meant to include only the components shown in fig. 13.

Accordingly, embodiments of the present application also provide a computer-readable storage medium storing a computer program, where the computer program can implement the steps or functions of the information display method provided in the foregoing embodiments when 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 the electronic device. The second memory 1401 may be implemented by any type of volatile or non-volatile storage 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 second processor 1402, coupled to the second memory 1401, is configured to execute the program stored in the second memory 1401, to:

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 with the reminding event.

When the second processor 1402 executes the program in the second memory 1401, the functions other than the above functions may be implemented, and the descriptions of the foregoing embodiments may be referred to specifically.

Further, as shown in fig. 14, the electronic apparatus further includes: a second communication component 1403, a second display 1404, a second power component 1405, a second audio component 1406, and the like. Only some of the components are schematically shown in fig. 14, and it is not meant that the electronic device includes only the components shown in fig. 14.

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

Fig. 15 is a schematic structural diagram of an electronic device according to yet 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 the electronic device. The first memory 1501 may be implemented by any type or combination of volatile or non-volatile 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 or optical disks.

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

the third processor 1502, coupled to the third memory 1501, is configured to execute the program stored in the third memory 1501 to:

in response to a touch operation of a user for the add control, controlling the third display 1504 to display label creation guidance information;

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

When executing the program in the third memory 1501, the third processor 1502 may also implement other functions in addition to the above functions, which may be specifically referred to the descriptions of the foregoing embodiments.

Further, as shown in fig. 15, the electronic apparatus further includes: a third communication component 1503, a third power component 1505, a third audio component 1506, and the like. Only some of the components are schematically shown in fig. 15, and it is not meant that the electronic device includes only the components shown in fig. 15.

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

The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.

Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; 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 solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims

1. An information display method, comprising:

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

creating a reminding event according to the first event type;

and associating the first date with the reminding event.

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

acquiring corresponding template contents according to the first event type;

and creating the reminding event according to the template content.

4. The method of claim 3, further comprising:

and modifying the template content in response to a modification event of the template content by the user.

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

the associating operation comprises: dragging operation from a first position to a second position aiming at 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 comprises: continuous clicking operation aiming at the label control corresponding to the first event type and the first date; or

The associating operation comprises: the method comprises the steps of selecting operation of a label control corresponding to the first event type, dragging operation of the label control corresponding to the first event type from the first position to the second position, and long-press operation staying at the second position.

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

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

7. The method of any of claims 1 to 4, further comprising:

displaying an adding control for adding an event type on a calendar interface;

8. The method of claim 7, wherein the 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 of the label control corresponding to the at least one event type, wherein the control is added before.

9. The method of claim 7, wherein creating content comprises at least one of: label name, label control color, label control shape, template content.

10. The method of any of claims 1 to 4, further comprising:

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

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

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 with the reminding event.

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

acquiring corresponding template contents according to the first event type;

and creating the reminding event according to the template content.

13. The method of claim 12, further comprising:

14. An event type creation method, comprising:

displaying an adding control for adding an event type on a calendar interface;

15. The method of claim 14, wherein creating content comprises at least one of: label name, label control color, label control shape, template content.

16. The method of claim 14 or 15, further comprising:

17. An electronic device, comprising: the first processor is connected with the first memory; wherein the content of the first and second substances,

the first memory is used for storing programs;

18. An electronic device, comprising: a second memory and a second processor; wherein the content of the first and second substances,

the second memory is used for storing programs;

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 with the reminding event.

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

the third memory is used for storing programs;