CN117875925A

CN117875925A - Schedule management method and schedule management device

Info

Publication number: CN117875925A
Application number: CN202211230407.4A
Authority: CN
Inventors: 鲍新彤
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2022-09-30
Filing date: 2022-09-30
Publication date: 2024-04-12
Also published as: WO2024066863A1; WO2024066863A9

Abstract

The scheme supports the marking of important schedules by users, and for the important schedules, the display positions of the important schedules are in front of the common schedules, so that the users can more intuitively see the important schedules. In addition, for the important schedules, the interface for displaying the schedules can be unfolded to display the information of the important schedules, namely, the information of the important schedules displayed on the interface is more than that of other schedules, so that a user can intuitively acquire more information of the important schedules, and the user experience is improved.

Description

Schedule management method and schedule management device

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a method and an apparatus for schedule management.

Background

An application program capable of realizing schedule management in the electronic equipment supports a user to create or access a plurality of schedules from other application programs. Different schedules are of different importance to the user, e.g. are conference schedules, and conferences involving important content are often of higher importance than normal regular meetings. The current schedule management application cannot highlight the schedule important to the user, which may cause the user to miss the important schedule.

Disclosure of Invention

In view of this, the present application provides a schedule management method and apparatus to solve at least some of the above problems, and the disclosed technical solution is as follows:

in a first aspect, the present application provides a schedule management method, applied to an electronic device, where the method includes: displaying a first interface, wherein the first interface comprises a first day Cheng Kapian, and the first calendar card comprises schedule information and schedule priority, wherein the schedule priority is none; and in response to the operation of selecting the schedule priority as important, displaying a second interface, wherein the second interface comprises a second schedule card, the schedule priority in the second schedule card is important, and the second schedule card contains more schedule information than the first schedule card. Therefore, the scheme supports that the user can manually mark the important schedules, and the information of the important schedules is displayed on the interface more than other schedules, so that the user can conveniently and intuitively know more information of the important schedules, and the user experience is improved.

In a possible implementation manner of the first aspect, the schedule information includes a schedule title; the second calendar card also includes an important identifier, the important identifier being located before the calendar title. Thus, the user can recognize that the schedule is an important schedule after seeing the important identifier in the schedule display area.

In a possible implementation manner of the first aspect, the schedule priority includes none, importance and ignorance. It can be seen that the scheme omits the level combined to the priority, and each interface for displaying the schedule comprises the priority setting item, so that a user can easily find an ignored entry, and the operation of the user is convenient.

In a possible implementation manner of the first aspect, in response to the selecting the schedule priority as the important operation, displaying a second interface includes: responding to the operation of clicking the schedule priority on the first schedule card, and displaying a priority setting option popup window on the first interface, wherein the priority setting option popup window comprises a no-level option, an important level option and an neglect option; and in response to an operation of selecting the importance level option on the priority setting option popup, displaying a second interface.

In a possible implementation manner of the first aspect, before displaying the first interface, the method further includes: displaying a third interface, wherein the third interface comprises a first button, and the first button is used for newly creating a schedule; in response to an operation of the first button, displaying a first interface, the first interface further including a save button; in response to an operation selecting the calendar priority as important, displaying a second interface comprising: responding to the operation of schedule priority on the first interface, displaying a priority setting option popup on the first interface, wherein the priority setting option popup comprises a no-level option, an importance level option and an neglect option; responding to the operation of selecting an important level option on a priority setting option popup window, displaying a first interface, wherein schedule priority in the first interface is updated to be important; the second interface is displayed in response to an operation of the save button. Therefore, the user can mark the important schedules on the newly built schedule page, and the user can mark the important schedules when creating the new schedules.

In a possible implementation manner of the first aspect, the schedule information includes participants, and the method further includes: when the schedule priority is detected to be an important schedule, acquiring participants in all schedules containing the participants; selecting a preset number of participants meeting preset conditions from all the participants of the schedules, and determining the participants as recommended participants, wherein the preset conditions comprise that the frequency of participating in important schedules is greater than a preset threshold value; a recommender list is generated that includes recommended participants. Therefore, after the important schedule is detected, the participants meeting certain conditions can be selected from all the participants in the important schedule by combining the participants in the important schedule to be recommended to the user as important participants, so that the user can directly add the important participants from the recommended persons, the user operation is reduced, and the speed of adding the important participants is improved.

In a possible implementation manner of the first aspect, after generating the recommendation list, the method further includes: when a new important calendar is detected, the recommended participants in the recommender list are updated based on the participants of the new important calendar. It can be seen that the scheme can update the recommender list according to the update of the important schedules so that the recommenders in the recommender list are always important participants of the user's interest.

In a possible implementation manner of the first aspect, the method further includes: displaying a first important participant interface, wherein the first important participant interface comprises a recommender list, the recommender list comprises at least one participant item, and the participant item comprises participant information and an add button; in response to operation of the add button, a second important participant interface is displayed, the second important participant interface including an important participant list including important participant items, each important participant item including an added participant and a remove button.

In a possible implementation manner of the first aspect, the first important participant interface further includes an add other participant button; after displaying the first important participant interface, the method further comprises: in response to an operation of the add other participant button, displaying a first selected participant interface, the first selected participant interface including a first participant list of all schedules; in response to an operation of selecting any one of the first participant list, a third important participant interface is displayed, the third important participant interface including an important participant list including the selected participant. Therefore, not only the human-made important participants in the recommender list can be added, but also other human-made important participants can be added, so that the requirements of users are met.

In a possible implementation manner of the first aspect, the first calendar card further includes a participant setting item; after displaying the first interface, the method further comprises: in response to an operation of the participant setting item, displaying a schedule participant interface, the schedule participant interface including a second participant list and an edit important participant button, the second participant list including all participants in a schedule contained in the first schedule card; in response to an operation of the important participant button, displaying a second selected participant interface, the second selected participant interface including a participant selection list; in response to an operation of selecting a participant in the participant selection list, the selected important participant is marked as an important participant, and the important participant list is updated. Therefore, the user can directly set a certain participant to be an important participant in the participants of a certain day, and the requirements of the user are met.

In a possible implementation manner of the first aspect, after adding the important participant, the method further includes: after detecting that the participants of the non-important schedules comprise important participants, automatically marking the non-important schedules as important schedules, wherein the non-important schedules are schedules with priority being none. Therefore, the non-important schedules containing important participants can be automatically marked as important schedules without manual marking by a user, so that the user operation is reduced, and the user experience is improved.

In a possible implementation manner of the first aspect, after displaying the second interface, the method further includes: displaying a setting popup window, wherein the setting popup window comprises only displaying important first setting items; in response to an operation of the first setting item, only important schedules are displayed in respective interfaces displaying schedules. Therefore, the important schedules are screened and displayed in the schedules with more schedules, so that a user can pay attention to the important schedules, and important things are avoided being missed.

In a possible implementation manner of the first aspect, after displaying the first interface, the method further includes: responding to the operation of the first schedule card, displaying a fourth interface, wherein the fourth interface comprises the schedule priority of schedules in the first schedule card, and the schedule priority is none; after the fact that the first prompt popup window is not displayed is determined, the first prompt popup window is displayed on a fourth interface, and the first prompt popup window comprises prompt information for prompting a user to mark an important schedule.

In a possible implementation manner of the first aspect, displaying the fourth interface in response to the operation on the first date card includes: responding to clicking operation on the first schedule card, displaying a fourth interface, wherein the fourth interface displays schedule detail information of schedules in the first schedule card, and the schedule detail information comprises titles, start-stop time and schedule priority, and the schedule priority is absent; alternatively, the first calendar card further includes a second button; in response to operation of the first date card, displaying a fourth interface comprising: responding to clicking operation of the second button, displaying a fourth interface, wherein the fourth interface comprises a third schedule card, the schedule displayed in the third schedule card is the same as the schedule displayed in the first schedule card, the schedule information displayed by the third schedule card is more than the schedule information displayed by the first schedule card, and the schedule priority in the third schedule card is none; or, in response to an operation on the first date card, displaying a fourth interface comprising: and responding to the long-press operation of the first schedule card, displaying a fourth interface, wherein the fourth interface comprises a fourth schedule card, the schedule displayed by the fourth schedule card is the same as that displayed by the first schedule card, and the fourth schedule card is displayed in a popup window mode.

In a second aspect, the present application further provides another schedule management method, and a desktop card setting item, where a schedule priority is important; in response to an operation of the desktop card setting item, a first desktop card of a first schedule is displayed on the desktop, the first desktop card including a number of days between a current date and an execution date of the first schedule. Therefore, the scheme can add the desktop card of the important schedule on the desktop, and the desktop card can display the number of days apart from the execution date of the important schedule, so that the user can clearly see the remaining period of the important schedule at a glance, and further remind the user to execute the important schedule or make full preparation for the important schedule.

In a possible implementation manner of the second aspect, before displaying the first interface, the method further includes: displaying a second interface, wherein the second interface comprises a newly built schedule button; and responding to the operation of the new schedule button, and displaying a first interface. Therefore, the scheme supports the addition of the desktop card of the schedule when the user newly builds the schedule, and avoids repeated operation of the user.

In a possible implementation manner of the second aspect, after displaying the first interface, the method further includes: responding to the operation of the desktop card setting item, and after the desktop card corresponding to the added first schedule is detected, displaying a first popup window on a first interface, wherein the first popup window comprises a cancel button, a confirm button and information for prompting a user whether to repeatedly add the desktop card; in response to an operation of the ok button, a second desktop card of the first schedule is added, the second desktop card being identical in content to the first desktop card. Therefore, the scheme supports the user to repeatedly add the desktop card of a certain schedule, for example, the desktop card of the same schedule is added on different desktop pages, so that the user can see the schedule on each desktop page, the presentation rate of the desktop card is improved, and the user can pay attention to the schedule more easily.

In a possible implementation manner of the second aspect, the method further includes: displaying a third interface, wherein the third interface comprises a blank desktop card and a first button, and the blank desktop card comprises an adding schedule button; displaying a blank desktop card on the desktop in response to an operation of the first button; in response to operation of the add schedule button, displaying a select schedule interface, the select schedule interface including a selectable schedule; in response to an operation of selecting a schedule at the schedule selection interface, displaying a desktop, the desktop including a third desktop card, the third desktop card including information of the selected schedule, and a number of days between a current date and an execution date of the selected schedule.

In a third aspect, the present application further provides an electronic device, including: one or more processors, memory, and a touch screen; the memory is used for storing program codes; the processor is configured to execute program code to cause the electronic device to implement the schedule management method of any one of the first aspect and the second aspect.

In a fourth aspect, the present application also provides a computer-readable storage medium having instructions stored thereon that, when executed on an electronic device, cause the electronic device to perform the schedule management method of any one of the first and second aspects.

In a fifth aspect, the present application also provides a computer program product having stored thereon an execution, which when run on an electronic device causes the electronic device to perform the schedule management method of any one of the first and second aspects.

It should be appreciated that the description of technical features, aspects, benefits or similar language in this application does not imply that all of the features and advantages may be realized with any single embodiment. Conversely, it should be understood that the description of features or advantages is intended to include, in at least one embodiment, the particular features, aspects, or advantages. Therefore, the description of technical features, technical solutions or advantageous effects in this specification does not necessarily refer to the same embodiment. Furthermore, the technical features, technical solutions and advantageous effects described in the present embodiment may also be combined in any appropriate manner. Those of skill in the art will appreciate that an embodiment may be implemented without one or more particular features, aspects, or benefits of a particular embodiment. In other embodiments, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic structural diagram of an electronic device according to an embodiment of the present application;

FIG. 2-1 is a schematic diagram of an interface for manually marking important schedules according to an embodiment of the present application;

2-2 are schematic diagrams of another new calendar interface provided by an embodiment of the present application;

FIG. 3 is an interface schematic diagram of a calendar detail view provided by an embodiment of the present application;

FIG. 4 is a schematic diagram of another interface for manually marking important schedules provided by an embodiment of the present application;

FIG. 5 is a schematic illustration of an interface for manually marking important schedules according to an embodiment of the present application;

FIG. 6 is a schematic illustration of an interface for manually marking important schedules according to an embodiment of the present application;

FIG. 7 is a schematic diagram of an interface for new function guidance for important schedules provided by an embodiment of the present application;

Fig. 8 is a schematic rule diagram for determining important participants according to an embodiment of the present application.

FIG. 9 is a schematic illustration of an interface for new function guidance for important participants provided by an embodiment of the present application;

FIG. 10 is a schematic illustration of an interface for adding important participants provided in an embodiment of the present application;

FIG. 11 is a schematic illustration of an important participant human interface provided by an embodiment of the present application;

FIG. 12 is a schematic illustration of another interface for adding important participants provided by an embodiment of the present application;

FIG. 13 is a schematic illustration of yet another interface for adding important participants provided by an embodiment of the present application;

FIG. 14 is a schematic diagram of an automatic marking of important schedules provided in an embodiment of the present application;

FIG. 15 is a schematic view of an interface for removing important participants provided in an embodiment of the present application;

FIG. 16 is a schematic illustration of another important participant human interface provided by an embodiment of the present application;

FIG. 17 is a schematic illustration of yet another important participant human interface provided by an embodiment of the present application;

FIG. 18 is a schematic diagram of an interface for screening important schedules according to an embodiment of the present application;

FIG. 19 is a schematic diagram of another interface for screening important schedules according to an embodiment of the present application;

FIG. 20 is a schematic diagram of an interface for screening important schedules according to an embodiment of the present application;

FIG. 21 is a schematic view of an interface for adding calendar cards to a desktop according to an embodiment of the present application;

FIG. 22 is a schematic view of a calendar card display provided in an embodiment of the present application;

FIG. 23 is a schematic illustration of a calendar card style provided in an embodiment of the present application;

FIG. 24 is a schematic illustration of another interface for adding calendar cards to a desktop according to an embodiment of the present application;

FIG. 25 is a schematic illustration of yet another interface for adding calendar cards to a desktop provided in accordance with an embodiment of the present application;

FIG. 26 is a schematic illustration of an interface for selecting a calendar interface provided by an embodiment of the present application;

fig. 27 is an interface schematic diagram of a calendar card operation according to an embodiment of the present application.

Detailed Description

The terms first, second, third and the like in the description and in the claims and drawings are used for distinguishing between different objects and not for limiting the specified sequence.

In the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as examples, illustrations, or descriptions. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

The user may create a schedule of a plurality of different time periods within the same date, e.g., 8:00-9:00: schedule 1, 10:00-11:00: schedule 2, 13: 00-14:30: in the schedule 3, in the related art, the schedules are generally ordered according to the sequence of the starting times of the schedules, the schedules which can be displayed in the display interface are limited, and the schedule displaying mode may lead to that the important schedules are arranged at the back, so that the user needs to manually slide the display interface upwards to see the information of the important schedules. In addition, the information displayed for different schedules is substantially the same, and important information cannot be highlighted, for example, a start time and an end time are displayed for both a conference schedule and a credit card repayment schedule. The importance degree of the conference schedule is higher than that of the credit card repayment for the user, however, the displayed schedule information does not highlight the importance of the conference schedule, and more information of the conference schedule is not displayed, namely, for the important schedule of the user and the common schedule, the displayed information and the prompt function are not different, and the user can only subjectively distinguish which important schedules are important schedules, so that the user can miss the important schedules.

In order to solve the technical problems, the inventor of the application provides a schedule management method which supports a user to mark important schedules, and for the important schedules, the display position of the important schedules is in front of a common schedule, so that the user can more intuitively see the important schedules. In addition, for the important schedules, the interface for displaying the schedules can be unfolded to display the information of the important schedules, namely, the information of the important schedules displayed on the interface is more than that of other schedules, so that a user can intuitively acquire more information of the important schedules, and the user experience is improved.

The electronic device to which the schedule management method provided in the embodiments of the present application may be applied may be a mobile phone, a tablet computer, a desktop, a laptop, a notebook, an Ultra-mobile personal computer (Ultra-mobile Personal Computer, UMPC), a handheld computer, a netbook, a personal digital assistant (Personal Digital Assistant, PDA), a wearable electronic device, a smart watch, an augmented reality technology (augmented reality, AR) device, a Virtual Reality (VR) device, or the like. It should be understood that the terminal device according to the embodiment of the present application may have a function of setting a schedule, and the embodiment of the present application does not limit a specific technology and a specific device configuration adopted by the terminal device.

Fig. 1 is a schematic structural diagram of an electronic device according to an embodiment of the present application. As shown in fig. 1, the electronic device may include a processor 1, a memory 2, a display 3, a touch sensor 4, and a power management module 5.

It is to be understood that the configuration illustrated in this embodiment does not constitute a specific limitation on the electronic apparatus. In other embodiments, the electronic device may include more or fewer components than shown, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The processor 1 may comprise one or more processing units, and the different processing units may be separate devices or may be integrated in one or more processors. For example, in the present embodiment, the processor 1 may manage a schedule.

The memory 2 is used for storing computer executable program code and data, wherein the program code comprises instructions. The processor 1 manages schedules by executing program instructions stored in the memory 2.

The display 3 is used for displaying images, videos, etc., and may also display a series of graphical user interfaces (graphical user interface, GUIs), which are all the main screens of the electronic device. In general, the size of the display 3 of an electronic device is fixed and only limited controls can be displayed in the display 3 of the electronic device. A control is a GUI element that is a software component contained within an application program that controls all data processed by the application program and interactive operations on that data, and a user can interact with the control by direct manipulation (direct manipulation) to read or edit information about the application program. In general, controls may include visual interface elements such as icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, and the like.

The touch sensor 4 is also referred to as a "touch device". The touch sensor 4 may be disposed on the display screen 3, and the touch sensor 4 and the display screen 3 form a touch screen, which is also called a "touch screen". The touch sensor 4 is used to detect a touch operation acting on or near it. The touch sensor may communicate the detected touch operation to the application processor to determine the touch event type. Visual output related to the touch operation may be provided through the display 3. In other embodiments, the touch sensor 4 may also be disposed on the surface of the electronic device at a different location than the display 3.

The following describes embodiments of the present application by taking an example in which the electronic device is a mobile phone. The mobile phone has the function of setting schedules, and can support a user to set schedule reminding on a calendar application.

Further, the application program for managing schedules may include a calendar application program, a to-do application program, and the like, and the embodiment of the present application may be applied to any application program that can manage schedules. It should be understood that managing a schedule herein may include creating a new schedule, modifying the content of the schedule, and deleting all schedule-related operations, and the scope of managing a schedule is not limited in this application.

In the embodiment of the application, the user can manually mark the new schedule as an important schedule, or manually mark the existing schedule as an important schedule.

The process of manually marking important schedules when a user creates a new schedule will be described with reference to fig. 2-1.

Fig. 2-1 is a schematic diagram of an interface for manually marking important schedules according to an embodiment of the present application, which is described by taking creating a new schedule in a calendar application as an example, it should be understood that a new schedule may be created in other schedule management applications, which is not limited in this application.

When the handset detects that the user clicks on an icon of the calendar application, the interface 10 shown in a of fig. 2-1 may be displayed, the interface 10 being a month view interface of the calendar, the month view being for displaying all dates of the entire month, in this example all dates of the entire 9 months. In the month view, the current date is highlighted by default, although the interface may also highlight other dates selected by the user, such as the user may click on a numerical icon indicating the other dates to select the date. In one example, a specified date is highlighted by highlighting the logo, such as highlighting circle 11 identified as having a diameter greater than the diameter of the digital icon. As shown in a of fig. 2-1, the current date is, in this example, 2022, 9, 10.

The user can create a new calendar on the currently highlighted date by clicking on icon 12 as shown in a of fig. 2-1, in this example, the user clicking on icon 12 creates a calendar of 2022, 9, 10 days. Of course, the user may also click on other digital icons shown in a of FIG. 2-1 to select other dates, and further click on icon 12 to create a calendar for the other dates.

In one example, after clicking on icon 12, the user enters a new calendar interface shown in b of FIG. 2-1, which allows the user to fill in details of the new calendar. In this embodiment, as shown in b of fig. 2-1, the newly created schedule interface includes a priority setting field 24, and further includes a title setting field 21, a place setting field 22, a start-stop time setting field 23, and a reminder setting field 25.

The priority setting field 24 includes a priority setting item 241, and the user sets the priority of the newly created schedule by clicking on the priority setting item 241, and enters an interface 30 shown in c of fig. 2-1, on which a priority setting card 31 is displayed, on which all settable levels such as "important", "ignore", and "none" are displayed, as shown in c of fig. 2-1. The "important" means that the schedule is an important schedule, namely, the schedule which is focused by the user, the "neglect" means that the schedule can be ignored and the user does not need to pay attention, and the "none" means that the schedule which does not need to pay attention and cannot be ignored.

For example, in an example, the interface 30 shown in c of fig. 2-1 adds a gray-scale layer to the interface shown in b of fig. 2-1, and further displays the priority setting card 31 on the upper layer of the gray-scale layer, so that the priority setting card 31 may be highlighted, making the priority setting card 31 more noticeable, and making it easier for the user to pay attention to the priority setting card 31. Of course, in other embodiments, the prioritization card 31 may also be displayed directly on the interface shown in b of FIG. 2-1.

The user can select a selection button after any level, and select the level. In one example, the priority level selection button pattern is a radio button, i.e., the user may click on a button in an unselected state, causing the button to change to a selected state, while the button that was originally in the selected state changes to an unselected state. For example, in fig. 2-1 c, the selection button corresponding to the "important" level is currently in the non-selected state, and the user clicks the button to change to the selected state, and at the same time, the selection button corresponding to the "none" level changes from the selected state to the non-selected state.

In addition, the location of the priority setting card 31 may also be located elsewhere on the interface 30. The size, style and display position of the priority setting card and the style of the selection button in the priority setting card are not limited.

In another exemplary embodiment, as shown in fig. 2-2, an interface schematic diagram of another new calendar interface provided in an embodiment of the present application is shown. The new calendar interface shown in fig. 2-2 also includes a participant card 26, which participant card 26 may include an invitee option 261 and a participant option 262, differing from the new calendar interface shown in b of fig. 2-1.

The user adds an inviter to the calendar by operating the inviter option 261, for example, when the calendar is a calendar of an online meeting, the meeting inviter is added by the inviter option.

The user may add other participants of the calendar by manipulating participant options 262. In an example, after the user adds an inviter, the attendee options may include the inviter by default.

In addition, the newly created calendar interface of the present example may also include a meeting link field 27, which may be multiplexed with the location setting field in one possible implementation, such as the user clicking on the location setting field may paste the meeting link, or may also enter the location of the calendar.

After the user selects the "important" level in the interface shown in c of fig. 2-1, jumping to the interface shown in d of fig. 2-1, as shown in d of fig. 2-1, the priority setting item 241 in the interface displays the "important" level, after the user completes other information in the new schedule interface, clicking the completion icon 40 to save the new schedule, and jumping to the interface 50 of the month view shown in e of fig. 2-1.

The user can fold the date display area, i.e., the date display area is changed from 13 shown in a of fig. 2-1 to area 51 shown in e of fig. 2-1 by sliding up the area 13 displaying the date in the month view interface shown in a of fig. 2-1, and the date display area 51 displays only the row containing the currently highlighted date, thereby increasing the area of the schedule display area 52 below the date display area.

As shown in e of fig. 2-1, the schedule display area 52 is used to display all schedules requiring reminding of the user, including holidays, throttles, and other schedules, at the currently highlighted date (this example is 2022, 9, 10). In this example, the display position of the holiday schedule is located at the top of the schedule display area 52, i.e., the display position of the holiday schedule is before the other schedules. In other embodiments, the display location of the holiday schedule may be at the bottom of the schedule display area 52, i.e., the display location of the other schedules is before the holiday schedule. It should be understood that when the number of schedules on the date is large, the schedules cannot be displayed entirely in the schedule display area 52, and schedules that are not displayed can be displayed by sliding the schedule display area 52 upward.

In the embodiment of the present application, for a schedule whose priority is important, information of the schedule is displayed in a spread in the schedule display area 52 so that the user can directly learn more information of the schedule. For non-important schedule folding display, the display area of a schedule display area is saved. In this example, as shown in e of fig. 2-1, an important schedule of "design seminar" is displayed in the card 56 in an expanded manner, and a non-important schedule of "train trip" (or referred to as a normal schedule) is displayed in the card 57 in a folded manner.

As shown in e of fig. 2-1, the important calendar displayed by the card 56 is a meeting calendar, and the calendar information displayed by the card may include a calendar title 53, a calendar start-stop time "8:00 a.m. to 9:30 a.m." meeting invitees, attendees, accounts, and priority 55.

In one possible implementation, the title of the important calendar also includes an important identifier for representing the importance of the calendar, in this example "+|! Of course, in other embodiments, the important identifier may be other symbols, which the present application does not limit. Alternatively, for online conferences, the calendar information of the expanded display may also include a "join conference" link button.

Therefore, the user can keep the important information of the schedule clear without any operation on the unfolded and displayed card, and therefore the efficiency of acquiring the detailed information of the important schedule by the user is improved.

In addition, the card 56 may further include a folding button 54 beside the schedule title, and the user may change the schedule from the unfolded display state to the folded display state by clicking the folding button 54. It is understood that only important information such as the title of the schedule, the start-stop time, etc. may be displayed in the folded display state. As shown in e of fig. 2-1, the card 57 is in a folded display state, and the displayed contents include a schedule title, a start-stop time, a place, and an expansion button 58. The user can change the schedule from the folded display state to the unfolded display state by clicking the unfolding button 58, thereby displaying more information of the "train trip" schedule, such as a seat number, etc.

For the important schedules, schedule detailed information is expanded and displayed by default in each scene. For example, as shown in f of fig. 2-1, the schedule display area 61 displays three schedule information sequentially from top to bottom, wherein the design proposal meeting is an important schedule, and detailed information of the schedule is displayed by default. The train traveling schedule and the hotel check-in schedule are non-important schedules, and information of the two schedules is displayed in a folding mode.

In one possible implementation, calendar view interface 60 may be accessed by clicking on "calendar" button 14, shown in a of FIG. 2-1.

As shown in e of fig. 2-1, "ignore" is contained in the priority card 31 as one priority of the schedule, i.e., in the present embodiment, "ignore" is incorporated from more options of the schedule details interface to the priority of the schedule.

When the user clicks on the control 611 in the calendar details interface 610 shown in fig. 3 a, the user jumps to the interface shown in fig. 3 b, and the interface shown in fig. 3 b displays more tabs 612 on the calendar details interface 610, including the share and delete options, i.e., no "ignore" option is included in the more tabs 612 in the embodiment of the present application. After clicking on the schedule titled "design meeting", e or f in fig. 2-1, the user enters the schedule detail interface 610. It can be seen that, after merging "neglect" to the priority, the user can directly set the schedule to the "neglect" level in the priority setting item displayed on the interface e or f shown in fig. 2-1, so that the path for the user to enter the "neglect" function is shortened, the operation of the user is simplified, and the user experience is improved.

The process shown in fig. 2-1 is a process of manually marking a schedule as an important schedule in creating a new schedule scene, and an existing schedule may be marked as an important schedule by a manual marking method. For example, the existing schedule may be a schedule that has been created without setting priority, or may be a schedule imported from another application.

Fig. 4 is a schematic diagram of another interface for marking important schedules according to an embodiment of the present application, in which schedule information displayed on a month view interface of a calendar is taken as an example, and a procedure for manually marking an existing schedule as an important schedule is described.

As shown in a of fig. 4, the current priority of the "design solution meeting" schedule in the unfolded display state in the calendar month view interface 100 is "none", and the user can click the button 101 (such as a pull-down menu button) to jump to the interface shown in b of fig. 4, which includes the priority menu 102, and in this example, the priority menu 102 includes three levels of "important", "ignore", "none". The gray level layer is added to the upper layer of the row where the current priority (or selected level) is located, so that the current level (or selected level) of the schedule is highlighted, as shown in b of fig. 4, and the current priority is the gray level of the row where "none" is located. The user may select a level of non-highlighting in the priority menu 102, in this embodiment the user may select an "important" level, manually mark the calendar as an important calendar, and jump to the interface shown in fig. 4 c.

As can be seen from comparing the interfaces shown in c and a of fig. 4, after marking the schedule of the "design proposal meeting" as an important schedule, the priority setting item 104 of the schedule displays the "important" level, and the title 105 of the schedule further includes an important identifier "+|! ".

The embodiment of the application also provides an interface schematic diagram for manually marking the existing schedule as an important schedule in other scenes. Fig. 5 shows an interface diagram for marking a calendar as an important calendar on a calendar detail page.

In one possible implementation, a user clicking on calendar card 56 in e of FIG. 2-1 may jump to calendar details interface 200 shown in a of FIG. 5, where priority settings 201 show that the current priority is "none". The user may select other priorities by clicking on button 202. After clicking the button 202, the user jumps to the interface shown in b of fig. 5, and the interface adds a gray level layer on the upper layer of the schedule detail interface 200, and further displays the priority setting card 203 on the upper layer of the gray level layer, so that the priority setting card 203 can be more conspicuous. The priority setting card 203 is the same as the priority setting card 31 in the interface shown in c of fig. 2-1, and will not be described here again. In this embodiment, the user clicks the button 204 corresponding to the "important" level in the priority setting card 203, jumps to the schedule detail interface shown in c of fig. 5, where the priority item 205 in the interface displays that the current level is "important", and the schedule title 206 contains an important identifier "+|! ".

Referring to fig. 6, there is shown a schematic diagram of an interface for manually marking an important schedule according to another embodiment of the present application, in which a schedule shortcut interface is used as an example to illustrate a process of manually marking an important schedule.

In one possible implementation, a user may enter the interface shown in b of FIG. 6 by pressing the calendar display card 301 in a of FIG. 6 long, which displays a popup window 302 for displaying calendar information, such as calendar titles, start-stop times, priority options, and the like. The priority options include the current level of the schedule and button 303, the user clicks the button 303 and jumps to the interface shown in c of fig. 6, the interface further includes a priority menu 304 at the upper layer of the popup window 302, the user clicks the "important" option in the priority menu 304 and jumps to the interface shown in d of fig. 6, the priority item 306 of the schedule displayed in the popup window 302 of the interface is "important", and the schedule title 305 contains an important identifier "correspondingto-! ".

The priority menu 304 in this embodiment is the same as the priority menu 102 shown in b of fig. 4, and will not be described here.

In addition, as shown in interfaces b, c, and d of fig. 6, a card 307 is further included below the pop-up window 302, and the card 307 includes "share" and "delete" buttons. When the user clicks the "share" button 308, the user jumps to the share preview interface 401 shown in e of fig. 6, where the interface includes a share button 403, and further, the user clicks the share button 403 to forward the schedule information to other people. Further, if the user clicks a "delete" button in the card 307, the information of the schedule is deleted from the calendar application.

When the user does not use the important schedule setting function, the application program of schedule management prompts the user to set a schedule important to the user as an important schedule. Fig. 7 shows an interface diagram of a new function guide for setting an important schedule according to an embodiment of the present application.

For example, as shown in fig. 7 a, a card 70 is included on the month view interface, which is in a folded display state, i.e., only part of the information of the schedule, such as a title, start-stop time, and place, is displayed.

In one scenario, if the user clicks the expand button 701 in the card 70, the interface shown in b of fig. 7 is skipped, where the card 70 is in an expanded display state, and in this state, a prompt pop-up window 72 may be displayed, where the prompt pop-up window 72 is used to guide the user to use a function of manually marking a schedule as an important schedule. In one example, the text information in the reminder pop-up window 72 may include "mark important schedules, view more schedule information". In one example, the prompt pop-up window 72 may be located at an upper level of the interface 90, and further, the prompt pop-up window 72 disappears when the user clicks anywhere on the interface other than the prompt pop-up window 72.

In this example, the prompt pop-up window 72 is located above the priority item 73 so that the user can intuitively learn to mark an important schedule by operating the priority item 73.

In another scenario, if the user presses the card 70 in a of fig. 7 for a long time, the user jumps to the shortcut interface 80 shown in c of fig. 7, the interface including a schedule card 81, the schedule card 81 including a prompt pop-up window 83 above the priority item 82, the prompt pop-up window 83 being for displaying a function for guiding the user to mark important schedules using manual.

In yet another scenario, if the user clicks (clicks) on card 70 in a of fig. 7, jumps to the schedule details interface 90 shown in d of fig. 7, which includes a card 91, where card 91 is used to display a priority setting item, a reminder tab 92 is displayed above card 91, and further, reminder tab 92 may be located at an upper layer of interface 90.

Fig. 7 b, c, d respectively show interface diagrams for displaying new function prompt popups in different scenes, the prompt popups in different scenes have the same effect, that is, users are guided to use a schedule of which the manual mark is important, and the position, size and style of the prompt popups and the displayed content can be adjusted according to different display scenes, which is not limited in the application.

In addition, in one possible implementation, the prompt pop-up window may be displayed only on the interface that is touched first, and the prompt is not repeated in other scenarios, for example, in response to the user operation, the first entry is the scenario shown in b of fig. 7, and then the prompt pop-up window 72 is displayed on the interface shown in b of fig. 7. When entering the scenario shown in fig. 7 c and d, the prompt pop-up window is no longer displayed.

In one possible implementation, a participant meeting a certain condition (e.g., the frequency of the occurrence of the participant in the important schedule is greater than a preset threshold) may be selected from all the participants in the schedule as an important participant to be recommended to the user, or the user may also automatically add the important participant. After the important participants are available, the schedules of the participants including the important participants can be set as important schedules, manual marking of users is not needed, and user experience is further improved.

Referring to fig. 8, a rule diagram for determining important participants is shown.

In one possible implementation, as shown in fig. 8, the other participants are all participants who have appeared in the calendar, including Y other participants in this example. The participants meeting the preset condition are selected from the Y other participants as recommenders (i.e., participants that the user may be interested in), for example, the number of recommenders may be X in this example, where X < Y. Furthermore, a maximum value of X may be defined, such as X.ltoreq.5, i.e. a maximum of 5 participants are recommended to the user. Further, the user may select the participants in the recommender list as important participants. Of course, the user may also directly select a participant among other participants as an important participant.

In the embodiment of the application, the participants in the recommender list are updated according to the operation of adding or deleting important participants by the user.

In one embodiment of the application, after the user uses the function of marking the important schedules, the application program for managing the schedules counts all the participants appearing in the important schedules, selects the participants meeting the preset conditions as the recommenders, and prompts the user to add the important participants when the recommenders are not empty.

In other embodiments of the present application, the user may be prompted again to add a new important participant after the calendar-management application detects that all of the participants in the recommender list are updated.

Referring to fig. 9, an interface schematic diagram of a prompt box for prompting a user to add important participants is shown.

In an example, as shown in fig. 9, a prompt box 702 is displayed on a month view interface 701 of the calendar application, and the prompt box 702 is used for guiding the user to use the important participant function, in other words, prompting the user to add important participants, so as to further improve the user experience. Further, an important calendar may be automatically marked according to important participants added by the user.

In an example, as shown in fig. 9, the prompt 702 may be located between the date display area 705 and the schedule display area 706, and in this example, the prompt 702 may be located on the same layer as the date display area and the schedule display area. Of course, in other examples, the prompt box 702 may also be located at an upper layer of the date display area and the schedule display area, for example, the prompt box 702 is a pop-up window. For example, as shown in fig. 9, the prompt box 702 includes text information for prompting the user, such as "recommend important participants for you, intelligently mark schedules according to important participants for you, and not miss important things", and of course, the text information displayed in the prompt box 702 may be other content, which is not limited in this application. In addition, the prompt box 702 also includes an "add immediately" button 703 and a close button 704. After clicking the "Add immediately" button 703, the user may jump to the interface to add important participants. After the user clicks the close button 704, the prompt box 702 is closed, i.e., the prompt box 702 disappears.

The process of adding important participants will be described below in connection with fig. 10.

As shown in fig. 10 a, after the user clicks the more button 800, more tabs 801 are displayed, and the more tabs 801 include a "set" item 802. Further, after clicking on the "settings" item 802, the user jumps to the interface 803 shown in b of fig. 10, which includes an important participant settings card 804, and the user clicks a button 805 in the important participant settings card 804 to jump to the important participant interface shown in c of fig. 10.

As shown in fig. 10 c, the important participant interface includes a recommender list 806, and the recommender list 806 includes recommended participant settings items 807, e.g., each participant setting item 807 includes information about the participant (e.g., name and account, etc.) and an "add" button 808. After the user clicks the "Add" button 808, the participant is added to the list of important participants. For example, in this example, after clicking the "add" button in the participant item corresponding to the participants "Xiaomin" and "Long", the user jumps to the interface 809 shown in d of fig. 10.

As shown in fig. 10 d, the interface 809 includes an important participant list 810, which may be located above the recommender list 813. The important participant list 810 includes user added participants "Xiaomin" and "Long", and each important participant setting item 811 includes participant information (e.g., name and account, etc.) and a "remove" button 812. The user may click on the "remove" button 812 may delete the added important participant from the important participant list.

In one embodiment of the present application, the number of important participants is not limited, i.e. the number of participants in the list of important participants is not limited.

As shown in a of fig. 11, when the number of important participants in the important participant list is large, so that the window 901 displaying the important participant list cannot display all the important participants, in this case, a "more" button 902 is displayed in the window 901, and clicking on the "more" button 902 jumps to the interface shown in b of fig. 11, in which the important participant list is displayed using the window 903 having a larger display area. It will be appreciated that the user may display the important participant following the important participant "Wind" in the figure by sliding up and down the page displayed in window 903 to cause the important participant displayed in window 903 to change, for example, by sliding up the list of important participants in window 903.

Further, as shown in fig. 11 b, the bottom of the window 903 includes a "pack" button 904, and after the user clicks the "pack" button 904, the user jumps from the interface shown in fig. 11 b to the interface shown in fig. 11 a, that is, after clicking the "pack" button 904, the window 903 displaying the important participant becomes the window 901 having a smaller display area.

In one application scenario, the important participant that the user wants to add is not included in the recommender list, in which case other participants may be selected as important participants by "add other participants". Referring to fig. 12, another interface schematic for adding important participants is shown, which is provided in an embodiment of the present application.

As shown in fig. 12 a, the important participant interface 1000 includes an "add other participant" button 1002, in this example, button 1002 being located below the recommender list 1001. In other embodiments of the present application, button 1002 may be located at other positions, which is not limited in this application. After clicking the button 1002, the user jumps to the interface 1003 shown in fig. 12 b for selecting a participant.

As shown in fig. 12 b, the interface 1003 is used to display a complete participant list, and each participant option in the list includes information of the participant and a selection button 1004, and the user can click on the selection button 1004 to select the participant. In this example, after clicking the selection button 1004 corresponding to the participant "Dannle", the user jumps to the interface shown in c of fig. 12, where the selection button 1004 corresponding to the participant "Dannle" changes to the selected state, in this example, "v" indicates that the selection has been made, and of course, in other embodiments, "o" may also be used to indicate that the selection has been made.

As shown in c of fig. 12, the select participant list interface 1003 includes a button 1006, a close button 1007, and a search box 1008. Button 1006 is a save button that indicates that the user has completed, in this example, after selecting participant "Dannle" as the important participant, clicking on button 1006 saves the current selection, i.e., saves the result of "Dannle" as the important participant. After clicking the button 1006 shown in fig. 12 c, the user jumps to the interface shown in fig. 12 d. If the user clicks the close button 1007, the interface 1003 is closed and the user can return to the interface shown in a of fig. 12. If there are many participants in the overall participant list, the user may input at least part of the names or initials of the participants to be searched in the search box 1008, i.e. the corresponding participants may be searched. In addition, the bottom of the interface shown in c of fig. 12 also includes a "full-select" button, and after the user clicks the "full-select" button, all the participants in the all-participant list are in the selected state.

As shown in d of fig. 12, the important participant interface 1009 includes a window 1010 for displaying an important participant, the window 1010 for displaying an information item of the important participant, and an operation button such as a "remove" button, as in the interface shown in d of fig. 10. The user clicking on the "remove" button may delete the participant from the list of important participants.

Furthermore, in an exemplary embodiment of the present application, the participants are maintained in the participant's account dimension, and the accounts of the same participant in different applications may be considered as different participants, as shown in fig. 12 b, including two participants whose names are "alisalalee", but whose accounts are different, maintained as two different participants, namely, two participants corresponding to 1005 and 1012 in fig. 12 b.

In another application scenario, where the existing calendar includes participants, such as a conference calendar, the user may directly set the participants in the calendar as important participants.

FIG. 13 is a schematic illustration of yet another interface for adding important participants provided by embodiments of the present application.

The interface shown in a of FIG. 13 is a calendar details interface 1100 that includes a participant card 1101, all of the participants in the calendar being included in participant card 1101, and further, the card includes a button 1102. The user clicks on button 1102 and jumps to participant interface 1104 shown in fig. 13 b.

As shown in b of fig. 13, the participant interface 1104 includes information of all participants of the schedule. In this example, the calendar is an online meeting calendar, which typically includes one inviter, others, to participate. For example, an inviter refers to a person who creates an online meeting that may invite other people to participate in the online meeting with whom the person is creating. In an embodiment of the present application, the inviter may default to an important participant and include an important identifier in the participant item, for example, as shown in b of fig. 13, the inviter item 1106 includes information such as name "Xiaomin" and account of the inviter, 11061 is shown as an important identifier, and the important identifier is "VIP" in this example.

As shown in b of fig. 13, the area shown by 1107 is other participants of the schedule, and the user can slide up and down on the area to update the participants displayed in the area, for example, the user slides up, then the currently displayed participant in the area will follow the up slide, and at the same time, the participants below the participant "Long" are displayed. The top of the interface 1104 shown in b of fig. 13 also includes a back button 1105, which the user clicks to return to the interface shown in a of fig. 13.

In one embodiment of the present application, the bottom of the participant interface 1104 shown in fig. 13 b also includes a "edit important participant" button 1108, and after clicking on the button 1108, the user jumps to the select participant interface 1112 shown in fig. 13 c.

As shown in fig. 13 c, the select participant interface 1112 includes a region 1114 for displaying the inviter and a region 1115 for displaying the other participants, each participant display item in regions 1114 and 1115 including a select button 1113.

In the embodiment of the present application, the inviter defaults to an important participant, and therefore, the selection button 1113 in the inviter display item defaults to a selected state, in this example, the selection button 1113 in the inviter 'Xiaomin' display item defaults to a selected state. Further, the user selects the other participant "Lee" as an important participant, and the selection button 1113 of the participant display item becomes a selected state. In an example, the selection button may be "o", the selected state may be "v", and of course, in other embodiments, the selected state may also be given other symbols, and similarly, the selection button may also be given other patterns, which is not limited in this application.

As shown in c of fig. 13, an area 1109 is further included above the inviter display area, the area 1109 including a finish button 1110 and a close button 1111, and may also include the number of important participants that have been selected. After clicking the finish button 1110, the user jumps to the interface shown in d of fig. 13, clicks the close button 1111, and returns to the interface shown in b of fig. 13.

In contrast to the schedule details page interface shown in a of fig. 13, the interface shown in d of fig. 13 is a schedule details page interface including an important participant display item 1206 in addition to the participant display item 1205. Participant display item 1205 is used to display all participants of the calendar. The important participant display item 1206 is used to display important participants involved in the schedule, such as, in this example, important participants are "Xiaomin" and "Lee".

Furthermore, the participant display item 1205 also includes a button 1209, and the user clicks on the button 1209 to jump to the participant interface shown as e in fig. 13, including the inviter display area 1201 and other participant display areas. The inviter display area 1201 is for displaying invitees related to the schedule. The other participant display area is used to display the participants other than the inviter involved in the schedule. In one embodiment of the present application, the inviter display item by default includes an important identifier 1203, such as "VIP", and the display item 1202 of the other participant "Lee" selected by the user also includes the important identifier 1203. In addition, in the interface shown in fig. 13 e, a back button 1204 is further included above the inviter display area, and after the user clicks the back button 1204, the user jumps to the interface shown in fig. 13 d, i.e., the date detail page interface.

After the user edits the important participants, the application program for managing the schedules updates the important participant list, and when the important participants are detected to be contained in the non-important schedule participants, the non-important schedule can be automatically marked as the important schedule, and the process does not need manual operation of the user, so that the user experience is further improved. For example, the interface shown in d of FIG. 13 includes an important identifier in calendar title 1208, such as "+|! "and the priority displayed in the priority option 1207 is" important ".

Similarly, other view interfaces are also included in other view interfaces of the schedule, for example, a month view interface 1301 shown in fig. 14, identifying that an important participant "Lee" is included in the participants of the non-important schedule of the "design study meeting", automatically marking the non-important schedule as an important schedule, including an important identifier in a schedule title 1302 in the interface, as shown in fig. 14, and a priority display item displaying that the priority of the schedule is "important". In this embodiment, after the automatic marking is an important schedule, the change items of other views are not repeated.

In addition, the content of the foregoing important schedules is also applicable to schedules that are automatically marked as important, and will not be described herein.

Fig. 11 to fig. 13 are diagrams illustrating a procedure of adding an important participant according to an embodiment of the present application, and conversely, an important participant added to an important participant list may be deleted.

Referring to fig. 15, an interface schematic diagram of deleting important participants is shown.

As shown in a of fig. 15, the important participant interface 1400 includes an important participant list in which each participant display item includes a "remove" button 1401 from which the user can delete the participant from the important participant list by clicking the "remove" button 1401.

In one possible implementation, after clicking the "remove" button 1401 shown in a of fig. 15, the user jumps to the interface 1402 shown in b of fig. 15, which adds a gray-scale layer on top of the interface 1400 shown in a of fig. 15, and further, displays a prompt window 1403 on top of the gray-scale layer, so that the prompt window 1403 may be highlighted, thereby guiding the user to view the content in the prompt box 1403.

As shown in b of fig. 15, the prompt window 1403 may include a schedule status change that may cause inclusion of an important participant after removal of the participant, and question prompt information that may be added again, and a "cancel" button, a "remove" button 1404. The user clicks the "cancel" button and returns to the interface shown in a of fig. 15, and the user clicks the "remove" button and jumps to the interface shown in c of fig. 15. In this example, only one participant in the list of important participants becomes empty when the user deletes the participant. Therefore, as shown in c of fig. 15, the important participant list is not included in the important participant interface 1405, and only the recommender list 1406 is displayed.

In one application scenario, no participants are included in the recommender list, i.e. the recommender list is empty. As shown in fig. 16, in such a scenario, when the user clicks a button 1601 in the important participant setting item in the interface 1600 shown in a of fig. 16, the recommender list is not displayed. The interface 1600 shown in a of fig. 16 is the same as the setting items contained in the interface 803 shown in b of fig. 10, and the manner of entering the interface is also the same, and will not be described here again.

In one case, all schedules in the application for managing schedules are not important schedules, i.e., do not include important schedules, in which case the user clicks the button 1601 to jump to the interface 1603 shown in b of fig. 16, which includes displaying text prompt information 1604 of important participants for prompting the addition of important participant functions and addition modes. In addition, the interface includes a "know more" button 1605, and after the user clicks the "know more" button 1605, the user can jump to an interface that details the "important participant" function, for example, a function introduction page for "important participant" in a machine skill application.

In another case, the application for managing schedules includes an important schedule, in which case, the user clicks the button 1601 and jumps to an interface 1606 shown in c of fig. 16, and the interface includes a text prompt 1607 concerning important participants, which is used to prompt the user to add important participants, and a prompt containing a schedule of important participants defaulting to an important schedule. The interface shown in fig. 16 c also includes an "add other participants" button 1608, and after the user clicks the "add other participants" button 1608, the user can jump to the interface shown in fig. 12 b. As with the interface shown in b of fig. 16, the interface shown in c of fig. 16 also includes a "know more" button.

It should be appreciated that in this embodiment, the user's operations of adding and deleting important participants may affect the participants in the recommender list.

In addition, as shown in a of fig. 17, the important participant interface 1500 further includes a detail button 1501, and after the user clicks the detail button 1501, the user jumps to an interface 1502 shown in b of fig. 17, where a gray layer is added to the interface shown in a of fig. 17, and a prompt window 1503 is further displayed on the gray layer, where the prompt window 1503 is used to display information about functions of the important participant, and the prompt window further includes a "know more" button 1504. The interface displayed after the user clicks the "know more" button 1504 is the same as the interface displayed after clicking the "know more" button in fig. 16 b and c, and will not be described here.

In order to facilitate the user to view the information of the important schedules, only the important schedules can be displayed through the setting. Referring to fig. 18, an interface schematic diagram for screening important schedules according to an embodiment of the present application is shown.

As shown in a of fig. 18, the month view interface 1700 of the calendar application includes a button 1701, and after the user clicks the button 1701, the user jumps to the interface shown in b of fig. 18, and a setting item window 1702 including a "display only important" setting item 1703 is displayed at an upper layer of the month view interface 1700, and after the user clicks the "display only important" setting item 1703, the user jumps to the interface 1704 shown in c of fig. 18.

The interface 1700 shown in a of fig. 18 includes an important schedule and a non-important schedule, such as a schedule of a train trip, etc., whereas the interface 1704 shown in c of fig. 18 includes only an important schedule, and does not display a non-important schedule. In this embodiment, schedules of "mid-autumn festival" and "teacher festival" are displayed by default. Of course, in other embodiments, it may be configured that only the important options are selected to be displayed, then the holiday schedule and the non-important schedule are not displayed, and only the important schedule is displayed, which is not limited in this application.

In addition, the bottom of the interface shown in c of fig. 18 further includes a prompt 1705 for "currently only displaying important schedules" for reminding the user that the current interface does not display non-important schedules. In other embodiments of the present application, the prompt 1705 of "currently only displaying important schedules" may also be in other forms, for example, an identifier that indicates that the current screen is in a screening state may also be displayed in a blank space of the current interface or in an upper layer of the interface. The present application does not limit the identifier representing the screening status.

In another embodiment of the present application, the user may also resume displaying the entire calendar. For example, as shown in c of fig. 18, after the user clicks the button 1701, the interface shown in d of fig. 18 is skipped to include the setting item window 1707, and is different from the setting item window 1702 shown in b of fig. 18 in that the setting item window 1707 includes the "all schedule" setting item 1706, and in that the setting item window 1702 is the "display only important" setting item 1703. After clicking the "all schedules" setting item 1706, the user jumps to the interface shown in a of fig. 18, i.e., displays all schedules.

In one possible implementation, the content displayed on the settings in the settings window 1702, 1707 may be updated according to user operations, e.g., displaying all schedules for a certain date in the current view, then the settings in the settings window are "display only important". And after the user clicks on the "display only important" setting item, the setting item in the setting item window becomes "all schedules".

In another possible implementation, the content of the setting item display in the setting item windows 1702 and 1707 is fixed, e.g., whether only important schedules are displayed in the current view or not, the setting item window will display "only important/all schedules". The content style of the setting item displayed by the setting item window is not limited in the application.

After the user sets to display only the important schedules, the important schedules are synchronously updated in other scenes displaying the schedules.

Referring to fig. 19, there is shown an interface schematic of a calendar view provided in an embodiment of the present application, where a of fig. 19 is a calendar view interface 1801, and the interface displays all calendars, including, for example, an important calendar 1802 and non-important calendars 1803, 1804. After the user selects to display only the important schedule, the interface becomes the interface shown in b of fig. 19.

As shown in b of fig. 19, the schedule view interface 1805 displays only important schedules at respective dates, and does not display non-important schedules. For example, an important schedule of 9 months 10 is displayed in the area 1806, and an important schedule of 9 months 11 days is displayed in the area 1807. In addition, a prompt 1808 of "currently only displaying important schedules" is also included at the bottom of the interface.

Referring to fig. 20, an interface schematic diagram of a calendar desktop card according to an embodiment of the present application is shown.

As shown in fig. 20 a, the desktop 1900 includes a calendar card 1901, the calendar card 1901 including a schedule at the current date (9 months 10). If the current date includes a plurality of schedules, all schedules under the date cannot be displayed due to the limited display area of the calendar card 1901, for example, important schedules may be displayed preferentially, and non-important schedules may be displayed after being ordered according to the start-stop time.

For example, as shown in a of fig. 20, in this example, the calendar card 1901 includes an important schedule 1902 and a non-important schedule 1903, and at the same time, the bottom of the calendar card 1901 also includes a prompt message 1904 of "also other 2 schedules" to remind the user that there is a schedule that is not displayed on the current day.

When the user selects to display only the important schedule, the calendar card 1901 changes to the display interface shown in b of fig. 20, and as shown in b of fig. 20, the calendar card 1901 displays only the important schedule 1902 and does not display the non-important schedule. In addition, the bottom of calendar card 1901 may also display a reminder 1905 of "no other important calendar today".

In the embodiment of the application, the desktop is called a desktop application, a home screen, or a desktop, for example, in an android system, the desktop is also called a desktop Launcher (desktop). For ease of description, it is referred to herein generally as a desktop.

In another embodiment of the present application, the application managing the calendar also supports adding a single calendar card, otherwise known as a calendar card, on the desktop.

In one scenario, the user may add a calendar card for a new important calendar to the desktop as it is created. Referring to fig. 21, an interface schematic diagram of adding a calendar card according to an embodiment of the present application is shown.

In one possible implementation, the function of adding the schedule card on the desktop may be provided only for the important schedules, that is, only the display interface of the important schedules has a function entry for adding the desktop card, and the interface of the non-important schedules has no function entry for adding the desktop card. Of course, in other embodiments of the present application, a calendar card of the calendar may be added on the desktop for all calendars, which is not limited in this application.

As shown in a of fig. 21, after setting "important" in the priority setting item 2002 in the newly created schedule interface 2001, the user jumps to the interface 2003 shown in b of fig. 21, and the interface 2003 further includes an "add desktop card" setting item 2004 including a setting button 2005, the setting button 2005 shown in b of fig. 21 being in an unopened state, and the user clicking the setting button 2005 and then turning into an on state, the setting button 2005 shown in c of fig. 21 being in an on state.

After clicking the button 2006 shown in c in fig. 21, the user jumps to the interface shown in d in fig. 21, which includes the important schedule display area 2008, and at the same time, adds a schedule card of the important schedule to the desktop. In addition, a prompt 2009 of "schedule has been added to the desktop" is also included at the bottom of the interface. In an exemplary embodiment, the prompt automatically disappears after a predetermined period of time is displayed. The interface shown in d of fig. 21 also includes information 2007 indicating the corresponding date of the schedule, in this example, a 9 month 9 day schedule is created at 2022, 9 month 8, i.e., a daily schedule is created today.

As shown in e of fig. 21, the schedule card 2010 is a new schedule card for an important schedule "design solution meeting". The schedule card 2010 includes a number of days 2011, in this example, 1 day from the date of execution of the schedule, and further includes an area 2012 for displaying the date of execution of the schedule, in this example, 2022, 9 days.

Referring to fig. 22, a schematic diagram of a calculation rule of a countdown day and a positive day provided in an embodiment of the present application is shown. In the embodiment of the present application, the countdown day refers to the remaining days when the current date reaches the execution date of the schedule.

For example, as shown in fig. 22, in the present example, the schedule execution date is 2022, 9 months, 9 days, the current date is 2022, 9 months, 8 days, and the current date is not the schedule execution date, so the 9 months, 8 days show the reciprocal days from the schedule execution date displayed on the schedule card. In an exemplary embodiment, the "1 day after" is a wedding commemorative day displayed on the calendar card 2013 displayed on 9 months and 8 days, and the execution date of the calendar, i.e., 2022, 9 months and 9 days, is displayed.

When the current date is 2022, 9, the current date is the date of execution of the schedule, and in an exemplary embodiment, the calendar card 2014 displayed on 2022, 9, no longer displays the reciprocal days, but directly displays "wedding commemorative day" and the execution date 2022, 9 of the schedule.

The current date is 2022, 9, 10 days, and the current date has exceeded the schedule execution date. In an exemplary embodiment, the calendar card 2015 displayed on day 2022, month 9 and 10 may display that "1 day ago" is a wedding commemorative day, and may also display the execution date of the calendar, i.e., day 2022, month 9 and 10. The content displayed on the schedule card can be adjusted according to actual requirements, and the application is not limited to the content.

In addition, the calendar card 2010 shown in e of fig. 21 is only one specific example, and other types and sizes of calendar cards may be included. As shown in fig. 23, which is a schematic diagram of the sizes of three possible calendar cards, the size of the calendar card 2016 is the same as the size of the calendar card 2010 shown in fig. 21 e, the size of the calendar card 2017 is twice the size of the calendar card 2016, and the size of the calendar card 2018 is half the size of the calendar card 2016. Of course, other sized calendar cards may be included in other embodiments of the present application, which is not limited in this regard.

The process of adding a calendar card to a desktop during a new calendar has been described above in connection with fig. 21. In other embodiments of the present application, calendar cards may also be added to the desktop for existing calendars (e.g., created calendars, or calendars imported from other applications).

Referring to fig. 24, another interface schematic for adding a calendar card according to an embodiment of the present application is shown.

As shown in a of fig. 24, the schedule details interface 2101 is detailed information of an important schedule "design proposal meeting", which includes a desktop card setting item 2102, the desktop card setting item 2102 including an "add" button, and a user can add a schedule card of the important schedule on the desktop by clicking the "add" button.

In one case, the important calendar has not added a calendar card, and in this case, the user clicks the "add" button shown in a of fig. 24 and jumps to the desktop interface shown in b of fig. 24. As shown in b of fig. 24, the desktop interface includes a calendar card 2103 of an important calendar "design proposal meeting", and the calendar card 2103 displays the same content as the calendar card shown in fig. 22, and will not be described again here.

In another case, the important calendar has added a calendar card, in which case the user jumps to interface 2104 shown in c of fig. 24 after clicking the "add" button shown in a of fig. 24. As shown in c of fig. 24, the interface is formed by adding a gray-scale layer to the interface shown in a of fig. 24, and further, a prompt window 2105 is displayed on the gray-scale layer. The prompt window 2105 includes a prompt to the user that the calendar has added a desktop card.

For example, in one example, the text information displayed by the prompt window 2105 may be "do not add repeatedly" a current calendar already has a desktop card? "in addition, the prompt window 2105 also includes a" cancel "button and a" ok "button. If the user clicks the cancel button, the process of adding a desktop card to the calendar is not performed. If the user clicks the 'ok' button, the process of adding the desktop card to the schedule is continuously executed, in this case, at least two corresponding schedule cards of the schedule are provided on the desktop, and the content displayed by the at least two schedule cards is the same.

The desktop cards added during newly creating the schedule or the desktop cards added to the existing schedule are desktop cards corresponding to the existing schedule and then added. In another embodiment of the present application, a blank schedule card may be added first, and then, a schedule displayed on the blank schedule card may be selected.

Referring to fig. 25, another interface schematic for adding a calendar card according to an embodiment of the present application is shown.

In one possible implementation, as shown in a of fig. 25, the user may perform a two-finger pinch operation on the desktop 2200, and enter the interface shown in b of fig. 25, which is a desktop editing interface, where an upper area of the interface displays a desktop page 2201 that can be edited, and the currently displayed desktop page may be replaced by sliding the desktop page left and right. The bottom area of the interface displays operational options such as wallpaper, calendar card 2202, switching effects, desktop settings, etc.

After clicking on the calendar card 2202, the user jumps to the interface shown in c of fig. 25, which is a calendar card interface, the interface includes a region 2203 for displaying the style of the calendar card, for example, in this example, the style of the calendar card 2204 is currently displayed, and the currently displayed style of the calendar card can be replaced by sliding the region left and right. In addition, an "Add to desktop" button 2205 is also included at the bottom of the calendar card interface. After clicking the "Add to desktop" button 2205, the user jumps to the interface shown in FIG. 25 d.

After the user clicks the "add to desktop" button 2205, as shown in d of fig. 25, a calendar card 2206 added by the user is displayed on the desktop interface, and the calendar card 2206 includes a button 2207 for adding a calendar, and after the user clicks the button 2207, the user jumps to the interface for selecting a calendar.

In an exemplary embodiment, the interface for selecting a schedule includes three pages, namely "holiday", "schedule", "birthday", one of which can be selected arbitrarily by the user and any one of which is selected to be added to the schedule card. As shown in e of fig. 25, the "schedule" page includes a plurality of schedules on a plurality of dates, for example, in this example, the "schedule" page includes 3 schedules of 9 months and 9 days, and 2 schedules of 9 months and 10 days. The user can select one of the schedules at will and add the selected schedule to the schedule card on the desktop. Each calendar item includes a selection button that may include two display states, a selected state and a non-selected state. In one example, button 2209 represents a selected state and button 2210 represents a non-selected state.

In one example, as shown in fig. 26 a, a diagram of a "holiday" page, and fig. 26 b, a diagram of a "birthday" page. Similar to the "calendar" page, as shown in fig. 26 a, the "holiday" page 2301 includes a plurality of holiday options 2302, each of which includes a selection button. As shown in b of fig. 26, the "birthday" page 2303 includes a plurality of birthday options 2304, each of which includes a selection button, which is not described in detail herein.

In this example, after the user selects the schedule of the "design solution seminar", the user jumps to the interface shown in f of fig. 25, and the schedule card 2211 shown in the interface adds the information of the schedule selected to be added by the user, compared with the blank card 2206 shown in d of fig. 25, wherein the schedule card 2211 is the same as the schedule information contained in the schedule card shown in fig. 22, and the details are not repeated here.

According to the process of adding the schedule card on the desktop, the user can add the important schedule into the schedule card on the desktop, so that the user does not need to open an application program for managing the schedule, and directly sees the reciprocal days or the positive days of the schedule on the desktop, the operation of checking the important schedule by the user is reduced, the efficiency of paying attention to the important schedule by the user is further improved, and the user is prevented from missing the important schedule.

In another embodiment of the present application, the user may also edit or remove calendar cards that have been added to the desktop. In an exemplary embodiment, a user pressing a calendar card on a desktop for a long time may edit or remove the calendar card.

Referring to fig. 27, an interface schematic diagram of an operation schedule card according to an embodiment of the present application is shown.

As shown in a of fig. 27, the desktop interface includes a calendar card 2401, and the user long presses the calendar card 2401 to the interface shown in b of fig. 27, which also includes an operations tab 2402 below the calendar card 2401, which operations tab 2402 includes editing and removal in one example. After clicking "remove", the user jumps to the interface shown in c of fig. 27, which is the desktop interface after deleting the calendar card 2401.

In another possible implementation manner, the user may edit the schedule in the schedule card 2401 by clicking the "edit" in the operation tab 2402, for example, change the schedule information displayed by the schedule card, for example, add the schedule of the "design solution seminar" in the schedule card 2401 in the original state, and make the schedule card display the information of another schedule through the "edit" operation, which is not described herein.

Therefore, according to the scheme provided by the embodiment, aiming at the schedule card added to the desktop, a user can directly operate, such as editing the schedule in the schedule card, or removing the schedule card, so that the user does not need to enter an application program for managing the schedule to operate, the operation complexity of the user is reduced, and the user experience is improved.

In still another embodiment of the present application, after a user modifies or deletes a schedule in an application program for managing a schedule, contents in a schedule card corresponding to the schedule are updated synchronously, for example, after the user deletes the schedule, the schedule card corresponding to the schedule may be changed into a blank card, or the schedule card displaying the schedule may be deleted directly. For another example, after the user modifies the content in the schedule, the corresponding content in the schedule card corresponding to the schedule is updated synchronously.

For example, if the user deletes the "design seminar" calendar of 2022, 9 in the calendar application, the calendar card 2401 in fig. 27 a becomes a blank card in one example, and the user can add other calendars in this calendar card 2401.

In another example, after deleting the "design seminar" calendar of 2022, 9 in the calendar application, the calendar card 2401 in a of fig. 27 is synchronously deleted.

Therefore, according to the scheme provided by the embodiment, after the user operates the schedule in the application program for managing the schedule, the schedule card corresponding to the schedule is synchronously updated, namely, the schedule in the application for managing the schedule and the content in the schedule card are automatically synchronized, so that manual operation of the user is not needed, and user experience is improved.

From the foregoing description of the embodiments, it will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of functional modules is illustrated, and in practical application, the above-described functional allocation may be implemented by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to implement all or part of the functions described above. The specific working processes of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which are not described herein.

In the several embodiments provided in this embodiment, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical functional division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown 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 units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present embodiment may be integrated in one processing unit, each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present embodiment may be essentially or a part contributing to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to perform all or part of the steps of the method described in the respective embodiments. And the aforementioned storage medium includes: flash memory, removable hard disk, read-only memory, random access memory, magnetic or optical disk, and the like.

The foregoing is merely a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A schedule management method, applied to an electronic device, the method comprising:

displaying a first interface, wherein the first interface comprises a first day Cheng Kapian, the first calendar card comprises schedule information and schedule priority, and the schedule priority is none;

and in response to the operation that the schedule priority is important, displaying a second interface, wherein the second interface comprises a second schedule card, the schedule priority in the second schedule card is important, and the second schedule card contains more schedule information than the first schedule card.

2. The method of claim 1, wherein the calendar information comprises a calendar title; the second calendar card further includes an important identifier, the important identifier being located before the calendar title.

3. The method of claim 1 or 2, wherein the calendar priority comprises none, significant, and ignore.

4. A method according to any one of claims 1 to 3, wherein said displaying a second interface in response to selecting said calendar priority as important comprises:

responding to the operation of clicking the schedule priority on the first schedule card, and displaying a priority setting option popup window on the first interface, wherein the priority setting option popup window comprises a no-level option, an importance level option and an neglect option;

and responding to the operation of selecting the important level option on the priority setting option popup window, and displaying the second interface.

5. A method according to any one of claims 1 to 3, wherein prior to said displaying the first interface, the method further comprises:

displaying a third interface, wherein the third interface comprises a first button, and the first button is used for creating a new schedule;

in response to an operation of the first button, displaying a first interface, the first interface further comprising a save button;

the responding to the operation that the schedule priority is selected to be important displays a second interface, comprising:

Responding to the operation of schedule priority on the first interface, and displaying a priority setting option popup window on the first interface, wherein the priority setting option popup window comprises a no-level option, an important level option and an neglect option;

responding to the operation of selecting an important level option on the priority setting option popup window, displaying a first interface, wherein the schedule priority in the first interface is updated to be important;

and displaying the second interface in response to the operation of the save button.

6. The method of any one of claims 1 to 5, wherein the calendar information includes a participant, the method further comprising:

when the schedule priority is detected to be an important schedule, acquiring participants in all schedules containing the participants;

selecting a preset number of participants meeting preset conditions from the participants of all schedules to determine the participants as recommended participants, wherein the preset conditions comprise that the frequency of participating in important schedules is greater than a preset threshold;

a recommender list is generated, the recommender list comprising the recommending participants.

7. The method of claim 6, wherein after the generating a recommendation list, the method further comprises:

When a new important schedule is detected, the recommended participants in the recommender list are updated based on the participants of the new important schedule.

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

displaying a first important participant interface, wherein the first important participant interface comprises a recommender list, the recommender list comprises at least one participant item, and the participant item comprises participant information and an add button;

in response to operation of the add button, a second important participant interface is displayed, the second important participant interface including an important participant list including important participant items, each of the important participant items including an added participant and a remove button.

9. The method of claim 8, wherein the first important participant interface further comprises an add other participant button; after displaying the first important participant human interface, the method further comprises:

in response to the operation of the add other participants button, displaying a first selected participant interface, the first selected participant interface including a first participant list of all schedules;

In response to an operation of selecting any one of the first participant list, a third important participant interface is displayed, the third important participant interface including an important participant list including the selected participant.

10. The method of any one of claims 1 to 9, wherein the first day card further comprises a participant setting; after displaying the first interface, the method further comprises:

in response to an operation of the participant setting item, displaying a schedule participant interface, wherein the schedule participant interface comprises a second participant list and an edit important participant button, and the second participant list comprises all participants in a schedule contained in the first schedule card;

in response to operation of the important participant button, displaying a second selected participant interface, the second selected participant interface comprising a participant selection list;

in response to an operation of selecting a participant in the participant selection list, the selected important participant is marked as an important participant, and the important participant list is updated.

11. The method according to any one of claims 8 to 10, wherein after adding the important participant, the method further comprises:

After detecting that the participants of the non-important schedules comprise important participants, automatically marking the non-important schedules as important schedules, wherein the non-important schedules are schedules with priority being none.

12. The method of any one of claims 1 to 11, wherein after displaying the second interface, the method further comprises:

displaying a setup popup comprising displaying only important first setup items;

in response to an operation of the first setting item, only important schedules are displayed in respective interfaces displaying schedules.

13. A schedule management method, applied to an electronic device, the method comprising:

displaying a first interface, wherein the first interface comprises a schedule priority of a first schedule and a desktop card setting item, and the schedule priority is important;

in response to an operation of the desktop card setting item, a first desktop card of the first schedule is displayed on a desktop, the first desktop card including a number of days between a current date and an execution date of the first schedule.

14. The method of claim 13, wherein prior to displaying the first interface, the method further comprises:

Displaying a second interface, wherein the second interface comprises a newly-built schedule button;

and responding to the operation of the new schedule button, and displaying the first interface.

15. The method of claim 13 or 14, wherein after displaying the first interface, the method further comprises:

responding to the operation of the desktop card setting item, and after detecting that the desktop card corresponding to the first date is added, displaying a first popup window on the first interface, wherein the first popup window comprises a cancel button, a determination button and information for prompting a user whether to repeatedly add the desktop card;

and responding to the operation of the determination button, adding a second desktop card of the first schedule, wherein the second desktop card is the same as the first desktop card in content.

16. The method according to any one of claims 13 to 15, further comprising:

displaying a third interface, wherein the third interface comprises a blank desktop card and a first button, and the blank desktop card comprises a schedule adding button;

displaying the blank desktop card on a desktop in response to an operation of the first button;

responsive to operation of the add schedule button, displaying a select schedule interface, the select schedule interface including a selectable schedule;

In response to an operation of selecting a schedule at the select schedule interface, displaying a desktop including a third desktop card including information of the selected schedule and a number of days between a current date and an execution date of the selected schedule.

17. An electronic device, the electronic device comprising: one or more processors, memory, and a touch screen; the memory is used for storing program codes; the processor is configured to execute the program code to cause the electronic device to implement the schedule management method according to any one of claims 1 to 16.

18. A computer readable storage medium having instructions stored thereon which, when executed on an electronic device, cause the electronic device to perform the schedule management method of any one of claims 1 to 16.