WO2024066863A1 - 日程管理方法及装置 - Google Patents

日程管理方法及装置 Download PDF

Info

Publication number
WO2024066863A1
WO2024066863A1 PCT/CN2023/115428 CN2023115428W WO2024066863A1 WO 2024066863 A1 WO2024066863 A1 WO 2024066863A1 CN 2023115428 W CN2023115428 W CN 2023115428W WO 2024066863 A1 WO2024066863 A1 WO 2024066863A1
Authority
WO
WIPO (PCT)
Prior art keywords
schedule
important
interface
participant
card
Prior art date
Application number
PCT/CN2023/115428
Other languages
English (en)
French (fr)
Other versions
WO2024066863A9 (zh
Inventor
鲍新彤
Original Assignee
荣耀终端有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 荣耀终端有限公司 filed Critical 荣耀终端有限公司
Publication of WO2024066863A1 publication Critical patent/WO2024066863A1/zh
Publication of WO2024066863A9 publication Critical patent/WO2024066863A9/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/0482—Interaction with lists of selectable items, e.g. menus
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G06F3/04842—Selection of displayed objects or displayed text elements
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management

Definitions

  • the present application relates to the field of computer technology, and in particular to a schedule management method and device.
  • An application that can implement schedule management in electronic devices, supporting users to create or access multiple schedules from other applications.
  • Different schedules have different levels of importance to users. For example, if they are all meeting schedules, the importance of meetings involving important content is usually higher than that of ordinary meetings.
  • Current schedule management applications cannot highlight schedules that are important to users, which may cause users to miss important schedules.
  • the present application provides a schedule management method and device to solve at least part of the above problems, and the disclosed technical solution is as follows:
  • the present application provides a schedule management method, which is applied to an electronic device, and the method includes: displaying a first interface, the first interface includes a first schedule card, the first schedule card includes schedule information and schedule priority, and the schedule priority is none; in response to the operation of selecting the schedule priority as important, displaying a second interface, the second interface includes a second schedule card, the schedule priority in the second schedule card is important, and the schedule information contained in the second schedule card is more than the schedule information contained in the first schedule card.
  • the schedule information includes a schedule title; the second schedule card also includes an important identifier, and the important identifier is located before the schedule title. In this way, the user can recognize that the schedule is an important schedule after seeing the important identifier in the schedule display area.
  • the schedule priority includes none, important and ignore. It can be seen that the solution merges ignore into the priority level, and each interface showing the schedule includes a priority setting item, so that the user can easily find the ignore entrance, which is convenient for user operation.
  • a second interface in response to an operation of selecting a schedule priority as important, a second interface is displayed, including: in response to an operation of clicking on a schedule priority on a first schedule card, a priority setting option pop-up window is displayed on the first interface, the priority setting option pop-up window including a no level option, an important level option, and an ignore option; in response to an operation of selecting an important level option on the priority setting option pop-up window, the second interface is displayed.
  • the method before displaying the first interface, further includes: displaying a third interface, the third interface including a first button, the first button being used to create a new schedule; in response to an operation on the first button, displaying the first interface, the first interface also including a save button; in response to an operation of selecting a schedule priority as important, displaying a second interface, including: in response to an operation on the schedule priority on the first interface, displaying a priority setting option pop-up window on the first interface, the priority setting option pop-up window including a no level option, an important level option, and an ignore option; in response to an operation on the priority
  • the operation of selecting the importance level option on the setting option pop-up window displays the first interface, and the priority of the schedule in the first interface is updated to important; in response to the operation of the save button, the second interface is displayed. It can be seen that the user can mark important schedules on the new schedule page, so that the user can mark important schedules when creating a new schedule.
  • the schedule information includes participants
  • the method further includes: when it is detected that the schedule priority is an important schedule, obtaining the participants in all schedules that include the participants; selecting a preset number of participants that meet preset conditions from the participants in all schedules to determine as recommended participants, the preset conditions including that the frequency of participating in important schedules is greater than a preset threshold; generating a recommender list, the recommender list including the recommended participants.
  • the method further includes: when a new important schedule is detected, updating the recommended participants in the recommender list based on the participants of the new important schedule. It can be seen that the solution can update the recommender list according to the update of the important schedule, so that the recommenders in the recommender list are always important participants that the user pays attention to.
  • the method also includes: displaying a first important participant interface, the first important participant interface including a recommender list, the recommender list including at least one participant item, the participant item including participant information and an add button; in response to an operation on the add button, displaying a second important participant interface, the second important participant interface including an important participant list, the important participant list including important participant items, each important participant item including an added participant and a remove button.
  • the first important participant interface also includes an add other participant button; after displaying the first important participant interface, the method further includes: in response to an operation on the add other participant button, displaying a first participant selection interface, the first participant selection interface including a first participant list of all schedules; in response to an operation on selecting any participant in the first participant list, displaying a third important participant interface, the third important participant interface including an important participant list, the important participant list including the selected participant.
  • the first schedule card also includes a participant setting item; after displaying the first interface, the method further includes: in response to an operation on 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 the schedule included in the first schedule card; in response to an operation on the important participant button, displaying a second participant selection interface, the second participant selection interface including a participant selection list; in response to an operation of selecting a participant in the participant selection list, marking the selected important participant as an important participant, and updating the important participant list.
  • the user can directly set a participant as an important participant among the participants of a schedule, meeting the needs of the user.
  • the method further includes: upon detecting that the participants of a non-important schedule include important participants, automatically marking the non-important schedule as an important schedule, wherein the non-important schedule is a schedule with a priority of none.
  • the non-important schedule is a schedule with a priority of none.
  • the method further includes: displaying a setting pop-up window, the setting pop-up window including displaying only important first setting items; in response to an operation on the first setting item, displaying the schedule Only important schedules are displayed in each interface of the system. It can be seen that in a schedule with many schedules, filtering and displaying important schedules can enable users to focus on important schedules and avoid missing important things.
  • the method after displaying the first interface, also includes: in response to an operation on the first schedule card, displaying a fourth interface, the fourth interface including the schedule priority of the schedule in the first schedule card, and the schedule priority is none; after determining that the first prompt pop-up window has not been displayed, displaying the first prompt pop-up window on the fourth interface, the first prompt pop-up window including prompt information prompting the user to mark important schedules.
  • displaying a fourth interface in response to an operation on a first schedule card, includes: in response to a click operation on the first schedule card, displaying a fourth interface, the fourth interface displays schedule details information of the schedule in the first schedule card, the schedule details information includes a title, a start and end time, and a schedule priority, and the schedule priority is none; or, the first schedule card also includes a second button; in response to an operation on the first schedule card, displaying a fourth interface includes: in response to a click operation on the second button, displaying a fourth interface, the fourth interface includes a third schedule card, the schedule displayed in the third schedule card is the same as the schedule displayed in the first schedule card, and the schedule information displayed in the third schedule card is more than the schedule information displayed in the first schedule card, and the schedule priority in the third schedule card is none; or, in response to an operation on the first schedule card, displaying a fourth interface includes: in response to a long press operation on the first schedule card, displaying a fourth interface, the
  • the present application also provides another schedule management method, and a desktop card setting item, the schedule priority is important; in response to the operation of the desktop card setting item, a first desktop card of a first schedule is displayed on the desktop, and the first desktop card includes the number of days between the current date and the execution date of the first schedule.
  • the scheme can add a desktop card of an important schedule on the desktop, and the desktop card can display the number of days from the execution date of the important schedule, so that the user can see the remaining period of the important schedule at a glance, and further remind the user to execute the important schedule or make adequate preparations for the important schedule.
  • the method before displaying the first interface, the method further includes: displaying a second interface, the second interface including a new schedule button; and in response to an operation on the new schedule button, displaying the first interface. It can be seen that the solution supports adding a desktop card of a schedule when the user creates a new schedule, thereby avoiding repeated operations by the user.
  • the method further includes: in response to an operation on a desktop card setting item, and after detecting that a desktop card corresponding to the first schedule has been added, displaying a first pop-up window on the first interface, the first pop-up window including a cancel button, an OK button, and information prompting the user whether to repeat adding the desktop card; in response to an operation on the OK button, adding a second desktop card of the first schedule, the second desktop card having the same content as the first desktop card.
  • the scheme supports users to repeatedly add desktop cards of a schedule, for example, adding desktop cards of the same schedule on different desktop pages, so that users can see the schedule on each desktop page, improving the presentation rate of desktop cards, and making it easier for users to pay attention to the schedule.
  • the method also includes: displaying a third interface, the third interface includes a blank desktop card and a first button, the blank desktop card includes an add schedule button; in response to an operation on the first button, displaying a blank desktop card on the desktop; in response to an operation on the add schedule button, displaying a schedule selection interface, the schedule selection interface includes selectable schedules; in response to an operation of selecting a schedule in the schedule selection interface, displaying a desktop, the desktop includes a third desktop card, the third desktop card includes information of the selected schedule, and the number of days between the current date and the execution date of the selected schedule.
  • the present application also provides an electronic device, the electronic device comprising: one or more processors, a memory and a touch screen; the memory is used to store program code; the processor is used to run the program code, so that the electronic device implements the schedule management method of any one of the first aspect and the second aspect.
  • the present application further provides a computer-readable storage medium having instructions stored thereon, which, when executed on an electronic device, enables the electronic device to implement the schedule management method of any one of the first and second aspects.
  • the present application further provides a computer program product having an executable program stored thereon, which, when the computer program product is run on an electronic device, enables the electronic device to implement the schedule management method of any one of the first aspect and the second aspect.
  • FIG1 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application.
  • FIG2-1 is a schematic diagram of an interface for manually marking important schedules provided in an embodiment of the present application.
  • FIG2-2 is a schematic diagram of another new schedule interface provided in an embodiment of the present application.
  • FIG3 is a schematic diagram of an interface of a schedule details view provided in an embodiment of the present application.
  • FIG4 is a schematic diagram of another interface for manually marking important schedules provided in an embodiment of the present application.
  • FIG5 is a schematic diagram of another interface for manually marking important schedules provided in an embodiment of the present application.
  • FIG6 is a schematic diagram of an interface for manually marking important schedules provided in an embodiment of the present application.
  • FIG7 is a schematic diagram of an interface for guiding a new function regarding an important schedule provided by an embodiment of the present application.
  • FIG8 is a schematic diagram of a rule for determining important participants provided in an embodiment of the present application.
  • FIG9 is a schematic diagram of an interface for guiding new functions of important participants provided in an embodiment of the present application.
  • FIG10 is a schematic diagram of an interface for adding important participants provided in an embodiment of the present application.
  • FIG11 is a schematic diagram of an important participant interface provided in an embodiment of the present application.
  • FIG12 is a schematic diagram of another interface for adding important participants provided in an embodiment of the present application.
  • FIG13 is a schematic diagram of another interface for adding important participants provided in an embodiment of the present application.
  • FIG14 is a schematic diagram of an automatic marking of important schedules provided in an embodiment of the present application.
  • FIG15 is a schematic diagram of an interface for removing important participants provided in an embodiment of the present application.
  • FIG16 is a schematic diagram of another important participant interface provided in an embodiment of the present application.
  • FIG17 is a schematic diagram of another important participant interface provided in an embodiment of the present application.
  • FIG18 is a schematic diagram of an interface for screening important schedules provided in an embodiment of the present application.
  • FIG19 is a schematic diagram of another interface for screening important schedules provided in an embodiment of the present application.
  • FIG20 is a schematic diagram of another interface for screening important schedules provided in an embodiment of the present application.
  • 21 is a schematic diagram of an interface for adding a schedule card on a desktop according to an embodiment of the present application.
  • FIG22 is a schematic diagram of a schedule card display content provided in an embodiment of the present application.
  • FIG23 is a schematic diagram of a schedule card format provided in an embodiment of the present application.
  • 24 is a schematic diagram of another interface for adding a schedule card on the desktop provided in an embodiment of the present application.
  • 25 is a schematic diagram of another interface for adding a schedule card on the desktop provided in an embodiment of the present application.
  • FIG26 is a schematic diagram of an interface for selecting a schedule provided in an embodiment of the present application.
  • FIG. 27 is a schematic diagram of an interface for a schedule card operation provided in an embodiment of the present application.
  • words such as “exemplary” or “for example” are used to indicate examples, illustrations or descriptions. Any embodiment or design described as “exemplary” or “for example” in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as “exemplary” or “for example” is intended to present related concepts in a specific way.
  • a user can create multiple schedules of different time periods on the same date, for example, 8:00-9:00: Schedule 1, 10:00-11:00: Schedule 2, 13:00-14:30: Schedule 3.
  • multiple schedules are usually sorted in the order of their start time.
  • the schedules that can be displayed in the display interface are limited. This way of displaying schedules may cause important schedules to be placed at the back, and the user needs to manually slide up the display interface to see the information of important schedules.
  • the information displayed for different schedules is basically the same, and the key information cannot be highlighted.
  • the start time and end time are displayed for both the meeting schedule and the credit card repayment schedule. For users, the importance of the meeting schedule is higher than that of the credit card repayment.
  • the displayed schedule information does not highlight the importance of the meeting schedule, nor does it display more information about the meeting schedule. That is, for the user's important schedule and ordinary schedule, the displayed information and prompt function are the same. The user can only subjectively distinguish which are important schedules, which may cause the user to miss important schedules.
  • the inventor of the present application provides a schedule management method, which supports users to mark important schedules.
  • the display position of important schedules is before ordinary schedules, so that users can see important schedules more intuitively.
  • the interface displaying the schedule will expand to display the information of the important schedule, that is, the information of important schedules displayed on the interface is more than that of other schedules, so that users can intuitively know more information about important schedules, improving user experience.
  • the electronic devices to which the schedule management method provided in the embodiments of the present application can be applied may be mobile phones, tablet computers, desktops, laptops, notebook computers, ultra-mobile personal computers (Ultra-mobile Personal Computer, UMPC), handheld computers, netbooks, personal digital assistants (Personal Digital Assistant, PDA), wearable electronic devices, smart watches, augmented reality technology (augmented reality, AR) devices, virtual reality (virtual reality, VR) devices, etc.
  • the terminal device involved in the embodiments of the present application only needs to have the function of setting a schedule, and the embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal device.
  • FIG1 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application.
  • the electronic device can It includes a processor 1, a memory 2, a display screen 3, a touch sensor 4, and a power management module 5.
  • the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device.
  • the electronic device may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently.
  • the components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.
  • the processor 1 may include one or more processing units, and different processing units may be independent devices or integrated into one or more processors. For example, in the embodiment of the present application, the processor 1 may manage the schedule.
  • the memory 2 is used to store computer executable program codes and data, wherein the program codes include instructions.
  • the processor 1 manages the schedule by executing the program instructions stored in the memory 2.
  • the display screen 3 is used to display images, videos, etc.
  • the display screen can also display a series of graphical user interfaces (GUIs), which are the main screens of the electronic device.
  • GUIs graphical user interfaces
  • a control is a GUI element, which is a software component included in an application program, and controls all data processed by the application program and the interactive operations on the data. Users can interact with the control through direct manipulation to read or edit the relevant information of the application program.
  • a control can include visual interface elements such as icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, etc.
  • the touch sensor 4 is also called a "touch control device”.
  • the touch sensor 4 can be arranged on the display screen 3.
  • the touch sensor 4 and the display screen 3 form a touch screen, also called a "touch control screen”.
  • the touch sensor 4 is used to detect touch operations acting on or near it.
  • the touch sensor can pass the detected touch operation to the application processor to determine the type of touch event.
  • Visual output related to the touch operation can be provided through the display screen 3.
  • the touch sensor 4 can also be arranged on the surface of the electronic device, which is different from the position of the display screen 3.
  • the following is an example of an electronic device being a mobile phone to illustrate the embodiment of the present application.
  • the mobile phone has a function of setting a schedule, and can support a user to set a schedule reminder on a calendar application.
  • the application for managing schedules may include a calendar application and a to-do list application, etc., and the embodiments of the present application may be applied to any application that can manage schedules. It should be understood that managing schedules herein may include all schedule-related operations such as creating a new schedule, modifying the content of a schedule, and deleting a schedule, and the present application does not limit the scope of managing schedules.
  • a user can manually mark a new schedule as an important schedule when creating a new schedule, or manually mark an existing schedule as an important schedule.
  • FIG 2-1 is a schematic diagram of an interface for manually marking important schedules provided in an embodiment of the present application. This embodiment is explained by taking the example of creating a new schedule in a calendar application. It should be understood that a new schedule can also be created in other schedule management applications, and this application does not limit this.
  • the interface 10 shown in a of Figure 2-1 can be displayed.
  • the interface 10 is the month view interface of the calendar.
  • the month view is used to display all dates of the entire month. In this example, all dates of the entire September are displayed.
  • the current date is highlighted by default.
  • the interface can also highlight other dates selected by the user, such as the user can click on the digital icon indicating other dates to select the date.
  • the specified date is highlighted by highlighting the mark, such as highlighting the mark as a circle 11 whose diameter is larger than the diameter of the digital icon.
  • the current date is September 10, 2022.
  • the user can create a new schedule for the currently highlighted date by clicking icon 12 as shown in a of FIG2-1.
  • the user can also click other digital icons as shown in a of FIG2-1 to select other dates, and further click icon 12 to create a schedule for the other dates.
  • the new schedule interface shown in FIG2-1 b is entered, and the user fills in the detailed information of the new schedule.
  • the new schedule interface includes a priority setting column 24, a title setting column 21, a location setting column 22, a start and end time setting column 23, and a reminder setting column 25.
  • the priority setting bar 24 includes a priority setting item 241.
  • the user sets the priority of the newly created schedule by clicking the priority setting item 241, and enters the interface 30 shown in c of FIG. 2-1.
  • a priority setting card 31 is displayed on the interface, and all configurable levels are displayed on the card, such as "Important”, “Ignore” and “None".
  • “Important” means that the schedule is an important schedule, that is, the schedule that the user focuses on
  • “Ignore” means that the schedule can be ignored and the user does not need to pay attention to it
  • “None” means that the schedule does not need to be focused on but cannot be ignored.
  • the interface 30 shown in c of FIG. 2-1 adds a grayscale 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 grayscale layer, so that the priority setting card 31 can be highlighted, making the priority setting card 31 more eye-catching and making it easier for users to pay attention to the priority setting card 31.
  • the priority setting card 31 can also be directly displayed on the interface shown in b of FIG. 2-1.
  • the selection button style of the priority level is a radio button, that is, the user can click a button in an unselected state to make it selected, and at the same time, the button that was originally selected becomes unselected.
  • the selection button corresponding to the "Important" level in c of Figure 2-1 is currently unselected. After the user clicks the button, it becomes selected. At the same time, the selection button corresponding to the "None" level changes from a selected state to an unselected state.
  • the priority setting card 31 may also be located at other locations of the interface 30.
  • the embodiment of the present application does not limit the size, style, display position of the priority setting card, and the style of the selection button in the priority setting card.
  • FIG2-2 another schematic diagram of a new schedule interface provided in an embodiment of the present application is shown.
  • the difference from the new schedule interface shown in FIG2-1 b is that the new schedule interface shown in FIG2-2 also includes a participant card 26, which may include an inviter option 261 and a participant option 262.
  • the user adds inviters to the schedule by operating the inviter option 261 .
  • the schedule is an online meeting schedule
  • the user adds the meeting inviters through the inviter option.
  • the user can add other participants of the schedule by operating the participant option 262.
  • the participant option can include the inviter by default.
  • the new schedule interface of this example may also include a conference link bar 27.
  • the conference link bar may be reused with the location setting bar. For example, the user may paste the conference link by clicking the location setting bar, or may enter the location of the schedule.
  • the user can slide up the area 13 showing the date in the month view interface shown in a of FIG. 2-1 to collapse the date display area, that is, the date display area changes from 13 shown in a of FIG. 2-1 to area 51 shown in e of FIG. 2-1, and the date display Area 51 only displays the row containing the currently highlighted date, thereby increasing the area of schedule display area 52 below the date display area.
  • the schedule display area 52 is used to display all schedules that need to be reminded to the user under the currently highlighted date (September 10, 2022 in this example), including holidays, solar terms and other schedules.
  • the display position of the holiday schedule is located at the top of the schedule display area 52, that is, the display position of the holiday schedule is before other schedules.
  • the display position of the holiday schedule may be at the bottom of the schedule display area 52, that is, the display position of other schedules is before the holiday schedule. It should be understood that when the number of schedules on this date is large, they cannot all be displayed in the schedule display area 52, and the undisplayed schedules can be displayed by sliding the schedule display area 52 upward.
  • the information of the schedule is expanded and displayed in the schedule display area 52 so that the user can directly obtain more information about the schedule.
  • the schedule display is folded to save the display area of the schedule display area.
  • the important schedule of "Design Solution Seminar” is expanded and displayed in card 56, while the non-important schedule (or ordinary schedule) of "Train Travel” is folded and displayed in card 57.
  • the important schedule displayed by expanding card 56 is a meeting schedule.
  • the expanded schedule information may include schedule title 53 , schedule start and end time “8:00 am to 9:30 am”, meeting inviter, participant, account, and priority 55 .
  • the title of the important schedule also includes an important identifier for indicating the importance of the schedule.
  • the important identifier is "!.
  • the important identifier can also be other symbols, which is not limited by the present application.
  • the expanded schedule information can also include a link button for "Join the meeting".
  • a folding button 54 may be included next to the schedule title. The user can click the folding button 54 to change the schedule from an expanded display state to a folded display state. It is understandable that in the folded display state, only very important information such as the title, start and end time of the schedule can be displayed. As shown in e of Figure 2-1, card 57 is in a folded display state, and the displayed content includes the schedule title, start and end time, location, and an expand button 58. The user can click the expand button 58 to change the schedule from a folded display state to an expanded display state, thereby displaying more information of the "train travel" schedule, such as the seat number.
  • the schedule details are displayed in an expanded manner by default in each scene.
  • the schedule display area 61 displays the information of three schedules from top to bottom, among which the design plan discussion meeting is an important schedule, and the detailed information of the schedule is displayed in an expanded manner by default.
  • the train trip and hotel check-in schedules are non-important schedules, and the information of these two schedules is displayed in a collapsed manner.
  • the schedule view interface 60 may be entered by clicking the “Schedule” button 14 shown in a of FIG. 2-1 .
  • “Ignore” is included in the priority card 31 as a priority of the schedule, that is, in the embodiment of the present application, “Ignore” is merged from more options of the schedule details interface into the priority of the schedule.
  • the interface shown in FIG. 3 b When the user clicks the control 611 in the schedule details interface 610 shown in FIG. 3 a, the interface shown in FIG. 3 b is jumped to, and the interface shown in FIG. 3 b displays a more tab sheet 612 on the schedule details interface 610, including share and delete options, that is, the more tab sheet 612 in the embodiment of the present application does not include an "ignore” option. It is obvious that after the user clicks on the schedule titled "Design Solution Seminar" in e or f of FIG2-1, the schedule details interface 610 is entered.
  • the process shown in Figure 2-1 is the process of manually marking a schedule as an important schedule in the scenario of creating a new schedule.
  • Existing schedules can also be manually marked as important schedules.
  • the existing schedule can be a created schedule without setting a priority, or it can also be a schedule imported from other applications.
  • FIG. 4 is a schematic diagram of another interface for marking an important schedule provided in an embodiment of the present application.
  • This embodiment takes the schedule information displayed in the month view interface of the calendar as an example to illustrate the process of manually marking an existing schedule as an important schedule.
  • the current priority of the "Design Solution Seminar Meeting" schedule in the expanded display state in the calendar's month view interface 100 is "None".
  • the user can click button 101 (such as a drop-down menu button) to jump to the interface shown in b of FIG4 , which includes a priority menu 102.
  • the priority menu 102 includes three levels: “Important”, "Ignore", and "None”.
  • a grayscale layer is added to the upper layer of the row where the current priority (or selected level) is located, thereby highlighting the current level (or selected level) of the schedule.
  • the row where the current priority is "None” is grayscale.
  • the user can select a non-highlighted level in the priority menu 102.
  • the user can select the "Important” level, manually mark the schedule as an important schedule, and jump to the interface shown in c of FIG4 .
  • the priority setting item 104 of the schedule displays the “important” level, and the title 105 of the schedule also includes an important identifier “!”.
  • the embodiment of the present application also provides an interface schematic diagram for manually marking an existing schedule as an important schedule in other scenarios.
  • Figure 5 shows an interface schematic diagram for marking a schedule as an important schedule on the schedule details page.
  • the user clicks the schedule card 56 in e of FIG. 2-1 to jump to the schedule details interface 200 shown in a of FIG. 5 , in which the priority setting item 201 shows that the current priority is "none".
  • the user can select other priorities by clicking button 202.
  • the user jumps to the interface shown in b of FIG. 5 , which adds a grayscale layer on the upper layer of the schedule details interface 200, and further displays a priority setting card 203 on the upper layer of the grayscale layer, so that the priority setting card 203 can be made more eye-catching.
  • the priority setting card 203 here is the same as the priority setting card 31 in the interface shown in c of FIG. 2-1 , and will not be repeated here.
  • the user clicks the button 204 corresponding to the "important" level in the priority setting card 203 to jump to the schedule details interface shown in c of FIG. 5 , in which the priority item 205 shows that the current level is "important", and the schedule title 206 contains an important identifier "!.
  • FIG. 6 a schematic diagram of another interface for manually marking important schedules provided in an embodiment of the present application is shown.
  • the process of manually marking important schedules is explained by taking the schedule quick operation interface as an example.
  • the user can enter the interface shown in FIG. 6 b by long pressing the schedule display card 301 in FIG. 6 a, and the interface displays a pop-up window 302, which is used to display schedule information, such as schedule title, start and end time, priority options, etc.
  • the priority options include the current level of the schedule and a button 303.
  • the interface is jumped to the interface shown in FIG. 6 c, which also includes a priority menu 304 on the upper layer of the pop-up window 302.
  • the priority menu 304 in this embodiment is the same as the priority menu 102 shown in FIG. 4 b , and will not be described again here.
  • a card 307 is also included below the pop-up window 302, and the card 307 includes a "share” and a "delete” button.
  • the “share” button 308 it jumps to the sharing preview interface 401 shown in e of FIG6 , which includes a share button 403. Further, the user clicks the share button 403 to forward the schedule information to others.
  • the share button 403 to forward the schedule information to others.
  • the schedule information is deleted from the calendar application.
  • FIG7 shows a schematic diagram of an interface for guiding a new function of setting an important schedule provided in an embodiment of the present application.
  • the month view interface includes a card 70 , which is in a folded display state, that is, only partial information of the schedule is displayed, such as the title, start and end time, and location.
  • the user clicks the expansion button 701 in the card 70, the user is redirected to the interface shown in b of FIG. 7 , in which the card 70 is in an expanded display state, in which a prompt pop-up window 72 may be displayed, and the prompt pop-up window 72 is used to guide the user to use the function of manually marking a schedule as an important schedule.
  • the text information in the prompt pop-up window 72 may include "Mark important schedules and view more schedule information".
  • the prompt pop-up window 72 may be located in the upper layer of the interface 90.
  • the prompt pop-up window 72 disappears.
  • the prompt pop-up window 72 is located above the priority item 73 , so that the user can intuitively know to mark an important schedule by operating the priority item 73 .
  • the quick operation interface 80 shown in c of Figure 7 which includes a schedule card 81.
  • the schedule card 81 includes a prompt pop-up window 83 located above the priority item 82.
  • the prompt pop-up window 83 is used to display and guide the user to use the function of manually marking important schedules.
  • the prompt pop-up window 92 can be located in the upper layer of the interface 90.
  • Figure 7 b, c, and d respectively show interface schematic diagrams of displaying new function prompt pop-up windows in different scenarios.
  • the functions of the prompt pop-up windows in different scenarios are the same, namely, guiding users to manually mark important schedules.
  • the position, size, style and displayed content of the prompt pop-up window can be adjusted according to different display scenarios, and this application does not limit this.
  • the above-mentioned prompt pop-up window may be displayed only on the first interface accessed, and the prompt is not repeated in other scenes.
  • the scene shown in FIG. 7 b is entered for the first time, and the prompt pop-up window 72 is displayed on the interface shown in FIG. 7 b.
  • the prompt pop-up window is no longer displayed.
  • participants who meet certain conditions can be selected from all participants in the schedule and recommended to the user as important participants, or the user can automatically add important participants.
  • the schedule containing the important participants can be set as an important schedule without the need for users to manually mark it, further improving the user experience.
  • FIG. 8 a schematic diagram of a rule for determining important participants provided in an embodiment of the present application is shown.
  • other participants are participants who have appeared in all schedules, including Y other participants in this example. Participants who meet the preset conditions are selected from the Y other participants as recommended participants.
  • Recommenders i.e., participants that the user may pay attention to.
  • the number of recommenders can be X, where X ⁇ Y.
  • the maximum value of X can be limited, such as X ⁇ 5, that is, a maximum of 5 participants are recommended to the user.
  • the user can select participants in the recommender list as important participants. Of course, the user can also directly select participants from other participants as important participants.
  • the participants in the recommender list will be updated according to the user's operation of adding or deleting important participants.
  • the schedule management application will count all participants who have appeared in all important schedules and select participants who meet the preset conditions as recommenders. When the recommender list is not empty, the user is prompted to add important participants.
  • the schedule management application when the schedule management application detects that all participants in the recommender list are updated, the user may be prompted again to add new important participants.
  • FIG. 9 there is shown a schematic diagram of an interface of a prompt box for prompting a user to add important participants provided in an embodiment of the present application.
  • a prompt box 702 is displayed on the month view interface 701 of the calendar application, and the prompt box 702 is used to guide the user to use the important participant function, in other words, to prompt the user to add important participants to further improve the user experience. Furthermore, important schedules can be automatically marked according to the important participants added by the user.
  • the prompt box 702 may be located between the date display area 705 and the schedule display area 706. In this example, the prompt box 702 may be located in 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 in the upper layer of the layer where the date display area and the schedule display area are located, such as the prompt box 702 is a pop-up window.
  • the prompt box 702 includes text information for prompting the user, such as "Recommending important participants for you, intelligently marking schedules according to your important participants, don't miss important things", of course, the text information displayed in the prompt box 702 may also be other content, which is not limited in this application.
  • the prompt box 702 also includes an "Add Now” button 703 and a close button 704. After the user clicks the "Add Now” button 703, it can jump to the interface for adding important participants. After the user clicks the close button 704, the prompt box 702 is closed, that is, the prompt box 702 disappears.
  • a more tab sheet 801 is displayed, and the more tab sheet 801 includes a “settings” item 802. Further, after the user clicks the “settings” item 802, the interface 803 shown in b of FIG10 is jumped to, and the interface includes an important participant setting card 804. The user clicks a button 805 in the important participant setting card 804 to jump to the important participant interface shown in c of FIG10 .
  • the important participant interface includes a recommender list 806, and the recommender list 806 includes recommended participant setting items 807.
  • each participant setting item 807 includes the participant's information (such as name and account, etc.) and an "add" button 808.
  • the participant is added to the important participant list.
  • the interface jumps to the interface 809 shown in d of FIG. 10 .
  • the interface 809 includes an important participant list 810, which may be located above the recommender list 813.
  • the important participant list 810 includes the participants “Xiaomin” and “Long” added by the user, and each important participant setting item 811 includes the participant’s information (such as name and account, etc.) and a “Remove” button 812. The user can click the “Remove” button 812 to delete the added important participant from the important participant list.
  • the number of important participants is not limited, that is, the number of participants in the important participant list is not limited.
  • a "more” button 902 will be displayed in the window 901. Clicking the "more” button 902 jumps to the interface shown in b of FIG11 , in which a window 903 with a larger display area is used to display the important participant list.
  • the user can change the important participants displayed in the window 903 by sliding the page displayed in the window 903 up and down. For example, when sliding the important participant list in the window 903 upward, the important participants after the important participant "Wind" in the figure can be displayed.
  • the bottom of the window 903 includes a “Collapse” button 904.
  • the interface jumps from the interface shown in b of FIG11 to the interface shown in a of FIG11 . That is, after clicking the “Collapse” button 904, the window 903 displaying important participants becomes a window 901 with a smaller display area.
  • the important participant that the user wants to add is not included in the recommender list.
  • other participants can be selected as important participants through "Add other participants”.
  • FIG. 12 another interface schematic diagram of adding important participants provided in an embodiment of the present application is shown.
  • the important participant interface 1000 includes an "add other participants" button 1002.
  • the button 1002 is located below the recommender list 1001. In other embodiments of the present application, the button 1002 may also be located in other locations, which is not limited in the present application. After the user clicks the button 1002, the user is redirected to the participant selection interface 1003 shown in FIG. 12 b.
  • the interface 1003 is used to display a list of all participants.
  • Each participant option in the list includes the participant's information and a selection button 1004.
  • the user can click the selection button 1004 to select the participant.
  • the interface shown in FIG. 12 c is jumped to the interface, in which the selection button 1004 corresponding to the participant "Dannle" becomes selected.
  • “ ⁇ ” indicates that it has been selected.
  • " ⁇ " including “ ⁇ ” can also be used to indicate that it has been selected.
  • the participant list selection interface 1003 includes a button 1006, a close button 1007, and a search box 1008.
  • Button 1006 is a save button indicating completion.
  • the current selection result is saved after clicking button 1006, that is, the result of saving "Dannle” as an important participant is saved.
  • the interface shown in d of FIG. 12 is jumped to. 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 .
  • the user can enter at least part of the name or initials of the participant to be searched in the search box 1008, and the corresponding participant can be searched.
  • the bottom of the interface shown in c of FIG. 12 also includes a "Select All” button. After the user clicks the "Select All” button, all participants in the list of all participants are selected.
  • the interface 1009 includes a window 1010 for displaying important participants.
  • the window 1010 is used to display information items of important participants, and operation buttons, such as a “remove” button. The user clicks the “remove” button to delete the participant from the important participant list.
  • participant accounts are maintained in the dimension of participant accounts. Accounts of the same person in different applications are considered different participants, as shown in FIG. 12 b, including two participants whose names are both "AlisaLee" but whose accounts are different, and are maintained as two different participants, namely, 1005 and 1012 in FIG. 12 b. The two corresponding participants.
  • FIG. 13 is a schematic diagram of another interface for adding important participants provided in an embodiment of the present application.
  • the interface shown in a of FIG13 is a schedule details interface 1100, which includes a participant card 1101, which includes all participants of the schedule, and a button 1102. After the user clicks the button 1102, the user is redirected to the participant interface 1104 shown in b of FIG13.
  • the participant interface 1104 includes information of all participants of the schedule.
  • the schedule is an online meeting schedule
  • an online meeting usually includes an inviter, and the others are participants.
  • the inviter refers to the person who creates the online meeting, and this person can invite other people to participate in the online meeting he or she established.
  • the inviter can be defaulted to an important participant, and an important identifier can be included in the participant item.
  • the inviter item 1106 includes the name of the inviter "Xiaomin" and account information, and 11061 is shown as an important identifier.
  • the important identifier in this example is "VIP".
  • the area shown in 1107 is other participants of the schedule.
  • the user can slide this area up and down to update the participants displayed in the area. For example, if the user slides up, the participants currently displayed in the area will slide up with it, and at the same time, the participants below the participant "Long" will be displayed.
  • the top of the interface 1104 shown in FIG. 13 b also includes a return button 1105. The user clicks the button 1105 to return to the interface shown in FIG. 13 a.
  • the bottom of the participant interface 1104 shown in FIG13 b also includes an “Edit Important Participants” button 1108 . After the user clicks the button 1108 , the user is redirected to the participant selection interface 1112 shown in FIG13 c .
  • the interface 1112 for selecting participants includes an area 1114 for displaying the inviter and an area 1115 for displaying other participants.
  • Each participant display item in areas 1114 and 1115 includes a selection button 1113 .
  • the inviter is an important participant by default, so the selection button 1113 in the inviter display item is selected by default.
  • the selection button 1113 in the display item of the inviter "Xiaomin” is selected by default.
  • the selection button 1113 of the participant display item will be changed to the selected state.
  • the selection button can be " ⁇ " and the selected state can be " ⁇ ".
  • the selected state can also be other symbols.
  • the selection button can also be other styles, and the present application does not limit this.
  • an area 1109 which includes a completion button 1110 and a close button 1111, and may also include the number of selected important participants.
  • the completion button 1110 After the user clicks the completion button 1110, it jumps to the interface shown in d of FIG13 , and after clicking the close button 1111, it returns to the interface shown in b of FIG13 .
  • the interface shown in d of FIG. 13 is a schedule details page interface that includes not only the participant display item 1205 but also the important participant display item 1206.
  • the participant display item 1205 is used to display all participants of the schedule.
  • the important participant display item 1206 is used to display the important participants involved in the schedule, for example, in this example, the important participants are "Xiaomin" and "Lee".
  • the participant display item 1205 also includes a button 1209. The user clicks the button 1209 to jump to the participant interface shown in FIG. 13e.
  • the interface includes the inviter display area 1201 and other participant display areas. Area 1201 is used to display the inviters involved in the schedule. The other participant display area is used to display the participants involved in the schedule other than the inviter.
  • the inviter display item includes an important identifier 1203 by default, such as "VIP", and the display item 1202 of the other participant "Lee" selected by the user also includes the important identifier 1203.
  • a return button 1204 is also included above the inviter display area. After the user clicks the return button 1204, it jumps to the interface shown in d of Figure 13, that is, the schedule details page interface.
  • the schedule management application updates the list of important participants.
  • the non-important schedule can be automatically marked as an important schedule. This process does not require manual operation by the user, further improving the user experience.
  • the schedule title 1208 includes an important identifier, such as "!, and the priority displayed in the priority option 1207 is "Important".
  • view interfaces also include identifiers in other view interfaces of the schedule. For example, as shown in the month view interface 1301 of FIG. 14, it is identified that the participants of the non-important schedule "Design Solution Seminar" include the important participant "Lee”, and the non-important schedule is automatically marked as an important schedule. As shown in FIG. 14, the schedule title 1302 in the interface includes an important identifier, and the priority display item shows that the priority of the schedule is "important". This embodiment will not repeat the changes in other views after the schedule is automatically marked as an important schedule.
  • 11 to 13 are the process of adding important participants provided in the embodiment of the present application. Conversely, the important participants who have been added to the list of important participants can be deleted.
  • FIG. 15 there is shown a schematic diagram of an interface for deleting important participants provided in an embodiment of the present application.
  • the interface 1400 of important participants includes a list of important participants.
  • Each participant display item in the list includes a “remove” button 1401 .
  • the user can delete the participant from the list of important participants by clicking the “remove” button 1401 .
  • the interface jumps to the interface 1402 shown in b of Figure 15, which adds a grayscale layer on the upper layer of the interface 1400 shown in a of Figure 15, and further displays a prompt window 1403 on the upper layer of the grayscale layer, so that the prompt window 1403 can be highlighted, thereby guiding the user to view the content in the prompt box 1403.
  • the prompt window 1403 may include the changes in the schedule status including the participant that may be caused by removing the important participant, as well as the question prompt information that can be added again, as well as the "Cancel" button and the "Remove” button 1404.
  • the "Cancel” button After the user clicks the "Cancel” button, it returns to the interface shown in a of FIG. 15 , and after the user clicks the "Remove” button, it jumps to the interface shown in c of FIG. 15 .
  • the recommender list does not include any participant, that is, the recommender list is empty.
  • the recommender list is not displayed.
  • the interface 1600 shown in FIG16 a has the same setting items as interface 803 shown in FIG10 b, and the method of entering the interface is also the same, which will not be described in detail here.
  • all schedules in the schedule management application are not important schedules, that is, they do not contain important schedules.
  • the interface 1603 shown in b of FIG. 16 is jumped to.
  • the interface includes text prompt information 1604 showing important participants.
  • the prompt information is used to prompt the function and method of adding important participants.
  • the interface also includes a "Learn More" button 1605. After the user clicks the "Learn More" button 1605, he can jump to the interface that details the "Important Participants" function, for example, the function introduction page about "Important Participants" in the game playing skills application.
  • the application for managing schedules includes important schedules.
  • the interface 1606 shown in FIG. 16c is displayed.
  • the interface includes a text prompt message 1607 of "Follow important participants".
  • the text prompt message is used to prompt the user to add important participants.
  • Schedules containing important participants are defaulted as prompt messages of important schedules.
  • the interface shown in FIG. 16c also includes an "Add other participants" button 1608.
  • the interface shown in FIG. 12b is displayed.
  • the interface shown in FIG. 16c also includes a "Learn more" button.
  • the important participant interface 1500 further includes a details button 1501.
  • the interface 1502 shown in b of FIG17 is jumped to.
  • the interface adds a grayscale layer on the upper layer of the interface shown in a of FIG17 , and further displays a prompt window 1503 on the upper layer of the grayscale layer.
  • the prompt window 1503 is used to display the information of the important participant function.
  • the prompt window also includes a "Learn More" button 1504.
  • the interface displayed after the user clicks the "Learn More" button 1504 is the same as the interface displayed after clicking the "Learn More" button in b and c of FIG16 , and will not be repeated here.
  • FIG. 18 a schematic diagram of an interface for filtering important schedules provided in an embodiment of the present application is shown.
  • the month view interface 1700 of the calendar application includes a button 1701. After the user clicks the button 1701, it jumps to the interface shown in b of Figure 18.
  • a setting item window 1702 is displayed on the upper layer of the month view interface 1700.
  • the window includes a "show only important" setting item 1703. After the user clicks the "show only important" setting item 1703, it jumps to the interface 1704 shown in c of Figure 18.
  • the interface 1700 shown in a of FIG. 18 includes important schedules and non-important schedules, such as train travel schedules, while the interface 1704 shown in c of FIG. 18 includes only important schedules, and non-important schedules are not displayed.
  • the schedules for "Mid-Autumn Festival" and "Teacher's Day” are displayed by default.
  • the bottom of the interface shown in c of FIG. 18 also includes a prompt message 1705 of "Currently only important schedules are displayed", which is used to remind the user that the current interface does not display non-important schedules.
  • the prompt message 1705 of "Currently only important schedules are displayed” can also be in other forms. For example, an identifier indicating that the current filtering state is displayed in a blank space of the current interface or in the upper layer of the interface. The present application does not limit the identifier indicating the filtering state.
  • the user can also restore the display of all schedules.
  • the interface shown in FIG. 18 d is jumped to, which includes a setting item window 1707, which is different from the setting item window 1702 shown in FIG. 18 b in that the setting item window 1707 includes a "all schedules" setting item 1706, while the setting item window 1702 includes a "only show important" setting item 1703.
  • the interface is jumped to the interface shown in FIG. 18 a, that is, all schedules are displayed.
  • the contents displayed on the setting items in the setting item windows 1702 and 1707 may be based on The user's operation updates, for example, if all schedules for a certain date are displayed in the current view, the setting item in the setting item window is "Show only important". After the user clicks the "Show only important" setting item, the setting item in the setting item window changes to "All schedules".
  • the content displayed in the setting items in the setting item windows 1702 and 1707 remains fixed. For example, regardless of whether only important schedules are displayed in the current view, the setting item window will display "only important/all schedules". This application does not limit the content style of the setting items displayed in the setting item window.
  • FIG. 19 a schematic diagram of an interface of a schedule view provided by an embodiment of the present application is shown, where a of FIG. 19 is a schedule view interface 1801, and the interface displays all schedules, for example, including important schedules 1802 and non-important schedules 1803 and 1804. After the user chooses to display only important schedules, the interface changes to the interface shown in b of FIG. 19 .
  • the schedule view interface 1805 only displays important schedules for each date, and does not display non-important schedules. For example, the important schedules for September 10 are displayed in area 1806, and the important schedules for September 11 are displayed in area 1807. In addition, a prompt message 1808 "Only important schedules are currently displayed" is also included at the bottom of the interface.
  • FIG. 20 there is shown a schematic diagram of an interface of a schedule desktop card provided in an embodiment of the present application.
  • the desktop 1900 includes a calendar card 1901, and the calendar card 1901 includes schedules for the current date (September 10). If the current date includes multiple schedules, all schedules for the date cannot be displayed due to the limited display area of the calendar card 1901. For example, important schedules can be displayed first, and non-important schedules can be displayed after being sorted by start and end time.
  • the calendar card 1901 includes an important schedule 1902 and a non-important schedule 1903.
  • the bottom of the calendar card 1901 also includes a prompt message 1904 of "There are 2 other schedules" to remind the user that there are undisplayed schedules on that day.
  • the calendar card 1901 changes to the display interface shown in FIG. 20 b. As shown in FIG. 20 b, the calendar card 1901 only displays important schedules 1902, and does not display non-important schedules. In addition, a prompt message 1905 "No other important schedules today" may be displayed at the bottom of the calendar card 1901.
  • the desktop is also called a desktop application, a home screen, or a Launcher, etc.
  • the desktop is also called a desktop launcher (Launcher).
  • the desktop is collectively referred to as the desktop in this article.
  • the schedule management application also supports adding a single schedule card, or a schedule card, to the desktop.
  • FIG. 21 a schematic diagram of an interface for adding a schedule card provided in an embodiment of the present application is shown.
  • the function of adding a schedule card on the desktop can be provided only for important schedules, that is, only the display interface of important schedules has a function entry for adding a desktop card, and the interface of non-important schedules does not have a function entry for adding a desktop card.
  • schedule cards for all schedules can be added on the desktop, and the present application does not limit this.
  • the interface 2003 shown in b of FIG. 21 is jumped to the interface 2003, which also includes an “Add Desktop Card” setting item 2004.
  • the “Add Desktop Card” setting item 2004 includes a setting button 2005.
  • the setting button 2005 shown in b of FIG. 21 is not in an open state. After the user clicks the setting button 2005, it becomes an open state, as shown in c of FIG. 21 2005 is the open state.
  • the button 2006 shown in c in Figure 21 After the user clicks the button 2006 shown in c in Figure 21, it jumps to the interface shown in d in Figure 21, which includes an important schedule display area 2008. At the same time, the schedule card of the important schedule is added to the desktop. In addition, at the bottom of the interface, there is also a prompt message 2009 that "the schedule has been added to the desktop". In an exemplary embodiment, the prompt message disappears automatically after being displayed for a preset period of time.
  • the interface shown in d in Figure 21 also includes information 2007 indicating the corresponding date of the schedule. In this example, a schedule for September 9 is created on September 8, 2022, that is, a schedule for tomorrow is created today.
  • schedule card 2010 is a schedule card for a newly created important schedule "design solution discussion meeting".
  • the schedule card 2010 includes the number of days 2011 from the current date to the execution date of the schedule. In this example, the countdown number of days is 1 day.
  • the schedule card also includes an area 2012 for displaying the execution date of the schedule. In this example, the execution date of the schedule is September 9, 2022.
  • countdown days refer to the number of days remaining from the current date to the execution date of the schedule.
  • the schedule execution date is September 9, 2022
  • the current date is September 8, 2022.
  • the current date is not the schedule execution date, so the countdown to the schedule execution date is displayed on the schedule card displayed on September 8.
  • the schedule card 2013 displayed on September 8 shows that "1 day later" is the wedding anniversary, and displays the execution date of the schedule, that is, September 9, 2022.
  • the current date is September 9, 2022
  • the current date is the schedule execution date.
  • the schedule card 2014 displayed on September 9, 2022 no longer displays the countdown days, but directly displays "Wedding Anniversary” and the execution date of the schedule, September 9, 2022.
  • the schedule card 2015 displayed on September 10, 2022 may display that "1 day ago" is the wedding anniversary, and may also display the execution date of the schedule, that is, September 10, 2022.
  • the content displayed on the schedule card can be adjusted according to actual needs, and this application does not limit this.
  • schedule card 2010 shown in FIG. 21e is only a specific example, and schedule cards of other styles and sizes may also be included. As shown in FIG. 23, there are three possible sizes of schedule cards.
  • the size of schedule card 2016 is the same as that of schedule card 2010 shown in FIG. 21e, the size of schedule card 2017 is twice that of schedule card 2016, and the size of schedule card 2018 is half that of schedule card 2016.
  • schedule cards of other sizes may also be included, and the present application does not limit this.
  • a schedule card can also be added to the desktop for an existing schedule (such as a created schedule or a schedule imported from other applications).
  • FIG. 24 there is shown another schematic diagram of an interface for adding a schedule card provided in an embodiment of the present application.
  • the schedule details interface 2101 is the detailed information of the important schedule "Design Plan Discussion Meeting".
  • the interface includes a desktop card setting item 2102.
  • the desktop card setting item 2102 includes an "Add” button. The user can add the schedule card of the important schedule on the desktop by clicking the "Add" button.
  • the important schedule has not been added with a schedule card.
  • the desktop interface is jumped to the desktop interface shown in FIG. 24b.
  • the desktop interface includes a schedule card 2103 of the important schedule "Design Solution Discussion Meeting".
  • the content displayed in the schedule card 2103 is the same as that shown in FIG.
  • the schedule card shown is the same as that shown in the figure, so it will not be repeated here.
  • the important schedule has been added with a schedule card.
  • the interface 2104 shown in FIG. 24c is jumped to.
  • the interface adds a gray layer on the upper layer of the interface shown in FIG. 24a, and further, a prompt window 2105 is displayed on the upper layer of the gray layer.
  • the prompt window 2105 includes a desktop card to remind the user that the schedule has been added.
  • the text information displayed in the prompt window 2105 may be "The current schedule already has a desktop card, do you want to add it again?"
  • the prompt window 2105 also includes a "Cancel” button and an "OK” button. If the user clicks the "Cancel” button, the process of adding a desktop card for the schedule is not executed. If the user clicks the "OK” button, the process of adding a desktop card for the schedule continues to be executed. In this case, there will be at least two schedule cards corresponding to the schedule on the desktop, and the contents displayed in the at least two schedule cards are the same.
  • the schedule is first created and then the desktop card corresponding to the schedule is added.
  • a blank schedule card can also be added first, and then the schedule displayed on the blank schedule card can be selected.
  • FIG. 25 there is shown another schematic diagram of an interface for adding a schedule card provided in an embodiment of the present application.
  • a user can perform a two-finger pinch operation on the desktop 2200 to enter the interface shown in b of FIG. 25 , which is a desktop editing interface.
  • the upper area of the interface displays editable desktop pages 2201, and the currently displayed desktop page can be changed by sliding the desktop page left or right.
  • the bottom area of the interface displays operation options, such as wallpaper, calendar card 2202, switching effects, desktop settings, etc.
  • the interface is a schedule card interface, which includes an area 2203, which is used to display the style of the schedule card.
  • the style of the calendar card 2204 is currently displayed, and the style of the currently displayed schedule card can be changed by sliding the area left and right.
  • the bottom of the schedule card interface also includes an "Add to Desktop" button 2205. After the user clicks the "Add to Desktop” button 2205, the interface shown in d of FIG. 25 is jumped.
  • the schedule card 2206 added by the user is displayed on the desktop interface.
  • the schedule card 2206 includes a button 2207 for adding a schedule. After the user clicks the button 2207, it jumps to the interface for selecting a schedule.
  • the interface for selecting a schedule includes three pages: "Holidays", “Schedule", and "Birthday".
  • the user can select any one of the pages and select any one from the page to add to the schedule card.
  • the "Schedule" page includes multiple schedules under multiple dates.
  • the "Schedule” page includes 3 schedules on September 9 and 2 schedules on September 10.
  • the user can select any one of the schedules and add it to the schedule card on the desktop.
  • Each schedule item includes a selection button, and the selection button can include two display states, namely a selected state and a non-selected state.
  • button 2209 represents a selected state
  • button 2210 represents a non-selected state.
  • FIG. 26 a it is a schematic diagram of the “Holiday” page
  • FIG. 26 b is a schematic diagram of the “Birthday” page.
  • the “Holiday” page 2301 includes multiple holiday options 2302, and each holiday option includes a selection button.
  • the “Birthday” page 2303 includes multiple birthday options 2304, and each birthday option includes a selection button, which will not be repeated here.
  • schedule card 2211 shown in the interface has an additional user-selected schedule card 2212.
  • Schedule information wherein schedule card 2211 contains the same schedule information as that contained in the schedule card shown in FIG. 22 , and will not be described in detail here.
  • the user can also edit or remove the schedule card added on the desktop.
  • the user can edit or remove the schedule card by long pressing the schedule card on the desktop.
  • FIG. 27 there is shown a schematic diagram of an interface for operating a schedule card provided in an embodiment of the present application.
  • the desktop interface includes a schedule card 2401.
  • the user long presses the schedule card 2401 to jump to the interface shown in FIG27 b.
  • the interface also includes an operation tab 2402 below the schedule card 2401.
  • the operation tab 2402 includes edit and remove. After the user clicks "Remove", it jumps to the interface shown in FIG27 c, which is the desktop interface after the schedule card 2401 is deleted.
  • the user can edit the schedule in the schedule card 2401 by clicking "Edit” in the operation tab 2402, for example, changing the schedule information displayed on the schedule card.
  • the schedule card 2401 adds the schedule of "Design Project Workshop”.
  • the schedule card can display the information of another schedule, which will not be repeated here.
  • the solution provided in this embodiment allows users to directly perform operations on schedule cards that have been added to the desktop, such as editing the schedule in the schedule card, or removing the schedule card, without the user having to enter the schedule management application to perform operations, thereby reducing the complexity of user operations and improving user experience.
  • the content in the schedule card corresponding to the schedule is updated synchronously.
  • the schedule card corresponding to the schedule can become a blank card, or the schedule card displaying the schedule can be directly deleted.
  • the corresponding content in the schedule card corresponding to the schedule is updated synchronously.
  • the schedule card 2401 in a of Figure 27 becomes a blank card, and the user can add other schedules to the schedule card 2401.
  • the schedule card corresponding to the schedule is synchronously updated, that is, the schedule in the schedule management application and the content in the schedule card are automatically synchronized without the need for manual operation by the user, thereby improving the user experience.
  • the disclosed system, device and method can Implemented by other means.
  • the device embodiments described above are only schematic, for example, the division of the modules or units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.
  • Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple 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.
  • each functional unit in each embodiment of the present embodiment may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.
  • the technical solution of this embodiment is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can 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 each embodiment.
  • the aforementioned storage medium includes: flash memory, mobile hard disk, read-only memory, random access memory, disk or optical disk and other media that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Computer Interaction (AREA)
  • Data Mining & Analysis (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Calculators And Similar Devices (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

本申请提供了一种日程管理方法及装置，该方案支持用户标记重要日程，对于重要日程，重要日程的显示位置在普通日程之前，这样用户可以更直观地看到重要日程。而且，对于重要日程，显示日程的界面会展开显示该重要日程的信息，即界面上显示的重要日程的信息多于其他日程，从而使用户可以直观地获知重要日程的更多信息，提高用户体验。

Description

日程管理方法及装置
本申请要求于2022年09月30日提交中国国家知识产权局、申请号为202211230407.4、发明名称为“日程管理方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机技术领域，尤其涉及日程管理方法及装置。
背景技术
电子设备中可以实现日程管理的应用程序，支持用户创建或从其他应用程序中接入多个日程。不同的日程对用户而言重要程度不同，例如，都是会议日程，涉及重要内容的会议的重要程度通常高于普通例会。目前的日程管理应用中无法突出对用户而言重要的日程，可能会导致用户遗漏重要日程。
发明内容
有鉴于此，本申请提供了一种日程管理方法及装置，以解决上述至少部分问题，其公开的技术方案如下：
第一方面，本申请提供了一种日程管理方法，应用于电子设备，该方法包括：显示第一界面，第一界面包括第一日程卡片，第一日程卡片包括日程信息和日程优先级，日程优先级为无；响应于选择日程优先级为重要的操作，显示第二界面，第二界面包括第二日程卡片，第二日程卡片中的日程优先级为重要，第二日程卡片包含的日程信息多于第一日程卡片包含的日程信息。可见，采用该方案支持用户可以手动标记重要日程，界面上显示重要日程的信息多于其他日程，从而方便用户直观地获知重要日程的更多信息，提高用户体验。
在第一方面一种可能的实现方式中，日程信息包括日程标题；第二日程卡片还包括重要标识符，重要标识符位于日程标题之前。这样，用户在看到日程显示区域中的重要标识符后就能识别出该日程是重要日程。
在第一方面一种可能的实现方式中，日程优先级包括无、重要和忽略。可见，该方案将忽略合并至优先级的级别，显示日程的各个界面都包括优先级设置项，这样，用户很容易找到忽略的入口，方便用户操作。
在第一方面一种可能的实现方式中，响应于选择日程优先级为重要的操作，显示第二界面，包括：响应于点击第一日程卡片上的日程优先级的操作，在第一界面上显示优先级设置选项弹窗，优先级设置选项弹窗包括无级别选项、重要级别选项和忽略选项；响应于在优先级设置选项弹窗上选择重要级别选项的操作，显示第二界面。
在第一方面一种可能的实现方式中，在显示第一界面之前，该方法还包括：显示第三界面，第三界面包括第一按钮，第一按钮用于新建日程；响应于对第一按钮的操作，显示第一界面，第一界面还包括保存按钮；响应于选择日程优先级为重要的操作，显示第二界面，包括：响应于对第一界面上的日程优先级的操作，在第一界面上显示优先级设置选项弹窗，优先级设置选项弹窗包括无级别选项、重要级别选项和忽略选项；响应于在优先级 设置选项弹窗上选择重要级别选项的操作，显示第一界面，第一界面中的日程优先级更新为重要；响应于对保存按钮的操作，显示第二界面。可见，用户在新建日程页面即可标记重要的日程，这样，用户在创建新日程时就可以标记重要日程。
在第一方面一种可能的实现方式中，日程信息包括参与人，该方法还包括：当检测到日程优先级为重要的日程后，获取包含参与人的全部日程中的参与人；从全部日程的参与人中，选取符合预设条件的预设数量个参与人确定为推荐参与人，预设条件包括参与重要日程的频次大于预设阈值；生成推荐人列表，推荐人列表包括推荐参与人。可见，当检测到重要日程后，可以结合重要日程中的参与人从全部日程的参与人中选取符合一定条件的参与人作为重要参与人推荐给用户，以便用户可以直接从推荐人中添加重要参与人，减少了用户操作，提高了添加重要参与人的速度。
在第一方面一种可能的实现方式中，在生成推荐列表之后，该方法还包括：当检测到新的重要日程后，基于新的重要日程的参与人更新推荐人列表中的推荐参与人。可见，该方案可以根据重要日程的更新来更新推荐人列表，以便推荐人列表中的推荐人总是用户关注的重要参与人。
在第一方面一种可能的实现方式中，该方法还包括：显示第一重要参与人界面，第一重要参与人界面包括推荐人列表，推荐人列表包括至少一个参与人项，参与人项包括参与人信息和添加按钮；响应于对添加按钮的操作，显示第二重要参与人界面，第二重要参与人界面包括重要参与人列表，重要参与人列表包括重要参与人项，每个重要参与人项包括添加的参与人和移除按钮。
在第一方面一种可能的实现方式中，第一重要参与人界面还包括添加其他参与人按钮；在显示第一重要参与人界面之后，该方法还包括：响应于对添加其他参与人按钮的操作，显示第一选择参与人界面，第一选择参与人界面包括全部日程的第一参与人列表；响应于选择第一参与人列表中的任一参与人的操作，显示第三重要参与人界面，第三重要参与人界面包括重要参与人列表，重要参与人列表包括选择的参与人。可见，除可以添加推荐人列表中的参与人为重要参与人，还可以添加其他参与人为重要参与人，满足了用户的需求。
在第一方面一种可能的实现方式中，第一日程卡片还包括参与人设置项；在显示第一界面之后，该方法还包括：响应于对参与人设置项的操作，显示日程参与人界面，日程参与人界面包括第二参与人列表和编辑重要参与人按钮，第二参与人列表包括第一日程卡片包含的日程中的全部参与人；响应于对重要参与人按钮的操作，显示第二选择参与人界面，第二选择参与人界面包括参与人选择列表；响应于在参与人选择列表中选择参与人的操作，将选择的重要参与人标记为重要参与人，并更新重要参与人列表。这样，用户可以直接在某日程的参与人中设置某个参与人为重要参与人，满足用户的需求。
在第一方面一种可能的实现方式中，在添加重要参与人之后，该方法还包括：检测到非重要日程的参与人中包含重要参与人后，将非重要日程自动标记为重要日程，非重要日程是优先级为无的日程。这样，可以将包含重要参与人的非重要日程自动标记为重要日程，无需用户手动标记，减少了用户操作，提高了用户体验。
在第一方面一种可能的实现方式中，在显示第二界面之后，该方法还包括：显示设置弹窗，设置弹窗包括仅显示重要的第一设置项；响应于对第一设置项的操作，在显示日程 的各个界面中仅显示重要的日程。可见，在日程较多的日程，筛选重要日程并显示可以使用户关注重要日程，避免遗漏重要的事情。
在第一方面一种可能的实现方式中，在显示第一界面之后，该方法还包括：响应于对第一日程卡片的操作，显示第四界面，第四界面包括第一日程卡片中日程的日程优先级，日程优先级为无；确定未显示过第一提示弹窗后，在第四界面上显示第一提示弹窗，第一提示弹窗包括提示用户标记重要的日程的提示信息。
在第一方面一种可能的实现方式中，响应于对第一日程卡片的操作，显示第四界面，包括：响应于对第一日程卡片的点击操作，显示第四界面，第四界面显示第一日程卡片中日程的日程详情信息，日程详情信息包括标题、起止时间和日程优先级，日程优先级为无；或者，第一日程卡片还包括第二按钮；响应于对第一日程卡片的操作，显示第四界面，包括：响应于对第二按钮的点击操作，显示第四界面，第四界面包括第三日程卡片，第三日程卡片中显示的日程与第一日程卡片中显示的日程相同，且第三日程卡片显示的日程信息多于第一日程卡片显示的日程信息，第三日程卡片中的日程优先级为无；或者，响应于对第一日程卡片的操作，显示第四界面，包括：响应于对第一日程卡片的长按操作，显示第四界面，第四界面包括第四日程卡片，第四日程卡片显示的日程与第一日程卡片显示的日程相同，第四日程卡片以弹窗形式显示。
第二方面，本申请还提供了另一种日程管理方法，和桌面卡片设置项，日程优先级为重要；响应于对桌面卡片设置项的操作，在桌面上显示第一日程的第一桌面卡片，第一桌面卡片包括当前日期与第一日程的执行日期之间的天数。可见，该方案可以在桌面上添加重要日程的桌面卡片，该桌面卡片可以显示距离该重要日程的执行日期的天数，使用户可以一目了然地看到重要日程的剩余期限，进一步提醒用户执行重要日程或为重要日程做充分的准备。
在第二方面一种可能的实现方式中，在显示第一界面之前，该方法还包括：显示第二界面，第二界面包括新建日程按钮；响应于对新建日程按钮的操作，显示第一界面。可见，该方案支持在用户新建日程时就添加该日程的桌面卡片，避免用户反复操作。
在第二方面一种可能的实现方式中，在显示第一界面之后，该方法还包括：响应于对桌面卡片设置项的操作，且检测到已添加第一日程对应的桌面卡片后，在第一界面上显示第一弹窗，第一弹窗包括取消按钮、确定按钮和提示用户是否重复添加桌面卡片的信息；响应于对确定按钮的操作，添加第一日程的第二桌面卡片，第二桌面卡片与第一桌面卡片的内容相同。可见，该方案支持用户重复添加某日程的桌面卡片，例如，在不同的桌面页面上添加同一日程的桌面卡片，从而使用户在各个桌面页面上都可以看到该日程，提高了桌面卡片的呈现率，进而使用户更容易关注到该日程。
在第二方面一种可能的实现方式中，该方法还包括：显示第三界面，第三界面包括空白桌面卡片和第一按钮，空白桌面卡片包括添加日程按钮；响应于对第一按钮的操作，在桌面上显示空白桌面卡片；响应于对添加日程按钮的操作，显示选择日程界面，选择日程界面包括可选择的日程；响应于在选择日程界面选择日程的操作，显示桌面，桌面包括第三桌面卡片，第三桌面卡片包括已选择的日程的信息，以及当前日期与已选择的日程的执行日期之间的天数。
第三方面，本申请还提供了一种电子设备，电子设备包括：一个或多个处理器、存储器和触摸屏；存储器用于存储程序代码；处理器用于运行程序代码，使得电子设备实现第一方面和第二方面中任一项的日程管理方法。
第四方面，本申请还提供了一种计算机可读存储介质，其上存储有指令，当指令在电子设备上运行时，使得电子设备第一方面和第二方面中任一项的日程管理方法。
第五方面，本申请还提供了一种计算机程序产品，其上存储有执行，当计算机程序产品在电子设备上运行时，使得电子设备第一方面和第二方面中任一项的日程管理方法。
应当理解的是，本申请中对技术特征、技术方案、有益效果或类似语言的描述并不是暗示在任意的单个实施例中可以实现所有的特点和优点。相反，可以理解的是对于特征或有益效果的描述意味着在至少一个实施例中包括特定的技术特征、技术方案或有益效果。因此，本说明书中对于技术特征、技术方案或有益效果的描述并不一定是指相同的实施例。进而，还可以任何适当的方式组合本实施例中所描述的技术特征、技术方案和有益效果。本领域技术人员将会理解，无需特定实施例的一个或多个特定的技术特征、技术方案或有益效果即可实现实施例。在其他实施例中，还可在没有体现所有实施例的特定实施例中识别出额外的技术特征和有益效果。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本申请实施例提供的一种电子设备的结构示意图；
图2-1是本申请实施例提供的一种手动标记重要日程的界面示意图；
图2-2是本申请实施例提供的另一种新建日程界面的示意图；
图3是本申请实施例提供的一种日程详情视图的界面示意图；
图4是本申请实施例提供的另一种手动标记重要日程的界面示意图；
图5是本申请实施例提供的又一种手动标记重要日程的界面示意图；
图6是本申请实施例提供的再一种手动标记重要日程的界面示意图；
图7是本申请实施例提供的一种关于重要日程的新功能引导的界面示意图；
图8是本申请实施例提供的一种确定重要参与人的规则示意图。
图9是本申请实施例提供的一种关于重要参与人的新功能引导的界面示意图；
图10是本申请实施例提供的一种添加重要参与人的界面示意图；
图11是本申请实施例提供的一种重要参与人界面的示意图；
图12是本申请实施例提供的另一种添加重要参与人的界面示意图；
图13是本申请实施例提供的又一种添加重要参与人的界面示意图；
图14是本申请实施例提供的一种自动标记重要日程的示意图；
图15是本申请实施例提供的一种移除重要参与人的界面示意图；
图16是本申请实施例提供的另一种重要参与人界面的示意图；
图17是本申请实施例提供的又一种重要参与人界面的示意图；
图18是本申请实施例提供的一种筛选重要日程的界面示意图；
图19是本申请实施例提供的另一种筛选重要日程的界面示意图；
图20是本申请实施例提供的又一种筛选重要日程的界面示意图；
图21是本申请实施例提供的一种在桌面上添加日程卡片的界面示意图；
图22是本申请实施例提供的一种日程卡片显示内容的示意图；
图23是本申请实施例提供的一种日程卡片样式的示意图；
图24是本申请实施例提供的另一种在桌面上添加日程卡片的界面示意图；
图25是本申请实施例提供的又一种在桌面上添加日程卡片的界面示意图；
图26是本申请实施例提供的一种选择日程界面的界面示意图；
图27是本申请实施例提供的一种日程卡片操作的界面示意图。
具体实施方式
本申请说明书和权利要求书及附图说明中的术语“第一”、“第二”和“第三”等是用于区别不同对象，而不是用于限定特定顺序。
在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
用户可以在同一个日期内创建多个不同时间段的日程，例如，8:00～9:00：日程1，10:00～11:00：日程2，13：00～14:30：日程3，相关技术中，通常按照多个日程的起始时间的先后顺序对多个日程进行排序，显示界面内可以显示的日程有限，这种显示日程的方式可能导致重要日程排在后面，需要用户手动向上滑动显示界面才能看到重要日程的信息。此外，不同日程显示的信息基本相同，无法突出重点信息，例如，对于会议日程和信用卡还款日程都显示开始时间和结束时间。对用户而言会议日程的重要程度高于信用卡还款，但是，显示的日程信息并未突出会议日程的重要性，也未显示会议日程的更多信息，即，对于用户重要的日程与普通日程，显示的信息及提示功能均无差别，用户只能主观分辨哪些是重要日程，这样可能导致用户遗漏重要日程。
为了解决上述技术问题，本申请的发明人提供了一种日程管理方法，支持用户标记重要日程，对于重要日程，重要日程的显示位置在普通日程之前，这样用户可以更直观地看到重要日程。而且，对于重要日程，显示日程的界面会展开显示该重要日程的信息，即界面上显示的重要日程的信息多于其他日程，从而使用户可以直观地获知重要日程的更多信息，提高用户体验。
可以应用本申请实施例提供的日程管理方法的电子设备可以是手机、平板电脑、桌面型、膝上型、笔记本电脑、超级移动个人计算机(Ultra-mobile Personal Computer，UMPC)、手持计算机、上网本、个人数字助理(Personal Digital Assistant，PDA)、可穿戴电子设备、智能手表、增强现实技术(augmented reality，AR)设备、虚拟现实(virtual reality，VR)设备等。应理解，本申请实施例涉及的终端设备具有设置日程的功能即可，本申请的实施例对终端设备所采用的具体技术和具体设备形态不做限定。
图1是本申请实施例提供的一种电子设备的结构示意图。如图1所示，电子设备可以 包括处理器1、存储器2、显示屏3、触摸传感器4、电源管理模块5。
可以理解的是，本实施例示意的结构并不构成对电子设备的具体限定。在另一些实施例中，电子设备可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件的组合实现。
处理器1可以包括一个或多个处理单元，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中。例如，在本申请实施例中，处理器1可以对日程进行管理。
存储器2用于存储计算机可执行程序代码和数据，其中，该程序代码包括指令。处理器1通过执行存储在存储器2中的程序指令，对日程进行管理。
显示屏3用于显示图像，视频等，显示屏还可以显示一系列图形用户界面(graphical user interface，GUI)，这些GUI都是该电子设备的主屏幕。一般来说，电子设备的显示屏3的尺寸是固定的，只能在该电子设备的显示屏3中显示有限的控件。控件是一种GUI元素，它是一种软件组件，包含在应用程序中，控制着该应用程序处理的所有数据以及关于这些数据的交互操作，用户可以通过直接操作(direct manipulation)来与控件交互，从而对应用程序的有关信息进行读取或者编辑。一般而言，控件可以包括图标、按钮、菜单、选项卡、文本框、对话框、状态栏、导航栏、Widget等可视的界面元素。
触摸传感器4，也称“触控器件”。触摸传感器4可以设置于显示屏3，由触摸传感器4与显示屏3组成触摸屏，也称“触控屏”。触摸传感器4用于检测作用于其上或附近的触摸操作。触摸传感器可以将检测到的触摸操作传递给应用处理器，以确定触摸事件类型。可以通过显示屏3提供与触摸操作相关的视觉输出。在另一些实施例中，触摸传感器4也可以设置于电子设备的表面，与显示屏3所处的位置不同。
下面以电子设备是手机为例对本申请实施例进行阐述。该手机具有设置日程的功能，可以支持用户在日历应用上设置日程提醒。
此外，管理日程的应用程序可以包括日历应用程序和待办事项应用程序等，本申请实施例可以应用于可以管理日程的任意应用程序。应理解，本文中的管理日程可以包括创建新日程，修改日程的内容，以及删除日程等所有与日程相关的操作，本申请对管理日程的范围不作限定。
在本申请实施例中，用户可以在新建日程时手动标记为重要日程，或者，对已有日程手动标记为重要日程。
下面结合附图2-1对用户在创建新日程时手动标记重要日程的过程进行说明。
图2-1是本申请实施例提供的一种手动标记重要日程的界面示意图，本实施例以在日历应用程序中创建新日程为例进行说明，应理解，也可以在其他日程管理应用程序中创建新的日程，本申请对此不做限定。
当手机检测到用户点击日历应用程序的图标时，可以显示图2-1的a所示的界面10，该界面10为日历的月视图界面，月视图用于显示整个月份的所有日期，该示例中显示整个9月份的所有日期。在月视图中，默认突出显示当前日期，当然该界面还可以突出显示用户选择的其他日期，如用户可以点击指示其他日期的数字图标选中该日期。在一示例中，通过突出显示标识突出显示指定日期，如突出显示标识为直径大于数字图标直径的圆11。如图2-1的a所示，该示例中，当前日期是2022年9月10。
用户可以通过点击如图2-1的a所示的图标12创建当前突出显示的日期下的新日程，该示例中，用户点击图标12创建的是2022年9月10日的日程。当然，用户也可以点击图2-1的a所示的其他数字图标选择其他日期，进一步点击图标12创建该其他日期的日程。
在一示例中，用户点击图标12后，进入图2-1的b所示的新建日程界面，该界面供用户填写新日程的详细信息。本实施例中，如图2-1的b所示，新建日程界面包括优先级设置栏24，还包括标题设置栏21、地点设置栏22、起止时间设置栏23、提醒设置栏25。
优先级设置栏24包括优先级设置项241，用户通过点击优先级设置项241设置该新建日程的优先级，进入图2-1的c所示的界面30，如图2-1的c所示，该界面上显示优先级设置卡片31，该卡片上显示所有可设置的级别，如“重要”、“忽略”和“无”。“重要”表示该日程是重要日程，即用户重点关注的日程，“忽略”表示该日程可以忽略、用户无需关注的日程，“无”表示无需重点关注也不能忽略的日程。
例如，在一示例中，图2-1的c所示的界面30在图2-1的b所示的界面上增加一层灰度图层，进一步在灰度图层的上层显示优先级设置卡片31，这样，可以突出显示优先级设置卡片31，使得优先级设置卡片31更醒目，使用户更容易关注到优先级设置卡片31。当然，在其他实施例中，也可以直接在图2-1的b所示的界面上直接显示优先级设置卡片31。
用户可以选择任一级别后的选择按钮，选中该级别。在一示例中，优先级级别的选择按钮样式是单选按钮，即用户可以点击处于未选中状态的按钮，使该按钮变为选中状态，与此同时，原本处于选中状态的按钮变为非选中状态。例如，图2-1的c中“重要”级别对应的选择按钮当前为非选中状态，用户单击该按钮后变为选中状态，与此同时，“无”级别对应的选择按钮由选中状态变为非选中状态。
此外，优先级设置卡片31的位置还可以位于界面30的其他位置。本申请实施例对优先级设置卡片的大小、样式、显示位置，以及优先级设置卡片中选择按钮的样式不做限定。
在另一示例性实施例中，如图2-2所示，示出了本申请实施例提供的另一种新建日程界面的界面示意图。与图2-1的b所示的新建日程界面的不同之处在于，图2-2所示新建日程界面还包括参与人卡片26，该参与人卡片26可以包括邀请人选项261和参与人选项262。
用户通过操作邀请人选项261添加日程的邀请人，例如，该日程是线上会议的日程时，通过邀请人选项添加会议邀请人。
用户可以通过操作参与人选项262添加日程的其他参与人。在一示例中，在用户添加邀请人后，参与人选项可以默认包括该邀请人。
此外，本示例的新建日程界面还可以包括会议链接栏27，在一种可能的实现方式中，会议链接栏可以与地点设置栏复用，如用户点击地点设置栏可以粘贴会议链接，或者，也可以输入日程的位置。
用户在图2-1的c所示的界面选择“重要”级别后，跳转至图2-1的d所示的界面，如图2-1的d所示，该界面中的优先级设置项241显示“重要”级别，用户填写完新建日程界面中的其他信息后，点击完成图标40后保存新建的日程，并跳转至图2-1的e所示的月视图的界面50。
用户可以通过上滑图2-1的a所示的月视图界面中显示日期的区域13，折叠日期显示区域，即日期显示区域由图2-1的a所示的13变为如图2-1的e所示的区域51，日期显示 区域51仅显示包含当前突出显示的日期所在行，从而增大日期显示区域下方的日程显示区域52的面积。
如图2-1的e所示，日程显示区域52用于显示当前突出显示的日期(本示例是2022年9月10日)下的全部需提醒用户的日程，包括节日、节气和其他日程。本示例中，节日日程的显示位置位于日程显示区域52的顶部，即节日日程的显示位置在其他日程之前。在其他实施例中，节日日程的显示位置可以在日程显示区域52的底部，即其他日程的显示位置在节日日程之前。应理解，当该日期下的日程数量较多时，无法全部显示在日程显示区域52内，可以通过向上滑动日程显示区域52显示未显示的日程。
在本申请实施例中，对于优先级为重要的日程，在日程显示区域52内展开显示该日程的信息，以便用户可以直接获知该日程的更多信息。对于非重要日程折叠显示，节省日程显示区域的显示面积。本示例中，如图2-1的e所示，在卡片56中展开显示“设计方案研讨会”的重要日程，而在卡片57中折叠显示“火车出行”的非重要日程(或称为普通日程)。
如图2-1的e所示，卡片56展开显示的重要日程是会议日程，展开显示的日程信息可以包括日程标题53，日程起止时间“早上8:00～上午9:30”，会议邀请人、参与人、帐户、优先级55。
在一种可能的实现方式中，重要日程的标题中还包括用于表示日程重要性的重要标识符，本示例中重要标识符为“！”，当然，在其他实施例中，重要标识符还可以是其他符号，本申请对此不做限制。可选地，对于线上会议，展开显示的日程信息还可以包括“加入会议”的链接按钮。
可见，用户无需对展开显示的卡片进行任何操作即可对该日程的重要信息一览无余，因此，提高了用户获取重要日程的详细信息的效率。
此外，卡片56中，日程标题旁还可以包括折叠按钮54，用户可以通过点击折叠按钮54，该日程由展开显示状态变为折叠显示状态。可以理解的是，折叠显示状态下，可以仅显示该日程的标题、起止时间等非常重要的信息。如图2-1的e所示，卡片57为折叠显示状态，显示的内容包括日程标题、起止时间、地点，以及展开按钮58。用户可以通过点击展开按钮58，使该日程由折叠显示状态变为展开显示状态，从而显示“火车出行”日程的更多信息，如座位号等。
对于重要日程，在各场景中均默认为展开显示日程详细信息。例如，如图2-1的f所示的日程视图界面60，日程显示区域61从上至下依次显示三个日程的信息，其中，设计方案研讨会议为重要日程，默认展开显示该日程的详细信息。火车出行和酒店入住两个日程为非重要日程，折叠显示此两个日程的信息。
在一种可能的实现方式中，可以通过点击图2-1的a所示的“日程”按钮14进入日程视图界面60。
如图2-1的e所示，“忽略”作为日程的一个优先级包含在优先级卡片31中，即，本申请实施例，将“忽略”从日程详情界面的更多选项合并至日程的优先级。
当用户点击如图3的a所示的日程详情界面610中的控件611后，跳转至图3的b所示的界面，而图3的b所示的界面在日程详情界面610上显示更多选项卡片612，包括分享和删除选项，即，本申请实施例中的更多选项卡片612中不包括“忽略”选项。需要说 明的是，用户点击图2-1的e或f中标题为“设计方案研讨会议”的日程后，进入日程详情界面610。可见，将“忽略”合并至优先级后，用户可以直接在图2-1的e或f所示的界面上显示的优先级设置项将日程设置为“忽略”等级，缩短了用户进入“忽略”功能的路径，简化了用户的操作，提高了用户体验。
图2-1所示过程是在创建新日程场景下手动标记日程为重要日程的过程，对于已有日程也可以通过手动标记方式标记为重要日程。例如，已有日程可以是已创建的日程，且未设置优先级，或者，还可以是从其他应用程序中导入的日程。
图4是本申请实施例提供的另一种标记重要日程过程的界面示意图，本实施例以日历的月视图界面显示的日程信息为例，说明对于已有日程手动标记为重要日程的过程。
如图4的a所示，日历的月视图界面100中处于展开显示状态的“设计方案研讨会议”日程的当前优先级是“无”，用户可以点击按钮101(如下拉菜单按钮)，跳转至图4的b所示的界面，该界面包括优先级菜单102，本示例中，优先级菜单102包括“重要”、“忽略”、“无”三个级别。当前优先级(或选中级别)所在行的上层增加灰度图层，从而突出显示日程的当前级别(或选中级别)如图4的b所示，当前优先级为“无”所在行为灰度。用户可以选择优先级菜单102中非突出显示的级别，本实施例中，用户可以选择“重要”级别，将该日程手动标记为重要日程，并跳转至图4的c所示的界面。
对比图4的c和a所示的界面可知，将“设计方案研讨会议”的日程标记为重要日程后，该日程的优先级设置项104中显示“重要”级别，以及，该日程的标题105中还包括重要标识符“！”。
本申请实施例还提供了其他场景中手动将已有日程标记为重要日程的界面示意图。图5示出了在日程详情页面将日程标记为重要日程的界面示意图。
在一种可能的实现方式中，用户点击图2-1的e中的日程卡片56可以跳转至如图5的a所示的日程详情界面200，该界面中的优先级设置项201显示当前优先级为“无”。用户可以通过点击按钮202选择其他优先级。用户点击按钮202后跳转至图5的b所示的界面，该界面在日程详情界面200的上层增加灰度图层，进一步在灰度图层的上层显示优先级设置卡片203，这样，可以使优先级设置卡片203更醒目。此处的优先级设置卡片203与图2-1的c所示界面中的优先级设置卡片31相同，此处不再赘述。本实施例中，用户点击优先级设置卡片203中的“重要”级别对应的按钮204，跳转至图5的c所示的日程详情界面，该界面中的优先级项205显示当前级别为“重要”，而且，日程标题206中包含重要标识符“！”。
参见图6，示出了本申请实施例提供的又一种手动标记重要日程的界面示意图，本实施例以日程快捷操作界面为例说明手动标记重要日程的过程。
在一种可能的实现方式中，用户可以通过长按图6的a中的日程显示卡片301进入图6的b所示的界面，该界面显示弹窗302，弹窗302用于显示日程信息，如日程标题、起止时间、优先级选项等。优先级选项包括日程的当前级别和按钮303，用户点击按钮303后跳转至图6的c所示的界面，该界面在弹窗302上层还包括优先级菜单304，用户点击优先级菜单304中的“重要”选项，跳转至图6的d所示的界面，该界面的弹窗302中显示的日程的优先级项306为“重要”，而且，日程标题305中包含重要标识符“！”。
本实施例中的优先级菜单304与图4的b所示的优先级菜单102相同，此处不再赘述。
此外，如图6的b、c、d所示的界面中，弹窗302的下方还包括卡片307，卡片307包括“分享”和“删除”按钮。当用户点击“分享”按钮308后，跳转至图6的e所示的分享预览界面401，该界面包括分享按钮403，进一步地，用户点击分享按钮403可以将该日程的信息转发给其他人。此外，如果用户点击卡片307中的“删除”按钮，则从日历应用中删除该日程的信息。
当用户未使用过重要日程设置功能时，日程管理的应用程序会提示用户可以将对用户而言重要的日程设置为重要日程。图7示出了本申请实施例提供的一种设置重要日程的新功能引导的界面示意图。
例如，如图7的a所示，月视图界面上包括卡片70，该卡片处于折叠显示状态，即仅显示日程的部分信息，如，标题、起止时间和地点。
在一种场景中，若用户点击卡片70中的展开按钮701，跳转至图7的b所示的界面，该界面中卡片70处于展开显示状态，该状态下可以显示提示弹窗72，该提示弹窗72用于引导用户使用手动标记日程为重要日程的功能。在一示例中，提示弹窗72中的文字信息可以包括“标记重要的日程，查看更多日程信息”。在一示例中，提示弹窗72可以位于界面90的上层，此外，当用户点击该界面上除提示弹窗72外的任意位置后，提示弹窗72消失。
在本示例中，提示弹窗72位于优先级项73的上方，使得用户可以直观地获知通过操作优先级73标记重要的日程。
在另一种场景中，若用户长按图7的a中的卡片70，跳转至图7的c所示的快捷操作界面80，该界面包括日程卡片81，日程卡片81包括位于优先级项82上方的提示弹窗83，该提示弹窗83用于显示引导用户使用手动标记重要的日程的功能。
在又一种场景中，若用户点击(单击)图7的a中的卡片70，跳转至图7的d所示的日程详情界面90，该界面包括卡片91，卡片91用于显示优先级设置项，在卡片91的上方显示提示弹窗92，此外，提示弹窗92可以位于界面90的上层。
图7的b、c、d分别示出了不同场景下显示新功能提示弹窗的界面示意图，不同场景中的提示弹窗的作用相同，即引导用户使用手动标记重要的日程，提示弹窗的位置、大小和样式及所显示的内容可以根据不同显示场景调整，本申请对此不做限定。
此外，在一种可能的实现方式中，可以仅在首先触达的界面上显示上述的提示弹窗，其他场景中不再重复提示，例如，响应用户的操作，首次进入的是图7的b所示的场景，则在图7的b所示的界面上显示提示弹窗72。当进入图7的c和d所示的场景时，不再显示提示弹窗。
在一种可能的实现方式中，可以从所有日程中的参与人中选出符合一定条件(如参与人出现在重要日程中的频次大于预设阈值)的参与人作为重要参与人推荐给用户，或者，用户还可以自动添加重要参与人。有重要参与人后，可以将参与人包含重要参与人的日程设置为重要日程，无需用户手动标记，进一步提高用户体验。
参见图8，示出了本申请实施例提供的一种确定重要参与人的规则示意图。
在一种可能的实现方式中，如图8所示，其他参与人是所有日程中出现过的参与人，本示例中包括Y个其他参与人。从这Y个其他参与人中选出符合预设条件的参与人作为推 荐人(即，用户可能会关注的参与人)，例如，本示例中推荐人的数量可以是X个，其中，X＜Y。此外，还可以限定X的最大值，如X≤5，即最多向用户推荐5个参与人。进一步，用户可以选择推荐人列表中的参与人作为重要参与人。当然，用户也可以直接选择其他参与人中的参与人作为重要参与人。
在本申请实施例中，推荐人列表中的参与人会根据用户的添加或删除重要参与人的操作更新。
在本申请的一个实施例中，用户使用标记重要日程的功能后，管理日程的应用程序会将统计所有重要日程中出现过的参与人，并选出符合预设条件的参与人作为推荐人，当推荐人列表不为空时，提示用户添加重要参与人。
在本申请的其他实施例中，当管理日程的应用程序检测到推荐人列表中的参与人全部更新后，也可以再次提示用户添加新的重要参与人。
参见图9，示出了本申请实施例提供的一种提示用户添加重要参与人的提示框的界面示意图。
在一示例中，如图9所示，在日历应用程序的月视图界面701上显示提示框702，该提示框702用于引导用户使用重要参与人功能，换言之，提示用户添加重要参与人，进一步提高用户体验。进一步，可以根据用户添加的重要参与人自动标记重要日程。
在一示例中，如图9所示，提示框702可以位于日期显示区域705与日程显示区域706之间，本示例中，提示框702可以与日期显示区域及日程显示区域位于同一图层。当然，在其他示例中，提示框702还可以位于日期显示区域及日程显示区域所在图层的上层，如提示框702为弹窗。例如，如图9所示，提示框702包括用于提示用户的文本信息，如“为您推荐重要参与人，根据您的重要参与人智能标记日程，不要错过重要的事情”，当然，提示框702中显示的文本信息还可以是其他内容，本申请对此不做限定。此外，提示框702还包括“立即添加”按钮703和关闭按钮704。用户点击“立即添加”按钮703后，可以跳转至添加重要参与人的界面。用户点击关闭按钮704后，关闭提示框702，即提示框702消失。
下面将结合图10介绍添加重要参与人的过程。
如图10的a所示，用户点击更多按钮800后，显示更多选项卡片801，该更多选项卡片801中包括“设置”项802。进一步，用户点击该“设置”项802后，跳转至图10的b所示的界面803，该界面包括重要参与人设置卡片804，用户点击重要参与人设置卡片804中的按钮805跳转至图10的c所示的重要参与人界面。
如图10的c所示，重要参与人界面包括推荐人列表806，推荐人列表806中包括推荐的参与人设置项807，例如，每个参与人设置项807包括参与人的信息(如姓名及帐户等)和“添加”按钮808。用户点击“添加”按钮808后，将该参与人添加至重要参与人列表中。例如，本示例中，用户点击参与人“Xiaomin”和“Long”对应的参与人项中的“添加”按钮后，跳转至图10的d所示的界面809。
如图10的d所示，界面809包括重要参与人列表810，该重要参与人列表可以位于推荐人列表813的上方。重要参与人列表810中包括用户添加的参与人“Xiaomin”和“Long”，每个重要参与人设置项811包括参与人的信息(如姓名及帐户等)及“移除”按钮812。用 户可以点击“移除”按钮812可以将已添加的重要参与人从重要参与人列表中删除。
在本申请的一个实施例中，不限定重要参与人的数量，即不限制重要参与人列表中的参与人的数量。
如图11的a所示，当重要参与人列表中的重要参与人的数量较多，导致显示重要参与人列表的窗口901无法显示全部重要参与人，此种情况下，会在窗口901显示“更多”按钮902，点击该“更多”按钮902跳转至图11的b所示的界面，该界面中采用显示面积更大的窗口903显示重要参与人列表。可以理解，用户通过上下滑动窗口903中显示的页面从而使窗口903中显示的重要参与人变更，例如，向上滑动窗口903中的重要参与人列表时，可以显示该图中重要参与人“Wind”之后的重要参与人。
此外，如图11的b所示，窗口903的底部包括“收起”按钮904，用户点击“收起”按钮904后，从图11的b所示的界面跳转至图11的a所示的界面，即点击“收起”按钮904后，显示重要参与人的窗口903变为显示面积更小的窗口901。
在一种应用场景中，用户想要添加的重要参与人未包含在推荐人列表中，此种情况下，可以通过“添加其他参与”选择其他参与人作为重要参与人。参见图12，示出了本申请实施例提供的另一种添加重要参与人的界面示意图。
如图12的a所示，重要参与人界面1000包括“添加其他参与人”按钮1002，本示例中，按钮1002位于推荐人列表1001的下方。在本申请的其他实施例中，按钮1002还可以位于其他位置，本申请对此不做限定。用户点击按钮1002后跳转至图12的b所示的选择参与人的界面1003。
如图12的b所示，界面1003用于显示全部参与人列表，该列表中的每个参与人选项包括参与人的信息及选择按钮1004，用户可以点击选择按钮1004选中该参与人。本示例中，用户点击参与人“Dannle”对应的选择按钮1004后，跳转至图12的c所示的界面，该界面中参与人“Dannle”对应的选择按钮1004变为已选中状态，本示例中，“√”表示已选中，当然，在其他实施例中，还可以采用“○”中包括“·”来表示已选中。
如图12的c所示，选择参与人列表界面1003包括按钮1006、关闭按钮1007和搜索框1008。按钮1006为表示已完成的保存按钮，本示例中，用户选择参与人“Dannle”为重要参与人后，点击按钮1006后保存当前选择结果，即保存“Dannle”为重要参与人的结果。用户点击图12的c所示的按钮1006后，跳转至图12的d所示的界面。若用户点击关闭按钮1007则关闭界面1003，可以退回至图12的a所示的界面。若全部参与人列表中的参与人很多，用户可以在搜索框1008中输入要搜索的参与人的至少部分名字或首字母等，即可搜索到相应的参与人。此外，在图12的c所示的界面的底部还包括“全选”按钮，用户点击该“全选”按钮后全部参与人列表中的所有参与人都为选中状态。
如图12的d所示，为重要参与人界面1009，与图10的d所示的界面相同，界面1009包括用于显示重要参与人的窗口1010，窗口1010用于显示重要参与人的信息项，以及操作按钮，如“移除”按钮。用户点击“移除”按钮可以从重要参与人列表中删除该参与人。
此外，在本申请一示例性实施例中，参与人以参与人的帐户维度进行维护，同一个人在不同应用中的账户会被视为不同的参与人，如图12的b所示，包括两个参与人姓名都是“AlisaLee”，但帐户不同，作为两个不同的参与人维护，即图12的b中的1005和1012 对应的两个参与人。
在另一种应用场景中，已有日程中包含参与人，例如会议日程，用户可以直接将日程中的参与人设置为重要参与人。
图13是本申请实施例提供的又一种添加重要参与人的界面示意图。
图13的a所示的界面是日程详情界面1100，该界面包括参与人卡片1101，参与人卡片1101中包括该日程的全部参与人，此外，该卡片还包括按钮1102。用户点击按钮1102后跳转至图13的b所示的参与人界面1104。
如图13的b所示，参与人界面1104包括日程的全部参与人的信息。本示例中，该日程为线上会议日程，线上会议通常包括一个邀请人，其他人为参与人。如，邀请人是指创建线上会议的人，此人可以邀请其他人参与其建立的线上会议。在本申请一实施例中，可以默认邀请人为重要参与人，并在该参与人项中包含重要标识符，例如，如图13的b所示，邀请人项1106包括邀请人的姓名“Xiaomin”及帐户等信息，11061所示为重要标识符，本示例中的重要标识符是“VIP”。
如图13的b所示，1107所示的区域为日程的其他参与人，用户可以上下滑动此区域，以更新该区域所显示的参与人，例如，用户向上滑动，则该区域当前显示的参与人会跟随向上滑动，与此同时，显示参与人“Long”以下的参与人。图13的b所示的界面1104的顶部还包括返回按钮1105，用户点击该按钮1105返回至图13的a所示的界面。
在本申请一个实施例中，图13的b所示的参与人界面1104的底部还包括“编辑重要参与人”的按钮1108，用户点击按钮1108后，跳转至图13的c所示的选择参与人的界面1112。
如图13的c所示，选择参与人的界面1112包含用于显示邀请人的区域1114，以及用于显示其他参与人的区域1115，区域1114和1115中的每个参与人显示项都包括选择按钮1113。
在本申请实施例中，邀请人默认是重要参与人，因此，邀请人显示项中的选择按钮1113默认为选中状态，本示例中，邀请人“Xiaomin”的显示项中的选择按钮1113默认为选中状态。此外，用户选择其他参与人“Lee”作为重要参与人，则该参与人显示项的选择按钮1113变为选中状态。在一示例中，选择按钮可以是“○”，选中状态可以采用“√”，当然，在其他实施例中，选中状态还可以采用其他符号，同理，选择按钮也可以采用其他样式，本申请对此不做限定。
如图13的c所示，在邀请人显示区域上方还包括区域1109，该区域1109包括完成按钮1110和关闭按钮1111，以及还可以包括已选择的重要参与人的数量。用户点击完成按钮1110后，跳转至图13的d所示的界面，点击关闭按钮1111后，返回图13的b所示的界面。
与图13的a所示的日程详情页界面相比，图13的d所示的界面是日程详情页界面除包括参与人显示项1205之外，还包括重要参与人显示项1206。参与人显示项1205用于显示该日程的所有参与人。重要参与人显示项1206用于显示该日程涉及的重要参与人，例如，本示例中，重要参与人为“Xiaomin”和“Lee”。
此外，参与人显示项1205还包括按钮1209，用户点击该按钮1209跳转至图13的e所示的参与人界面，该界面包括邀请人显示区域1201和其他参与人显示区域。邀请人显示 区域1201用于显示该日程涉及的邀请人。其他参与人显示区域用于显示该日程涉及的除邀请人外的参与人。在本申请的一个实施例中，邀请人显示项默认包括重要标识符1203，如“VIP”，以及，用户选中的其他参与人“Lee”的显示项1202也包括重要标识符1203。此外，图13的e所示的界面中，在邀请人显示区域的上方还包括返回按钮1204，用户点击该返回按钮1204后，跳转至图13的d所示的界面，即日程详情页界面。
用户编辑重要参与人后，管理日程的应用程序更新重要参与人列表，当检测到非重要日程的参与人中包含重要参与人时，可以将该非重要日程自动标记为重要日程可见，此过程无需用户手动操作，进一步提高了用户体验。例如，图13的d所示的界面，日程标题1208中包括重要标识符，如“！”，以及，优先级选项1207中显示的优先级为“重要”。
同理，其他视图界面同样包括标识在该日程的其他视图界面中，例如，如图14所示的月视图界面1301，识别出“设计方案研讨会议”的非重要日程的参与人中包括重要参与人“Lee”，则自动将该非重要日程标记为重要日程，如图14所示，该界面中的日程标题1302中包括重要标识符，以及，优先级显示项显示该日程的优先级是“重要”。本实施例不再赘述自动标记为重要日程后，其他视图的变化项。
此外，前述的重要日程的内容同样适用于自动标记为重要的日程，此处不再赘述。
图11～图13为本申请实施例提供的添加重要参与人的过程，反之，可以删除已添加至重要参与人列表中的重要参与人。
参见图15，示出了本申请实施例提供的一种删除重要参与人的界面示意图。
如图15的a所示，重要参与人的界面1400包括重要参与人列表，该列表中每个参与人显示项包括“移除”按钮1401，用户可以通过点击该“移除”按钮1401，从重要参与人列表中删除该参与人。
在一种可能的实现方式中，用户点击图15的a所示的“移除”按钮1401后，跳转至图15的b所示的界面1402，该界面在图15的a所示的界面1400的上层增加灰度图层，进一步，在该灰度图层的上层显示提示窗1403，这样可以突出显示提示窗1403，从而引导用户查看提示框1403中的内容。
如图15的b所示，提示窗1403可以包括移除重要参与人后可能引起包含该参与人的日程状态变化，以及，可以再次添加的问题提示信息，以及“取消”按钮、“移除”按钮1404。用户点击“取消”按钮后返回至图15的a所示的界面，用户点击“移除”按钮后跳转至图15的c所示的界面。本示例中，重要参与人列表中只有一个参与人，当用户将此参与人删除后，重要参与人列表变为空。因此，如图15的c所示，重要参与人界面1405中不包括重要参与人列表，而只显示推荐人列表1406。
在一种应用场景中，推荐人列表中不包含参与人，即推荐人列表为空。如图16所示，此种场景下，当用户点击图16的a所示的界面1600中的重要参与人设置项中的按钮1601后，不显示推荐人列表。其中，图16的a所示的界面1600与图10的b所示的界面803中包含的设置项相同，而且，进入该界面的方式也相同，此处不再赘述。
在一种情况下，管理日程的应用中的所有日程都不是重要日程，即不包含重要日程，此种情况下，用户点击按钮1601后跳转至图16的b所示的界面1603，该界面包括显示重要参与人的文本提示信息1604，该提示信息用于提示添加重要参与人功能及添加方式。此 外，该界面还包括“了解更多”按钮1605，用户点击“了解更多”按钮1605后，可以跳转至详细介绍“重要参与人”功能的界面，例如，玩机技巧应用中关于“重要参与人”的功能介绍页。
在另一种情况下，管理日程的应用中包括重要日程，此种情况下，用户点击按钮1601后跳转至图16的c所示的界面1606，该界面包括“关注重要参与人”的文本提示信息1607，该文本提示信息用于提示用户添加重要参与人，含有重要参与人的日程默认为重要日程的提示信息。而且，图16的c所示的界面还包括“添加其他参与人”按钮1608，用户点击“添加其他参与人”按钮1608后，可以跳转至图12的b所示的界面。与图16的b所示的界面相同，图16的c所示的界面也包括“了解更多”按钮。
应理解，本实施例中，用户添加和删除重要参与人的操作会影响推荐人列表中的参与人。
此外，如图17的a所示，重要参与人界面1500还包括详情按钮1501，用户点击详情按钮1501后，跳转至图17的b所示的界面1502，该界面在图17的a所示的界面上层增加了灰度图层，进一步在灰度图层上层显示提示窗1503，该提示窗1503用于显示重要参与人功能的信息，此外，该提示窗还包括“了解更多”按钮1504。用户点击“了解更多”按钮1504后显示的界面与点击图16的b和c中的“了解更多”按钮后所显示的界面相同，此处不再赘述。
为了方便用户查看重要日程的信息，还可以通过设置仅显示重要日程。参见图18，示出了本申请实施例提供的一种筛选重要日程的界面示意图。
如图18的a所示，日历应用的月视图界面1700包括按钮1701，用户点击该按钮1701后，跳转至图18的b所示的界面，在月视图界面1700的上层显示设置项窗口1702，该窗口包括“仅显示重要”设置项1703，用户点击“仅显示重要”设置项1703后，跳转至图18的c所示的界面1704。
如图18的a所示的界面1700包括重要日程和非重要日程，如火车出行的日程等，而图18的c所示的界面1704仅包括重要日程，不显示非重要日程。需要说明的是，本实施例中“中秋节”和“教师节”的日程默认显示。当然，在其他实施例中，也可以设置为，在选择仅显示重要选项后，不显示节日类日程和非重要日程，仅显示重要日程，本申请对此不做限定。
此外，图18的c所示的界面的底部还包括“当前仅显示重要日程”的提示信息1705，用来提醒用户当前界面未显示非重要日程。在本申请的其他实施例中，“当前仅显示重要日程”的提示信息1705还可以是其他形态，例如，还可以在当前界面的空白处或该界面的上层显示表示当前处于筛选状态的标识符。本申请对表示筛选状态的标识符不做限定。
在本申请的另一实施例中，用户还可以恢复显示全部日程。例如，如图18的c所示，用户点击按钮1701后，跳转至图18的d所示的界面，该界面包括设置项窗口1707，与图18的b所示的设置项窗口1702的不同之处在于，设置项窗口1707包括“全部日程”设置项1706，而设置项窗口1702中是“仅显示重要”设置项1703。用户点击“全部日程”设置项1706后，跳转至图18的a所示的界面，即显示全部日程。
在一种可能的实现方式中，设置项窗口1702、1707中的设置项上显示的内容可以根据 用户的操作更新，例如，当前视图中显示某一日期的全部日程，则设置项窗口中的设置项为“仅显示重要”。而在用户点击“仅显示重要”设置项后，设置项窗口中的设置项变为“全部日程”。
在另一种可能的实现方式中，设置项窗口1702和1707中的设置项显示的内容固定不变，例如，无论当前视图中是否是仅显示重要日程，该设置项窗口中会显示“仅显示重要/全部日程”。本申请对设置项窗口所显示的设置项的内容样式不做限定。
用户设置为仅显示重要日程后，在其他显示日程的场景中同步更新为只显示重要日程。
参见图19，示出了本申请实施例提供的一种日程视图的界面示意图，图19的a为日程视图界面1801，而且，该界面显示全部日程，例如，包括重要日程1802和非重要日程1803、1804。在用户选择仅显示重要的日程后，该界面变为图19的b所示的界面。
如图19的b所示，日程视图界面1805仅显示各个日期下的重要日程，不显示非重要日程。例如，区域1806中显示9月10的重要日程，区域1807中显示9月11日的重要日程。此外，在该界面底部还包括“当前仅显示重要日程”的提示信息1808。
参见图20，示出了本申请实施例提供的一种日程桌面卡片的界面示意图。
如图20的a所示，桌面1900包括日历卡片1901，日历卡片1901包括当前日期(9月10)下的日程。若当前日期包括多个日程，由于日历卡片1901的显示面积有限，无法显示该日期下的全部日程，例如，可以优先显示重要日程，非重要日程可以按照起止时间进行排序后再显示。
例如，如图20的a所示，本示例中，日历卡片1901包括重要日程1902和非重要日程1903，与此同时，日历卡片1901的底部还包括“还有其他2个日程”的提示信息1904，以提醒用户当日还有未显示的日程。
用户选择仅显示重要日程后，日历卡片1901变为图20的b所示的显示界面，如图20的b所示，日历卡片1901仅显示重要日程1902，不显示非重要日程。此外，日历卡片1901的底部还可以显示“今天没有其他重要日程”的提示信息1905。
本申请实施例中，桌面或称为桌面应用，主屏幕，或Launcher等，例如，在安卓系统中，桌面又称为桌面启动器(Launcher)。为了方便描述，本文中统称为桌面。
在本申请的另一个实施例中，管理日程的应用还支持在桌面上添加单个日程的卡片，或称为日程卡片。
在一种场景中，用户可以在创建新的重要日程时，就在桌面上添加该日程的日程卡片。参见图21，示出了本申请实施例提供的一种添加日程卡片的界面示意图。
在一种可能的实现方式中，可以只针对重要日程提供在桌面添加日程卡片的功能，即仅有重要日程的显示界面才有添加桌面卡片的功能入口，非重要日程的界面没有添加桌面卡片的功能入口。当然，在本申请的其他实施例中，针对全部日程都可以在桌面上添加该日程的日程卡片，本申请对此不做限定。
如图21的a所示，用户在新建日程界面2001中的优先级设置项2002中设置为“重要”后，跳转至图21的b所示的界面2003，界面2003还包括“添加桌面卡片”设置项2004，该“添加桌面卡片”设置项2004包括设置按钮2005，图21的b中显示的设置按钮2005为未开启状态，用户点击该设置按钮2005后变为开启状态，如图21的c所示的设置按钮 2005为开启状态。
用户点击图21中的c所示的按钮2006后，跳转至图21的d所示的界面，该界面包括重要日程显示区域2008，与此同时，将该重要日程的日程卡片添加至桌面。此外，在该界面的底部还包括“日程已添加至桌面”的提示信息2009。在一示例性实施例中，该提示信息显示预设时长后自动消失。图21的d所示的界面还包括指示日程对应日期的信息2007，本示例中，在2022年9月8日创建9月9日的日程，即今日创建明日的日程。
如图21的e所示，日程卡片2010即新建重要日程“设计方案研讨会议”的日程卡片。该日程卡片2010包括当前日期距离该日程执行日期的天数2011，本示例中倒数天数为1天，此外，该日程卡片还包括用于显示该日程的执行日期的区域2012，本示例中该日程的执行日期是2022年9月9日。
参见图22，示出了本申请实施例提供的倒数日与正数日的计算规则示意图。本申请实施例中，倒数日是指当前日期到达日程的执行日期的剩余天数。
例如，如图22所示，本示例中，日程执行日期是2022年9月9日，当前日期是2022年9月8日，当前日期未到日程执行日期，因此9月8日显示的日程卡片上显示的距离日程执行日期的倒数天数。在一示例性实施例中，9月8日显示的日程卡片2013上显示“1天后”是结婚纪念日，并显示该日程的执行日期，即2022年9月9日。
当前日期是2022年9月9日时，当前日期即日程执行日期，在一示例性实施例中，2022年9月9日显示的日程卡片2014不再显示倒数天数，而是直接显示“结婚纪念日”及该日程的执行日期2022年9月9日。
当前日期是2022年9月10日时，当前日期已经超过日程执行日期。在一示例性实施例中，2022年9月10日显示的日程卡片2015可以显示“1天前”是结婚纪念日，以及还可以显示该日程的执行日期，即2022年9月10日。日程卡片上显示的内容可以根据实际需求调整，本申请对此不做限定。
此外，图21的e所示的日程卡片2010仅是一个具体的示例，还可以包括其他样式、大小的日程卡片。如图23所示，为三种可能的日程卡片的大小示意图，日程卡片2016的大小与图21的e所示的日程卡片2010相同，日程卡片2017的大小是日程卡片2016的两倍，而日程卡片2018的大小是日程卡片2016的一半。当然，在本申请其他实施例中，还可以包括其他大小的日程卡片，本申请对此不做限定。
前面已结合图21介绍了在新建日程的过程中在桌面上添加日程卡片的过程。在本申请的其他实施例中，对于已有日程(如创建完成的日程，或从其他应用程序导入的日程)也可以在桌面上添加日程卡片。
参见图24，示出了本申请实施例提供的另一种添加日程卡片的界面示意图。
如图24的a所示，日程详情界面2101是重要日程“设计方案研讨会议”的详细信息，该界面包括桌面卡片设置项2102，该桌面卡片设置项2102包括“添加”按钮，用户可以通过点击“添加”按钮在桌面上添加该重要日程的日程卡片。
在一种情况下，该重要日程未添加过日程卡片，此种情况下，用户点击图24的a所示的“添加”按钮后，跳转至图24的b所示的桌面界面。如图24的b所示，桌面界面包括重要日程“设计方案研讨会议”的日程卡片2103，日程卡片2103所显示的内容与图22所 示的日程卡片相同，此处不再赘述。
在另一种情况下，该重要日程已经添加了日程卡片，此种情况下，用户点击图24的a所示的“添加”按钮后，跳转至图24的c所示的界面2104。如图24的c所示，该界面在图24的a所示的界面上层增加一灰度图层，进一步，在该灰度图层上层显示提示窗2105。该提示窗2105包括提醒用户该日程已添加桌面卡片。
例如，在一示例中，提示窗2105显示的文本信息可以是“当前日程已有桌面卡片，是否重复添加？”，此外，提示窗2105还包括“取消”按钮和“确定”按钮。如果用户点击“取消”按钮后，不执行为该日程添加桌面卡片的流程。如果用户点击“确定”按钮，继续执行为该日程添加桌面卡片的流程，此种情况下，桌面上会有至少两个该日程对应的日程卡片，且这至少两个日程卡片显示的内容相同。
上述的在新建日程时添加桌面卡片，或者针对已有日程添加桌面卡片，均是先有日程再添加该日程对应的桌面卡片。在本申请另一实施例中，还可以先添加空白日程卡片，然后，再选择在该空白日程卡片上显示的日程。
参见图25，示出了本申请实施例提供的另一种添加日程卡片的界面示意图。
在一种可能的实现方式中，如图25的a所示，用户可以在桌面2200上进行双指捏合操作，进入图25的b所示的界面，该界面是桌面编辑界面，该界面的上方区域显示可以编辑的桌面页面2201，可以通过左右滑动桌面页面更换当前显示的桌面页面。该界面的底部区域显示操作选项，如壁纸、日历卡片2202、切换效果、桌面设置等。
用户点击日程卡片2202后跳转至图25的c所示的界面，该界面是日程卡片界面，该界面包括区域2203，该区域用于显示日程卡片的样式，如，本示例中，当前显示的是日历卡片2204的样式，可以通过左右滑动该区域更换当前显示的日程卡片的样式。此外，在日程卡片界面的底部还包括“添加到桌面”按钮2205。用户点击“添加到桌面”按钮2205后，跳转至图25的d所示的界面。
用户点击“添加到桌面”按钮2205后，如图25的d所示，在桌面界面上显示用户添加的日程卡片2206，该日程卡片2206包括添加日程的按钮2207，用户点击该按钮2207后，跳转至选择日程的界面。
在一示例性实施例中，选择日程的界面包括“节日”、“日程”、“生日”三个页面，用户可以任意选择其中一个页面，并从该页面中选择任一个添加至日程卡片。如图25的e所示，“日程”页面包括多个日期下的多个日程，例如，本示例中，“日程”页面包括9月9日的3个日程，以及9月10的2个日程。用户可以任意选择其中一个日程，添加至桌面的日程卡片中。每个日程项包括选择按钮，选择按钮可以包括两种显示状态，即选中状态和非选中状态。在一示例中，按钮2209表示选中状态，而按钮2210表示非选中状态。
在一示例中，如图26的a所示，为“节日”页面的示意图，图26的b为“生日”页面的示意图。与“日程”页面相似，如图26的a所示，“节日”页面2301包括多个节日选项2302，且每个节日选项均包括一个选择按钮。如图26的b所示，“生日”页面2303包括多个生日选项2304，且每个生日选项均包括一个选择按钮，此处不再赘述。
本示例中，用户选择“设计方案研讨会”的日程后，跳转至图25的f所示的界面，该界面所示的日程卡片2211与图25的d所示的空白卡片2206相比，增加了用户选择添加的 日程的信息，其中，日程卡片2211与图22所示的日程卡片所包含的日程信息相同，此处不再赘述。
由上述的在桌面上添加日程卡片的过程可知，用户可以将重要日程添加至桌面的日程卡片中，这样，无需用户打开管理日程的应用程序，直接在桌面上看到该日程的倒数天数或正数天数，降低了用户查看重要日程的操作，进一步提高了用户关注重要日程的效率，避免用户错过重要日程。
在本申请的另一实施例中，用户还可以编辑或移除桌面上已添加的日程卡片。在一示例性实施例中，用户长按桌面上的日程卡片可以编辑或移除该日程卡片。
参见图27，示出了本申请实施例提供的一种操作日程卡片的界面示意图。
如图27的a所示，桌面界面包括日程卡片2401，用户长按该日程卡片2401跳转至图27的b所示的界面，该界面在日程卡片2401的下方还包括操作选项卡2402，在一示例中，该操作选项卡2402包括编辑和移除。用户点击“移除”后，跳转至图27的c所示的界面，该界面为删除日程卡片2401后的桌面界面。
在另一种可能的实现方式中，用户通过点击操作选项卡2402中的“编辑”，可以编辑日程卡片2401中的日程，例如，更改该日程卡片显示的日程信息，例如，原始状态下日程卡片2401中添加的是“设计方案研讨会”的日程，通过“编辑”操作可以使该日程卡片显示另一个日程的信息，此处不再赘述。
可见，本实施例提供的方案，针对已经添加至桌面的日程卡片，用户可以直接进行操作，如编辑日程卡片中的日程，或者，移除该日程卡片，无需用户进入管理日程的应用程序中进行操作，降低了用户操作复杂度，提高了用户体验。
在本申请的又一实施例中，用户在管理日程的应用程序中，修改或删除日程后，该日程对应的日程卡片中的内容同步更新，例如，用户删除日程后，该日程对应的日程卡片可以变为空白卡片，或者，直接删除显示该日程的日程卡片。又如，用户修改该日程中的内容后，该日程对应的日程卡片中的相应内容同步更新。
例如，如果用户在日历应用程序中删除2022年9月9日的“设计方案研讨会”日程后，在一示例中，图27的a中的日程卡片2401变为空白卡片，用户可以在该日程卡片2401中添加其他日程。
在另一示例中，在日历应用程序中删除2022年9月9日的“设计方案研讨会”日程后，图27的a中的日程卡片2401同步删除。
可见，本实施例提供的方案，用户在管理日程的应用程序中操作日程后，该日程对应的日程卡片同步更新，即管理日程应用中的日程与日程卡片中的内容自动同步，无需用户手动操作，提高了用户体验。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本实施例所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以 通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本实施例各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器执行各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：快闪存储器、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (18)

  1. 一种日程管理方法，其特征在于，应用于电子设备，所述方法包括：
    显示第一界面，所述第一界面包括第一日程卡片，所述第一日程卡片包括日程信息和日程优先级，所述日程优先级为无；
    响应于选择所述日程优先级为重要的操作，显示第二界面，所述第二界面包括第二日程卡片，所述第二日程卡片中的日程优先级为重要，所述第二日程卡片包含的日程信息多于所述第一日程卡片包含的日程信息。
  2. 根据权利要求1所述的方法，其特征在于，所述日程信息包括日程标题；所述第二日程卡片还包括重要标识符，所述重要标识符位于所述日程标题之前。
  3. 根据权利要求1或2所述的方法，其特征在于，所述日程优先级包括无、重要和忽略。
  4. 根据权利要求1至3任一项所述的方法，其特征在于，所述响应于选择所述日程优先级为重要的操作，显示第二界面，包括：
    响应于点击所述第一日程卡片上的日程优先级的操作，在所述第一界面上显示优先级设置选项弹窗，所述优先级设置选项弹窗包括无级别选项、重要级别选项和忽略选项；
    响应于在所述优先级设置选项弹窗上选择重要级别选项的操作，显示所述第二界面。
  5. 根据权利要求1至3任一项所述的方法，其特征在于，在所述显示第一界面之前，所述方法还包括：
    显示第三界面，所述第三界面包括第一按钮，所述第一按钮用于新建日程；
    响应于对所述第一按钮的操作，显示第一界面，所述第一界面还包括保存按钮；
    所述响应于选择所述日程优先级为重要的操作，显示第二界面，包括：
    响应于对所述第一界面上的日程优先级的操作，在所述第一界面上显示优先级设置选项弹窗，所述优先级设置选项弹窗包括无级别选项、重要级别选项和忽略选项；
    响应于在所述优先级设置选项弹窗上选择重要级别选项的操作，显示第一界面，所述第一界面中的日程优先级更新为重要；
    响应于对所述保存按钮的操作，显示所述第二界面。
  6. 根据权利要求1至5任一项所述的方法，其特征在于，所述日程信息包括参与人，所述方法还包括：
    当检测到日程优先级为重要的日程后，获取包含参与人的全部日程中的参与人；
    从所述全部日程的参与人中，选取符合预设条件的预设数量个参与人确定为推荐参与人，所述预设条件包括参与重要日程的频次大于预设阈值；
    生成推荐人列表，所述推荐人列表包括所述推荐参与人。
  7. 根据权利要求6所述的方法，其特征在于，在所述生成推荐列表之后，所述方法还包括：
    当检测到新的重要日程后，基于所述新的重要日程的参与人更新所述推荐人列表中的推荐参与人。
  8. 根据权利要求1至7任一项所述的方法，其特征在于，所述方法还包括：
    显示第一重要参与人界面，所述第一重要参与人界面包括推荐人列表，所述推荐人列 表包括至少一个参与人项，所述参与人项包括参与人信息和添加按钮；
    响应于对所述添加按钮的操作，显示第二重要参与人界面，所述第二重要参与人界面包括重要参与人列表，所述重要参与人列表包括重要参与人项，每个所述重要参与人项包括添加的参与人和移除按钮。
  9. 根据权利要求8所述的方法，其特征在于，所述第一重要参与人界面还包括添加其他参与人按钮；在显示所述第一重要参与人界面之后，所述方法还包括：
    响应于对所述添加其他参与人按钮的操作，显示第一选择参与人界面，所述第一选择参与人界面包括全部日程的第一参与人列表；
    响应于选择所述第一参与人列表中的任一参与人的操作，显示第三重要参与人界面，所述第三重要参与人界面包括重要参与人列表，所述重要参与人列表包括选择的参与人。
  10. 根据权利要求1至9任一项所述的方法，其特征在于，所述第一日程卡片还包括参与人设置项；在显示第一界面之后，所述方法还包括：
    响应于对所述参与人设置项的操作，显示日程参与人界面，所述日程参与人界面包括第二参与人列表和编辑重要参与人按钮，所述第二参与人列表包括所述第一日程卡片包含的日程中的全部参与人；
    响应于对所述重要参与人按钮的操作，显示第二选择参与人界面，所述第二选择参与人界面包括参与人选择列表；
    响应于在所述参与人选择列表中选择参与人的操作，将选择的重要参与人标记为重要参与人，并更新重要参与人列表。
  11. 根据权利要求8至10任一项所述的方法，其特征在于，在添加重要参与人之后，所述方法还包括：
    检测到非重要日程的参与人中包含重要参与人后，将所述非重要日程自动标记为重要日程，所述非重要日程是优先级为无的日程。
  12. 根据权利要求1至11任一项所述的方法，其特征在于，在显示第二界面之后，所述方法还包括：
    显示设置弹窗，所述设置弹窗包括仅显示重要的第一设置项；
    响应于对所述第一设置项的操作，在显示日程的各个界面中仅显示重要的日程。
  13. 一种日程管理方法，其特征在于，应用于电子设备，所述方法包括：
    显示第一界面，所述第一界面包括第一日程的日程优先级和桌面卡片设置项，所述日程优先级为重要；
    响应于对所述桌面卡片设置项的操作，在桌面上显示所述第一日程的第一桌面卡片，所述第一桌面卡片包括当前日期与所述第一日程的执行日期之间的天数。
  14. 根据权利要求13所述的方法，其特征在于，在显示第一界面之前，所述方法还包括：
    显示第二界面，所述第二界面包括新建日程按钮；
    响应于对所述新建日程按钮的操作，显示所述第一界面。
  15. 根据权利要求13或14所述的方法，其特征在于，在显示第一界面之后，所述方法还包括：
    响应于对所述桌面卡片设置项的操作，且检测到已添加所述第一日程对应的桌面卡片后，在所述第一界面上显示第一弹窗，所述第一弹窗包括取消按钮、确定按钮和提示用户是否重复添加桌面卡片的信息；
    响应于对所述确定按钮的操作，添加所述第一日程的第二桌面卡片，所述第二桌面卡片与所述第一桌面卡片的内容相同。
  16. 根据权利要求13至15任一项所述的方法，其特征在于，所述方法还包括：
    显示第三界面，所述第三界面包括空白桌面卡片和第一按钮，所述空白桌面卡片包括添加日程按钮；
    响应于对所述第一按钮的操作，在桌面上显示所述空白桌面卡片；
    响应于对所述添加日程按钮的操作，显示选择日程界面，所述选择日程界面包括可选择的日程；
    响应于在所述选择日程界面选择日程的操作，显示桌面，所述桌面包括第三桌面卡片，所述第三桌面卡片包括已选择的日程的信息，以及当前日期与所述已选择的日程的执行日期之间的天数。
  17. 一种电子设备，其特征在于，所述电子设备包括：一个或多个处理器、存储器和触摸屏；所述存储器用于存储程序代码；所述处理器用于运行所述程序代码，使得所述电子设备实现如权利要求1至16任一项所述的日程管理方法。
  18. 一种计算机可读存储介质，其特征在于，其上存储有指令，当所述指令在电子设备上运行时，使得所述电子设备执行如权利要求1至16任一项所述的日程管理方法。
PCT/CN2023/115428 2022-09-30 2023-08-29 日程管理方法及装置 WO2024066863A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211230407.4A CN117875925A (zh) 2022-09-30 2022-09-30 日程管理方法及装置
CN202211230407.4 2022-09-30

Publications (2)

Publication Number Publication Date
WO2024066863A1 true WO2024066863A1 (zh) 2024-04-04
WO2024066863A9 WO2024066863A9 (zh) 2024-06-06

Family

ID=90475969

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/115428 WO2024066863A1 (zh) 2022-09-30 2023-08-29 日程管理方法及装置

Country Status (2)

Country Link
CN (1) CN117875925A (zh)
WO (1) WO2024066863A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101075309A (zh) * 2006-12-28 2007-11-21 腾讯科技（深圳）有限公司 一种电子日历中的事件显示方法和系统
CN108021397A (zh) * 2017-11-14 2018-05-11 维沃移动通信有限公司 一种日程处理方法、装置及移动终端
CN108647067A (zh) * 2018-04-12 2018-10-12 青岛真时科技有限公司 一种日程显示方法和装置
CN115063103A (zh) * 2022-06-14 2022-09-16 前景智能交通科技(苏州)有限公司 一种日程管理方法、系统、存储介质及电子设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101075309A (zh) * 2006-12-28 2007-11-21 腾讯科技（深圳）有限公司 一种电子日历中的事件显示方法和系统
CN108021397A (zh) * 2017-11-14 2018-05-11 维沃移动通信有限公司 一种日程处理方法、装置及移动终端
CN108647067A (zh) * 2018-04-12 2018-10-12 青岛真时科技有限公司 一种日程显示方法和装置
CN115063103A (zh) * 2022-06-14 2022-09-16 前景智能交通科技(苏州)有限公司 一种日程管理方法、系统、存储介质及电子设备

Also Published As

Publication number Publication date
CN117875925A (zh) 2024-04-12
WO2024066863A9 (zh) 2024-06-06

Similar Documents

Publication Publication Date Title
JP6789272B2 (ja) インテリジェントな予約の提案
TWI564734B (zh) 用於提供經擴充的通訊服務的動態導覽欄之方法及計算設備
Scott et al. Designing web interfaces: Principles and patterns for rich interactions
TWI569198B (zh) 用於經擴充的通訊服務的動態最小化導覽欄
JP5021030B2 (ja) メール内に埋め込まれたカレンダーイベント、通知、及びアラートバー
RU2395841C2 (ru) Усовершенствованный пользовательский интерфейс для обеспечения управления задачами и информации календаря
CN107426403B (zh) 移动终端
US8347224B2 (en) Content viewing method, content viewing apparatus, and storage medium in which a content viewing program is stored
RU2391700C2 (ru) Пространства совместной работы
US20150143258A1 (en) Email and task management services and user interface
US20140082521A1 (en) Email and task management services and user interface
US20110231409A1 (en) System and method for predicting meeting subjects, logistics, and resources
US20100205567A1 (en) Adaptive ui regions for enterprise applications
US20100070910A1 (en) Data-Oriented User Interface for Mobile Device
GB2535980A (en) A communication interface
US20110202624A1 (en) Techniques for sharing content
CN112905094B (zh) 一种对象操作处理的方法、装置以及计算机存储介质
WO2024188206A1 (zh) 会话管理方法、装置及电子设备
WO2018069728A1 (en) Improvements relating to messaging applications
US20130139092A1 (en) Method of inputting data entries of a service in one continuous stroke
WO2024066863A1 (zh) 日程管理方法及装置
KR20130025301A (ko) 디스플레이 장치 및 그 ｕｉ 제공 방법
Vandome iPad for Seniors in easy steps, -covers all iPads with iPadOS 13 including iPad mini and iPad Pro
Rich iPad and iPhone tips and tricks
Kao et al. BlackBerry Pearl 3G For Dummies

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23870106

Country of ref document: EP

Kind code of ref document: A1