Search Images Maps Play YouTube News Gmail Drive More »
Sign in
Screen reader users: click this link for accessible mode. Accessible mode has the same essential features but works better with your reader.

Patents

  1. Advanced Patent Search
Publication numberUS20150370462 A1
Publication typeApplication
Application numberUS 14/494,404
Publication date24 Dec 2015
Filing date23 Sep 2014
Priority date20 Jun 2014
Also published asCN106462834A, CN106796684A, EP3158516A1, EP3158517A1, US9746997, US20150370421, US20150370422, US20150370440, US20150370463, US20150370464, US20150370904, US20150372829, WO2015196003A1, WO2015196004A1, WO2015196005A1, WO2015196006A2, WO2015196006A3, WO2015196007A1, WO2015196008A1, WO2015196009A1
Publication number14494404, 494404, US 2015/0370462 A1, US 2015/370462 A1, US 20150370462 A1, US 20150370462A1, US 2015370462 A1, US 2015370462A1, US-A1-20150370462, US-A1-2015370462, US2015/0370462A1, US2015/370462A1, US20150370462 A1, US20150370462A1, US2015370462 A1, US2015370462A1
InventorsNeel Joshi, Jeannine Boone, Joan Li, Montine Rummel, Johanna Hawkins, Mark Healy
Original AssigneeMicrosoft Corporation
Export CitationBiBTeX, EndNote, RefMan
External Links: USPTO, USPTO Assignment, Espacenet
Creating calendar event from timeline
US 20150370462 A1
Abstract
Creation of a calendar event from a timeline is provided. An application such as a calendar application detects a create action to create an event on the timeline. Details of the event are captured that includes a subject name of the event and an event date. The event is displayed on the timeline based on the details. A save action is detected to save the event. The event is displayed on a calendar associated with the timeline based on the details.
Images(11)
Previous page
Next page
Claims(20)
What is claimed is:
1. A method executed on a computing device to create a calendar event from a timeline, the method comprising:
detecting a create action to create an event on the timeline;
capturing details of the event;
displaying the event on the timeline based on the details;
detecting a save action to save the event; and
displaying the event on a calendar associated with the timeline based on the details.
2. The method of claim 1, further comprising:
capturing an event date as one of the details.
3. The method of claim 1, further comprising:
capturing a subject name of the event as one of the details.
4. The method of claim 1, further comprising:
displaying an event entry control to capture the details of the event.
5. The method of claim 4, further comprising:
providing a calendar control in the event entry control to capture an event date as one of the details; and
providing a text entry control in the event entry control to capture a subject name of the event as one of the details.
6. The method of claim 5, further comprising:
providing a date picker control as the calendar control, wherein the date picker displays dates of a month that includes an event date associated with the create action on the timeline.
7. The method of claim 5, further comprising:
highlighting a current date on the calendar control in response to a detection that the current date is within a date range of a month displayed by the calendar control, wherein the month includes an event date associated with the create action on the timeline.
8. The method of claim 1, further comprising:
rendering the event in a transparent form within the timeline on an event date associated with the create action, prior to a detection of the save action.
9. The method of claim 1, further comprising:
transitioning the event from a transparent form to an opaque form within the timeline on an event date associated with the create action in response to a detection of the save action.
10. The method of claim 1, further comprising:
highlighting the event on the calendar through an animation that includes one from a set of: a blinking animation applied to the event, a rotating animation applied to the event, a fade in animation applied to the event, and an animated object that encompasses the event.
11. The method of claim 1, further comprising:
scrolling to a time period within the timeline that includes an event date associated with the create action in response to a detection of the date selection event on an event entry control, wherein the time period includes one from a set of a date, a week, and a month.
12. A computing device to create a calendar event from a timeline, the computing device comprising:
a display device;
a memory;
a processor coupled to the memory and the display device, the processor executing a calendar application in conjunction with instructions stored in the memory, wherein the calendar application is configured to:
detect a create action to create an event on the timeline;
capture details of the event;
display the event on the timeline based on the details, on the display device;
detect a save action to save the event; and
display the event on a calendar associated with the timeline based on the details, on the display device.
13. The computing device of claim 12, wherein the calendar application is further configured to:
display an event entry control that includes a date picker control to capture an event date as one the details and a text entry control to capture a subject name of the event as one of the details, wherein the date picker is overlaid adjacent to the event date associated with the create action on the timeline.
14. The computing device of claim 13, wherein the calendar application is further configured to:
detect a date selection action that selects a new date on the date picker control.
15. The computing device of claim 14, wherein the calendar application is further configured to:
display the event in a transparent form on the new date within the timeline.
16. The computing device of claim 14, wherein the calendar application is further configured to:
scroll the calendar to a time period that includes the new date.
17. The computing device of claim 13, wherein the calendar application is further configured to:
display the text entry control in a top section of the event entry control and the date picker control below the text entry control within the event entry control.
18. A computer-readable memory device with instructions stored thereon to create a calendar event from a timeline, the instructions comprising:
detecting a create action to create an event on the timeline;
displaying an event entry control that includes a date picker control to capture an event date and a text entry control to capture a subject name of the event, wherein the date picker is overlaid adjacent to the event date associated with the create action on the timeline;
capturing the subject name and the event date of the event;
displaying the event on the timeline based on the subject name and the event date;
detecting a save action to save the event; and
displaying the event on a calendar associated with the timeline based on the subject name and the event date.
19. The computer-readable memory device of claim 18, wherein the instructions further comprise:
rendering the event in a transparent form on the timeline on the event date, prior to a detection of the save action; and
transitioning the event from a transparent form to an opaque form on the timeline in response to a detection of the save action.
20. The computer-readable memory device of claim 18, wherein the instructions further comprise:
scrolling to a time period on the calendar that includes the event date; and
highlighting the event on the calendar through an animation.
Description
    RELATED APPLICATIONS
  • [0001]
    This applications claims the benefit of U.S. Provisional Patent Application Ser. No. 62/015,350 filed on Jun. 20, 2014. The disclosure of the provisional application is incorporated herein in its entirety.
  • BACKGROUND
  • [0002]
    Legacy calendar views in scheduling applications provide limited information. Alternatively, the legacy calendar views in scheduling applications provide excessive information. Legacy calendar views are usually used in detailed configurations for daily and weekly actions. However, users are underserved in long term synapsis of associated actions in legacy calendar views. Addition of actions and other items into legacy calendar views prove challenging for long term synapsis of associated actions.
  • SUMMARY
  • [0003]
    This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary is not intended to exclusively identify key features or essential features of the claimed subject matter, nor is it intended as an aid in determining the scope of the claimed subject matter.
  • [0004]
    Embodiments are directed to creating a calendar event from a timeline. In some example embodiments, a calendar application may detect a create action to create an event on the timeline. Details of the event may be captured. The details may include a subject name of the event and an event date. The event may be displayed on the timeline based on the details. A save action may be detected to save the event. The event may be displayed on a calendar associated with the timeline based on the details.
  • [0005]
    These and other features and advantages will be apparent from a reading of the following detailed description and a review of the associated drawings. It is to be understood that both the foregoing general description and the following detailed description are explanatory and do not restrict aspects as claimed.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • [0006]
    FIG. 1 is a conceptual diagram illustrating an example of creating a calendar event from a timeline, according to embodiments;
  • [0007]
    FIG. 2 illustrates an example of a create action to create a calendar event from a timeline, according to embodiments;
  • [0008]
    FIG. 3 illustrates an example of an event entry control provided to create a calendar event from a timeline, according to embodiments;
  • [0009]
    FIG. 4 illustrates an example of selecting another event date while creating a calendar event from a timeline, according to embodiments;
  • [0010]
    FIG. 5 illustrates an example of changing an event date while creating a calendar event from a timeline, according to embodiments;
  • [0011]
    FIG. 6 illustrates an example of a save action to create a calendar event from a timeline, according to embodiments;
  • [0012]
    FIG. 7 illustrates an example of a calendar event created on a calendar from a timeline, according to embodiments;
  • [0013]
    FIG. 8 is a simplified networked environment, where a system according to embodiments may be implemented;
  • [0014]
    FIG. 9 illustrates a general purpose computing device, which may be configured to create a calendar event from a timeline; and
  • [0015]
    FIG. 10 illustrates a logic flow diagram for a process to create a calendar event from a timeline, according to embodiments.
  • DETAILED DESCRIPTION
  • [0016]
    As briefly described above, a calendar event may be created from a timeline by a calendar application. A create action may be detected to create an event on a timeline. Details of the event may be captured. The event may be displayed on a timeline based on the details. A save action may be detected to save the timeline. The event may be displayed on a calendar associated with the timeline based on the details.
  • [0017]
    In the following detailed description, references are made to the accompanying drawings that form a part hereof, and in which are shown by way of illustrations specific embodiments or examples. These aspects may be combined, other aspects may be utilized, and structural changes may be made without departing from the spirit or scope of the present disclosure. The following detailed description is therefore not to be taken in a limiting sense, and the scope of the present invention is defined by the appended claims and their equivalents.
  • [0018]
    While the embodiments will be described in the general context of program modules that execute in conjunction with an application program that runs on an operating system on a computing device, those skilled in the art will recognize that aspects may also be implemented in combination with other program modules.
  • [0019]
    Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that embodiments may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and comparable computing devices. Embodiments may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
  • [0020]
    Embodiments may be implemented as a computer-implemented process (method), a computing system, or as an article of manufacture, such as a computer program product or computer readable media. The computer program product may be a computer storage medium readable by a computer system and encoding a computer program that comprises instructions for causing a computer or computing system to perform example process(es). The computer-readable storage medium is a computer-readable memory device. The computer-readable memory device includes a hardware device that includes a hard disk drive, a solid state drive, a compact disk, a memory chip, among others. The computer-readable storage medium can for example be implemented via one or more of a volatile computer memory, a non-volatile memory, a hard drive, and a flash drive.
  • [0021]
    Throughout this specification, the term “platform” may be a combination of software and hardware components to create a calendar event from a timeline. Examples of platforms include, but are not limited to, a hosted service executed over a plurality of servers, an application executed on a single computing device, and comparable systems. The term “server” generally refers to a computing device executing one or more software programs typically in a networked environment. However, a server may also be implemented as a virtual server (software programs) executed on one or more computing devices viewed as a server on the network. More detail on these technologies and example embodiments may be found in the following description.
  • [0022]
    FIG. 1 is a conceptual diagram illustrating an example of creating a calendar event from a timeline, according to embodiments.
  • [0023]
    In a diagram 100, a computing device 104 may execute a calendar application 102. The computing device may include a tablet device, a laptop computer, a desktop computer, a smart phone, among others. The computing device 104 may display the calendar application 102 to a user 106. The user 106 may be allowed to interact with the calendar application 102 through an input device or touch enabled display component of the computing device 104. The user 106 may interact with the calendar application 102 with a keyboard based input, a mouse based input, a voice based input, a pen based input, a gesture based input, among others. The gesture based input may include one or more touch based actions such as a touch action, a swipe action, a combination of each, among others.
  • [0024]
    The calendar application 102 may include a timeline 120 as a component. The timeline 120 may include a linear presentation of events during a time period divided based on a time unit such as a day. Events presented on the timeline may be duplicates of the events on a calendar view of the calendar application 102. A user 106 may be allowed to interact with the timeline 120 to create a calendar event. The calendar event may be registered on the timeline 120 and saved into the calendar view of the calendar application 102.
  • [0025]
    While the example system in FIG. 1 has been described with specific components including the computing device 104, the calendar application 102, the timeline 120, embodiments are not limited to these components or system configurations and can be implemented with other system configuration employing fewer or additional components.
  • [0026]
    FIG. 2 illustrates an example of a create action to create a calendar event from a timeline, according to embodiments.
  • [0027]
    In a diagram 200, a calendar application 202 that displays a calendar view and a timeline 220 used to create a calendar event may be described. The calendar application 202 may display a date picker component 204. The date picker component 204 may allow a user to select a date from a displayed range. The selected date may be displayed in the calendar view that displays the date within a date range that is configurable. The date range of the calendar view may include a day, a week, a month, a year, among others. A current date range may be illustrated with a date range label 208. The date range may also be partitioned vertically based on a time unit such as day 210. The time units may be scrollable. The calendar view may also be partitioned horizontally based on an hour based unit 212. The hour based units may be scrollable. An “all day” unit may persist on a top section of the calendar view to show one or more events that last during a time unit such as a day. A calendar displayed on the calendar view may be selectable through a calendar selection control 206. The calendar application 202 may display one or more calendars that may be selectable through the calendar selection control 206 and other calendar selection controls displayed adjacent to the calendar selection control 206.
  • [0028]
    The timeline 220 may display a linear presentation of events on the calendar view. The timeline 220 may display a date range of events that may be scrollable through a scroll control 224. The date range may be presented with a date range label 222. The date range may be partitioned based on time units such as an hour, a day 228, a week, a month, a year, among others. The date range may be selectable based on a selection of the range by a user through a range selection control such as “weekly,” among others. An event 214 on the calendar view of the calendar application 202 may be duplicated in an event 226 on the timeline 220.
  • [0029]
    The calendar application 202 may detect a create action 230 on the timeline 220. The create action 230 may include a click event registered through a mouse input. Other input formats such as a touch action on a date displayed by the timeline may be registered as a create action to create a calendar event on the calendar view.
  • [0030]
    FIG. 3 illustrates an example of an event entry control provided to create a calendar event from a timeline, according to embodiments.
  • [0031]
    In a diagram 300, a calendar application 302 may display an event entry control 306 to capture details of an event 304 within a timeline 320. The event entry control 306 may be displayed in response to create action on an event date within the timeline 320. A calendar control may be provided on the event entry control to capture an event date as a detail of the event 304. The calendar control may include a date picker control. The date picker control may display dates of a month that includes an event date associated with the create action on the timeline. A current date may be highlighted on the calendar control in response to a detection that the current date is within a date range of a month displayed by the calendar control. The month may include an event date associated with the create action on the timeline.
  • [0032]
    A text entry control may also be provided on the event entry control 306 to capture a subject name of the event 304 as a detail. The event 304 may be displayed as an empty event container on the date associated with the create action on the timeline 320. The event entry control 306 may also provide a save control to save the event 304 in a calendar and display the event 304 on the calendar view of the calendar application 302. A cancel control may also be provided on the event entry control to cancel an operation to save the event 304 on the timeline and the calendar.
  • [0033]
    A selection action 330 on the text entry control may initiate one or more operations to register a subject name of the event 304. The subject name of the event 304 may be input by an external entity such as a user. In addition, the text entry control may be displayed on a top section of the event entry control 306. The date picker control may be placed below the text entry control. The save and cancel controls may be placed below the date picker control, adjacent to each other.
  • [0034]
    FIG. 4 illustrates an example of selecting another event date while creating a calendar event from a timeline, according to embodiments.
  • [0035]
    In a diagram 400, a date selection action 430 to change an event date of an event on a timeline 420 may be detected by a calendar application 402. The calendar application 402 may display an event entry control 406 to collect details of an event 404 within the timeline 420. A subject name of the event 404 input into a text entry control may be displayed on the event 404 within the timeline 420. The event 404 within the timeline may be rendered in a transparent form on an event date associated with the creation action, prior to a detection of a save action on the save control within the event entry control 406.
  • [0036]
    The date selection action 430 may select a new date 408 on the date picker control to change the event date of the event 404 within the timeline. The new date 408 may be used to move the event 404 to a new location on the timeline associated with the new date 408. The timeline may be scrolled to a time period that includes the new date 408. The calendar view may also be scrolled to a time period that includes the new date 408.
  • [0037]
    FIG. 5 illustrates an example of changing an event date while creating a calendar event from a timeline, according to embodiments.
  • [0038]
    In a diagram 500, the event 510 may be moved to a new location by the calendar application 502 within a timeline 520 based on an event date 508 selected on an event entry control 506. The location may include the event date 508 within the timeline 520. The event may be displayed in a transparent form because a save action to save the event in the calendar may not be detected yet. The event 510 may be moved to different locations in transparent form multiple times. The transparent form may illustrate a temporary status of the event 510 prior to a save action.
  • [0039]
    FIG. 6 illustrates an example of a save action to create a calendar event from a timeline, according to embodiments.
  • [0040]
    In a diagram 600, the event 610 may be saved in response to a detection of a save action 630 on a save control within an event entry control 606, by a calendar application 602. Operations to save the event 610 may be initiated in response to the save action 630. The event 610 may be transitioned from a transparent form to an opaque form within a timeline 620 on an event date associated with the create action in response to a detection of the save action 630.
  • [0041]
    FIG. 7 illustrates an example of a calendar event created on a calendar from a timeline, according to embodiments.
  • [0042]
    In response to the save action, the event 710 may be saved in the calendar and displayed on the calendar view of a calendar application 702. The event 710 within the timeline 720 may be displayed as an event 712 on the calendar view. The event 710 may be a duplicate of the event 712. The event 712 may be highlighted on the calendar view through an animation. The animation may include a blinking animation applied to the event 712. The animation may also include a rotating animation applied to the event 712. The animation may also include a fade in animation applied to the event 712. An animated object may also be used to encompass the event 712.
  • [0043]
    Alternatively, an event 712 created on the calendar view may be saved to an associated calendar and duplicated as an event 710 on the timeline 720.
  • [0044]
    The technical effect of creating a calendar event from a timeline may be enhancements in creation, management, and display of events compared to static event presentation based solutions.
  • [0045]
    The example scenarios and schemas in FIG. 1 through 7 are shown with specific components, data types, and configurations. Embodiments are not limited to systems according to these example configurations. Creating a calendar event from a timeline may be implemented in configurations employing fewer or additional components in applications and user interfaces. Furthermore, the example schema and components shown in FIG. 1 through 7 and their subcomponents may be implemented in a similar manner with other values using the principles described herein.
  • [0046]
    FIG. 8 is an example networked environment, where embodiments may be implemented. A calendar application configured to create a calendar event from a timeline may be implemented via software executed over one or more servers 814 such as a hosted service. The platform may communicate with client applications on individual computing devices such as a smart phone 813, a laptop computer 812, or desktop computer 811 (‘client devices’) through network(s) 810.
  • [0047]
    Client applications executed on any of the client devices 811-813 may facilitate communications via application(s) executed by servers 814, or on individual server 816. A calendar application may capture details of an event and display the event on the timeline based on details. In response to a detection of a save action to save the event, the event may be saved in a calendar and displayed on a calendar view associated with the timeline, based on the details. The calendar application may store data associated with the timeline in data store(s) 819 directly or through database server 818.
  • [0048]
    Network(s) 810 may comprise any topology of servers, clients, Internet service providers, and communication media. A system according to embodiments may have a static or dynamic topology. Network(s) 810 may include secure networks such as an enterprise network, an unsecure network such as a wireless open network, or the Internet. Network(s) 810 may also coordinate communication over other networks such as Public Switched Telephone Network (PSTN) or cellular networks. Furthermore, network(s) 810 may include short range wireless networks such as Bluetooth or similar ones. Network(s) 810 provide communication between the nodes described herein. By way of example, and not limitation, network(s) 810 may include wireless media such as acoustic, RF, infrared and other wireless media.
  • [0049]
    Many other configurations of computing devices, applications, data sources, and data distribution systems may be employed to create a calendar event from a timeline. Furthermore, the networked environments discussed in FIG. 8 are for illustration purposes only. Embodiments are not limited to the example applications, modules, or processes.
  • [0050]
    FIG. 9 illustrates a general purpose computing device, which may be configured to create a calendar event from a timeline, arranged in accordance with at least some embodiments described herein.
  • [0051]
    For example, the computing device 900 may be used to create a calendar event from a timeline. In an example of a basic configuration 902, the computing device 900 may include one or more processors 904 and a system memory 906. A memory bus 908 may be used for communication between the processor 904 and the system memory 906. The basic configuration 902 may be illustrated in FIG. 9 by those components within the inner dashed line.
  • [0052]
    Depending on the desired configuration, the processor 904 may be of any type, including, but not limited to, a microprocessor (μP), a microcontroller (μC), a digital signal processor (DSP), or any combination thereof. The processor 904 may include one more levels of caching, such as a level cache memory 912, a processor core 914, and registers 916. The processor core 914 may include an arithmetic logic unit (ALU), a floating point unit (FPU), a digital signal processing core (DSP Core), or any combination thereof. A memory controller 918 may also be used with the processor 904, or in some implementations, the memory controller 918 may be an internal part of the processor 904.
  • [0053]
    Depending on the desired configuration, the system memory 906 may be of any type including but not limited to volatile memory (such as RAM), non-volatile memory (such as ROM, flash memory, etc.), or any combination thereof. The system memory 906 may include an operating system 920, a calendar application 922, and a program data 924. The calendar application 922 may create a calendar event from a timeline. Details of the event may be captured to display the event on the timeline based on the details. The event may be displayed on a calendar view of a calendar, based on the details, in response to a save action to save the event in the calendar. Components of the calendar application 922 (such as a user interface) may also be displayed on a display device associated with the computing device 900. An example of the display device may include a hardware screen that may be communicatively coupled to the computing device 900. The display device may include a touch based device that detects gestures such as a touch action. The display device may also provide feedback in response to detected gestures (or any other form of input) by transforming one or more views such as the timeline, displayed by the touch based device. The program data 924 may also include, among other data, a timeline data 928, or the like, as described herein. The timeline data 928 may include the event, subject name of the event, the event date, among others.
  • [0054]
    The computing device 900 may have additional features or functionality, and additional interfaces to facilitate communications between the basic configuration 902 and any desired devices and interfaces. For example, a bus/interface controller 930 may be used to facilitate communications between the basic configuration 902 and one or more data storage devices 932 via a storage interface bus 934. The data storage devices 932 may be one or more removable storage devices 936, one or more non-removable storage devices 938, or a combination thereof. Examples of the removable storage and the non-removable storage devices may include magnetic disk devices, such as flexible disk drives and hard-disk drives (HDD), optical disk drives such as compact disk (CD) drives or digital versatile disk (DVD) drives, solid state drives (SSD), and tape drives, to name a few. Example computer storage media may include volatile and nonvolatile, removable, and non-removable media implemented in any method or technology for storage of information, such as computer-readable instructions, data structures, program modules, or other data.
  • [0055]
    The system memory 906, the removable storage devices 936, and the non-removable storage devices 938 may be examples of computer storage media. Computer storage media may include, but may not be limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD), solid state drives, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which may be used to store the desired information and which may be accessed by the computing device 900. Any such computer storage media may be part of the computing device 900.
  • [0056]
    The computing device 900 may also include an interface bus 940 for facilitating communication from various interface devices (for example, one or more output devices 942, one or more peripheral interfaces 944, and one or more communication devices 966) to the basic configuration 902 via the bus/interface controller 930. Some of the example output devices 942 may include a graphics processing unit 948 and an audio processing unit 950, which may be configured to communicate to various external devices, such as a display or speakers via one or more A/V ports 952. One or more example peripheral interfaces 944 may include a serial interface controller 954 or a parallel interface controller 956, which may be configured to communicate with external devices, such as input devices (for example, keyboard, mouse, pen, voice input device, touch input device, etc.) or other peripheral devices (for example, printer, scanner, etc.) via one or more I/O ports 958. An example communication device 966 may include a network controller 960, which may be arranged to facilitate communications with one or more other computing devices 962 over a network communication link via one or more communication ports 964. The one or more other computing devices 962 may include servers, client equipment, and comparable devices.
  • [0057]
    The network communication link may be one example of a communication media. Communication media may be embodied by computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and may include any information delivery media. A “modulated data signal” may be a signal that has one or more of the modulated data signal characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), microwave, infrared (IR), and other wireless media. The term computer-readable media, as used herein, may include both storage media and communication media.
  • [0058]
    The computing device 900 may be implemented as a part of a general purpose or specialized server, mainframe, or similar computer, which includes any of the above functions. The computing device 900 may also be implemented as a personal computer including both laptop computer and non-laptop computer configurations.
  • [0059]
    Example embodiments may also include creating a calendar event from a timeline. These methods may be implemented in any number of ways, including the structures described herein. One such way may be by machine operations, using devices of the type described in the present disclosure. Another optional way may be for one or more of the individual operations of the methods to be performed in conjunction with one or more human operators performing some of the operations while other operations may be performed by machines. These human operators need not be co-located with each other, but each may be with a machine that performs a portion of the program. In other examples, the human interaction may be automated such as by pre-selected criteria that may be machine automated.
  • [0060]
    FIG. 10 illustrates a logic flow diagram for a process to create a calendar event from a timeline, according to embodiments. Process 1000 may be implemented on a calendar application of the cloud based service.
  • [0061]
    Process 1000 begins with operation 1010, where a create action may be detected to create an event on a timeline. At operation 1020, the details of the event may be captured. The details may include a subject name of the event and an event date. The event may be displayed on the timeline based on the details at operation 1030. At operation 1040, a save action to save the event may be detected. The event may be displayed on a calendar associated with the timeline based on the details at operation 1050.
  • [0062]
    The operations included in process 1000 are for illustration purposes. A calendar application according to embodiments may be implemented by similar processes with fewer or additional steps, as well as in different order of operations using the principles described herein.
  • [0063]
    According to some examples, a method that is executed on a computing device to create a calendar event from a timeline may be described. The method may include detecting a create action to create an event on the timeline, capturing details of the event, displaying the event on the timeline based on the details, detecting a save action to save the event, and displaying the event on a calendar associated with the timeline based on the details.
  • [0064]
    According to other examples, the method may further include capturing an event date as one of the details. A subject name of the event may be captured as one of the details. The method may further include displaying an event entry control to capture the details of the event, providing a calendar control in the event entry control to capture an event date as one of the details, and providing a text entry control in the event entry control to capture a subject name of the event as one of the details. A date picker control may be provided as the calendar control, where the date picker displays dates of a month that includes an event date associated with the create action on the timeline. A current date may be highlighted on the calendar control in response to a detection that the current date is within a date range of a month displayed by the calendar control, where the month includes an event date associated with the create action on the timeline.
  • [0065]
    According to further examples, the method may further include rendering the event in a transparent form within the timeline on an event date associated with the create action, prior to a detection of the save action. The event may be rendered from a transparent form to an opaque form within the timeline on an event date associated with the create action in response to a detection of the save action. The event may be highlighted on the calendar through an animation that includes one from a set of: a blinking animation applied to the event, a rotating animation applied to the event, a fade in animation applied to the event, and an animated object that encompasses the event. The method may further include scrolling to a time period within the timeline that includes an event date associated with the create action in response to a detection of the date selection event on an event entry control, where the time period includes one from a set of a date, a week, and a month.
  • [0066]
    According to some examples, a computing device to create a calendar event from a timeline may be described. The computing device may include a display device, a memory, a processor coupled to the memory and the display device. The processor may be configured to execute a calendar application in conjunction with instructions stored in the memory. The calendar application may be configured to detect a create action to create an event on the timeline, capture details of the event, display the event on the timeline based on the details, on the display device, detect a save action to save the event, and display the event on a calendar associated with the timeline based on the details, on the display device.
  • [0067]
    According to other examples, the calendar application is further configured to display an event entry control that includes a date picker control to capture an event date as one the details and a text entry control to capture a subject name of the event as one of the details, where the date picker is overlaid adjacent to the event date associated with the create action on the timeline and detect a date selection action that selects a new date on the date picker control. The event may be displayed in a transparent form on the new date within the timeline. The calendar application is further configured to scroll the calendar to a time period that includes the new date. The text entry control may be displayed in a top section of the event entry control and the date picker control below the text entry control within the event entry control.
  • [0068]
    According to some examples, a computer-readable memory device with instructions stored thereon to create a calendar event from a timeline may be described. The instructions may include actions that are similar to the method described above.
  • [0069]
    According to some examples, a method that is executed on a computing device to create a calendar event from a timeline may be described. The method may include a means for detecting a create action to create an event on the timeline, a means for capturing details of the event, a means for displaying the event on the timeline based on the details, detecting a save action to save the event, and a means for displaying the event on a calendar associated with the timeline based on the details.
  • [0070]
    The above specification, examples and data provide a complete description of the manufacture and use of the composition of the embodiments. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims and embodiments.
Patent Citations
Cited PatentFiling datePublication dateApplicantTitle
US20060069604 *30 Sep 200430 Mar 2006Microsoft CorporationUser interface for providing task management and calendar information
US20080082925 *29 Sep 20063 Apr 2008Microsoft CorporationBifocal view: a novel calendar user interface
US20080307323 *10 Jun 200711 Dec 2008Patrick Lee CoffmanCalendaring techniques and systems
US20090292690 *14 Oct 200826 Nov 2009Daniel Jason CulbertMethod and System for Automatic Event Administration and Viewing
US20110239146 *23 Mar 201029 Sep 2011Lala DuttaAutomatic event generation
US20140082536 *17 Sep 201220 Mar 2014Ciprian CostaScheduling Events on an Electronic Calendar Utilizing Fixed-positioned Events and a Draggable Calendar Grid
US20140365107 *15 Nov 201311 Dec 2014Apple Inc.Specifying Travel Times for Calendared Events
US20150347983 *29 Sep 20143 Dec 2015Apple Inc.Intelligent Appointment Suggestions
Legal Events
DateCodeEventDescription
23 Sep 2014ASAssignment
Owner name: MICROSOFT CORPORATION, WASHINGTON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:JOSHI, NEEL;BOONE, JEANNINE;LI, JOAN;AND OTHERS;SIGNING DATES FROM 20140908 TO 20140922;REEL/FRAME:033801/0803
9 Jan 2015ASAssignment
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034747/0417
Effective date: 20141014
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:039025/0454
Effective date: 20141014